This file contains instructions for installing the TokenExpress adapter driver. It contains information specific to the installation and operation of Intel's TokenExpress™ adapters only. Please refer to the appropriate Network Operation System documentation for any NOS-specific questions or other information.

You can get the latest drivers and instructions from one of Intel's online services. Always check the revision date of the document to make sure you have the latest copy. For more information, see the inside back cover of the installation guide or the help file "Using Intel's Automated Customer Support."

Installing and configuring the Intel® TokenExpress™ DLC driver for IBM Environments

The TokenExpress adapter installation program (INSTIBM.BAT) is dependent upon whether or not your application requires the IBM Netbios protocol.

If Netbios is NOT used, the installation program creates a \NETWORK directory on the specified destination drive and copies the TokenExpress adapter DLC driver (OC02DLC.SYS) and the TokenExpress interrupt arbitrator (OC01IA.SYS) files into it.

If Netbios IS required, the IBM interrupt 5c arbitrator (DXMA0MOD.SYS) and the Netbios (DXMT0MOD.SYS) files are copied to the \NETWORK directory along with the TokenExpress adapter DLC driver (OC02DLC.SYS).

The IBM interrupt 5c arbitrator and Netbios files are found on the IBM LAN Support Program diskette (must be purchased from IBM* Corporation).

To install the TokenExpress adapter DOS DLC driver, do the following:

1. Insert the Intel adapter driver diskette into drive A:.
   
   
2. Run the TokenExpress adapter driver installation program by typing
   A:\IBM\DOS\INSTIBM src dest

   where "src" is the drive containing the driver diskette and "dest" is the drive where the files will be written. For example,

   A:\IBM\DOS\INSTIBM A: C:
   
   
3. Follow the directions on your monitor to complete the installation.

   NOTE: If you are using DOS LAN Requester, you may experience some problems when using the IBM Interrupt 5C Arbitrator (DXMA0MOD.SYS). (This file is copied from the IBM LAN Support diskette when installing IBM's NETBIOS (DXMT0MOD.SYS)).

   You can eliminate the problem by using the Interrupt 5C Arbitrator (OC01IA.SYS) supplied on the TokenExpress adapter driver diskette. This is done as follows:

   1. Insert the Intel driver diskette into drive A:
   2. Copy the TokenExpress Adapter Interrupt 5C Arbitrator into the \NETWORK where you installed your TokenExpress adapter DLC driver (OC02DLC.SYS). For example, if you installed your DLC driver on drive C:, you would enter the command
      
      
      COPY A:\IBM\DOS\OC01IA.SYS C:\NETWORK
      
      
   3. Edit your CONFIG.SYS file and delete the entry for the IBM* Interrupt 5C Arbitrator (DXMA0MOD.SYS).
      
      
   4. Add an entry for the TokenExpress™ Adapter Interrupt 5C Arbitrator (OC01IA.SYS) *immediately preceding* the entry for the TokenExpress adapter DLC driver (OC02DLC.SYS). For example,

      :
      DEVICE=C:\NETWORK\OC01IA.SYS <- Add this line
      DEVICE=C:\NETWORK\OC02DLC.SYS <- before this line!
      :

4. Remove the Intel driver diskette from drive A: and reboot your system.
   
   
5. Install IBM DOS LAN Requester

   DOS LAN Requester software is currently packaged with LAN Server or LAN Enabler. Use the IBM DOS Lan Requestor Installation Manual for installation instructions. This process basically copies the Lan Requestor files needed to connect to Lan Server*.

An optional country code can be specified when loading the interrupt 5C arbitrator OC01IA.SYS. Drivers loaded subsequently may then use this country code to display messages in the selected language.

The country code is specified in the CONFIG.SYS file as follows:

device = (path)\OC01IA.SYS <optional country code>

The supported values are:

The TokenExpress adapter DLC driver supports four (4) optional parameters.

These parameters are specified in the CONFIG.SYS file as follows:

device = (path)\OC02DLC.SYS -E<...> -N<...> -L -A -S -P

The parameter definitions are:

-E<AdapterNumber><EarlyRelease>

AdapterNumber
Identifies the adapter as either primary or secondary. (0 = primary, 1 = secondary)

EarlyRelease
Enables/disables Early Token Release. ETR is enabled by default. (0 = enable, 1= disable)

NOTE:This parameter is ignored if the data rate is 4 Mbps.

-N<AdapterNumber><NodeAddress>

AdapterNumber
Identifies the adapter as either primary or secondary. (0 = primary, 1 = secondary)

NodeAddress
Zero (0) or a locally administered node address A '0' forces the use of the adapter's burned-in address (BIA) and overrides an application's use of a local address. The locally administered node address is a 12-digit hexadecimal number starting with 4, 5, 6, or 7.

-S Sets the minimum number of Link Stations.

-P Sets the minimum number of SAPS.

-L Causes the driver to copy all transmit data into a local buffer before transferring it to the network. It may be necessary to use this with the TokenExpress ISA Adapter if all the following conditions are met: 1) the adapter is configured as a Bus Master, 2) an expanded memory board is installed, and 3) the application transfers data directly from expanded memory to the network. In addition, this parameter may be needed if the expanded memory manager does not support VCPI and/or the DPMI standards.

Specifying this parameter causes the driver to use more memory and should only be specified if necessary. Do not use this parameter if the adapter is configured to operate in programmed I/O mode.

-A Causes the driver to treat the first adapter found as the secondary adapter (1) and ignore any other adapter. If this parameter is not specified, the adapter with the lowest I/O address setting is automatically designated as the primary adapter (0) and the other adapter is the secondary adapter.

Example: To configure a system that has two TokenExpress adapters with locally administered addresses (the first adapter using address 400000001066, the second adapter using 400000002067 and having Early Token Release disabled), the following entry would be placed in your CONFIG.SYS file:

device=<path>\OC02DLC.SYS -N0400000001066 -N1400000002067 -E11

Creating Multiple SAPs for the TokenExpress™ 16 Adapter

Extra SAPS can be configured on optional parameters on the device driver OC02DLC.SYS or with IBM's DXMT0MOD.SYS is loaded.

IBM Lan Support Program users can create multiples SAPs (Service Access Points) for the TokenExpress™ 16 adapters using the DLC drivers. For the TokenExpress 16 drivers you must include in your CONFIG.SYS file.

Sample CONFIG.SYS:

DEVICE=C:\(path)\OC01IA.SYS
DEVICE=C:\(path)\OC02DLC.SYS -P05 -S040

OR

DEVICE=C:\(path)\OC01IA.SYS
DEVICE=C:\(path)\OC02DLC.SYS
DEVICE=C:\(path)\DXMT0MOD.SYS ES=3 EST=3 CF=Y

NOTE: Replace "(path)" with the complete path to the directory containing the TokenExpress 16 drivers.

OC02DLC.SYS Parameters
-P05 Configures a minimum of 5 SAPS
-S040 Configures a minimum of 40 Link Stations

DXMT0MOD.SYS Parameters
ES=3 Configures 3 Extra Saps (valid range is 0 - 99)
EST=3 Configures 3 Extra link Stations (valid range is 0 - 254)
CF=Y Configures Call.Far function to prevents applications from
intercepting INT 5C. (IBM Lan Support Program terminates if
application Intercepts INT 5C). Recommended for MS Windows users.

NOTE: For more details on LAN Support driver parameters, consult chapter 5 of the the LAN Support 1.3x documentation or contact IBM.

* Third-party trademarks are the property of their respective owners.

This applies to:

TokenExpress™ 16/p Adapter