Remote Booting to Novell NetWare with ODI
drivers
In order to remote boot onto a Novell NetWare network using ODI drivers
(for Apricot on-board Ethernet, 3Com, Western Digital, or other cards), you should be
aware of the following issues.....
Firstly, as with 'normal' remote booting, if you are running with DOS 5,
you will need to run RPLFIX on the boot image file you generate after having run DOSGEN.
See Novell Newsletter Issue 13 for more details. Also (if applicable) see IPB 2086 which
explains how to correctly configure a remote booting DOS 5 machine to run with Windows and
WINA20.386.
In order to remote boot with an ODI driver, you must run the Novell
supplied RPLODI.COM (found in the \DOSODI directory on your WSGEN disk, or on your DOS ODI
Workstation disk) after you run LSL, but before you load the LAN driver; i.e.
LSL
RPLODI
82592ODI
IPXODI
TCPIP
TELAPI
NETX
Finally, because NetWare remote booting is done via raw IPX using
Ethernet_802.3, you need to ensure that your NET.CFG file defines the frame type
ETHERNET_802.3 before any other frame types; i.e.
| Link Support |
|
Buffers 8 1568 |
|
MemPool 4096 |
| Link Driver 82592ODI |
|
INT #1 10 |
|
PORT #1 400 |
|
DMA #1 6,7 |
|
Frame Ethernet_802.3 |
|
Frame Ethernet_II |
|
Protocol IPX 0 Ethernet_802.3 |
| Protocol TCPIP |
|
ip_address |
89.89.20.49 |
|
ip_netmask |
255.0.0.0 |
|
tcp_sockets |
16 |
|
udp_sockets |
16 |
|
raw_sockets |
4 |
|
nb_sessions |
8 |
|
nb_commands |
16 |
|
nb_adapter |
0 |
|
nb_domain |
If NET.CFG does NOT define the frame types in this order, the remote
program load facility will lose communication with the server as soon as the LAN driver
(in this case 82592ODI.COM) is loaded.
----------oOo---------- |
