** ** ** VIA Rhine Family Fast Ethernet Adapter ** ** RPL BOOTROM for remote-booting Windows 95 ** ** v4.38 Aug 2005 ** ** Introduction: ============= This document shows you how to configure the Remote-Boot service in Windows NT Server 3.5, 3.51, 4.0 for remote-booting Windows 95 client. Contents of the Subdirectory: ============================= RPLWIN95.TXT This file. RPL.LOM The bootrom binary file for Lan On Motherboard.. RPL.32 The 32K bootrom binary file for Network Interface Card. RPL.64 The 64K bootrom binary file for Network Interface Card. FETND.DOS The NDIS2 driver require for remote boot. W95BB.CNF The configuration file require for remote boot win95. PROTOCOL.INI The configuration file require for remote boot. FETND3.INF The NDIS3 driver INF file require for remote boot Windows 95 from NT server. FETND3R.SYS The NDIS3 driver require for remote boot Windows 95 from NT server. Requirement: ============ * A Windows NT 4.0 server with the Remoteboot Service installed and configured. Earlier versions of NT do not support Windows 95 clients. * A workstation running Windows 95 with connections to the NT server. This workstation should have a CD-ROM drive. If not, the NT server must have a CD-ROM drive installed and configured for sharing. * Windows 95 on CD-ROM. Make sure the CD-ROM contains the NETSETUP.EXE program. You must purchase the correct licensed copy of Windows 95 for network installation. * An Rhine Family Fast Ethernet adapter with bootROM. You must be able to remoteboot from the NT server with this bootROM. Installation: ============= Before starting the installation process, make sure that the adapter is properly installed and configured. You can use the diagnostic program (A:\DIAG.EXE) to make sure your connection with the network is correct. Setup Procedure for DOS ----------------------- 1. The BOOTROM installation procedures are identical in Windows NT Server 3.5, 3.51, 4.0. First, install the Remoteboot Service on the NT Server: Choose "Control Panel\Network\Add Software" and select "Remoteboot Service", follow the screen instruction to install. 2. Use "File Manager" in NT Server 3.5, 3.51 or "Windows Explorer" in NT Server 4.0 to share the following directory: \windows\rpl\rpl\rplfiles, suppose \windows is your Windows NT directory. 3. Copy all the MS-DOS 6.22 files as follow: attrib -s -h -r c:\io.sys attrib -s -h -r c:\msdos.sys copy c:\io.sys c:\windows\rpl\rplfiles\binfiles\dos622 copy c:\msdos.sys c:\windows\rpl\rplfiles\binfiles\dos622 copy c:\dos622\*.* c:\windows\rpl\rplfiles\binfiles\dos622 attrib +s +h +r c:\io.sys attrib +s +h +r c:\msdos.sys 4. Copy the NDIS2 driver for "PCI Fast Ethernet Adapter" as follow: copy a:\bootrom\fetnd.dos c:\windows\rpl\bblock\ndis md c:\windows\rpl\bblock\netbeui\fetnd copy a:\bootrom\fetnd.cnf c:\windows\rpl\bblock\netbeui\fetnd copy a:\bootrom\protocol.ini c:\windows\rpl\bblock\netbeui\fetnd 5. Run RPLCMD to add a bblock record for the adapter as follow: net start remoteboot ;run in MSDOS prompt rplcmd ;Follow the example below to enter data Adapter Boot Config Profile Service Vendor Wksta [Quit] V Add Del Enum: A VendorName=004063 ;upper 6 digits of your adapter's ethernet ID VendorComment=xx...x ;type your vendor string. optional. Adapter Boot Config Profile Service Vendor Wksta [Quit] B Add Del Enum:A BootName=DOSV1 VendorName=004063 ;upper 6 digits of your adapter's ethernet ID BbcFile=BBLOCK\NETBEUI\FETND\FETND.CNF BootCommet=xx...x ;optional string WindowsSize=0 Adapter Boot Config Profile Service Vendor Wksta [Quit] C Add Del Enum:A ConfigName=DOS622V1 BootName=DOSV1 DirName=DOS DirName2=DOS622 FitShared=FITS\DOS622.FIT FitPersonal=FITS\DOS622P.FIT ConfigComment=DOS 6.22 FETND DirName3= ;press "Enter" DirName4= ;press "Enter" Adapter Boot Config Profile Service Vendor Wksta [Quit] Q 6. Run "Control Panel\Services", select "Remoteboot Service" and change the "Startup" option to "Automatic". Now reboot NT Server, remoteboot service will be started automatically. 7. Run "Remoteboot Manager" from "Administrative Tools" a. Choose "Remoteboot\New Profile.." to create a Profile Name according to the DOS 6.22 FETND configuration. b. Choose "Remoteboot\New Workstation.." to create a Workstation Name according to the profile name and your Adapter Ethernet ID. 8. Now the remoteboot server is ready, boot your workstation with "BOOTROM plug in PCI Fast Ethernet Adapter", then you can access the NT Server from your workstation. Setup Procedure for Windows 95 ------------------------------ 1.Installing SBS for Windows 95 Clients (1) On the server that will contain SBS files, create a shared directory with 90 MB of space available. The shared directory can have any name. (for example, \\server direcotry\sharedir as \\NT4S\SBS). (2) As you share the directory, assign read-only permission for regular users and full access for administrators. (3) Install one regular Windows 95 client on the network or use an existing one. You will use this client to configure the SBS server. (4) Log on to the Windows 95 client using an account that has wirte access to the shared directory on the SBS server. (5) Make sure you use Windows 95 UPGRADE Version. Put the Windows 95 compact disc in the client CD-ROM dirve. In Windows Explorer, switch to the Admin\Nettools\netsetup directory. (6) Double-click Netsetup.exe (7) In the Server-Based Setup dialog box, click Set Path, and specify the path to the SBS server; then click OK, A network name for a server (for example, \\server1\sharedir as \\NT4S\SBS). (8) Click Install a. Set the source path for Windows 95 files. b. This is the path to the compact disc on the client. c. If asked, specify that you do not want to create a default setup script. d. Provide a CD Key number for product identification. e. If you support only remoteboot clients, click Server. f. If you support other SBS functions as well, click User choice. g. Do not click Local hard drive. h. Server-Based Setup copies Windows 95 files to the SBS shared directory. (9) Copy driver file fetnd3r.sys from diskette to shared directory on SBS server. For example: copy [boot win95 by rpl]\fetnd3r.sys \\NT4S\system (10) At the remoteboot server, put the compact disc containing the Windows NT remoteboot for Windows 95 files into a drive. Run win95srv.bat to update the Windows 95 files for remotebooting. For example: E: cd \client\rpl\update win95srv.bat <dest> <dest> is the shared directory on the SBS server as \\NT4S\SBS (11) At the remoteboot server, start Remoteboot Manager. (12) On the Configure Menu, click Check Configuration to activate the new configurations. 2. Installing the First Windows 95 Client (1) Installing the first Windows 95 client requires booting that client first to MS-DOS 6.2.x (Refer the section "Setup up procedure for DOS"). (2) Machines directories can reside on the remoteboot server. Mkdir c:\rplmachines Net share machines=c:\rplmachines (3) Use the net logon command to log on using an account that has read access to the SBS server and write access to the shared directory that will contain this client machine directory. (4) Synchronize the time and date settings of the client, the SBS server, and the remoteboot server. Differing settings can interfere with Windows 95 Setup. The format of this command is net time /domain:server /set for example : net time /domain:NT4S /set (5) Use the net use command to map driver letters to the SBS server and machine directory location, and then determine the highest drive letter in use on the computer. For example, if you have a local hard drive with one partition, C: will be mapped to the remoteboot server, D: will be the local hard drive, E: is reserved for use as a RAM drive, and F: and higher are available for use. You would type: net use f: \\sbs_server\win95_share as net use I: \\NT4S\SBS net use j: \\mach_server\mach_share as net use j: \\NT4S\Machines (6) Change to the drive letter mapped to the SBS directory. (7) Run the Windows 95 Setup program by typing: setup /t:temppath as follows: setup /t:j:\client1.tmp 1. In the Server-based Setup dialog box, click Setup Windows to run from a network server. 2. In the Startup method dialog box, click Start Windows form the network (remote boot server). 3. In the machine Directory dialog box, when asked where to install Windows 95, type the path of the machine directory (using the drive letter specified in Step 4, for example, J:\client1). 4. In the Setup Options dialog box, click Custom setup. In the Analyzing You Computer dialog box, click No, I want to modify the hardware by myself. 5. Exculde as many hardware types and items form autodetection as possible. If autodetection crashes, run Setup again and exclude more items form autodetection. Note: We sugget exeluding serial port detection. It conflicts your network adapter easily. 6. In the Select Components dialog box, click to clear the Communications check box (unless the client has a modem and you intend to use dial-up networking). 7. In the Network Configuration dialog box, check that your network adapter and desired. Note: Don't remove Diup-Up adapter in installation procedure. 8. If there are no network adapters shown, you must add and configure your network adapter. Note: Make sure your adapter driver is for boot rom, not for Windows 95. You can get these files in this folder. 9. In the Identification dialog box, make sure that the workgroup for this client is the same as the workgroup or domain of the SBS server and machine directory server. 10. When the Windows 95 Setup program is done, reboot the client. The client will not yet boot to Windows 95; however you must complete more steps first. 3. Create a profile for the Windows 95 client At the remoteboot server (or a client running Remoteboot manager focused on the remoteboot, start Remoteboot manager) (1) Boot the client to MS-DOS 6.2x to confirm that the MS-DOS configuration is correct. For details, see adding a New Clientt¡¨ earlier in this chapter. (2) Copy w95bb.cnf to \\NT4S\RPL\BBLOCK\NETBEUI\FETND (3) Use the rplcmd utility to add a boot block record for the new adapter C:\NT4S\RPL>rplcmd Adapter Boot Config Profile Service Vendor Wksta [Quit]: B Add Del Enum: A BootName=W95V1 VendorName=004063 BbcFile=BBLOCK\NETBEUI\FETND\W95ND.CNF All other parameters are optional BootComment=Name of the adapter WindowSize=0 Adapter Boot Config Profile Service Vendor Wksta[Quit]:C Add Del Enum: A ConfigName=Win95V1 BootName=W95V1 DirName=DOS DirName2=Win95 FitShared=FITS\WIN95.FIT FitPersonal=FITS\WIN95P.FIT All other parameters are optional ConfigComment=Windows 95 <adapter name> DirName3= DirName4= (4) Edit the client workstation record to assign the client to the Widnows 95 profile. (5) You must also copy \protocol.ini and \fetnd.dos NDIS driver to c:\machine0\client1\suboot directory. copy \fetnd3r.sys file to c:\sbsfiles\system directory. note: if you lost fetnd3r.sys file that win95 system will show the message "you can now safely turn off your computer.if you want to restart your computer" (6) Next, you must manually edit the following files found in the C:\machine0\client1\SUBOOT directory * AUTOEXEC.BAT * MSDOS.SYS * PROTOCOL.INI --- this folder * FETND.DOS --- this folder * SYSTEM.DAT (7) To edit the registry file SYSTEM.DAT use REGEDIT.EXE to export its contents to text file, edit the text file, then import the text file back into SYSTEM.DAT. See the example below. regedit /L:system.dat /E registry.txt edit registry.txt regedit /L:system.dat /C registry.txt (8) Please note that REGEDIT must be run from the DOS command prompt. It will not work as intended if you load it from a DOS session under Windows 95. The easiest way to do this is to remoteboot from your first Windows 95 client, and, when the message "Starting Windows 95" appears, press the F8 function key. When the boot menu appears, select the Step-by-step Confirmation option, answer Yes to each line except WIN.COM. When prompted to start WIN.COM answer No. This will drop you to the DOS command prompt. (9) Export system.dat miniregistry file as follows: regedit /L:system.dat /E registry.txt (10) Edit REGISTRY.TXT by searching and replacing all occurences of the new PCI machine environment and driver name . For example: old register.txt new register,txt "transport"="*netbeui,*nwlink," --> "transport"="*netbeui,*nwlink,ndishlp.sys" "netcard"=" " --> "netcard"="fetnd.dos" You should also modify following environment variable: "BootDir"="A:\\" --> "BootDir"="C:\\" "BootHost"="A:\\" --> "BootHost"="C:\\" "WinbootDir"="A:\\" --> "WinbootDir"="D\\winboot" "HostWinBootDir="A:\\" --> "HostWinBootDir="C:\\" (11) After modifying REGISTRY.TXT you must update SYSTEM.DAT by importing the new information. regedit /L:system.dat /C registry.txt (12) Remove the hidden, system, and read only attributes from SYSTEM.DAT by entering: attrib -r -s -h system.dat (13) copy new system.dat to c:\machine0\client3\suboot directory. (14) At the remoteboot server run the Rpl\Bin\win95clt.bat program by typing: cd <systemroot>\rpl\bin win95clt mach_directory \\rpl_server profile_name For example: win95clt \\NT4S\machines\client1 \\NT4S w95rhine (15) At the SBS server, edit machines.ini file in the SBS directory and add the following lines for the new client: [adapter id] SYSDATPATH=g:\machine_dir g=\\machine_dir\mach_share For example, you might add the following lines to machines.ini:  SYSDATPATH=j:\client1 j=\\NT4S\machines (16) Reboot the Widnows 95 client. The client will now boot to Windows 95 and complete the Windows 95 Setup program.Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.