   LAN Manager Remote Boot workstations

  LAN Manager* 2.1 RPL Installation

  This document applies to the EtherExpress(tm) 16, 16TP, 16C, FLASH,
  FLASH TP, FLASHC, MCA, and MCA/TP adapters.  It contains installation 
  notes for installing the driver.  It does not explain how to configure an 
  EtherExpress adapter.  For instructions about configuring the adapter, 
  see the printed installation guide.

  
  BEFORE YOU BEGIN
  ================
  This document assumes that the RPL workstations are running DOS 5.0 or 
  later (remote OS/2 workstations are not supported), and that the server 
  is using LAN Manager's default file structure.
  
  If you have a hard disk in the RPL workstations you will need to execute
  Microsoft's RPLENABL command before those workstations can boot from the
  network.  See the Microsoft LAN Manager Administrator Guide for more
  information on RPLENABL.
  
  Chapter 13 of the LAN Manager Administrator Guide is on remote boot
  workstations.  Complete the sections on "Preparing the Server, Installing 
  LAN Manager with Remote Selections, and Setting up for MS-DOS and MS-OS/2
  Workstations."
  
  A note in Chapter 13 Section 4 refers to MSDOS.SYS, IO.SYS, IBMDIO.COM, and
  IBMDOS.COM.  Use the File Manager to turn off the SYSTEM and HIDDEN file
  attributes for these files.  You can verify these attributes are correct by
  displaying a directory listing for C:\LANMAN\RPL\RPLFILES\BINFILES\DOS500.
  
  If the MSDOS.SYS and IO.SYS files are not visible in this virtual root
  directory when booting an RPL workstation, an error appears:
  "NON-SYSTEM DISK insert DOS disk and strike any key."
  
  The name of the server MUST conform to the DOS naming convention (eight
  characters or less).
  
  Be sure RPLINST runs successfully before you continue.  This is an 
  indication that the DOS directory is installed correctly.
  
  Setting up an RPL workstation is a fairly detailed process.  If you have
  additional questions about the remote boot process, refer to your LAN 
  Manager documentation.
  
  PROCEDURE
  =========
  
  1.   Make sure the REMOTEBOOT service is not running.  This can be done by
       entering the command NET STOP REMOTEBOOT at the server's OS/2 prompt.
  
       NOTE:   You will need to be logged in as NET ADMIN.
  
  2.   Remove all references to Intel EtherExpress (EXP16) card in the RPL.MAP 
       & RPLMGR.INI files located in the C:\LANMAN\RPL directory. These 
       entries probably don't exist unless you manually entered them.
  
        To help determine if RPL.MAP & RPLMGR.INI contain references to 
        the EtherExpress card:
  
        -    Look for lines that begin with 00AA00?????? in the RPL.MAP file. 
             If so, remove them.  
        -    Look for configurations that contain "bblink = RDOSIN" or 
             "adapters=00AA00??????." If so, remove them.
  
  3.   Edit the RPL.MAP file to include information about the EtherExpress
       adapter.  (Path: \LANMAN\RPL\RPL.MAP)
  
       Use existing entries in the the RPL.MAP file.  Modify them to look like
       the following lines.  We show each entry as two lines, but in the 
       RPL.MAP file each entry will be on ONE line.
  
     CHECK THE SYNTAX AND SPACING CAREFULLY!
  
     In the Boot Block Records
     -------------------------
     yyyyyyyyyyyy BBLOCK\NETBEUI\EXP16\DOSBB.CNF 2 6 A ~ DOS~INTEL~
     EXP16      00AA00 ~ ,,, ~  RDOSIN ~ ~ ~ ~ ~ ~
  
     In the Workstation Records
     --------------------------
     00AA00?????? INTEL D FITS\DOS500 (RPL_SERVER_NAME) S ~ ~ ~ ,,, ~
     RDOSIN  ~ DEFAULT *~New~Intel~Exp16~*~ ~ ~
  
     NOTE:     The RPL_Server_Name must conform to the DOS naming convention.
  
  4.   Edit the RPLMGR.INI file to include information about the EtherExpress
       adapter.
  
       In the Configuration section of the RPLMGR.INI file, add these new
       sections for the EtherExpress adapter.
  
     [configuration]
     name = INTEL
     os = DOS500
     dirname = DOS
     dirname2 = DOS500
     bblink = RDOSIN
     fitfileshared = fits\DOS500
     comment = DOS 5.00 EtherExpress card
     adapter = 00AA00??????
  
  5.   Copy the EtherExpress DOS NDIS driver from the Intel disk:
       (A:\MSLANMAN.DOS\DRIVERS\ETHERNET\EXP16\EXP16.DOS) to the
       C:\LANMAN\RPL\BBLOCK\NDIS directory.
  
  6.   Create the directory C:\LANMAN\RPL\BBLOCK\NETBEUI\EXP16.  In this
       directory create a PROTOCOL.INI and a DOSBB.CNF file.
  
     Example of the PROTOCOL.INI file
     --------------------------------
          [protman]
              drivername = protman$
              dynamic = yes
              priority = netbeui
  
          [netbeui]
              drivername = netbeui$ 
              bindings = EXP16
              names = 5
              ncbs = 8
              packets = 20
              pipeline = 10
              sessions = 4
              stacksize = 512
              lanabase = 0
  
          [EXP16]
              IOADDRESS = 0x300  
              DRIVERNAME = EXP16$
              RPL  
  
     NOTE:     The IOADDRESS line should match the I/O address you chose for
               the EtherExpress adapter.
  
     Example of the DOSBB.CNF file
     -----------------------------
          ; DOS on INTEL ETHEREXPRESS   
          RPL BBLOCK\RPLBOOT.SYS
          LDR BBLOCK\RPLSTART.COM ~
          DAT BBLOCK\NETBEUI\EXP16\PROTOCOL.INI
          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\TCPDRV.DOS /I:C:\LANMAN.DOS ~ ~
          EXE BBLOCK\NETBEUI\NETBEUI.EXE ~ 10 ~
          DRV BBLOCK\NDIS\EXP16.DOS ~ ~ ~
          DRV BBLOCK\PROTMAN.DOS /I:C:\LANMAN.DOS ~ M
  
     NOTE:  You can copy the DOSBB.CNF file from the subdirectory of
            another network adapter, then modify it to match this example.
  
  7.   Create this directory structure:
  
       C:\LANMAN\RPL\RPLFILES\MACHINES\INTEL\DEFAULT\WKSTA
  
       Copy the PROTOCOL.INI you created in the previous step to the WKSTA
       directory.
  
  8. Update RPLMGR.
  
     -    Change to the C:\LANMAN\RPL and run RPLMGR.
     -    From the Remoteboot menu, choose NEW PROFILE.
     -    Enter Profile name, comment and configuration.
          Profile Name:  INTEL
          Comment:  Your comment here
          Configuration:  DOS500 EtherExpress card
       
          The configuration line should match the COMMENT line entry in
          the PLMRG.INI file.

     -    Choose "OK".
     -    When disk activity stops, exit RPLMGR.
  
  9.   Start the REMOTEBOOT service by entering the NET START REMOTEBOOT 
       at the OS/2 prompt.
  
       NOTE:  After the RPL installation is complete, configure the server to
              automatically start the REMOTEBOOT service.
  
  10.  Install the EtherExpress adapter as described in the Intel manual.
  
  11.  Attach the workstation to the network and turn it on.
  
  12.  The workstation will attach to the server and eventually return you to a
       "C:\" prompt.  The "C:\" is a virtual link to the
       C:\LANMAN\RPL\RPLFILES\MACHINES\INTEL\DEFAULT\WKSTA directory on the
       server.
  
       NOTE:   The workstation has limited file permissions until the user 
               executes a NET LOGON command.
  
  As you can se, this is a long process.  If the RPL workstation does not find
  the server (example error message: Searching for a DLC RPL server), go back
  through each step and check the syntax, spelling, and directory structures.
  
  
  RPLMGR OPTIONAL
  ===============
  Follow Microsoft's instructions in Chapter 13 of the Administrator's Guide 
  to configure personal or shared workstation profiles using RPLMGR.
  
                
* Third-party trademarks are the property of their respective owners.
