          Setting up LAN Manager Server for Remote Boot Service
          for Workstations with HP PC LAN Adapter/16+ Boot ROMs
          =====================================================

Information on how to use and install remote boot services with LAN Manager
2.1 is contained in the Microsoft LAN Manager Administrator's Guide, chapter
"Booting Workstations Remotely".

To setup the remote boot services to boot HP/16 Plus adapters, follow the
instructions below:

1.  Start install the remote boot service.

    Follow the instructions in the Microsoft LAN Manager Administrator's
    Guide, chapter "Booting Workstations Remotely" until the heading
    "Installing the Remoteboot Service".  Do not run the RPLINST utility.


2.  Run the HPPRPL batch file on the HP Support Disk.

    For example, if the HP Support Disk is in floppy drive A, enter the
    following commands at the command prompt:

        A:
        CD \RPL
        HPPRPL

   This will create directories, copy files, and append records to RPL.MAP
   and RPLMGR.INI in order to boot client PCs with the HP/16 Plus adapters.
   See the section "Advanced Topics", "Creating Remoteboot Configurations
   for New Adapters" in the LAN Manager Administrator's Guide for more
   insight into what HPPRPL has done.


3.  Complete installation of the remote boot server.

    Complete the installation of the remote boot service by changing back
    to the C:\LANMAN\RPL directory and continue following the directions
    in the LAN Manager Administrator's Guide beginning with the command
    to run RPLINST.



Using TCP/IP Protocols on Remoteboot Workstations (MS-DOS only)
=================================================================
Client workstations that are booting remotely must use NetBEUI to boot.

After the client is booted and MS-DOS is loaded, TCP/IP can be loaded on
the client in order that it can access servers using the TCP/IP protocol.
The server that is providing the remote boot service must use NetBEUI.
In addition, it may be (but does not need to be) setup with TCP/IP.

After using NetBEUI to setup the remote boot services, you can prepare your
server to operate with remote boot TCP/IP workstations using the following
procedure.  Note that this procedure is similar to the procedure described
in the README.RPL file on the OS/2 server disk.

To use NetBEUI and TCP/IP:

1. Ensure the server has the following subdirectory:
        LANMAN\RPL\RPLFILES\BINFILES\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP.

   Create this subdirectory if it does not exist.


2. Copy all the files from the \DRIVERS\PROTOCOL\TCIP subdirectory
   on the LAN Manager MS-DOS drivers disk to the
   LANMAN\RPL\RPLFILES\BINFILES\LANMAN.DOS\DRIVERS\PROTOCOL\TCPIP
   subdirectory on the server.


3. Change to this subdirectory on the server and enter the command
   "DECOMP input_file output_file" to decompress the files with the
   extensions ending in "$".

   * All .EX$ files should be decompressed to .EXE files, and
     UNLOAD.EXE should be renamed UNLOADT.EXE.
   * All .86$ files should be decompressed to .86 files.
   * All .CO$ files should be decompressed to .COM files.
   * All .DO$ files should be decompressed to .DOS files.

   (After the files have been decompressed, delete all files
   with the extensions ending in "$" to save disk space.)


4. Log on to the server as administrator, and run RPLINST to set
   the protection on these files.


5. Run RPLMGR to perform these functions:

   * To create profiles for the remote boot TCP/IP workstations,
     as required.

   * To create new workstations with an IP address, a subnet mask,
     and a gateway in the boxes provided.


6. Edit the profile's AUTOEXEC.BAT file, removing the REM command from the
   start of the UMB.COM line.


7. Edit the profile's CONFIG.SYS file, removing the REM command from the
   start of the DEVICE=NEMM.DOS line.

   AUTOEXEC.BAT and CONFIG.SYS are in the directory:

   * LANMAN\RPL\RPLFILES\PROFILES\(PROFILE_NAME)
     if the profile is used as a shared profile

   * LANMAN\RPL\RPLFILES\MACHINES\(COMPUTER_NAME)\(PROFILE_NAME)\PRO
     if the profile is used as a personal profile


8. After the client workstation has remotely booted, the user can load the
   TCP/IP protocol using the command "LOAD TCPIP". 

   The TCP/IP protocol can be unloaded using the command "UNLOAD TCPIP".



Miscellaneous Notes and Comments
================================
The Microsoft LAN Manager Administrator's Guide section "Configuring
Workstations with Hard Disks" and "Removing Workstations with Hard Disks"
instructs you to use a pair of programs "rplenabl.exe" and "rpldsabl.exe"
to enable and disable remote booting from PCs with hard disks.  These
programs do not work on all PCs. If your PC with a hard disk refuses to
boot remotely after running "rplenabl" you will have to use your PC
manufacturer's setup or configuration program to disable your hard drive.

LAN Manager 2.0 Servers do not support remote booting clients with HP PC
LAN Adapter/16+ cards.  You must upgrade your server to LAN Manager 2.1
in order to support remote booting of these clients.

The Microsoft LAN Manager Administrator's Guide states that for Microsoft
OS/2 workstations, the network adapter card must be set to use hardware
IRQ2.  IRQ2 is not supported by the HP PC LAN Adapter/16+, however in most
PCs you may use IRQ9 instead.
