![[Intel Navigation Header]](/CONTENT/PIX/1/HEADER.GIF)
TokenExpress(TM) Adapter: Troubleshooting Notes from Tech Support
Contents:
TO GET THE LATEST SOFTWARE FOR YOUR TOKENEXPRESS ADAPTER
Document # 6264.00
For the latest software for all ISA, MCA, and EISA 16/4 TokenExpress
adapters download the files TE16DSK1.EXE and TE16DSK2.EXE, for the
latest released software for the TokenExpress EISA/32 adapter, download
the files TE32DSK1.EXE and TE32DSK2.EXE from Intel's online services.
TE16DLC.EXE
DOS DLC Drivers (V1.58) for TokenExpress(TM) 16/4 adapters.
OC02DLC.SYS (v1.58) OC01IA.SYS (v1.09a) These drivers should be used in
place of previous versions if problems with loosing connections to LAN
Servers have been observed. See enclosed TEDLC.TXT for more
installation notes.
TE16RPL.EXE
Abstract:
TokenExpress(TM) adapter REMOTE BOOT RPL UPDATE V1.29 for TokenExpress
ISA 16/s, MCA and EISA 16/4 using BOOT8500 Universal Boot ROM.
TE16DSK1.EXE
Abstract:
TokenExpress(TM) Release 6 Driver Disk which includes TokenSet and
Novell drivers for the TokenExpress 16, TokenExpress MCA, and
TokenExpress EISA 16/4.
TE16DSK2.EXE
Abstract:
TokenExpress(TM) Release 6 Driver Disk which includes IBM and Microsoft
drivers for the TokenExpress 16, TokenExpress MCA, and TokenExpress EISA
16/4.
USING LOCALLY ADMINISTERED ADDRESSES (LAA) WITH THE TOKENEXPRESS CARD
For IBM:
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 NetWare:
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
NetWare 3.11 Server:
To use LAA at a NetWare 3.11 file server, you need to add the
NODE= option in the LOAD line for the driver.
Example LOAD line:
LOAD OCTOK161 PORT=A20 INT=5 DMA=5 NAME=LANA NODE=12345678
Note: The NODE= option has 8 digits after it. Locally
administered node adresses are 12 digits. NetWare 3.11
automatically inserts the first 4 digits (4000) before the 8
digits in the NODE= option.
If you are using an NDIS driver and change the I/O address of your
adapter with TOKENSET, you will need to add an "Adapter Number =" entry
to your PROTOCOL.INI file. Use the adapter number from the list below
that matches the setting you've selected in TOKENSET.
<AdapterNumber> identifies the I/O address of the adapter:
0 = I/O address 0A20H
1 = I/O address 0A24H
2 = I/O address 0A50H
3 = I/O address 0A54H
4 = I/O address 1A20H*
5 = I/O address 1A24H*
6 = I/O address 1A50H*
7 = I/O address 1A54H*
*addresses available only with the EISA/32 adapter
<NodeAddress> is the locally administered address, a 12-digit
hexadecimal number starting with 4, 5, 6 or 7. We recommend using
4000 as the first four digits.
For Lan Manager:
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:
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 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.
CONNECTING TO A NETWARE SERVER AND AN IBM HOST FROM A DOS WORKSTATION
When using the TokenExpress card in an IBM environment the following
drivers will need to be loaded:
* OC01IA.SYS (Interrupt arbitrator)
OC02DLC.SYS (DLC driver)
Insert the following lines in the CONFIG.SYS file:
DEVICE=<path>\OC01IA.SYS
DEVICE=<path>\OC02DLC.SYS
These drivers above replace the IBM files DXMA0MOD.SYS and DXMC0MOD.SYS.
When generating IPX.COM using the Novell program SHGEN or WSGEN, choose
the option "LAN Support Program" to get a shell with a DLC interface.
Use 3.10 version of IPX/SPX, previous versions do not work.
Insert the following lines in the AUTOEXEC.BAT file to attach to a
Novell server:
For IPX driver: For ODI driver:
IPX LSL
NETX LANSUP
IPXODI
NETX
LANSUP.COM is available with the IBM LAN Support Program and also
available from Novell's Netwire library on CompuServe in the archive
VLMUPx.EXE.
CONNECTING TO A NETWARE SERVER AND AN AS400 FROM A DOS WORKSTATION
When using the TokenExpress card in an IBM environment, along with
IPX.COM or other required ODI drivers, the following drivers will need
to be loaded:
* OC01IA.SYS (Interrupt arbitrator)
* OC02DLC.SYS (DLC driver)
Insert the following lines in the CONFIG.SYS file:
DEVICE=<path>\OC01IA.SYS
DEVICE=<path>\OC02DLC.SYS
These drivers above replace the IBM files DXMA0MOD.SYS and DXMC0MOD.SYS.
When generating IPX.COM using the Novell program SHGEN or WSGEN, choose
the option "LAN Support Program" to get a shell with a DLC interface.
Use IPX/SPX version 3.10, previous versions do not work.
Insert the following lines in the AUTOEXEC.BAT file:
For IPX driver: For ODI driver:
-------------- --------------
IPX LSL
NETX LANSUP
STARTPCS IPXODI
NETX
STARTPCS
If you are using the ODI drivers, insert the following lines in the
NET.CFG for the ODI configuration:
NET.CFG
Link Support
Buffers 4 4216
MemPool 4096
Link Driver LANSUP
Frame TOKEN-RING
Frame TOKEN-RING_SNAP
The NET.CFG file must be in the same directory as LANSUP.COM and LSL.COM
files.
The files LSL.COM, IPX.COM, IPXODI.COM, and NETX.COM are found on the
NetWare workstation diskettes. You can obtain the latest version of the
ODI drivers from Novell's NetWire on CompuServe.
LANSUP.COM is available with the IBM LAN Support Program.
CONNECTING TO A NETWARE SERVER AND AN IBM OS/2 LAN SERVER FROM A DOS ODI WORKSTATION
When using the TokenExpress card in an IBM environment the following
drivers will need to be loaded:
* OC01IA.SYS (Interrupt arbitrator)
* OC02DLC.SYS (DLC driver)
Insert the following lines in the CONFIG.SYS file:
DEVICE=<path>\OC01IA.SYS
DEVICE=<path>\OC02DLC.SYS
These drivers above replace the IBM files DXMA0MOD.SYS and DXMC0MOD.SYS.
When generating IPX.COM using the Novell program SHGEN or WSGEN, choose
the option "LAN Support Program" to get a shell with a DLC interface.
Use 3.10 version of IPX/SPX, previous versions do not work.
Insert the following lines in the AUTOEXEC.BAT file:
LSL
LANSUP
IPXODI
NETX
Insert the following lines in the NET.CFG
Link Support
Buffers 4 4216
MemPool 4096
Link Driver LANSUP
Frame TOKEN-RING
Frame TOKEN-RING_SNAP
The NET.CFG file must be in the same directory as LSL.COM and LANSUP.COM
files.
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's NetWire on CompuServe. LANSUP.COM is available
with the IBM LAN Support Program.
ERROR RECEIVED WHEN LOADING THE TOKENEXPRESS(TM) DRIVER SHIPPED WITH WINDOWS FOR WORKGROUPS
The TokenExpress(TM) driver shipping with Windows for Workgroups 3.11
may not be the current driver. The driver provided on the Intel driver
diskette is the most current. To install the driver from the Intel
driver diskette, follow the instructions below.
If Windows for Workgroups is already installed:
1. From the Network group, choose the Network Setup icon.
2. Choose Drivers.
3. Highlight the TokenExpress driver, then choose Remove.
4. Choose Add Adapter.
5. Choose Unlisted or Updated Network Adapter. When prompted, insert
the Intel driver diskette #2 into drive A and type the following
command:
A:\ <enter>
You will now see the configuration settings for the adapter.
6. Change the configuration settings, if needed, then choose OK to
accept the configuration.
If you are installing Windows for Workgroups for the first time:
1. Follow the steps covered in the Windows for Workgroups guide for a
first-time installation. During the installation when you are
asked to select an adapter, choose Select Other Adapter Not Listed.
When prompted, insert the Intel driver diskette into the A drive
and type the following command:
A:\ <enter>
You will now see the configuration settings for the adapter.
2. Change the configuration settings if needed, then choose OK to
accept the configuration.
CREATING MULTIPLE SAPS FOR THE TOKENEXPRESS 16 ADAPTER
Note: This information was reported by a customer and not
necessarily tested by Intel.
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
Note: Replace "(path)" with the complete path to the directory
containing the TokenExpress 16 drivers.
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.
Trademark information