The entries in the TokenExpress™ 16 adapter section may be divided into two groups; entries related to the configuration of the adapter itself, and entries related to the driver software.

The entries for the two groups as well as the syntax are:

Adapter Configuration Entries

IoBase = hex value
NodeAddress = hex value, hex value, hex value
NetAddress = value
EarlyRelease = value

A hex value has the format 0xdddd, where "d" may be any hexadecimal digit, e.g. 0x4ABC.

NetAddress and NodeAddress are two alternative formats for a node address.

TokenExpress™ 16 Configuration Entries

MaxFrameSize = value
MaxRequests = value
MaxTransmits = value
RecBufSize = value
RecBufCount = value
RecBufHigh = value
RPL
ReOpen = value
FrameStatus = value
TxBufferSize = value
SupportGDT = value
NDIS201

The following table summarizes the valid entries and values in the TokenExpress 16 adapter section:

The parameters have the following meaning:

Drivername
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\TOKENRNG directory followed by $. The MAC drivername is TE16$ or te16$.

IoBase
Selects the adapter that must be accessed by the driver module. This parameter is used when the driver module must use an adapter on a specific I/O base address.

MaxFrameSize
This parameter limits the maximum frame lengths that the driver supports. Some protocols, e.g. the IBM NetBIOS driver for DOS, require that the maximum frame size is below a certain value. The actual maximum frame length is the lowest value of MaxFrameSize, the ReceiveArea determined by RecBufSize, and RecBufCount and TxBufferSize.

NodeAddress
If this entry is specified, the specified value will be used in place of the universal burned-in node address on the adapter. Note that the entered address must be administered locally. Example:

NetAddress
Same as NodeAddress, but available for compatibility with IBM Extended Services 1.0 and LAN Server 2.0/3.0. Example:

Note the quotation marks enclosing the values. They are important as they make the protocol manager accept the value as a string and not as a large number.

The letter "t" can be inserted in front of the NetAddress value. This is recommended when configuring the MAC driver in Windows for Workgroups. Example:

MaxRequests
Sets the maximum number of outstanding GeneralRequests and configures the size of the GeneralRequest Queue.

MaxTransmits
Sets the maximum number of outstanding TransmitChain commands. This configures the size of the TransmitChain Request Queue.

RecBufSize
Configures the size of each receive buffer (in bytes) in the PC. The number of receive buffers is defined by the RecBufCount entry. RecBufSize multiplied by RecBufCount is the total Receive Area allocated in the PC.

The maximum size of frames which may be received and transmitted by the adapter is limited by the lowest value of these factors:

Ring speed, 17954 at 16 Mbps and 4472 at 4 Mbps.
ReceiveArea minus 256 (RecBufSize x RecBufCount - 256)
MaxFrameSize parameter (if defined in PROTOCOL.INI)
TxBufferSize parameter (if defined in PROTOCOL.INI)

RecBufHigh
Configures the Receive Buffer Pool in high (above 1M bytes) memory or low memory. A value of 0 (zero) causes TokenExpress 16 to try to allocate the Receive Buffer Pool in high memory and only if this fails to allocate from low memory. A value of 1 causes TokenExpress16 adapters to do the opposite, that is, try to allocate the Receive Buffer Pool in low memory, and only if this fails try to allocate from high memory. The parameter is only valid in OS/2.

RPL

EarlyRelease
If set to "NO," the "early token release" function on a 16 Mbps Token-Ring is disabled. The keyword is ignored on a 4 Mbps Token-Ring.

ReOpen
This parameter specifies re-opening of the adapter by the network driver if it closes due to a lobe error.

FrameStatus
When set to "NO," the status of all transmitted frames will be "SUCCESS" regardless of the actual frame status. "NO" is the default setting. If set to "YES," the actual frame status will be returned. Some protocol stacks depend on the actual frame status while others require "SUCCESS" on all transmitted frames. If you cannot make a connection to a machine on another ring, set the parameter to "YES."

TxBufferSize
This parameter specifies the size (in kilobytes) of PC memory to allocate for TransmitBuffers. The adapter requires TransmitBuffers if there are 16 MB or more of memory installed in the PC. If the parameter "SupportGDT" is set to "YES," use this parameter to change the TransmitBufferSize. If a TransmitBufferSize is defined, the adapter cannot transmit frames that are larger than this size. By default, no TransmitBufferSize is defined (which normally provides the best performance). See also the RecBufSize entry.

SupportGDT
To make the driver accept virtual addresses (GDT) in OS/2. This parameter specifies whether a protocol can transmit frames using virtual addresses, or if it must use physical addresses. If your protocols can only use virtual addresses, set this parameter to "YES" (indirectly sets Transmit Buffer Size to 20K). The Transmit Buffer Size of 20K can be reduced by using the TxBuffersize parameter. The default for SupportGDT is "NO" (it provides higher performance compared to "YES"). The parameter is only valid in OS/2.

NDIS201
This parameter specifies that the network driver may only support NDIS201, and not the IBM extension to the NDIS 2.01 standard denoted NDIS 2.02 and disable support for promiscuous (receive any packet on LAN) receive mode. The default is that this parameter is omitted, thus supporting LAN Station Manager, LAN Network Manager and IBM NDIS protocols that require NDIS 2.02. The "NDIS201" parameter must be used if you want to perform NDIS 2.01 conformance tests.

Multiple Adapter Configuration

You may install up to four Token-Ring adapters in your computer (up to two in DOS systems). Following these guidelines if installing more than one adapter:

• If your network operating system is Microsoft LAN Manager, follow the instructions in "Microsoft LAN Manager, Network Device Driver Guide" for multiple adapter configurations to obtain a CONFIG.SYS and PROTOCOL.INI file for your configuration.

  If your network operating system is IBM LAN Support Program, IBM NTS/2, IBM LAN Server or Microsoft Windows for Workgroups, the network installation utilities provided with the systems execute configuration with multiple adapters.

• Configure the adapters so that they have different I/O addresses. All adapters must also have different interrupt levels and DMA channels.

• The new PROTOCOL.INI will have two or more driver sections. The first section will be identified by "drivername=TE16$." The following sections will be identified by "drivername=TE162$," TE163$, and TE164$ respectively.

  In each of these sections, use the "IoBase=0x0nnnn" parameter to select the adapter for the driver module. ("0x0nnnn" identifies the I/O address of the corresponding adapter.)