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

You'll always find the most current version of the driver instructions and if the driver software has changed, you can get the latest drivers and instructions from Intel's online services. Always check the revision date of the document to make sure you have the most updated copy.

Installing and configuring the Intel TokenExpress adapter DLC driver for IBM PC LAN Version 1.31 or higher

General Guidelines 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 adapter 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.

4. Remove the Intel driver diskette from drive A: and reboot your system.

adapter DLC driver (OC02DLC.SYS) and the TokenExpress adapter interrupt 5C arbitrator (OC01IA.SYS) files to it.

If you require NETBIOS, the INSTIBM.BAT file copies the IBM interrupt 5C arbitrator (DXMA0MOD.SYS) and the NETBIOS (DXMT0MOD.SYS) files to the \NETWORK directory instead. The TokenExpress adapter DLC driver is always used.

Special Considerations
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:

01	US English
45	Danish
49	German

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

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). This parameter is ignored if the date 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.

-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 of 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.

To configure a system having 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

Note: The PC LAN installation program requires IBM PC-DOS version 3.3 or higher. If MS-DOS 3.3 or higher is used, the PC LAN installation program may display the message "DOS is not installed on target drive". Should this happen, you can either try using an OEM version of MS-DOS or use IBM PC-DOS.

This restriction applies to installation only.

Notes for use with Qualitas' 386MAX Memory Manager The 386MAX Memory Manager program allows physical memory above 1 Meg to be mapped into the address space between the video RAM and the BIOS ROM. You can free up conventional DOS memory by loading DXMA0MOD.SYS, OC02DLC.SYS and DXMT0MOD.SYS into this area.

Additional considerations:

• The driver may not work if 386MAX is used to backfill the lower 640 Kbytes (used if your 80386 machine does not have 640K low DOS memory without the 386MAX)

• Automatic recovery of unused shadow RAM by 386MAX should be disabled when using the TokenExpress MCA adapter because the shadow RAM may not be accessible. This is done by adding the "noxram" parameter to your existing 'device = 386max.sys' statement as follows:

  device = 386max.sys noxram

• Do NOT use the option 'EMS=0' when installing 386MAX.SYS. If using 386MAX version 4.08 or higher, you may use the NOFRAME option instead.

• The 386MAX program provides an VCPI interface. The DLC drivers should work with similar products that support the VCPI standard.

This applies to:

TokenExpress™ 16/p Adapter TokenExpress™ EISA 16/4 Adapter TokenExpress™ EISA 32 Adapter TokenExpress™ MCA Adapter