Setting up a Windows NT Server boot-image for remote booting DOS clients

To configure a Windows NT server to perform Remote Program Load, follow the instructions in the Microsoft Windows NT Server documentation for remote booting workstations that are fitted with IBM Token-Ring Adapters.

Then follow the instructions below.

The instructions below assume that you have Windows NT installed on drive C:\ of your server. If you use a different drive, replace C:\ with the drive-name that is correct for your installation

1. From the driver installation disk, copy the following files:

   MDGND.DOS
   MDGND30.BIN

   to the directory:

   C:\WINNT\RPL\BBLOCK\NDIS

2. Create the directory:

   C:\WINNT\RPL\BBLOCK\NETBEUI\MADGE

3. In the directory:

   C:\WINNT\RPL\BBLOCK\NETBEUI\IBMTOK

   copy the files:

   DOSBB.CNF
   PROTOCOL.INI

   to the directory:

   C:\WINNT\RPL\BBLOCK\NETBEUI\MADGE

4. Go to the directory:

   C:\WINNT\RPL\BBLOCK\NETBEUI\MADGE

   Modify the file:

   DOSBB.CNF

   as follows:

   i Replace the line:

   DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI

   with the lines:

   DAT BBLOCK\NETBEUI\MADGE\PROTOCOL.INI
   DAT BBLOCK\NDIS\MDGND30.BIN
   

   ii Replace the lines:

   DRV BBLOCK\NDIS\IBMTOK.SYS ~ 2 M
   DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M

   with the lines:

   DRV BBLOCK\NDIS\MDGND.DOS ~ ~ ~
   DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ ~

   ; NDIS2 on Madge 16/4 Adapter BASE D0H RPL BBLOCK\RPLBOOT.SYS LDR BBLOCK\RPLSTART.COM ~ ;DAT BBLOCK\NETBEUI\IBMTOK\PROTOCOL.INI DAT BBLOCK\NETBEUI\MADGE\PROTOCOL.INI DAT BBLOCK\NDIS\MDGND30.BIN DRV BBLOCK\RPLDISK.SYS ~ 4 M EXE BBLOCK\RPLPRO1.COM ~ 2 ~ 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\IBMTOK.DOS ~ 2 M ;DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M DRV BBLOCK\NDIS\MDGND.DOS ~ ~ ~ DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ ~

   Sample DOSBB.CNF file

5. Modify the PROTOCOL.INI file to include the correct driver information as follows:

   i The "bindings=" entry in each section must be:

   bindings=mdgnd_nif

   ii The final section must be:

   [mdgnd_nif]
   drivername = mdgnd$
   remoteboot=yes

6. Use the remoteboot command utility, RPLCMD.EXE, to add a boot-block record for the new adapter. For example, the following sequence of commands creates a sample boot-block record:

   C:\winnt\rpl> rplcmd
   Adapter Boot Config Profile Service Vendor Wksta [Quit]: b
   Add Del Enum: a
   BootName=DOSBP
   VendorName=0000F6
   BbcFile=BBLOCK\NETBEUI\MADGE\DOSBB.CNF
   BootComment=Madge 16/4 Adapter
   WindowSize=0

   In the example, 0000F6 represents the "vendor name" or network adapter prefix. The network adapter prefix is the first six digits of the adapter's identification number and is unique to Madge adapters.

   If you have installed several Madge adapters in the same computer, they all have the same adapter prefix. However, the BootName field and the workstation record field for each adapter have to be unique.

7. Use RPLCMD.EXE to add the new configuration. For example, the following sequence of commands creates a sample configuration:

   C:\winnt\rpl> rplcmd
   Adapter Boot Config Profile Service Vendor Wksta [Quit]: c
   Add Del Enum: a
   ConfigName=DOS622X
   BootName=DOSBP
   DirName=DOS
   DirName2=DOS622
   FitShared=fits\dos622.FIT
   FitPersonal=fits\dos622p.FIT
   ConfigComment=DOS 6.22 Madge 16/4 Adapter
   DirName3=
   DirName4=

   For BootName, enter the name of the boot-block record that you created in step 6.

   You have now finished configuring your Windows NT server to enable it to perform remote booting for DOS and Windows workstations.