|
Before You Start
You must configure and test the TokenExpress™ EISA LAN Adapter before setting
up the network driver in Windows NT*. Run the EISA Configuration Utility (ECU)
for your computer and assign an I/O base address, interrupt (IRQ), and select the
connector type (STP or UTP) to be used by the TokenExpress™ EISA 32 Adapter.
Write this configuration down because NT 4.0 installation will request the
TokenExpress Adapter I/O base address when adding the TokenExpress driver.
The next step is to run diagnostics on the TokenExpress Adapter.
You must boot the workstation with DOS, and then insert the TokenExpress
LAN Adapter Configuration disk into drive A:, at the DOS prompt type
A:DIAG
Select Run Diagnostics from the main menu to test the configuration
you have selected. If the TokenExpress™ LAN Adapter fails diagnostics it
may not function correctly under Windows NT*.
General Installation
- In Windows NT, double click the My Computer icon.
- In My Computer, double click the Control Panel icon
- In Control Panel, double click the Network icon.
- Select the Adapters tab and click Add.
- A list of available adapters will be displayed, select:
- Intel TokenExpress™ Server Adapter
- Specify the following options and click OK:
- I/O Base Address: xxxx-xxxx,xxxx-xxxx
- Bus Number: 0
- Early Token Release: Yes
- Full Transmit Status: Yes
- Network Address: (leave blank unless using LAA)
Where: xxxx-xxxx,xxxx-xxxx is the Base I/O address assigned to the TokenExpress EISA Adapter by your EISA Configuration Utility (ECU).
NOTE: See detailed information below for explanation of these options.
- From the Network window, select the Identification tab.
- Specify a unique Computer Name, then specify the name of the
Workgroup or Domain that you belong to. Select Close.
- Windows NT* will perform the binding process. If any additional network
software options were installed, you may be prompted for specific
information about settings for those protocols.
- When prompted to restart your computer in order for the changes to
take effect, select Yes.
Troubleshooting Tips:
At least one device or driver failed during system startup
If Windows NT* fails to detect or initialize the TokenExpress LAN
Adapter, you will get this error message in the Event Viewer:
?The Intel TokenExpress™ Server Adapter Driver service failed to
start due to the
following error: A device attached to the system is
not functioning.?
Try these steps:
- Verify that the I/O address and Interrupt used by the TokenExpress
Adapter are not being used by any other device in your workstation like
a sound card, faxmodem, scanner, tape backup, serial ports, parallel
ports, etc. Look at the documentation or setup programs for the other
installed adapters in your computer to verify which I/O address and
Interrupts they are using. Some sound cards use multiple interrupts
and I/O addresses. For example, a typical sound card will use an I/O
address of 220 and IRQ 5 for the sound port and an I/O address of 330
and IRQ 11 for the MIDI/Joystick port. Many adapters decode the Axx I/O
address range as 2xx; this may cause a conflict where you didn't expect
one. For example, a sound card using an I/O address of 220 would be in
conflict with the TokenExpress Adapter using A20.
- Verify that the TokenExpress Adapter passes all diagnostic tests
by running DIAG.BAT. If the TokenExpress Adapter fails
diagnostics it will not function correctly under Windows NT.
If diagnostics fail, try setting the TokenExpress Adapter
to a different interrupt, I/O address, or DMA setting.
Adapter passes diagnostics but still does not work with Windows NT*
If the adapter passes diagnostics but still does not work with Windows
NT, there could be a problem with your NT network configuration. If
you've made several attempts to configure Windows NT or had another
adapter installed before the TokenExpress Adapter, it may be necessary
to change the Windows NT Network setup to the default settings and
reinstall the TokenExpress LAN Adapter driver. Here's how:
- Choose the Network icon in Control Panel, select the Adapters tab.
- Highlight the Intel TokenExpress Server Adapter and click Remove.
- From the Network Settings window, click OK.
- Windows NT will have to reset for the changes to take effect. When
prompted, select Yes.
- Reinstall the TokenExpress Adapter driver following the General
Installation steps above.
TokenExpress Adapter Advanced Options:
I/O Base Address:
default = 0a18-0a23,0a30-0a3f
Select the I/O Base address assigned to the TokenExpress EISA 32 Adapter by
your EISA Configuration Utility. It must match the adapter I/O settings on
the installed TokenExpress Adapter.
Bus Number:
default = 0
Identifies the bus that the adapter has been installed in. 0 = single
bus.
Early Token Release:
default = YES
Enables or disables early token release. YES = enable, NO = disable.
(Default = NO). This is only available when running at 16 Mbps.
Full Transmit Status:
default = NO
Specifies whether transmit notification occurs. When set to YES, the
upper layer drivers are notified of the status of transmitted frames, if
the station received the frame and if it was able to copy the frame. If
there is a bridge/router on your network or you're having network
problems, set this value to ?Yes.?
If set to NO, no transmit notification occurs. All upper layer drivers
will assume that transmitted frames are successfully received and copied
by other stations.
Network Address:
default = (blank)
Specifies the Locally Administered Address (LAA) which replaces the TokenExpress
Adapters burned-in address. The new address must be locally administered using a 12
digit hexadecimal format. For example, ?400012345678.?
This applies to:
| 
