![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) Adapter: Remote Boot PROMs with RPL - MS LAN MAN v2.0
RPL DRIVER INSTALLATION ON LAN MANAGER 2.0
This file contains instructions specific for the installation and
operation of Intel's TokenExpress adapter driver. Refer to the
appropriate Network Operation System documentation for any NOS-specific
questions or other information.
These instructions apply to Release 5.0 of the software.
Installing and Configuring the Intel TokenExpress RPL Driver for MS Lan
Manger v2.0
Note: The Intel TokenExpress EISA/32 adapter does not support RPL
when used in a workstation. The remaining installation steps are
followed when the workstation contains one of the other members of
Intel's family of TokenExpress adapters.
This description is a supplement to the "Microsoft LAN Manager
Administrator's Guide." It describes how to prepare a LAN Manager 2.0
Server for RPL of LAN Manager workstations equipped with Intel
TokenExpress adapters.
Before installing RPL support for Intel adapters, you should prepare
your server for RPL support of DOS and OS/2 LAN Manager Workstations (if
required) as described in the "Microsoft LAN Manager Administrator's
Guide."
The various OEM-versions and revisions of Microsoft LAN Manager 2.0
differ somewhat in the directory structure of the RPL directory on the
server. As a result, the directory structure on your server may differ
from the directory structure assumed in the following descriptions.
Translate the suggested actions to the actual directory structure on
your server.
The files to be used for support of RPL of workstations with Intel
adapters are located on the Intel Adapter Driver Diskette #2 in the
directories \MSLANMAN\RPL and \MSLANMAN\RPL\RPL_20.
Common DOS and OS/2 Preparation
Make \LANMAN\RPL the current directory on your server and insert the
Intel Adapter Driver Diskette #2 in drive A. Edit the RPL.MAP file found
on your server and include the lines from the RPL.MAP file on the driver
diskette (the RPL.MAP file on the driver diskette is located in the
\MSLANMAN\RPL\RPL_20 directory). You should include the default
workstation records for the Intel adapter node addresses 005500??????.
Finally, copy the two boot block definition files for DOS and OS/2 from
the driver diskette to your server as follows:
copy a:\mslanman\rpl\rpl_20\d_olitok.cnf
copy a:\mslanman\rpl\rpl_20\o_olitok.cnf
Note: Because support of RPL for DOS workstations is a prerequisite
for RPL of OS/2 workstations, you should always carry out the following
step even if you will only be supporting RPL of OS/2 workstations.
Preparing for RPL of DOS Workstations
With LANMAN\RPL as current directory, make the OLITOKTOK directory by
typing the following:
md dos\olitoktok
Copy the driver files into the newly created directory as follows:
copy a:\mslanman\rpl\olitok.dos dos\olitoktok
copy a:\mslanman\rpl\rpl_20\protocol.ini dos\olitoktok
Preparing for RPL of OS/2 Workstations
Note: If you have not prepared your server for the RPL of DOS
workstations, you must do so now before continuing.
Preparation of your server for the RPL of OS/2 workstations:
1. Create an INTELTOK driver directory in the RPL\LANMAN directory
structure.
2. Create an Intel specific CONFIG.SYS in the RPL\MACHINES directory
structure.
3. Create an Intel specific FIT table referring to the Intel files
mentioned above.
Creating the OLITOKTOK Directory
With LANMAN\RPL as the current directory, make the OLITOKTOK directory
as follows:
md lanman\drivers\olitoktok
Copy the driver files into the newly created directory as follows:
copy a:\mslanman\rpl\olitokr.os2 lanman\drivers\olitoktok
copy a:\mslanman\rpl\protocol.ini lanman\drivers\olitoktok
Creating a CONFIG.SYS file for an OS/2 RPL workstation
The CONFIG.SYS file for an OS/2 rpl workstation must have the following
characteristics in the LAN Manager section:
1. The OLITOKR.OS2 MAC driver must be loaded from the
LANMAN\DRIVERS\OLITOKTOK directory.
2. The protocol manager driver must use the PROTOCOL.INI file from the
LANMAN\DRIVERS\OLITOKTOK directory.
A default CONFIG.SYS file for RPL of an OS/2 workstation is
typically located in the RPL\MACHINES\DEFAULT directory. An
Intel-specific CONFIG.SYS file (named CONFIG.INT) can be obtained
from an existing CONFIG.SYS for another adapter as follows:
3. Make LANMAN\MACHINES\DEFAULT your current directory.
4. Create the CONFIG.INT file by copying an existing CONFIG.SYS
copy config.sys config.int
5. Update CONFIG.INT by replacing the two appropriate lines in the LAN
Manager section with the following lines:
device=c:\lanman\drivers\protman\protman.os2
/i:c:\lanman\drivers\olitoktok
(above needs to be one line with space a between the two)
device=c:\lanman\drivers\olitoktok\olitokr.os2
6. Select the CONFIG.INT file as your CONFIG.SYS via the FIT-table
described below.
Creating the FIT-Table
The fit-tables will normally be located in the RPL\FITS directory. An
Intel-specific fit-table (named inteltok.fit) may be obtained from an
existing xx.fit for another adapter as follows:
1. Make LANMAN\RPL\FITS your current directory.
2. Create the OLITOKTOK.FIT file by copying an existing fit-table
copy xx.fit olitoktok.fit.
3. Update OLITOKTOK.FIT by replacing the definition of CONFIG.SYS with
the following line:
c:\config.sys machines\DEFAULT\config.int
4. Remove any existing definition of C:\LANMAN\PROTOCOL.INI from the
fit table.
Note that the OLITOKTOK.FIT file is referenced from one of the
server records in the RPL.MAP file.
5. Enable Default RPL Records
You are now ready to remote boot your workstations using Intel adapters.
However, the procedure differs for DOS and OS/2 workstations as outlined
below.
For RPL of DOS workstations with Intel adapters:
1. Type 'net stop remoteboot'
2. Update the Intel-specific default workstation records in the
RPL.MAP file so that the DOS record is enabled and the OS/2 record
is disabled.
3. Type 'net start remoteboot'
For RPL of OS/2 workstations with Intel adapters:
1. Type 'net stop remoteboot'
2. Update the Intel-specific default workstation records in the
RPL.MAP file so that the DOS record is disabled and the OS/2 record
is enabled.
3. Type 'net start remoteboot'
Trademark information