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 Intel's TokenExpress adapter NDIS driver conforms to Microsoft's NDIS Specification version 2.0.1. These drivers are on the TokenExpress adapter Drivers diskette in the following subdirectories:

For OS/2 Workstations:

\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK16\OLITOK16.OS2

For DOS Workstations:

\MSLANMAN.DOS\DRIVERS\TOKENRNG\OLITOK16\OLITOK16.DOS

In addition to the driver, the PROTOCOL.INI file may also need to be updated. A sample PROTOCOL.INI file is included in the same directory as the driver.

Note: Although this PROTOCOL.INI file specifically references an installation under Microsoft LAN Manager, it is useful in illustrating what items may be needed for other configurations.

The driver must be loaded via the CONFIG.SYS file using a "DEVICE=" statement. For example:

DEVICE=C:\MSLANMAN\DRIVERS\OLITOK.OS2

The DOS NDIS driver version of this file is located in the

\MSLANMAN.DOS\DRIVERS\OLITOK directory.

\MSLANMAN.OS2\DRIVERS\OLITOK directory.

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 "[OLITOK_NIF]" and should begin with the statement "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 a single entry in PROTOCOL.INI:

drivername = OLITOK$

Since the TokenExpress adapter driver implements the loopback function, the [DLC] section of PROTOCOL.INI does not need a "loopback =" entry. Optional parameters The optional entries for this adapter may be divided into two groups. The entries and syntax for the two groups are listed below.

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, 1, 2, or 3, 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)

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. Example:

NodeAddress=4000 0000 0000

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.

MAC Driver Configuration Entries:

MaxRequests = value
MaxTransmits = value
RecBufSize = value
RecBufCount = value
RecBufHigh = value
Rpl

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))

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))

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.

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

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 your NOS 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$." In each of those sections add the following:

   Adapter = [adapter number]

   Where [adapter number] is the number (0, 1, 2, or 3) 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.

This applies to:

TokenExpress™ 16/p Adapter