RPL workstations
NETWARE REMOTE BOOT INSTALLATION NOTES:
FOR THE INTEL EtherExpress(tm) 16 FAMILY OF NETWORK ADAPTERS
============================================================
This document applies to the EtherExpress(tm) 16, 16 TP, MCA, and
MCA TP. It contains installation notes on installing the driver
and troubleshooting tips.
NOTE: This document or an updated version (if the procedure
changed since this was written) is available on FaxBACK.
Document # 6410.
INTRODUCTION:
-------------
The boot ROM on EtherExpress cards contain information about the
network that enables a remote boot workstation to find a file server
and execute a boot program on the server. This boot program contains
the files necessary for a workstation to start up and log onto the
network. These files are typically called the boot image.
If you have more than one diskless workstation you can configure all
of them to use the same boot image or each workstation can have a
unique boot image. This document descibes both procedures.
The EtherExpress boot ROM supports either IPX or ODI workstations.
If you are using ethernet type II, use must use ODI driver. The
IPX configuration only supports ethernet 802.3.
If you have additional questions about the remote boot process, refer
to your NetWare documentation.
If You Are Using DOS 5.0:
-------------------------
If you are using DOS 5.0 or greater you will need a utility called
RPLFIX (dated 6/30/91 or later). This utility can be downloaded from
NetWire. The name of the downloadable file is RPLFX2.ZIP or
DOSUP5.ZIP. This file is in the Novell Library Forum - NetWare
Utilities Library (#6) Troubleshooting NetWare Boot PROM. Download
this file before going any farther. Novell updates files on a
regular basis and the downloadable file name may change. If you have
trouble finding these files, check with Novell technical support.
The EtherExpress 16 must be setup in a computer with a floppy disk
drive (so you can run SOFTSET) then move it to the diskless
workstation. This is not a concern for the EtherExpress MCA since
all Micro Channel computers have a floppy disk drive.
You will also need a blank diskette and a workstation, already on the
network, to run DOSGEN.
CONFIGURE THE ETHEREXPRESS CARD FOR THE BOOT ROM:
-------------------------------------------------
For complete information about configuring the EtherExpress adapter,
see either the EtherExpress Expert's Guide or Complete Guide.
1. Install the remote boot ROM.
EtherExpress 16: Insert the remote boot ROM into the socket on
the EtherExpress 16 card. Be sure to line up the notch on the
ROM with the notch on the socket.
EtherExpress MCA: The remote boot program is in FLASH memory on
the board. Go to the next step.
2. Configure the EtherExpress boot ROM.
EtherExpress 16: Select the boot ROM address range by running
the manual configuration option in SOFTSET.
EtherExpress MCA: Enable the boot ROM/FLASH option and select an
address range by running Set Configuration from the computer's
configuration utility.
NOTE: The Boot ROM requires 8K of memory in the the C0000
to DFFFFh address range.
PROCEDURE FOR SETTING UP A SINGLE BOOT IMAGE:
---------------------------------------------
1. Create a DOS boot disk containing the following files:
COMMAND.COM
CONFIG.SYS < optional
AUTOEXEC.BAT
IPX.COM < for IPX workstations only
NETX.COM
LSL.COM < for ODI workstations only
RPLODI.COM < for ODI workstations only
EXP16ODI.COM < for ODI workstations only
IPXODI.COM < for ODI workstations only
NETX, LSL, RPLODI, and IPXODI are on NetWare's WSGEN disk and
EXP16ODI is on the EtherExpress disk.
If you plan to load any additional drivers, they should also be
included on this boot disk.
Example AUTOEXEC.BAT files.
For IPX workstations: For ODI workstations:
PROMPT $P$G PROMPT
IPX LSL
NETX RPLODI
EXP16ODI
IPXODI
NETX
NOTE: RPLODI.COM must be loaded immediately after LSL and before
the EXP16ODI. RPLODI.COM must be version 1.02
(date 3/21/91) or newer. If you use an earlier version
you may get the error "RPLODI already active."
2. Log onto the network as supervisor and verify that these mappings
exist:
SYS:LOGIN
SYS:SYSTEM
If they don't, you will need to create them.
MAP F:=SYS:LOGIN
MAP G:=SYS:SYSTEM
3. Put the boot disk in drive A. Change to the LOGIN directory and
type:
G:DOSGEN
NOTE: For DOSGEN to work correctly, you should run DOSGEN from
the LOGIN directory not the SYSTEM directory.
DOSGEN creates a file called NET$DOS.SYS in the SYS:LOGIN
directory. NET$DOS.SYS contains all the files from your
boot disk.
4. Change the attributes of NET$DOS.SYS to: Shareable, Read/Write.
FLAG NET$DOS.SYS SRW
5. Unless you're running DOS 5.0 or greater, you're done. Reboot
the system and log onto the network using the remote boot ROM.
If you are running DOS 5.0, follow Novell's instructions for
running RPLFIX.
PROCEDURE FOR SETTING UP MULTIPLE BOOT IMAGES:
---------------------------------------------
1. Create a DOS boot disk containing the following files:
COMMAND.COM
CONFIG.SYS < optional
AUTOEXEC.BAT
IPX.COM
NETX.COM
LSL.COM < for ODI workstations only
RPLODI.COM < for ODI workstations only
EXP16ODI.COM < for ODI workstations only
IPXODI.COM < for ODI workstations only
NETX, LSL, RPLODI, and IPXODI are on NetWare's WSGEN disk and
EXP16ODI is on the EtherExpress disk.
If you plan to load any additional drivers, they must also be
included on this disk.
The AUTOEXEC.BAT file should contain only one line:
XXXX.BAT
WHERE: XXXX is a name you assign to the remote boot workstation.
Each remote boot workstation will have its own XXXX.BAT file.
Example XXXX.bat files.
For IPX workstations: For ODI workstations:
Prompt $p$g Prompt $p$g
IPX LSL
NETX RPLODI
EXP16ODI
IPXODI
NETX
NOTE: RPLODI.COM must be loaded immediately after LSL and before
the EXP16ODI. RPLODI.COM must be version 1.02
(date 3/21/91) or newer. If you use an earlier version
you may get the error "RPLODI already active."
Copy the XXXX.bat file to the LOGIN subdirectory on the server.
You can execute other commands by including them in the XXXX.bat
file. See Novell's documentation if you have questions.
2. Log onto the network as supervisor and verify that these mappings
exist:
SYS:LOGIN
SYS:SYSTEM
If they don't, you will need to create them.
MAP F:=SYS:LOGIN
MAP G:=SYS:SYSTEM
3. Put the boot disk in drive A. Change to the LOGIN directory and
type:
G:DOSGEN a: XXXX.sys
There MUST be a space between a: and XXXX.sys.
4. Change the attributes of the new file to Shareable, Read/Write:
Flag XXXX.sys SRW
5. Change to the LOGIN directory and create an ASCII file called:
BOOTCONF.SYS
Each line in this file defines a unique remote-boot workstation.
The format for this file is:
0xYYY,00AA00123456=XXXX.sys
WHERE:
- 0xYYY is the network address of the remote-boot workstation (It
should start with 0x).
- 00AA00123456 is the 12 digit ethernet address of the
EtherExpress card. This address is printed on the board or can
be displayed with SOFTSET (EtherExpress 16) or MCADIAGS
(EtherExpress MCA).
- XXXX.sys is the name of the boot image for this workstation.
You entered this name when you ran DOSGEN.
6. Unless you're running DOS 5.0 or greater, you're done. Reboot
the system and log onto the network using the remote boot ROM.
If you are running DOS 5.0, follow Novell's instructions for
running RPLFIX.
For additional information on setting up multiple boot images refer
to you Novell documentation.
When you power on a remote-boot workstation, the ROM finds the server
and looks for a BOOTCONF.SYS file. If it finds this file AND it
finds a line with its ethernet address it executes the XXXX.sys file.
If it does not find its ethernet address (or a BOOTCONF.SYS file), it
looks for NET$DOS.SYS and executes that instead.
TROUBLESHOOTING TIPS:
=====================
IF YOU ARE RUNNING MULTIPLE FILE SERVERS:
-----------------------------------------
Since there is no guarantee which file server will respond to first,
Novell requires that the boot images (BOOTCONF.SYS and NET$DOS.SYS)
be copied to each server.
NON 802.3 SERVERS:
------------------
The Boot ROM is configured for a FRAME type of 802.3. If you are
using a different FRAME type (i.e. Ethernet Type II), the server
must be configured to include both 802.3 and the other FRAME type.
You will also need to include a NET.CFG file in the boot image. This
NET.CFG files must also include both FRAME types with 802.3 first.
Example NET.CFG using Ethernet Type II and TCP/IP:
Link Support
Buffers 8
Mempool 4096
Protocol TCPIP
Bind EXP16ODI
Protocol IPX
Bind EXP16ODI
Link Driver EXP16ODI
PORT 300
Frame Ethernet_802.3
Protocol IPX 0 Ethernet_802.3
Frame Ethernet_II
Protocol TCPIP 8137 EthernetII
WILDCARDS:
----------
You cannot use wildcards in the BOOTCONF.SYS file with the
EtherExpress card.
COMPUTER WON'T BOOT FROM NETWORK:
---------------------------------
Make sure the computer will boot from the EXACT floppy disk used for
DOSGEN. If the remote boot workstation does not have a floppy drive,
try another computer with the SAME configuration.
Make sure the IPX matches the EtherExpress board. Type "IPX i" from
the floppy drive that contains IPX.COM.
- The Lan Option should say Intel EtherExpress
- The Hardware configuration should say AUTOMATIC or it should
match the i/o you selected in softset.
If you are using a memory manager make sure you EXCLUDE the memory for
the boot ROM.
