Interoperability with NetWare
Interoperability with NetWare |
|
Login scripts set the user environment on NetWare servers and are used when the servers are accessed. Therefore, they need to be set correctly for optimal performance. You might experience the following problems when login scripts are activated through Client Service for NetWare or Gateway Service for NetWare.
The user receives the following error message when the NetWare login script attempts to change context using a relative path: "The context you want to change to does not exist."
Nwscript.exe parses the NetWare login script. The CX command changes the context and can be used as follows: "cx ..". This should move the user's context one level up within the NDS hierarchy. Instead, the user receives an error message.
To correct this problem, use absolute paths in login scripts. For example, type:
cx .somecontainer
Error 255 is reported in line 668 of Spool.c when the login script containing the following line is run:
#COMMAND /c CAPTURE /S=servername /Q=quename
To correct this problem, replace the preceding line with the following:
#CAPTURE /S=<servername> /Q=<queuename>
Note
Capture.exe is not a supported application and often fails when run from the command-line interface. The login script processor does not actually run Capture.exe. Instead, it parses the command #CAPTURE and works in the background. Therefore, when you use the #CAPTURE command, you are running the actual Capture.exe file.