NDIS Driver Notes
NDIS Driver Notes for Intel's TokenExpress(TM) PRO adapter
==========================================================
Location of driver: disk 2 \NDIS\TPRO.DOS
\NDIS\TPRODOS.NIF
\NDIS\TPRO.OS2
\NDIS\TPROOS2.NIF
\DOS\TPRO.DOS
\DOS\TPROEDOS.NIF
\IBMOS2\TPRO.OS2
\IBMOS2\TPROEOS2.NIF
For sample configuration files, see the end of this document.
General Installation
--------------------
1. If you have a Plug and Play BIOS and are running OS/2*, Windows NT*,
or a NetWare* server, make sure you DISABLE Plug and Play
on your adapter using SoftSet2 (Advanced Options menu). These
environments don't support Plug and Play. If Plug and Play is enabled
in these environments, the NOS may not be able to find your adapter.
2. Many different network operating systems use a standard 2.0.1
version NDIS driver to talk to the network adapter. The
TokenExpress PRO adapter's NDIS driver conforms to Microsoft's
2.0.1 NDIS specification.
File Purpose
---- --------------------------------------------
TPRO.DOS NDIS driver for DOS workstations.
TPRO.OS2 NDIS driver for servers & OS/2 workstations.
PROTOCOL.INI Fragment of the general PROTOCOL.INI file. This
fragment contains information specific to the
TokenExpress PRO adapter. You'll need to add this
fragment to the general PROTOCOL.INI file.
TPROEOS2.NIF These are the extended Network Information files
TPROEDOS.NIF (NIF) that are used during the installation process.
These files are located in the following path:
DOS: \DOS
OS/2: \IBMOS2
TPROOS2.NIF These are the standard NIF files that are used with
TPRODOS.NIF Microsoft LAN Manager installations. Other Network
Operating systems may use these during their
installation. If needed, these files (one for DOS,
one for OS/2) are located in the following path:
DOS: \MSLANMAN.DOS\DRIVERS\NIF
OS/2: \MSLANMAN.OS2\DRIVERS\NIF
Hints and Tips
--------------
Installing multiple adapters in the same computer
-------------------------------------------------
If you're installing multiple adapters using the NDIS 2.01
driver, you may need to modify your PROTOCOL.INI file.
Make sure the first adapter listed in your PROTOCOL.INI file
has the lowest I/O address. For example,
[TPROEDOS_nif]
DriverName = TPRO$
IOADDRESS = 300
[TPROEDOS_nif]
DriverName = TPRO2$
IOADDRESS = 310
Configuring the MAC driver
--------------------------
This section explains how to modify the NDIS driver configuration
file (PROTOCOL.INI) to use the TokenExpress PRO adapter drivers.
A sample file, containing the recommended entries for configuring
the TokenExpress PRO DOS NDIS and OS/2 NDIS drivers, is included
on the Intel driver disk (disk 2).
The Intel-specific parameters needed to customize the PROTOCOL.INI
file are listed below.
If you need to change any of the TokenExpress PRO adapter's
parameters after installation, find the appropriate section in
the PROTOCOL.INI for the TokenExpress PRO adapter. This section
has the heading "[INTEL32_NIF]" or "[INTEL16_NIF]" and should
begin with the statement "drivername = OLISRV$" or "drivername =
OLITOK$". Add any new keywords or change their values as necessary.
Required Parameters
-------------------
The TokenExpress PRO adapter driver requires two entries in
PROTOCOL.INI: drivername = TPRO$ and IOaddress=xxx (where xxx
is the I/O Address of the card). "Drivername" can be any
characters (up to 7) followed by a dollar sign ($). The default
drivername is TPRO$. The driver name identifies the network driver.
The drivername (with small or capital letters) is the prefix portion
of the filename of the network driver in the DRIVERS directory
followed by $. The MAC drivername is TPROODI$.
Since the TokenExpress PRO adapter driver implements the loopback
function, the [DLC] section of PROTOCOL.INI does not need a
"loopback =" entry.
Optional Parameters
-------------------
Adapter Card Configuration Entries:
NetAddress = "[12 hexadecimal digits]"
NodeAddress = [hex value] [hex value] [hex value]
EarlyRelease = [YES/NO]
NetAddress
Same as NodeAddress, but available for compatibility with
IBM EE 1.0 and Lan Server 2.0. Example: NetAddress =
"005500876543"
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.
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:
[NetBEUI DLC.MAXOUT parameter]*[max number of sessions]
For DOS, this can be any number from 2 to 6. For OS/2, any
number from 2 to 100. The default is 6.
RecBufSize
Sets the size (in bytes) of the buffers in the Receive Buffer
pool. This number ranges from 256 to 5000. Default is 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 is 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 is 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.
This parameter is ignored for 4 Mbps LANs.
Rpl
If present, this 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.
Intel's FaxBack service is often updated with configuration
examples of certain NDIS based network operating systems. Call
FaxBack and order the catalog listing for TokenExpress Adapter
documents. If the configuration example is not listed, please consult
with your Network Services Supplier, or the vendor of that particular
operating system.
Sample configuration files
--------------------------
CONFIG.SYS (for DOS)
DEVICE=C:\path\PROTMAN.DOS /I:C:\path
DEVICE=C:\path\TPRO.DOS
CONFIG.SYS (for OS/2)
DEVICE=C:\path\PROTMAN.OS2 /I:C:\path
DEVICE=C:\path\TPRO.OS2
PROTOCOL.INI
[TPRO_NIF]
DRIVERNAME = TPRO$
MAXTRANSMITS = 40
RECBUFSIZE = 2048
REBUFCOUNT = 10
PROTOCOL.INI (for LAN Manager)
[PROTMAN]
DRIVERNAME = PROTMAN$
* Third-party trademarks are the property of their respective owners
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.