BEFORE YOU START: Test the EtherExpress™ PRO/10 adapter with SoftSet2. Reboot the workstation and insert the EtherExpress™ PRO/10 LAN Adapter Configuration and Driver disk into drive A. At the DOS prompt type:

Select Test Adapter from the main menu.

NOTE: SoftSet2 is a DOS program and will not run in Windows*. You must run SoftSet2 from DOS.

Installing Remoteboot service on the NT* server:

To Remoteboot to a Windows NT* 3.5 server, you must have the DLC and NetBEUI protocols loaded and the Remoteboot service installed on your NT* server. Follow these steps to set up your NT* server for Remoteboot:

1. In Control Panel, choose the Network icon
2. In the Network Settings dialog box, choose the Add Software button.
3. In the Add Network Software dialog box, select the DLC Protocol, and choose the Continue button
4. In the Network Settings dialog box, choose the Add Software button.
5. In the Add Network Software dialog box, select the NetBEUI Protocol, and choose the Continue button
6. In the Network Settings dialog box, choose the Add Software button.
7. In the Add Network Software dialog box, select the Remoteboot Service, and choose the Continue button
8. In the Remoteboot Setup dialog box, type the full path and directory name where you want to install the Remoteboot directory. The default is C:\WINNT35\RPL
9. In the Network Settings dialog box, choose OK button
10. Windows NT will complete the binding process and prompt you to restart the NT server, choose the Restart Now button
11. After the NT server restarts, open Control Panel and select the Services icon.
12. In the Services dialog box, select Remoteboot Service and choose the Start button.

Installing MS-DOS files for the Remoteboot workstations:

When a workstation Remoteboots to an NT* server, the Remoteboot server gives it a boot block which will load DOS. You must copy these DOS files to the NT server.

1. From the Remoteboot NT server, open file manager and SHARE the RPL directory (C:\WINNT35\RPL).
2. From a workstation with a DOS 6.22 directory on the hard disk, connect to the Remoteboot NT servers RPLFILES directory by typing:

   net use v: \\server_name\winnt35\rpl

   NOTE: If you have a workstation running Windows for Workgroups you can use File Manager to connect to the NT servers RPL directory.

3. Copy all the DOS files (including the hidden system files) from the workstation to the Remoteboot NT server directory C:\WINNT35\RPL\RPLFILES\BINFILES\DOS622.
   For example:
   copy c:\dos\*.* v:\binfiles\dos622
   attrib -s -h c:\io.sys
   attrib -s -h c:\msdos.sys
   copy c:\io.sys v:\binfiles\msdos622
   copy c:\msdos.sys v:\binfiles\msdos622
   attrib +s +h c:\io.sys
   attrib +s +h c:\msdos.sys
   
   NOTE: Copy files to an existing DOS directory on the Remoteboot NT server do not create a new directory. For example, any version of MS-DOS 6.2x must be copied into the existing DOS622 directory. Also, DO NOT assign the hidden attribute to the IO.SYS or the MSDOS.SYS file on the NT server.

Creating a Remoteboot configuration for the EtherExpress™ PRO/10:

1. From the Remoteboot NT* server, copy the EtherExpress™ PRO/10 driver EPRO.DOS and NIF file EPRODOS.NIF from the EtherExpress PRO/10 driver disk, SW release 3.0, to the Remoteboot NT server:
   
   COPY A:\NDIS\EPRO.DOS C:\WINNT35\RPL\BBLOCK\NDIS
   COPY A:\NDIS\STNDNIF\EPRODOS.NIF C:\WINNT35\RPL\BINFILES\LANMAN.DOS\DRIVERS\NIF
   
   
2. Create a directory for the EtherExpress™ PRO/10 adapter on the NT server:
   
   
   MD C:\WINNT35\RPL\BBLOCK\NETBEUI\EPRO
   
   
3. Copy the configuration files DOSBB.CNF and PROTOCOL.INI from the EtherExpress 16 directory to the EtherExpress PRO/10 directory:
   
   

   COPY C:\WINNT35\RPL\BBLOCK\NETBEUI\EXP16\DOSBB.CNF
   
   	C:\WINNT35\RPL\BBLOCK\NETBEUI\EPRO
   
   	COPY C:\WINNT35\RPL\BBLOCK\NETBEUI\EXP16\PROTOCOL.INI
   
   	C:\WINNT35\RPL\BBLOCK\NETBEUI\EPRO

