The following procedure describes how to run Windows 95 Setup from a setup script.
The network administrator can include this step in the login script to avoid user action.
If MSBATCH.INF exists in the Windows directory on the server containing the Windows 95 source files, Setup uses it by default. Otherwise, for example, you would type setup e:\mybatch.inf to run Setup using a setup script named MYSCRIPT.INF on drive E. To use a script in the SCRIPTS directory on a server named NTSVR1, you would type setup \\ntsvr1\scripts\mybatch.inf (provided, of course, that your operating system software can interpret UNC path names).
– Or –
Include the entire statement for running Windows 95 Setup in the login script, so that the user does not have to type anything at the command prompt.
When you run Windows 95 Setup in this way, Setup takes all settings from the custom script. For information not defined in the setup script, Windows 95 Setup migrates settings from an earlier version of Windows 3.x on the computer, uses built-in defaults, or prompts the user to provide information.
After copying files, Windows 95 Setup restarts the computer and begins the Run-Once setup operations (printer setup, program group conversions, and so on). When these operations are finished, Windows 95 is completely installed.
When the user quits Windows 95 Setup at this point, Setup writes all changes to the Registry. The user can restart the computer and log on with the usual logon name and password.
The network administrator can automate this process by providing each user with a floppy disk that contains the necessary files for starting the computer, connecting to the network, and running Windows 95 Setup with a custom setup script.