|Windows for Workgroups 3.11 Installation|
Contents of MSWFW311.TXT
Location of Driver: \WFW\EPRO.38_
Novell NetWare* files may be required
Before you start
- If you install Novell* NetWare* support on this workstation, you need
these Novell NetWare* files:
NETWARE.DRV, NETWARE.HLP, NWPOPUP.EXE, VIPX.386, VNETWARE.386
These files are not on the Intel® Configuration and Drivers disk. To
obtain these files, do one of the following:
- Download the self-extracting file WINDR2.EXE from the Novell NetWire*
forum on CompuServe* or Novell's FTP server on the Internet
- Call Novell* (1-800-NETWARE) to have the files sent to you.
- Contact a Novell NetWare* dealer in your area.
- To install proper driver support for Windows for Workgroups and
Novell NetWare* on the same workstation, you must set up the workstation
for NetWare* first using the DOS ODI client.
SoftSet2 can install the DOS ODI network driver for you. However, you
may need to alter your CONFIG.SYS, AUTOEXEC.BAT, and NET.CFG files so
they comply with your network.
- After logging into your NetWare* file server, start Windows* for
Workgroups, then run Network Setup.
You must configure and test the PRO/10 adapter with SOFTSET2.EXE before
adding the adapter to Network Setup in Windows* for Workgroups. You must
boot the workstation to DOS, then insert the Intel Configuration and
Drivers disk into drive A. At the DOS prompt type
1. Select "Automatic Setup" and let SoftSet2 configure the
EtherExpress PRO/10 adapter to work in your computer. Select "Change
Adapter Configuration" if you want to specify which interrupt and I/O
address the EtherExpress PRO/10 adapter will use.
When SoftSet2 asks for a network frame type, select the frame type
appropriate for your LAN. If you want to add extra frame types, do so in
your NET.CFG file.
Select "Test Adapter" from the main menu to test the configuration
you have selected. If the EtherExpress PRO/10 adapter fails diagnostics,
it may not function correctly under Windows for Workgroups.
NOTE: SoftSet2 is a DOS program and will not run in Windows for
Workgroups. You must run SoftSet2 from DOS. If Windows for Workgroups
loads automatically on your computer, you can boot to DOS by inserting a
DOS boot disk into your floppy disk drive A when rebooting,
or you can exit Windows for Workgroups to get back to DOS.
Hints and Tips
- Start Windows for Workgroups (WFW) with the /N parameter. This starts
WFW without starting any of the networking software. At the DOS prompt,
- Select the "Network Setup" icon in the Network Group.
- Click the "Networks" button. Select "Install Microsoft Windows
Network" and click "OK".
<Optional> To add Novell NetWare* support to this workstation, click
"Other," then select "Novell NetWare Shell 3.x" if you're using NETX, or
select "Novell NetWare Shell 4.x" if you're using VLMs. Click "OK".
<Optional> To share files and printers on this workstation, click the
"Sharing" button, then click "OK".
- Click the "Drivers" button.
- Click the "Add Adapter" button. Select "Unlisted or Updated Network
Adapter" and click "OK".
- Insert the Intel Configuration and Drivers disk into a drive and for
the path, type:
- Select "Intel EtherExpress PRO/10" adapter from the list and
- Specify the Interrupt, Base I/O port, and Transceiver type settings.
If you're not sure what they should be, make a selection here and after
WFW installation is complete, run SoftSet2 to make sure they are
correct. If you are using the AUI connector, select the AUI/DIX option
for Transceiver type.
Note: If you load Novell NetWare* ODI drivers, these settings are
assigned automatically for you.
- In the Network Drivers window, click "Close".
- In the Network Setup window, click "OK".
- In the Microsoft* Windows* Network Names window, enter a unique User
Name, the name of your new or existing Workgroup, and a unique Computer
Name for your workstation, then click "OK".
- Choose "Yes To All" when WFW asks if you want to replace the files
currently installed with the versions you are installing now.
- Insert the WFW disks when WFW asks for the driver update files. If
prompted for the NetWare files, insert the Novell* disk containing the
drivers from the Novell* file WINDR2.EXE. If prompted for the path of
EPRO.386, insert the Configuration and Drivers disk into a drive and for
the path, type
If prompted for the path of EPRO.DOS, insert the EtherExpress PRO/10
Configuration and Drivers disk in drive A and type
- When finished updating the files, WFW reports that it modified
several files. Click on "OK".
WFW changes your last drive to P. You may change this setting in your
WFW also alters your NET.CFG file. Check this file to make sure your
frame types load in the correct order for your network.
- When WFW prompts you to restart your computer for the changes to take
effect, click on "Restart Computer".
Remember to log into your NetWare server before starting WFW.
Windows for Workgroups won't load or locks up
- Error 58: While Loading Protocol Number 0...
If WFW fails to detect or initialize the EtherExpress PRO/10 adapter,
you 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 that the I/O address and interrupt used by the EtherExpress
PRO/10 adapter are not used by any other device (like sound cards,
faxmodems, serial ports, parallel ports, etc.) in your computer.
Look at the documentation or run the setup programs for the other
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, an I/O address of 330 and IRQ 11 for
the CD-ROM, and IRQ 2/9 for the MIDI/Joystick port.
- Verify that the EtherExpress PRO/10 adapter passes all diagnostic
tests by running SOFTSET2.EXE from DOS and selecting "Test Adapter". If
the EtherExpress PRO/10 adapter fails diagnostics, it will not function
correctly under Windows for Workgroups.
If On-Board diagnostics fail, try setting the EtherExpress PRO/10
adapter to a different I/O address, a different interrupt, or change
Force 8 bit operation to "Yes".
If On-Network diagnostics fail, there is likely a cable, connector, or
hub problem. Verify that the cabling you are using is connected properly
and that the cable isn't defective. For more information on cable
specifications, view the TPE or BNC Cabling Specification readme files
on the Configuration and Drivers disk.
Note: "Responder not found" is NOT an error. This message will be
displayed IF YOU ARE NOT RUNNING THE SOFTSET2 RESPONDER ON ANOTHER
MACHINE with an EtherExpress card or if the card cannot actually
communicate with the responder card. If you don't have a responder
running, or if the two cards can't communicate, the diagnostic will try
to send packets back to itself.
- If you use 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 unable 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 "EPROODI". When this error occurs,
you will need to manually edit the NET.CFG and PROTOCOL.INI that Windows
for Workgroups created to replace all instances of "XXXX" with
Here are the entries that need to be changed: In the PROTOCOL.INI,
under the section heading [net.cfg], verify the path specified for your
NET.CFG is correct. In the PROTOCOL.INI, change the section heading
[Link Driver XXXX] to [Link Driver EPROODI].
In the PROTOCOL.INI, under the section heading [NWLINK] change both
occurrences of "BINDINGS=XXXX" to "BINDINGS=EPROODI".
In the NET.CFG, change "Link Driver XXXX" to "Link Driver EPROODI"
After installing the EtherExpress PRO/10 adapter, if WFW won't load or
locks up, make sure the I/O address and interrupt used by the
EtherExpress PRO/10 adapter are not used by any other device (like sound
cards, faxmodems, serial ports, parallel ports, etc.) in your computer.
If you are using the BNC (coax) connector, you must have a terminated
cable attached to the EtherExpress PRO/10 adapter when you start Windows
for Workgroups. If you don't, Windows for Workgroups may hang.
Adapter passes diagnostics but still does not work with WFW
If the adapter passes diagnostics but still doesn't 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
EtherExpress PRO/10 adapter, you may need to restore the PROTOCOL.INI
file to its default settings and reinstall the EtherExpress PRO/10
adapter driver. Here's how:
Can't see other workstations
- Start WFW with the /N parameter. At the DOS prompt type
- Click 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 3 of the "General
Installation" section of this document.
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
- From the Control Panel, click 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 on "Log On."
This can also be a cable, connector, or hub problem. Verify that the
cabling you are using is connected properly and is not defective. Also,
try running diagnostics on the adapter\cabling by selecting "Run
Diagnostics on Network" in SoftSet2.
Windows for Workgroups creates the PROTOCOL.INI for you. This is
provided for reference. This is a sample with Microsoft NetBEUI and
IPX/SPX Compatible Transport with NetBIOS.
This applies to:
|End of Interactive Support Disclaimer
Intel will not provide future software updates to support new operating systems or improve compatibility with third-party devices and software products.
Solution ID: CS-010538|
Last Modified: 07-Oct-2013
Date Created: 15-Apr-2004