|
This installation document applies to the TokenExpress™ 16/p Adapter software release v7.0 which is available in the archive TE16DISK.EXE.
| Location of Driver: |
\WFW\TE16.38_ |
|
\WFW\OEMSETUP.INF | General Installation
1. Select the "Network Setup" icon in the Network Group.
2. If you are replacing a previous LAN adapter select the Remove button to delete that adapter.
3. Click on the Add Adapter button.
4. Choose Unlisted or Updated Network Adapter.
5. Insert the TokenExpress 16/p LAN Adapter Driver Diskette in drive "A" and specify the path A:\WFW for the location of the driver.
6. Select the Intel® TokenExpress™ 16 adapter.
All the basic options are set automatically for the TokenExpress 16. By default, the driver will search for an adapter at all supported I/O addresses. If you need to change this, or you want to review the settings, do the following:
7. Close, and when prompted, restart your computer so that changes take effect.
Hints And Tips
ERROR 58 WHILE LOADING PROTOCOL NUMBER 0...
If WFW fails to detect or initialize the TokenExpress adapter, you will get this error message when starting WFW:
THE FOLLOWING ERRORS OCCURRED WHILE LOADING PROTOCOL NUMBER 0:
ERROR 58: THE NETWORK HAS RESPONDED INCORRECTLY. YOU MAY NEED TO RECONFIGURE THE PROTOCOL USING NETWORK SETUP.
Try these steps:
- Verify the address selected in step 6 of the installation notes matches the I/O address being used by the TokenExpress 16 adapter.
- Verify that the I/O address and/or Interrupt being used by the TokenExpress adapter is 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. 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.
- Verify that the TokenExpress adapter passes all diagnostic tests by booting to DOS, running TE16DIAG.EXE, then selecting "TEST ADAPTER." If the TokenExpress adapter fails diagnostics it will not function correctly under Windows* for Workgroups.
- If diagnostics fail, try setting the TokenExpress adapter to use a different I/O address or a different Interrupt Also, verify that the cable is not defective and the ring speed you selected is correct.
WIndows* For Workgroups Won't Load Or Locks Up
After installing the TokenExpress™ adapter, if WFW won't load or locks up, make sure the I/O address and the Interrupt used by the TokenExpress adapter are not occupied by any other device (like sound cards, faxmodems, serial ports, parallel ports, etc.) in your workstation.
Adapter Passes Diagnostics But Still Does Not Work With WFW
If the adapter passes diagnostics but still does not work with WFW, there could be a problem with the PROTOCOL.INI file. If you've made several attempts to configure WFW or had another adapter installed before the TokenExpress adapter, it may be necessary to restore the PROTOCOL.INI file to its default settings and reinstall the TokenExpress adapter driver. Here's how:
- Start WFW with the /N parameter. At the DOS prompt type:
- C:\WINDOWS\WIN /N
- Select the "Network Setup" icon in the Network group.
- Click the "Networks" button. Select "No Windows Support For Networks" and click "OK."
- In the Network Setup window, click "OK."
- When WFW reports that it modified several files, click "OK."
- When WFW prompts you to reset your computer for the changes to take effect, click "Restart Computer."
After the workstation reboots, continue at step 1 of the "GENERAL INSTALLATION" section of this document.
Can't See Any Other Workstations
If Windows for Workgroups loads without error messages but you can't see any other computers on your network, verify that the name of the workgroup is correct and that you are logged on to the network. Here's how:
- Select the "CONTROL PANEL" icon.
- Select the "Network" icon.
- Verify the workgroup name on your computer is the same as the workgroup name on a working computer.
- If your Logon Status is "Not logged on," click "LOG ON."
This problem can also be caused by a problem with the cable, connectors, or hub. Verify that the cabling you are using is connected properly and that the cable is not defective.
Using Novell NetWare*
If you are using Novell NetWare*, and Windows for Workgroups fails to detect that the ODI drivers are loaded while running Network Setup, you will get this error message when starting Windows for Workgroups:
Because Windows* for Workgroups was not able to detect which ODI driver was loaded, it will add the variable "XXXX" to the NET.CFG and PROTOCOL.INI files where it should have specified "TE16ODI."
When this error occurs, you will need to manually edit the NET.CFG and PROTOCOL.INI files and replace all instances of "XXXX" with "TE16ODI". Here are the entries that need to be changed:
In PROTOCOL.INI, under the section heading [net.cfg], verify the path specified for your NET.CFG is correct.
In PROTOCOL.INI, change the section heading [Link Driver XXXX] to [Link Driver TE16ODI].
In PROTOCOL.INI, under the section heading [NWLINK], change both occurrences of "BINDINGS=XXXX" to "BINDINGS=TE16ODI."
In the NET.CFG, change "Link Driver XXXX" to "Link Driver TE16ODI."
This applies to:
| 
