NetWare Remote Boot
NetWare Remote Boot Installation Notes For Intel's
TokenExpress(TM) PRO adapter
==================================================
Location of Driver: \NWCLIENT\TPROODI.COM
\NWCLIENT\IPX.COM (IPX not yet available)
Sample configuration files
--------------------------
AUTOEXEC.BAT (For ODI workstation):
PROMPT $P$G
SET NWLANGUAGE=ENGLISH <--- USE WITH VLMS ONLY
LSL
TPROODI
ROUTE <--- Optional if using source routing
IPXODI
NETX <--- For NetWare 3.11 OR 3.12
VLM <--- For NetWare 3.12 OR 4.0X
AUTOEXEC.BAT (For IPX Workstation)
PROMPT $P$G
IPX
NETX
CONFIG.SYS
FILES=50
BUFFERS=25
LASTDRIVE=Z <--- For use with VLM's
NET.CFG
PREFERRED SERVER=<SERVER_NAME>
NETWARE DOS REQUESTER <--- For use with VLM's
FIRST NETWORK DRIVE = F <--- For use with VLM's
Remote boot overview
--------------------
1. Load & bind RPL at the file server.
2. Create a bootable floppy disk (single or multiple boot image)
3. Test the bootable floppy disk(s).
4. Run DOSGEN (single or multiple boot image).
5. Flag NET$DOS.SYS shareable, read/write (see below for multiple
boot image files).
6. Run TokenSet to configure the adapter for ODI remote boot.
7. Reboot the machine to remote boot off the file server.
Load & bind RPL
---------------
1. The TokenExpress PRO adapter's boot ROM is ODI based and
therefore requires the RPL nlm to be loaded on each segment of
the server that will have remote boot workstations.
Sample 3.12 autoexec.ncf with RPL added:
(in a 3.11 environment you'd load TPRO311.LAN)
LOAD C:\TPRO.LAN PORT=300 FRAME=TOKEN-RING NAME=SEG1
BIND IPX TO SEG1 NET=100
LOAD RPL
BIND RPL TO SEG1
LOAD ROUTE <--- Optional if using source routing
Setting up a single boot image
------------------------------
1. A Single boot image should be used if all your remote boot
workstations use the TokenExpress PRO adapter and if all of
them will use the same boot up files and DOS version.
Otherwise, refer to the instructions below for multiple boot
images.
2. Create a DOS bootable disk with the appropriate drivers. All
but the VLM's can be found on the driver disk (#2) in the
\NWCLIENT directory.
If using the ODI driver include these files:
COMMAND.COM <--- Format disk for format/s
AUTOEXEC.BAT <--- See above for sample
CONFIG.SYS <--- See above for sample
NET.CFG <--- See above for sample
LSL.COM
TPROODI.COM
IPXODI.COM
NETX.EXE <--- For NetWare 3.11 or 3.12
VLM.EXE (and related files) <--- For NetWare 3.12 or 4.01
If using the IPX driver include these files (IPX not yet
available):
COMMAND.COM
AUTOEXEC.BAT <--- See above for sample
CONFIG.SYS <--- See above for sample
NET.CFG <--- See above for sample
IPX.COM <--- IPX not yet available
NETX.EXE <--- For NetWare 3.11 or 3.12
Include any other drivers you plan to load on this boot disk.
BEFORE CONTINUING ON, MAKE SURE THE MACHINE WILL BOOT AND LOGIN
TO THE NETWORK WITH THIS BOOTABLE, FLOPPY DISK.
NOTE: Refer to your NetWare documentation for additional
information on remote booting with VLM's.
3. Log onto the network with supervisory rights and verify that
these mappings exist:
SYS:LOGIN
SYS:SYSTEM
If they don't exist, you will need to create them by typing the
following:
MAP F:=SYS:LOGIN
MAP G:=SYS:SYSTEM
4. 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.
5. Change the attributes of NET$DOS.SYS to Shareable, Read/Write.
FLAG NET$DOS.SYS SRW (NetWare 3.11 and 3.12)
FLAG NET$DOS.SYS SHRW (NetWare 4.01)
6. Copy the AUTOEXEC.BAT file from your floppy to the F:\LOGIN
directory. If you forget this step, you will receive an error
"batch file missing".
7. Configure the adapter for remote boot. Run TokenSet, select
the Change adapter option, choose a Flash chip address, and
select the NetWare ODI remote boot program. The NetWare IPX
remote boot program is not yet available.
This can also be done the first time you plug the adapter in
and turn the power on. Select the FLASHSET option, choose a
Flash chip address, and select the NetWare ODI remote boot
program.
Make sure you exclude this address range if you'll be loading
a memory manager.
Procedure for setting up multiple boot images
---------------------------------------------
1. Create a DOS 5.0 or 6.0 bootable disk that contains the files
listed in step 2 under the single boot image section.
2. 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. The XXXX.BAT file should contain the
information as listed in the appropriate AUTOEXEC.BAT file
under Sample configuration files above.
3. 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.
4. 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 by typing the
following:
MAP F:=SYS:LOGIN
MAP G:=SYS:SYSTEM
5. 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. XXXX is the
name you choose for your remote boot image file.
DOSGEN creates a file XXXX.SYS in the SYS:LOGIN directory. It
contains all the files from your boot disk.
6. Change the attributes of the new file to Shareable, Read/Write:
FLAG XXXX.SYS SRW (NetWare 3.11 and 3.12)
FLAG XXXX.SYS SHRW (NetWare 4.01)
7. 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,005500123456=XXXX.sys
where: 0xYYY is the network address of the remote-boot
workstation (It should start with 0x). This is the NET=#
that is specified on the BIND IPX line of your AUTOEXEC.NCF.
005500123456 is the 12 digit token ring address of the
TokenExpress PRO adapter. This address can be displayed by
running TokenSet, View Adapter Configuration.
XXXX.sys is the name of the boot image for this workstation.
You entered this name when you ran DOSGEN.
For additional information on setting up multiple boot images,
refer to your Novell documentation.
8. Configure the adapter for remote boot. Run TokenSet, select
the Change adapter option, choose a Flash chip address, and
select the NetWare ODI remote boot program. The NetWare IPX
remote boot program is not yet available.
This can also be done the first time you plug the adapter in
and turn the power on. Select the FLASHSET option, choose a
Flash chip address, and select the NetWare ODI remote boot
program.
Make sure you exclude this address range if you'll be loading
a memory manager.
Hints and Tips
--------------
1. Remote Boot Process:
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 if it finds a line with its Token Ring address it
executes the XXXX.sys file. If it does not find its Token Ring
address (or a BOOTCONF.SYS file), it looks for NET$DOS.SYS and
executes that instead.
2. 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. If you are using a memory manager make sure you
EXCLUDE the memory for the boot ROM.
3. Computer won't read your XXXX.sys file.
Check the syntax in the BOOTCONF.SYS.
4. You receive "error reading/opening boot disk image file."
Make sure a machine can boot with the EXACT floppy disk used
for DOSGEN. If you're using the BOOTCONF.SYS, there may be an
error/problem in it.
5. Later versions of Novell files (LSL.COM, ROUTE.COM, IPXODI.COM,
& NETX.EXE) can be downloaded from Novell on Compuserve,
NetWire, filename DOSUPx.EXE (example DOSUP9.EXE). Make sure
you have the latest Novell files.
6. RPL-ROM-FFC counts up and the workstation will not remote boot.
The RPL.nlm may not be loaded or RPL may not be bound to your
Token-ring board.
7. Copy the AUTOEXEC.BAT file from your floppy to the F:\LOGIN
directory. If you forget this step, you will receive an error
"batch file missing".
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.