• Where do I get the latest drivers for the TokenExpress™ LAN adapter?
  
  
• How do I identify which TokenExpress™ adapter I have?
  
  
• Will TokenSet detect all available I/O Addresses and IRQs?
  
  
• How do I get a Return Material Authorization (RMA) for a defective product?
  
  

TokenExpress™ 16 LAN Adapters

• How do I configure the TokenExpress 16 adapter for multiple SAPs?
  
  
• How do I connect to a Novell NetWare* file server and an IBM Host from a DOS/Windows* workstation?
  
  
• How do I configure a Locally Administered Address using the TokenExpress 16 LAN adapter?
  
  

TokenExpress™ PRO LAN Adapters

• How do I configure a Locally Administered Address for OS/2?
  
  
• How do I configure a Locally Administered Address for Windows for Workgroups?
  
  
• Why does Tokenset indicate that all addresses are used when I try to change the Flash Chip memory address?
  
  
• How do I install FlashVirusProtect from the FlashWorks disk?
  
  
• Can I use the TokenExpress PRO adapter to remote boot to Novell NetWare (ODI) or Microsoft Windows NT* (NDIS) file servers?
  
  

Q1. Where do I get the latest drivers for the TokenExpress™ LAN adapter?
A1. You can download the latest TokenExpress adapter drivers from Intel's Customer Support web site at support.intel.com.

Q2. How do I identify which TokenExpress™ adapter I have?
A2. Check the Network Adapter & Driver Identification Guide for the TokenExpress Family.

Q3. Will TokenSet detect all available I/O Addresses and IRQs?
A3. TokenSet can reliably detect most IRQs used in a computer. The best way to avoid IRQ conflicts is to load the device drivers for all other adapters before running TokenSet. If you still have problems with the computer after installing the adapter, make sure no other device uses the same IRQ as your TokenExpress PRO adapter.

Q4. How do I get a Return Material Authorization (RMA) for a defective product?
A4. Call Intel Customer Support at 1-916-377-7000. We will exchange the defective product if it is within the warranty period. You may be asked to provide proof of purchase, so please have it available.

TokenExpress™ 16 LAN Adapters

Q1. How do I configure the TokenExpress 16 adapter for multiple SAPs?
A1. IBM LAN Support Program users can create multiples SAPs (Service Access Points) for the TokenExpress 16 adapters using the DLC drivers. Here are the commands 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
DEVICE=C:\(path)\DXMT0MOD.SYS ES=3 EST=3 CF=Y

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.

Q2. How do I connect to a Novell NetWare* file server and an IBM Host from a DOS/Windows workstation?
A2. Insert the following lines in the CONFIG.SYS file:

DEVICE=\OC01IA.SYS
DEVICE=\OC02DLC.SYS

Insert the following lines in the AUTOEXEC.BAT file:

LSL
LANSUP
IPXODI
VLM

Link Support
        Buffers 4 4216
        MemPool 4096

Link Driver LANSUP
        Frame TOKEN-RING
        Frame TOKEN-RING_SNAP

The files LSL.COM, IPXODI.COM, and NETX.COM are available from the NetWare Workstation diskettes. You can obtain the latest version of the ODI drivers from Novell ^†. LANSUP.COM is available with the IBM LAN Support Program.

Q3. How do I configure a Locally Administered Address using the TokenExpress™ 16 LAN adapter?
A3. For DOS ODI workstation driver:

The ODI driver must be configured for LAA by modifying the NET.CFG file. Add the following statement to the link drivers section of the NET.CFG file:

NODE ADDRESS <NodeAdress>

Example:
NODE ADDRESS 400000000012

The NDIS driver must be configured for LAA by modifying the PROTOCOL.INI file. Add the following statement to the TokenExpress NIC section of the

NODEADDRESS="<NodeAddress>"

(Note the use of quotes and no spaces!!)

Example:
NODEADDRESS="400000000012"

For IBM OS/2 2.x and/or LAN Server 2.x:

The NDIS driver must be configured for LAA by modifying the PROTOCOL.INI file. Add the following statement to the TokenExpress NIC section of the PROTOCOL.INI file:

NETADDRESS="<NodeAddress>"

(Note the use of quotes and no spaces!!)

Example:
NETADDRESS="400000000012"

For IBM DLC:

The DLC driver must be configured for the LAA by modifying the CONFIG.SYS file. Valid choices for <AdapterNumber> in this configuration are 0 and 1. Add the following statement to the CONFIG.SYS file:

DEVICE=<path>\OC02DLC.SYS -N<AdapterNumber><NodeAddress>

Example:
Device=C:\OC02DLC.SYS -N0400000000012

For Windows* for Workgroups (v3.11):

1. From the Program Manager, choose the Network Setup icon.

2. Choose Drivers, then Setup.

3. Select Net Address, then click on the button to the left of the Value: field.

4. Type the local address in the Value: field. Include quotation marks around the address. For example:
   "400000000012"

5. Choose Set, then OK.

6. Exit the Network Setup dialog boxes. Network Setup modifies the PROTOCOL.INI file and prompts you to restart the computer.

TokenExpress™ PRO LAN Adapters

Q1. How do I configure a Locally Administered Address for OS/2?
A1. If you use LAPS to configure your adapter, don't set your locally administered address in LAPS. Instead, add the following line under the [tproeos2_nif] section in your PROTOCOL.INI file:

NODEADDRESS="400000000012"

Where 400000000012 is an example of a 12-digit locally administered address.

Note: If you configure your locally administered address during LAPS, you need to delete the NETADDRESS= lines in the protocol sections of your PROTOCOL.INI file. You'll also need to add the NODEADDRESS= line to the [tproeos2_nif] section.

Q2. How do I configure a Locally Administered Address for Windows* for Workgroups?
A2. If you want to set a locally administered address, add the following line under the [tpro] section in your PROTOCOL.INI file:

NODEADDRESS="400000000012"

Where 400000000012 is an example of a 12-digit locally administered address.

Q3. Why does Tokenset indicate that all addresses are used when I try to change the Flash Chip memory address?
A3. When a memory manager like EMM386 is running, TokenSet indicates that all memory addresses (except D000) are used, even if they are free. To change the flash chip address, follow these steps:

1. Temporarily disable the memory manager. For example, add a REM statement to the start of the memory manager command in your CONFIG.SYS file. Then reboot.

2. Run TokenSet and select a flash chip address. Note the address.

3. Exclude the memory range that the flash chip uses and re-enable the memory manager.

Q4. How do I install FlashVirusProtect from the FlashWorks disk?
A4. You can install FlashVirusProtect on any workstation containing a TokenExpress PRO adapter. Here's how:

1. Put a copy of the FlashWorks disk into a drive, switch to that drive and at the DOS prompt, type "SETUPFVP".

   The batch file decompresses files from the diskette and copies them to C:\VPROTECT.PC. It then starts the FlashVirusProtect configuration program.

2. Specify the configuration you want (see the FlashWorks Installation and User's Guide for details) and press F10.

3. Choose Yes to download the configuration to the flash adapter.

Q5. Can I use the TokenExpress™ PRO adapter to remote boot to Novell NetWare* (ODI) or Microsoft Windows* NT (NDIS) file servers?
A5. With our current release, the only Remote Program Load (RPL) supported is NetWare ODI. TokenSet's Remote boot program screen still lists other options, but NDIS remote boot is not supported.

This applies to:

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