Question : RPL is not working (Novell 4.11)

We are running Novell 4.11. When we boot with the 3.5-1.4 diskette on which the boot sequences are for making the boot image, the system loads without any problems. As soon as we do the DOSGEN on the server and want to boot remotely with the same netcard that has a PROM the system says that it can't find the server. To create the boot image we run DOSGEN from F:\Login (command line: F:\login\dosgen a:). Does anybody know what is wrong?

Answer : RPL is not working (Novell 4.11)

From Dayna Text:
Setting Up RPL Support

Setting up RPL support on the network is necessary only for remote workstations using the Novell Enhanced or IBM RPL PROMs. Remote workstations using the “old” or Novell IPX Remote Boot PROM do not need to set up RPL support. See “Making a Boot Image File Diskette” for more information.

Setting up RPL support requires you to do the following:



tLoad the RPL.NLM program on the NetWare server and bind it to the server's LAN driver.

tLoad the RPL.COM file on a local client workstation, if you need to boot from a NetWare server across a source routing bridge.

tEnsure that the required files are copied to the appropriate directories.

tCopy newer RPL files to the appropriate directories if existing files are not current.

NOTE: All of the files necessary for setting up a NetWare remote boot client workstation are located in the RPL directory on NetWare Client for DOS and MS Windows Disk 2.



Loading the RPL.NLM Program

The RPL.NLM file is a NetWare Loadable ModuleTM (NLM) program that acts as a protocol stack. It responds to the IBM architected Remote Program Load (RPL) frames as defined in the IBM Remote Program Load User's Guide.

The RPL.NLM program is used in networks that have diskless workstations installed with the RPL BIOS module known as a Remote Boot PROM. Currently, RPL is supported on the following network boards:



tIBM Ethernet boards (MCA and Model 25SX)

tIBM PC network boards

tIBM token-ring network boards

tNovell (or compatible) and third-party network boards with an Enhanced Remote Boot PROM installed



Procedure



1.At the server console, load the RPL.NLM program by typing

LOAD RPL

2.Bind the RPL.NLM program to the network board in the server by typing

BIND RPL TO network_board [parameter]

For example, to bind RPL to an NE2000 LAN driver with the Ethernet_802.2 frame type, you would type

BIND RPL TO NE2000 FRAME=ETHERNET_802.2

For details on how to use the BIND parameter for RPL at the command line, see “Remote Program Load (RPL) Software” in Chapter 3 of NetWare Client for DOS and Windows Technical Reference.

When the RPL.NLM program loads, it searches the SYS:LOGIN directory for a BOOTCONF.SYS file. If it finds one, the RPL.NLM program reads the BOOTCONF.SYS file into memory in order to make the file information available when a FIND frame is received from a client workstation. See “Configuring the BOOTCONF.SYS File” for more information.