The installation of a Windows NT diskless workstation must use a network card that supports NT remote boot. Among the many network cards, the first six digits of the card number are 0020AF and 00608C. The network card directly supports the remote start of NT. If you choose the two types of network cards, then you can ignore the content of the network card added in this article.
Set NT to be installed in D:\\WINNT directory, workstation network card I/O=300, IRQ=3, BOOTADRESS=C800 (use this setting as much as possible), the first six digits of the card number are 0000E8 (Measured by the attached program of the network card). 1. Add the DLC communication protocol via “Control Panel?Network?Add?Protocol" 2. Via “Control Panel?Network?Add?Service"Add“ Remote Start Service”. 3. Click the “Control Panel? Service” to activate the “Services” dialog box, select “Automatic” in the “Startup Type” option, and then click “OK”.
Second, add the network card under DOS6.22
1. Copy the MS-DOS driver of the network card to the D:\\WINNT\\RPL\\BBLOCK\\NDIS directory, generally its extension is .DOS. 2. Create a new D:\\WINNT\\RPL\\BBLOCK\\NETBEUI\\adapter directory (where adapter is a variable representing the name of the network card). Copy PROTOCOL.INI and DOSBB.CNF on the NIC driver to this directory. 3. Edit DOSBB.CNF to ensure the correctness of the *.DOS and PROTOCOL.INI working paths just copied. Re-edit DOSBB.CNF, change the line "& ldquo; EXE BBLOCK\\I13.COM ~~~” to EXE BBLOCK\\W95I13.COM ~~~” and save as W95BB.CNF. 4. Execute RPLCMD in MS-DOS mode D:\\WINNT\\RPLCMD Adapter Boot Config Profile Service Agent WKSTA [Exit]: V(Vender) (Adapter Boot Config Profile Vender [Quit]) Add Del Enum: A (Add VenderName=0000e8 (first six digits of the input card number) all other parameters are optional VenderComment= Adapter Boot Config Profile Service Agent WKSTA [Exit]: B (Boot Block) Add Del Enum: A BootName=boot1 VenderName=0000e8 (corresponding to VenderName BbcFile=BBLOCK\\NETBEUI\\adaper\\DOSBB.CNF (note the modification of the adapter) all other parameters are optional BootComment= WindowSize= Adapter Boot Config Profile Service Agent WKSTA [Exit]: C(Config) Add Del Enum: A ConfigName= Config1 BootName=boot1(corresponds to BootName) DirName=dos DirName2=dos622 FitShared=fits\\dos622.fit FitPersonal=fits\\dos622p.fit all other parameters are optional ConfigComment=My Config for Dos6.22 (new configuration) DirName3= DirName4= Adapter Boot Config Profile Service Agent WKSTA [Exit]: Q
Third, establish DOS6.22 diskless workstation
1. Copy DOS6.22 file to D:\\WINNT\\ RPL\\RPLFILES\\BINFILES\\DOS622 and remove the S and H properties of MSDOS.SYS and IO.SYS. 2. Start “Remote Boot Manager>, execute “Configure?Check Configuration" and select “Yes>;Execute"Configure? Fix Security", select “Yes>. 3. Create a startup profile and note the new configuration you created: My Config for Dos6.22. 4. Create a new workstation with the built configuration file, enter the workstation name at “WKSTA”, for example: WS1; enter the card number at “Adapter ID”, for example: 0000E8401BD1. 5. Start the remote workstation.
Fourth, the diskless workstation to install Windows 3.2
1. Start a remote workstation, appear when & ldquo; Type Remoteboot username, or press enter if it is WS1: & rdquo; time information, input & ldquo; ADMINISTRATOR & rdquo ;, then enter the appropriate password to log in. 2. Load the CD-ROM drive by modifying config.sys and autoexec.bat on the workstation. Restart your computer and log in again with ADMINISTRATOR. 3. Put the Windows 3.2 installation disk into the CD-ROM drive, execute SETUP/A to install Windows 3.2 to the C:\\WIN directory, and actually install it to the server's D:\\WINNT\\RPL\\RPLFILES\\BINRILES\\WIN directory. 4. Enter C:\\WIN, execute SETUP/N, and install Windows 3.2 to the C:\\Windows directory. Do not change it. Workstation-specific Windows 3.2 has been installed. 5. Back to the root directory, after executing XCOPY /E C\\Windows C\\WKSTA.PRO\\WIN, all workstations logged in with this profile can share Windows 3.2. During the installation of Windows 3.2, it is most likely to fail due to insufficient memory. Please pay attention to the problem by adjusting config.sys and autoexec.bat.
Five, install Windows 95 shared files
1. Create a shared directory (such as PWIN95S) on the NT server to save public files, and build another shared directory (such as: RPL95) for saving each The private file of the workstation. 2. Log in to a normal Windows 95 workstation, put the Windows 95 installation CD into the CD-ROM, execute ADMIN\\NETTOOLS\\NETSETUP\\NETSETUP.EXE, and install the Windows 95 files into \\\\NTS4\\PWIN95S (where NTS4 For the server name). Complete the installation by default. 3. Put the Windows NT CD on the server and execute the WIN95SRV.BAT file under CLIENTS\\RPL\\UPDATE\\WIN95. This step enables the files in PWIN95S to have network installation capabilities.
Sixth, add network card under Windows 95
Execute RPLCMD in MS-DOS mode of server D:\\WINNT\\RPLCMD Adapter boot Config configuration file service agent WKSTA [exit]:B Add Del Enum:A BootName =boot2 VenderName=0000e8 BbcFile=BBLOCK\\NETBEUI\\adaper\\W95BB.CNF all other parameters are optional BootComment= WindowSize= Adapter Boot Config Profile Service Agent WKSTA [Exit]: C Add Del Enum: A ConfigName=config2 BootName=boot2 DirName=dos DirName2=win95 FitShared=fits\\win95.fit FitPersonal=fits\\win95p.fit all other parameters are optional ConfigComment=My Config for Pwin95 DirName3= DirName4=
VII. Install the first Windows 95 diskless workstation< Br> 1. Log in to the MS-DOS diskless workstation and map the network drive. (Because Windows 95 remotely maps the C drive first, so the workstation local hard drive and CD drive letter starts from D. In addition, since Windows 95 also needs a virtual disk (RAMDRIVE), you need to keep a drive letter to RAMDRIVE. For convenience, We unplug the hard disk beforehand but keep the CD for installation.) NET USE F:\\\\NTS4\\PWIN95S NET USE G:\\\\NTS4\\RPL95 2. Execute SETUP on the F disk and install Windows 95 into the G:\\CLIENT1 directory. Install “Setup Options”Select“Custom”;"Analyzing Your Computer” dialog box select “No I want to modify the hardware list”, and delete all hardware; when the "Network Configuration” dialog box appears Please use “ select network card? Properties? Resources] set the network card IRQ and I /O address; the rest choose the default value of Windows 95. 3. Run “Remote Boot Manager” to execute “Check Configuration” and “Repair Security” to create a profile configured with “My Config for Pwin95”, for example: PROFILE95. 4. Execute D:\\WINNT\\RPL\\BIN\\WIN95CLT.BAT on the server to establish the mapping between the configuration file and the working directory and server, for example: Win95clt d:\\95rpl\\client1 \\\\NTS4 PROFILE95. 5. Modify the MACHINES.INI file in the D:\\PWIN95S directory. Startup information for joining the workstation, for example: [0000E84018C6] SYSDATPATH=G:\\CLIENT1 G=\\\\NTS4\\RPL95 (note the correspondence between the two lines) 6. Change the profile of the workstation to PROFILE95, restart the workstation, when “ Type the username, or press enter if it is 0000e84018c6:”, please enter the user name, for example: WS1 to complete the installation.
VIII. Install other Windows 95 diskless workstations
1. Start a MS-DOS diskless workstation. 2. Execute the NETSETUP.EXE program on the Windows 95 CD on a regular Windows 95 workstation. When the “Server Installation” dialog box appears, click “Set Path”. 3. When the “Server Path” dialog box appears, enter: \\\\NTS4\\PWIN95S, click “OK”. 4. Click the "Add" button in the "Installation directory of the machine" to enter the computer name, the working directory of the machine and the working directory of the first diskless workstation. For example: WS2; \\\\NTSR\\RPL95\\CLIENT2; \\\\NTS4\\RPL95\\CLIENT1. Continue to complete the installation. 5. Modify the workstation's boot record on the server, let it use the profile of the first workstation, modify MACHINES.INI, and join the workstation's information (the method is the same as above). 6. Restart the workstation and complete the installation. (Note: The workstation NIC settings should be the same as the first workstation NIC settings.)