4.5 Other Common Login Script Problems

4.5.1 Losing Path Statements after Login

After each login, the user would lose a part of the path specified in the autoexec.bat file. The user had a PATH statement in autoexec.bat and then mapped some search drives in the system login script (MAP S1:= MAP S2:= ). PATH statements are set up as search mappings when logged in to the network starting with s1, s2, etc. When you specifically MAP (S1:=), then you overwrite the existing search mapping (PATH). Solution: Doing a MAP INS on the search drives pushes the existing statements down the line without overwriting. Using MAP INS S16:= appends the map statements to the end of the line without overwriting those at the beginning.

4.5.2 Cannot Use the LOGIN and NLIST Utilities

Don't delete the login directory (sys:login) created during network installation. It contains the Novell LOGIN and NLIST utilities. If users run command line utilities, they can use these utilities to log in and view a list of available NetWare servers.

4.5.3 Cannot Execute External Command

This error occurs with external commands (such as CAPTURE) trying to run inside a login script. To troubleshoot this problem, make sure the COMSPEC is set. Then, make sure login.exe is being swapped out correctly.

4.5.4 LOGIN.EXE Problems

Because the language-enabled login.exe is so large, it must be swapped out before large executables can run. capture.exe is a good example of an external program frequently called in a login script. By default, login.exe tries to swap to extended memory first, then to expanded memory, and then to the current drive. If writing to a drive, be sure you have at least the Read and Write rights. If you are using a diskless workstation, this task can be accomplish by using the SWAP command right before the external command. SWAP out to a place on the server you have already mapped to and have been given the appropriate rights (for example, SWAP F:\USERS\%LOGIN_NAME). This allows login.exe to be swapped out and give the external program memory to execute. Also, when running an external command, you must either provide a explicit path to the file or have a search drive mapped to the location of the file before running the command. Typically, this will be sys:\public.

4.5.5 EXIT Command Doesn't Work

Make sure the syntax is right. EXIT "path:command" with the quotes is the right syntax. Ensure that the path and command you put in the quotes are not more than 14 characters long. The early versions of login.exe in NetWare 3.1x and the login.exe in NetWare 4.1 don't support more than 14 characters in the path. Also, remember that EXIT will exit you completely out of the login script, not allowing any other login scripts to run. If there is a user or profile login script that a user needs to execute, you should not use EXIT to get out of the system/container login script.

4.5.6 Login Script Does Unexpected Things

Make sure there are no viruses on the computer. Viruses have caused numerous strange problems with login scripts that have previously executed or should now execute correctly.

Also, temporarily delete any TSRs, because some have been known to cause login problems.

Using an ATTACH command to create an attachment to another NetWare 4.1x server in the same tree can also cause unexpected results such as intermittent premature termination of the login script. The ATTACH command makes a bindery connection that causes any previous eDirectory connections to that server to be destroyed. Using CAPTURE with the Server parameter also causes a bindery attachment to occur.