4. Edit the configuration file DOSBB.CNF in the EtherExpress PRO/10 directory (c:\winnt35\rpl\bblock\netbeui\epro\dossbb.cnf) and change all references from EXP16 to EPRO.

   Sample DOSBB.CNF:

   ; DOS on Intel EtherExpress PRO/10 Ethernet
   BASE D0H
   RPL BBLOCK\RPLBOOT.SYS
   LDR BBLOCK\RPLSTART.COM ~
   DAT BBLOCK\NETBEUI\EPRO\PROTOCOL.INI
   DRV BBLOCK\RPLDISK.SYS ~ ~
   EXE BBLOCK\RPLPRO1.COM ~ 2 ~
   EXE BBLOCK\I13.COM ~ ~ ~
   EXE BBLOCK\RPLBIND2.EXE ~ ~
   EXE BBLOCK\PROTMAN.EXE ~ ~
   EXE BBLOCK\RPLBIND1.EXE ~ ~
   ;DRV BBLOCK\IPXNDIS.DOS ~ ~ ~
   ;DRV BBLOCK\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
   EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
   DRV BBLOCK\NDIS\EPRO.DOS ~ ~ ~
   DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
   
   
5. Edit the configuration file PROTOCOL.INI in the EtherExpress™ PRO/10 directory (c:\winnt35\rpl\bblock\netbeui\epro\protocol.ini) and change all references from EXP16_NIF to EPRODOS_NIF, and the DRIVERNAME=EXP16$ to DRIVERNAME=EPRO$
   
   

   Sample PROTOCOL.INI:

   [protman]
   drivername = protman$
   dynamic = yes
   priority = netbeui [netbeui_xif]
   drivername = netbeui$
   bindings = eprodos_nif
   names = 6
   ncbs = 12
   packets = 20
   pipeline = 10
   sessions = 6 stacksize = 512
   lanabase = 0 [xnsnb_xif]
   drivername = xnsnb$
   bindings = eprodos_nif
   load = xnsnb[cbr]
   lanabase = 1 [xnstp_xif]
   drivername = xnstp$
   bindings = eprodos_nif
   load = xnstp[ub]
   lanabase = 1 [tcpip_xif]
   drivername = TCPIP$
   disabledhcp = (TCPIP_NO_DHCP)
   ipaddress0 = (TCPIP_ADDRESS)
   subnetmask0 = (TCPIP_SUBMASK)
   defaultgateway0 = (TCPIP_GATEWAY)
   tcpsegmentsize = 1450
   tcpwindowsize = 1450
   nbsessions = 6
   load = tcptsr[c],tinyrfc[c],emsbfr[cr]
   unload = "unloadt /notsr[dc]"
   bindings = eprodos_nif
   lanabase = 1 [ipx_xif]
   drivername = ipx$
   load = ipxmark[u],ipx[u]
   unload = ipxrel[c]
   bindings = eprodos_nif
   lanabase = 1 [msdlc_xif]
   drivername = msdlc$
   bindings = eprodos_nif
   load = msdlc[cb]
   unload = msdlc[u] [eprodos_nif]
   IOADDRESS = 0x300 ; <-- this is the I/O address of the
   EtherExpress PRO/10
   DRIVERNAME = EPRO$

6. Use the Windows NT* server command RPLCMD to add boot block record for the EtherExpress PRO/10 adapter. Below is a sample of the steps and required input:
   If you have the PRO/10+ adapter, the VendorName value should be 00A0C9. This value is the first 6 digits of the Ethernet address. You can run SoftSet2 to confirm what the Ethernet address is of the card you are installing
   c:\winnt35\rpl\rplcmd
   
   

   Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
   Add Del Enum: a
   BootName=DOSX
   VendorName=00AA00
   BcbFile=BBLOCK\NETBEUI\EPRO\DOSBB.CNF
   BootComment=EtherExpress PRO/10
   WindowSize=0 Adapter Boot Config Profile Service Vendor Wksta [Quit]: c Add Del Enum: a
   ConfigName=DOS622X
   BootName=DOSX
   DirName=DOS
   DirName2=DOS622
   FitShared=fits\dos622.FIT
   FitPersonal=fits\dos622p.FIT
   ConfigComment=Dos 6.22 EtherExpress PRO/10
   Dirname3=
   Dirname4=

Creating EtherExpress PRO/10 Profile:

A profile is a working environment shared by one or more workstations consisting of the same operating system and network adapter type. You must create a profile on the Remoteboot NT Server for the EtherExpress PRO/10 adapter.

