![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
TokenExpress(TM) Adapter: Installation, MS LAN Manager 2.x - DOS & OS/2
INSTALL AND CONFIGURE LAN MANAGER 2.X
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 adapter NDIS driver
for Microsoft LAN Manager 2.x
For any computer -- DOS, OS/2, workstation, or server -- follow the
directions below.
If LAN Manager is not already installed:
1. Install Lan Manager according to its installation instructions.
2. After the Lan Manager SETUP program finishes reading the standard
driver diskette, you will be asked if you would like to install any
additional diskettes. Select "YES".
3. When SETUP prompts you for a diskette, insert the TokenExpress
adapter driver diskette.
4. Highlight the Intel TokenExpress adapter in the displayed list and
press the Spacebar to select it.
5. Follow the directions on the screen to complete the installation.
If installing under LAN Manager 2.0:
1. Run the SETUP program from the computer's hard drive.
2. From the "Actions" menu, choose "Import".
3. When SETUP prompts you for a diskette, insert the TokenExpress
driver diskette.
4. Highlight the Intel TokenExpress adapter in the displayed list and
press the Spacebar to select it.
If this is the first Token-Ring adapter to be installed in this
computer, skip to step 7 below.
If this TokenExpress adapter replaces some other vendor's
Token-Ring adapter, continue with step 5.
5. From the "Actions" menu, choose "View/modify". At the "Hardware"
screen, remove the reference to the old adapter and protocol, and
add a reference to the TokenExpress adapter and protocol.
6. From the "Actions" menu, choose "Save".
7. Follow the directions on the screen to complete the installation.
If installing under LAN Manager 2.1:
1. Run the SETUP program from the computer's hard drive.
2. From the system menu, choose "Configuration".
3. From the pull-down menus, select "Network Drivers", "Add New
Config", and "Other Driver". When SETUP prompts you for a
diskette, insert the TokenExpress adapter driver diskette #2.
4. Highlight the Intel TokenExpress adapter in the displayed list and
press Enter.
5. Follow the directions on the screen to complete the installation.
Customizing the PROTOCOL.INI file
This section explains how to modify the Microsoft LAN Manager
configuration file (PROTOCOL.INI) to use the TokenExpress adapter
drivers. A sample file, containing the recommended entries for
configuring the TokenExpress adapter DOS NDIS and OS/2 NDIS drivers, is
included on the Intel driver diskette. The DOS version, common to all
Intel TokenExpress adapters, resides in the
\MSLANMAN.DOS\DRIVERS\TOKENRNG\OLITOK directory. The OS/2 version for
the Intel TokenExpress EISA/32 adapter is located in the
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK32 directory. The OS/2 version for
all other TokenExpress adapters is in the
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK directory.
The Intel-specific parameters needed to customize the PROTOCOL.INI file
are listed below.
If you need to change any of the TokenExpress adapter's parameters after
installation, find the appropriate section in the LANMAN\PROTOCOL.INI
for the TokenExpress adapter and add any new keywords or change their
values as necessary. (This section will have a heading "[OLITOK32_NIF]"
or "[OLITOK_NIF]" and should begin with the statement "drivername =
OLISRV$" or "drivername = OLITOK$").
For an overall introduction to configuring the LAN Manager network
drivers, refer to the Microsoft LAN Manager Network Device Driver Guide.
Required parameters
The TokenExpress adapter driver requires only one entry in PROTOCOL.INI:
For DOS NDIS (all TokenExpress adapters):
drivername = OLITOK$
For OS/2 NDIS (TokenExpress EISA/32 adapter only):
drivername = OLISRV$
For OS/2 NDIS (all other TokenExpress adapters):
drivername = OLITOK$
"drivername" can be any characters (up to 7) followed by a dollar sign
($).
Since the TokenExpress adapter driver implements the loopback function,
the [DLC] section of PROTOCOL.INI does not need a "loopback =" entry.
Optional parameters
Adapter Card Configuration Entries:
Adapter = [adapter number]
NodeAddress = [hex value] [hex value] [hex value]
EarlyRelease = [YES/NO]
Adapter selects the board to configure. [adapter number] must be 0 - 7,
where:
0 = "Primary" adapter (default, I/O address 0A20H)
1 = "Alternate" adapter (I/O address 0A24H)
2 = "Second primary" adapter (I/O address 0A50H)
3 = "Second alternate" adapter (I/O address 0A54H)
** 4 = "Third primary" adapter (I/O address 1A20H)
** 5 = "Third alternate" adapter (I/O address 1A24H)
** 6 = "Fourth primary" adapter (I/O address 1A50H)
** 7 = "Fourth alternate" adapter (I/O address 1A54H)
** Note: These addresses are only available with the Intel TokenExpress
EISA/32 adapter.
For an ISA board, use this parameter if you change the board's I/O
address switch setting.
For an MCA or EISA board, use this parameter if you change the I/O
address with the system configuration
utility.
NodeAddress Specifies the address which replaces the adapter's
Burned-In Address (BIA). (The new address must be locally
administered). [hex value] has the form 0xdddd; d = hexadecimal digit.
EarlyRelease Enables or disables Early Token Release. YES = enable, NO
= disable. (Default = YES)
MAC Driver Configuration Entries:
MaxRequests = value
MaxTransmits = value
RecBufSize = value
RecBufCount = value
RecBufHigh = value
Rpl
Where MaxRequests sets the maximum number of "General Requests." Can be
any value from 1 to 10. (Default = 6).
MaxTransmits sets the maximum number of outstanding "TransmitChain"
commands. On a server, this number should equal the product of the
following two numbers:
[value of NetBEUI DLC.MAXOUT parameter]*[maximum number of sessions]
For DOS: Can be any number from 2 to 6.
For OS/2: Can be any number from 2 to 100. (Default = 6)
RecBufSize Sets the size (in bytes) of the buffers in the Receive
Buffer pool. This number ranges from 256 to 5000. (Default = 512)
The maximum size of the frames which may be received by the adapter is:
min (MaxFs, RecBufSize x (RecBufCount -1))
RECOMMENDED MAX SIZE: The maximum amount of receive buffers, RecBufSize
x RecBufCount, should not exceed 64K bytes. In DOS workstations, this
number should not exceed 20Kb. In DOS RPL workstations, this number
should not exceed 7Kb.
RecBufCount Sets the number of buffers in the Receive Buffer Pool.
Can be any number from 4 to 10. (Default = 10)
The maximum size of the frames which may be received by the adapter is:
min (MaxFs, RecBufSize x (RecBufCount -1))
RECOMMENDED MAX SIZE: The maximum amount of receive buffers, RecBufSize
x RecBufCount, should not exceed 64K bytes. In DOS workstations, this
number should not exceed 20Kb. In DOS RPL workstations, this number
should not exceed 7Kb.
RecBufHigh determines where to load the Receive Buffer Pool. Can be
either 0 or 1. (Default = 0).
0 = first try loading into high memory; if that fails, try low memory.
1 = first try loading into low memory; try high memory if that fails.
EarlyRelease sets board to use early token release on 16 Mbps LANs. YES
= enable ETR, NO = disable ETR. (Default = YES)
This parameter is ignored for 4 Mbps LANs.
Rpl if present, postpones adapter initialization from workstation
boot-up time to NETBIND execution time. This ensures that the remote
boot process is not disturbed by the board's initialization and
diagnostics.
If you are installing two adapters in the same computer
To configure the PROTOCOL.INI file for two adapters in the same
computer:
1. Configure the adapters so that they have different I/O addresses
and interrupts. (For ISA boards, make sure they also have
different DMA channels.)
2. Follow the instructions in the LAN Manager "Network Device Driver
Guide" for multiple adapters, to establish CONFIG.SYS and
PROTOCOL.INI files that support multiple adapters.
3. Edit the PROTOCOL.INI file, and find the Intel adapter sections
that begin with "drivername = OLITOK$" and "drivername = OLITOK2$."
(If you are installing multiple EISA/32 adapters in your system
under OS/2, the parameters should read "drivername = OLISRV$" and
"drivername = OLISRV2$"). In each of those sections, add the
following:
Adapter = [adapter number]
where [adapter number] is the number (0-7 for the TokenExpress
EISA/32 adapter, 0-3 for all other TokenExpress adapters) you
assigned to that adapter in the Adapter Card Configuration entry.
For a description of the [adapter number] parameter, refer to
section I under OPTIONAL PARAMETERS, above.
Trademark information