A.3 Login Script

A.3.1 CAPTURE Execution in a Login Script

If you use a login script that contains an external CAPTURE command using capture.exe, the screen might go blank with a blinking cursor in the upper left corner. The capture eventually executes and the screen returns to normal.

This happens if Windows is set to “full screen” when the CAPTURE command is executed from the login script. Although the system might be working correctly, a slow server performing the capture with a blank screen might make it appear otherwise.

To correct this problem:

  1. Double-click My Computer, then click Control Panel > MS-DOS Console.

  2. In the Console Windows Properties dialog box, click the Options tab.

  3. From the Display Options group, click Window.

A.3.2 Login Script Command SET_TIME ON/OFF Error if a User Does Not Have Administrator Rights

Novell Client for Windows Properties > Advanced Settings contains a Set Station Time property. When this setting is On, and the logged-in user has administrator rights, the workstation time is synchronized with the network during GINA Login. The login script SET_TIME command has no effect on time synchronization, because the time is being synchronized before the script command is processed. When the setting is Off, the SET_TIME ON script command has an effect when scripts are run, and the workstation time is synchronized with the network.

If the logged-in user does not have administrator rights on the workstation, an error is displayed when the login script runs and the time is not synchronized.

A.3.3 Map.exe Utility

The map.exe utility might function improperly if the computer's DOS environment size is too small. If you encounter problems while running map.exe, increase the DOS environment size by adding or editing the SHELL= line in the Windows\system32\config.nt file. For example:

SHELL=%SYSTEMROOT%\SYSTEM32\COMMAND.COM /E:2048

Map.exe was not designed as a Windows executable and, therefore, does not recognize drives mapped to NT servers as network drives. Consequently, the MAP command does not list NT network drives. The Windows NT NET USE command can be used to correctly connect and list network drives for both NetWare and NT servers.

A.3.4 Drive Mappings Automatically Root Mapped

In Windows, all drive mappings made using the NetWare Login are root mapped. Because of this, programs cannot access directories above the directory that the drive is mapped to. This feature affects only MAP commands performed in a login script. After Windows has been started, Windows allows you to map only to the root.

You can turn off the default by adding SET MAPROOTOFF=“1” as the first line in the login script. This globally forces all workstations using the login script to not map root drives.

Or, you can perform the following procedure on a local workstation:

  1. Right-click My Computer.

  2. Click Properties > Advanced > Environment.

  3. Click New to create a new variable.

  4. Type MAPROOTOFF as a variable.

  5. Set the value of the MAPROOTOFF variable to 1.

  6. Click OK > OK.