1. On the Remoteboot NT Server from the Network Administration group, choose the Remoteboot Manager icon.
2. From the Remoteboot menu in Remoteboot Manager, choose New Profile.
3. For Profile Name, type a name for this profile. An example would be: DOS622
4. For Description, type a name that summarizes the profile for easy recognition like: MS-DOS 6.22 VGA & EtherExpress PRO/10
5. For Configuration, select: DOS 6.22 EtherExpress PRO/10
6. Choose OK

Enabling the FLASH chip for NDIS Remoteboot on the EtherExpress PRO/10:

The EtherExpress PRO/10 adapter must be configured for NDIS Remoteboot to Remoteboot to the NT server. You can do this using SoftSet2 or FlashSet.

1. On the Remoteboot workstation, run SoftSet2 from the EtherExpress PRO/10 driver disk, or you can use the FlashSet utility which comes up automatically when the EtherExpress PRO/10 adapter is first installed.
2. . If using SoftSet2, select Change Adapter Configuration from the main menu.
   
   If using FlashSet, select <ESC> from the main menu to go into manual setup.
3. Specify an address range for the Flash Chip. The default is DOOO-D3FFh.
4. Specify the Remoteboot type as NDIS.
5. Choose F10 to save the configuration and exit.

Enabling Remoteboot on the Workstation with a hard disk:

Before a workstation with a hard disk can be booted remotely, its hard disk must be properly configured for the Remoteboot service. Use the Microsoft utility RPLENABL to prepare the workstation for Remoteboot Service. Later, if you want to boot the workstation using the hard disk, run the Microsoft utility RPLDSABL to disable the Remoteboot configuration on the hard disk.

1. Copy the RPLENABL.EXE and RPLDSABL.EXE from the NT server to a floppy disk: COPY C:\WINNT35\RPL\RPLFILES\BINFILES\BINR\RPLENABLE.EXE A:\ COPY C:\WINNT35\RPL\RPLFILES\BINFILES\BINR\RPLDSABLE.EXE A:\
   
   
2. Take the floppy disk with the RPL files to the workstation with the hard disk and copy the files to the hard disk:
   COPY A:\RPLENABLE C:\
   COPY A:\RPLDSABLE C:\
   
   
3. To configure the workstations hard disk for remote boot, run RPLENABLE on that workstation:

Adding the Workstation to Windows NT Remoteboot Manager:

1. On the Remoteboot NT Server from the Network Administration group, choose the Remoteboot Manager icon.
   
   
2. Reboot the remoteboot workstation. The workstation does not actually boot, but it does send boot requests to the server. You will see the DLC RPL Server Retries counter increment.
   
   
3. In Remoteboot Manager on the NT server, select the View menu, choose Refresh. You should see the adapter record listed with the node address of the workstation sending boot requests to the server. The NT server will identify it as an EtherExpress 16 adapter.
   
   
4. Select the EtherExpress adapter record that has appeared, then from the Remoteboot menu choose Convert Adapters.
   
   
5. From the New Remoteboot Workstation dialog box, enter in a Wkstation Name
   
   
6. From the New Remoteboot Workstation dialog box, enter in a Description.
   
   
7. From the New Remoteboot Workstation dialog box, enter in a Password
   
   
8. From the New Remoteboot Workstation dialog box, select a Configuration Type. Select SHARED if this workstation can share its profile with other workstations. Select PERSONAL if the profile is a customized environment for a workstation
   
   
9. From the New Remoteboot Workstation dialog box, for Profile select: DOS 6.22 EtherExpress PRO
   
   
10. From the New Remoteboot Workstation dialog box , in the TCP/IP configuration, enter in the appropriate address only if the workstation will be using TCP/IP and will not be using DHCP for automatic address handling.
    
    
11. Choose the Add button.

What You See At The Workstation:

1. When you boot the workstation, a remoteboot logon prompt appears:

   Type Remoteboot username, or press enter if it is <workstation_name>

   This asks for the account name and password associated with this workstation itself, not the user's own account name and password. Once the remoteboot is complete, the user can logon using the NET LOGON command to log on with his or her's own username and password.

2. When the workstation has completed a remote boot, the current directory is C:\ which is a virtual drive. C:\DOS and C:\LANMAN.DOS directories provide access to DOS and Network utilities.

   Local hard disks, if present, are assigned drive letters starting with D, unlike the local boot case, where the local hard disk drive letters start with C.