Issue: This is to clarify when and how to use rplfix.com. The name "rplfix.com" is misleading -- it is not for IBM RPL proms.
Symptoms: When using DOS v5.0 or higher with traditional Novell Remote Boot proms,
workstations will hang as command.com is loading. The way to recognize this is that the autoexec.bat file will not execute --not even the first line of the autoexec. The config.sys
files will all load fine, because they load before command.com loads. If no autoexec.bat
is present, then the workstation will hang just before an A: prompt is presented on
the workstation screen. The A: prompt will never appear and the workstation will hang.
Solution: Use rplfix.com only with Novell Remote Boot Proms where the boot image (net$dos.sys) has DOS 5.0 or higher. Do not use rplfix.com with IBM RPL proms. Rplb.zip already has rplfix awareness built-into its files (shown next): token.rpl, ether.rpl, pcn2l.rpl, f1eth.rpl, rboot.rpl. Always use rplb.zip for IBM RPL proms. Do not use etherrpl.nlm or tokenrpl.nlm, etc., that shipps with NetWare v3.11.
In case there's a question, rplfix.zip's purpose in life is to enhance Novell Boot Prom code while it sits in ram below 640k. This fix keeps DOS 5.0's command.com from loading on top of the boot prom code in ram and killing the remote boot process.
If using a Novell Remote Boot Prom, rplfix is needed. Dosgen the net$dos.sys file and run rplfix against net$dos.sys with the following syntax:
RPLFIX F:NET$DOS.SYS <enter>
Steve Huntington
Note: Rplfix.com and rplodi.com can both be obtained from dosup7.zip. Both files are only for Novell Remote Boot Proms not IBM RPL proms.
