This section presents some information about creating login scripts that use an Upgrade account for installing Windows 95 on client computers. Some of the login script statements described in this section are related to using the STARTUP.GRP file for Windows for Workgroups, as described in "Preparing a STARTUP.GRP File" earlier in this chapter.
Tip
Avoid using relative path names in login scripts and setup scripts so that you can ensure the commands are run from the correct directory.
Also, for shared installations, after Windows 95 Setup is complete, make sure that all path statements in users' login scripts point to Windows 95, and not Windows 3.x or MS-DOS directories.
Login scripts for Microsoft real-mode network clients.
For a computer running MS-DOS or Windows 3.1 with a Microsoft real-mode network client, the login script should be similar to the following:
net start full
net use drive_letter: \\server\distshare
drive_letter:setup drive_letter:msbatch.infIf the client computer is running on a LAN Manager or Windows for Workgroups network, the login script must contain a net start full statement. On a Windows for Workgroups network, the real-mode network client for Windows for Workgroups or Windows 3.1 also requires the entry lmlogon=1 in the [Network] section of SYSTEM.INI. This ensures that the full network redirector is loaded and the user is validated for network logon. Other login script issues are discussed in the following section.
Login scripts for Windows NT networks.
For client computers running MS-DOS or Windows 3.1 on a Windows NT network where an Upgrade account is to be used to install Windows 95, the login script for must contain the following kinds of entries:
net use source_drive \\ntserver\distshare
source_drive:setup source_drive:msbatch.infIf this login script will be used to upgrade computers that are currently running Windows for Workgroups, the login script must contain the following kinds of entries to use a STARTUP.GRP:
net use source_drive \\ntserver\distshare
rename windowsdir\startup.grp *.sav
copy path\startup.grp windowsdir\startup.grpValue | Description |
Source_Drive | Maps a drive letter for the server containing the source files. This must be the same drive letter as specified in the STARTUP.GRP file. Check the lastdrive= setting in CONFIG.SYS to make sure that the drive letter specified on the preceding command line is a valid logical drive letter. If it is not, the network connection will not be made, and the Setup process will fail. |
\\NTServer\DistShare | Specifies the Windows NT computer that contains the Windows 95 source files. |
WindowsDir | Specifies the relative path to the user's Windows directory. |
Path | Specifies the path to the Startup group file. |
User_Windows | Specifies the relative path to the user's Windows directory that will contain STARTUP.GRP. Use the relative drive and directory designation ( . ) instead of the actual path to the Windows directory (for example, C:\WINDOWS). Do not use the WinDir environment variable, because WinDir is not an accessible environment variable in the script. |
For example, for a computer running Windows for Workgroups, the login script could be similar to the following:
net use k: \\ntserver\distshare
rename .\startup.grp *.sav
copy \winnt\system32\repl\import\scripts\startup.grp .\startup.grp
exitLogin scripts for installing Windows 95 on NetWare networks.
The login script for client computers running MS-DOS or Windows 3.1 must contain the following kinds of entries:
attach nwserver/DistShare:
map source_drive:nwserver/DistShare
source_drive:setup source_drive:msbatch.infValue | Description |
Source_Drive | Specifies the same drive letter as specified in the Startup group |
NWServer/DistShare | Specifies the NetWare server that contains the Windows 95 source files |
For example, for a computer running MS-DOS or Windows 3.1 with a real-mode network client, the login script could be similar to the following:
attach nwserver1/win95
map k:nwserver1/win95
k:setup k:msbatch.inf