|
This document contains instructions for installing the TokenExpress adapter
driver. It contains information specific to the installation and
operation of Intel's TokenExpress adapters only. Please refer to the
appropriate Network Operation System documentation for any NOS-specific
questions or other information.
Installing the remote boot PROM on the TokenExpress adapter:
- Follow the instructions in the manual that shipped with the remote
boot PROM.
- Be careful to position the boot PROM correctly on the TokenExpress
adapter. After you have installed the boot PROM, make sure none of the
pins were bent.
- Be aware of the Page Frame address, and the memory addresses of other
boards in your system before setting the RPL address location.
Installing and Configuring the Intel® TokenExpress adapter RPL Driver for NetWare*:
- Configure the server so your workstation can boot from the network.
You will need the TokenExpress adapter driver diskette and the
installation manual for your version of NetWare to set up the server.
Insert the following line in the file server's AUTOEXEC.NCF file:
- load TOKENRPL
The following is a typical AUTOEXEC.NCF file:
file server name TR_TEST
ipx internal net 63965
load c:\netware\octok161 slot=2 frame=TOKEN-RING name=seg1
bind ipx to seg1 net=100
load c:\netware\octok161 slot=2 frame=TOKEN-RING_SNAP name=seg2
bind ipx to seg2 net=200
load TOKENRPL
load route <----- (Optional if using Source Routing)
set allow unencrypted passwords=ON
- Create a bootable floppy disk. Copy the following files from the
NetWare WSGEN diskette to the bootable floppy disk:
LSL.COM
RPLODI.COM
ROUTE.COM (Optional, if using Source Routing)
IPXODI.COM
NETX.EXE
NOTE: The latest files are available from Novell
†.
- Copy the following file from the TokenExpress adapter driver diskette
#1 to the bootable floppy diskette:
- OCTOK16.COM
- Create an AUTOEXEC.BAT file on the bootable floppy disk which
contains the following lines:
prompt $p$g
lsl
rplodi
octok16
route (Optional if using Source Routing)
ipxodi
netx
- Create a generic CONFIG.SYS file on the bootable floppy disk like the
one that was used during testing:
- Without re-booting, from A:, type the following:
lsl
octok16
route (Optional if using Source Routing)
ipxodi
netx
f:
- Login as SUPERVISOR to the server onto which you will build the DOS
Remote Boot image.
- At the F:\LOGIN prompt, type the following:
- At this point, all files on the bootable diskette in drive A: will be
read and a boot image file will be created in the \LOGIN directory of
the server you are currently logged into. The name of this file will be
NET$DOS.SYS.
- Copy the AUTOEXEC.BAT file from the disk in drive A: to the F:\LOGIN
directory.
NOTE: If you forget this step, you will receive a "Batch file missing"
error during the remote boot process.
- Remove the bootable floppy diskette in the A: drive and re-boot the
workstation. The following screen will be displayed:
Intel TokenExpress FLASH RPL PROM for Novell & MS/IBM v1.12
Booting in 10 seconds with configuration:
Source : Local Disk
Press any key to change settings...
- Hit any key and the following screen appears:
Intel TokenExpress FLASH RPL PROM for Novell & MS/IBM v1.12
Messages: Boot Delay: Source: |
Extended 10
Local Disk |
Use up and down arrows to move, left arrow to adjust, ESC to continue.
- Using the arrow keys, change the settings so that:
Source = Novell Network and Server = Name of the server which contains the Boot Image.
The screen should now look like this:
Intel TokenExpress FLASH RPL PROM for Novell & MS/IBM v1.12
Messages: Boot Delay: Source: Node: Server: |
Extended
10 Novell Network 005500nnnnnn Your Remote Boot Server |
Use up and down arrows to move, left arrow to adjust, ESC to continue.
- Press ESC to continue, then type "y" to make the changes permanent.
- Once the workstation boots and attaches to the server, you may log into the network.
NOTE: For more information, refer to the NetWare* Installation manual. You will also find information in the manual on RPL, using multiple boot images, and the BOOTCONF.SYS file.

† This link will take you off of the Intel Web site. Intel does not control the content of the destination Web Site.
This applies to:
|