Networking Connectivity
Intel® Boot Agent
Windows NT* 4.0 RPL Remote Program Load (RPL) Installation & Configuration

This information is provided solely as a convenience to Intel customers. If you have questions about Microsoft Windows NT* 4.0 or the remoteboot process, consult your Windows NT documentation, your Windows NT 4.0 Resource Kit, or contact Microsoft for assistance.

The remoteboot process

When you start a computer, the operating system is loaded into memory. When a Remote Initial Program Load (RPL) ROM chip is placed on a network card, the client computer will retrieve startup and configuration software from the server when the client starts. This RPL ROM interrupts the computer's standard startup process and redirects the calls for the operating system to the NIC. The RPL ROM also establishes a basic network connection between the workstation and server during the startup process. This process is known as the remoteboot process. The following steps will detail the process on how to setup and configure the server side of RPL.

Windows NT 4.0

Install the NetBEUI and DLC protocols on the server. These protocols are required to run the Remoteboot service.

RPL Screen Capture #1

From the Start menu select Settings and then Control Panel.

Once the Control Panel appears, click the Network icon.

In the Network Setting dialog box, choose the Services tab and then select the Add button.

In the Select Network Service dialog box, choose the Remoteboot Service.

RPL Screen Capture #2

In the Remoteboot Setup dialog box, enter the complete path and directory name where the remoteboot directory is to be installed. By default this directory is <Systemroot>\RPL.

Click OK and complete the dialog boxes.

Once you have completed the install of the Remoteboot service, you will need to Start the Remoteboot Service, and launch Remoteboot Manager from the Start menu.

RPL Screen Capture #3

From the Menu bar, choose Configure and then Fix Security. The Fix Security process will create the RPLUSER local group and also assign the proper permissions throughout the RPL directory.

Boot a client remotely; this creates an adapter record on the server. If the client does not appear, select the View menu and Refresh.

RPL Screen Capture #4

The record can be converted to a workstation record, from the Remoteboot pull down menu, select Convert Adapters and add the client's name and profile.

RPL Screen Capture #4

If the record will not allow a Profile assignment, the VendorName will have to be added using RPLCMD.

Go to a Command Prompt (Start | Run | cmd)
*note: "<>" means press the "enter" key.
(V)endor <>
(A)dd <>
VendorName= "00A0C9" (or first six characters of MAC address) <>
VendorComment= "Intel" (Optional) <>

(B)oot <>
(A)dd <>
BootName= "W95" <>
VendorName= "00A0C9" (Or first 6 characters of MAC address) <>
BbcFile= "BBlock\netbeui\E100\W95BB.cnf <>
BootComment= (Optional) <>
WindowSize= "0x0" <>
quit <>

Create c:\winnt\rpl\bblock\netbeui\E100
Copy c:\winnt\rpl\bblock\netbeui\epro\* c:\winnt\rpl\bblock\netbeui\e100\*
Copy the newest e100b.dos driver (E100P Driver from to c:\winnt\rpl\bblock\ndis
Edit c:\winnt\rpl\bblock\netbeui\e100\protocol.ini
Last few lines, change the drivername to E100B$
Remove line "IOADDRESS= 0x300"
Save | Exit

Edit c:\winnt\bblock\netbeui\e100\win95bb.cnf
Change all directories from EPRO to E100
Change all Drivers (epro.dos) to E100B.dos

This applies to:

Intel® Boot Agent

Solution ID: CS-008194
Last Modified: 29-Sep-2014
Date Created: 11-Jan-2004
Back to Top