RPL Enhancements and Loading Protocols (87859)


The information in this article applies to:

  • Microsoft LAN Manager 2.1
This article was previously published under Q87859

SUMMARY

Remote Program Load (RPL) allows a remote network workstation to be booted from a local computer running the RPL service. A hard disk or floppy disk is not required on the remote workstation in order for the RPL feature to operate successfully. An RPL ROM must be installed on the workstation (usually on the network adapter) to initiate the RPL boot sequence.

MORE INFORMATION

RPL was implemented in LAN Manager version 2.0 and has been enhanced in LAN Manager 2.1. These enhancements are:

  • Improved usability: A highly automated full-screen interface helps you configure, install (RPLSETUP and RPLINST), and manage (RPLMGR) the RPL feature.
  • Improved security: Early log on with password can be used for remote boot clients.
  • Improved flexibility: FIT support for MS-DOS RPL.
  • Improved memory usage: RPL components use less RAM when initializing, and release more memory when terminating.
  • Improved flexibility with network adapters and diskless clients:
  • Western Digital EtherNet
  • 3Com EtherNet (EtherLink, EtherLink II, EtherLink Plus, EtherLink/MC, EtherLink 16, TokenLink)
  • EtherStart and 3Station
  • Novell NE1000, NE 2000
  • Nokia EtherNet IIe
  • IBM EtherNet support in addition to IBM token ring
LAN Manager 2.1 RPL does not provide support for LAN Manager 2.0 RPL image files.

The remote boot process uses the NetBEUI protocol. NetBEUI must always be running on the remote boot client because it is used to maintain the permanent C: redirection (the boot drive). However, TCP/IP and XNS can be dynamically loaded (one at a time) and unloaded on the workstation.

While Microsoft does not officially state that DLC is supported (mainly because MS-DOS DLC was not available in LAN Manager 2.1, and it was not in the test plan). However, you can use this same technique to load DLC on a LAN Manager 2.1 remote boot MS-DOS client (once DLC becomes available). Simply add DLC to the proper location in the embedded LANMAN.DOS drivers tree, and add a [dlc] section to PROTOCOL.INI in the boot block. Next, reboot and load DLC.

Modification Type:MajorLast Reviewed:9/30/2003
Keywords:KB87859
©2003 Microsoft Corporation. All rights reserved.