|
Intel's TokenExpress adapter NDIS driver conforms to Microsoft's NDIS
Specification version 2.0.1. Support for NDIS 2.02 (IBM extensions to
version 2.0.1) is included in the OS/2 driver for the TokenExpress
EISA/32 adapter. These drivers are on the TokenExpress adapter drivers
diskette #2 in the following subdirectories:
For OS/2 Workstations (TokenExpress EISA/32 adapters only):
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK32\OLITOK32.OS2
For DOS Workstations (TokenExpress EISA/32 adapters only):
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK32\OLITOK32.OS2
For OS/2 Workstations (all other TokenExpress adapters):
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK16\OLITOK.OS2
For DOS Workstations (all other TokenExpress adapters):
\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, to load the driver for Intel's TokenExpress
EISA/32 adapter your "DEVICE=" statement would read:
DEVICE=C:\MSLANMAN\DRIVERS\OLITOK32.OS2
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 for the Intel TokenExpress EISA/32 adapters resides in
the
\MSLANMAN.DOS\DRIVERS\TOKENRNG\OLITOK32 directory.
The OS/2 version for the Intel TokenExpress EISA/32 adapter is located
in the
\MSLANMAN.OS2\DRIVERS\TOKENRNG\OLITOK32 directory.
The DOS version for all other TokenExpress adapters is in the
\MSLANMAN.DOS\DRIVERS\TOKENRNG\INTELTOK directory.
The OS/2 version for all other TokenExpress adapters is in the
\MSLANMAN.OS2\DRIVERS\TOKENRNG\INTELTOK 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 =
OLITOK$" or "drivername = OLISRV$").
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:
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
($). The default drivername is 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 - 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 = try loading into high memory first; try low memory if that fails.
1 = try loading into low memory first; 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
- Configure the adapters so that they have different I/O addresses
and interrupts. (For ISA boards, make sure they also have
different DMA channels.)
- Follow the instructions in the your NOS guide for multiple
adapters, to establish CONFIG.SYS and PROTOCOL.INI files that
support multiple adapters.
- 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.
This applies to:
| 
