Readme of Archive [FL32NT.EXE]
Windows NT 3.5x
WINDOWS* NT 3.5x INSTALLATION NOTES:
FOR THE INTEL EtherExpress(TM) FLASH 32 LAN Adapters
-------------------------------------------------------
DRIVER LOCATION
===============
\FL32MINI.SYS
\OEMSETUP.INF
GENERAL INSTALLATION
====================
1. The EtherExpress(TM) FLASH 32 adapter should be configured and tested
prior to setting it up in Windows NT. You can either configure the
adapter by using FlashSet or by using the Eisa Configuration
Utility (ECU) that came with your computer.
2. In NT, open Control Panel and click the Network icon.
3. From the Network Settings window, click "Add Adapter".
4. A list of available adapters will be displayed. Choose
" Requires disk from manufacturer". and click "Continue".
5. Insert the disk with the EtherExpress FLASH 32 LAN Adapter drivers
into drive A:, specify the path as "A:\" and click "OK"
7. From the Select OEM Option window, select "Intel Flash32 EISA
LAN Adapter [Miniport]" and click "OK".
8. A dialog box will come up with four settings:
ON: 256 FIFO: 12
OFF: 10 SLOT: x
Where x = the slot where the Flash 32 is installed
Click "OK" to accept the adapter
9. From the Network Settings window, click "OK".
NT will then perform the binding process. If any additional network
software options were installed, you may be prompted for specific
information for these packages.
10. Restart NT when prompted, in order for the changes to take affect.
Troubleshooting Tips:
======================
AT LEAST ONE DEVICE OR DRIVER FAILED DURING SYSTEM STARTUP
----------------------------------------------------------
If Windows NT fails to detect or initialize the EtherExpress FLASH 32,
you will get this error message in the Event Viewer:
"The Intel EtherExpress FLASH 32 LAN Adapter Driver service failed to
start due to the following error: A device attached to the system is
not functioning. "
Try these steps:
1. Verify that the SLOT number specified in Windows NT is correct.
You can verify which slot the EtherExpress FLASH 32 adapter is using
by running FL32DIAG.EXE from DOS and selecting "VIEW CURRENT
CONFIGURATION" from the main menu.
2. Verify that interrupt being used by the EtherExpress FLASH 32 adapter
is not being used by any other device in your workstation, including
a sound card, faxmodem, scanner, tape backup, serial port, or
parallel port. You can verify which interrupt the EtherExpress
FLASH 32 adapter is using by running FL32DIAG.EXE and selecting
"VIEW CURRENT CONFIGURATION from the main menu.
Look at the documentation or setup programs for the other installed
adapters in your computer to verify what interrupts they are using.
Some sound cards use multiple interrupts. For example, a typical sound
card will use IRQ 5 for the sound port and IRQ 11 for the
MIDI/Joystick port.
3. Verify that the EtherExpress FLASH 32 passes all diagnostic tests
by running FL32DIAG.EXE from DOS and selecting "Run Diagnostics".
If the EtherExpress FLASH 32 fails diagnostics it will not function
correctly under Windows NT.
If On-Board diagnostics fail, try setting the adapter to use a
different interrupt, or try another EISA slot.
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 is not defective. For more information
on cable specifications, view the 10BaseT or COAX ethernet cabling
readme files on the EtherExpress FLASH 32 LAN adapter Configuration
and Drivers disk.
Note: "Responder not found" is NOT an error. This message will be
displayed IF YOU ARE NOT RUNNING THE SOFTSET RESPONDER ON ANOTHER
MACHINE with an EtherExpress card or if the card cannot actually
communicate with the responder card. If you do not have a responder
running or if the two cards cannot communicate, the diagnostics
will try to send packets back to itself.
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 EtherExpress FLASH 32 LAN adapter, it may be necessary
to change the Windows NT Network setup to the default settings and reinstall
the EtherExpress FLASH 32 LAN driver. Here's how:
1. Choose the Network icon in Control Panel.
2. Highlight the Intel EtherExpress Adapter and click "Remove".
3. From the Network Settings window, click "OK".
4. Windows NT will have to reset for the changes to take effect. When
prompted, select "Restart Now".
5. Reinstall the EtherExpress FLASH 32 LAN adapter following the
installation steps above.
EtherExpress FLASH 32 driver parameters:
========================================
ON
Range: 1-65535 DEFAULT Setting: ON=256
The ON parameter limits the number of clock cycles the EtherExpress(TM)
Flash32 adapter will hold the bus for data transfers. For best performance,
this setting should be high enough for the Transmit FIFO, to be filled, or the
Receive FIFO emptied in a single bus access. The default setting for this
parameter is 10 to insure wider compatibility.
OFF
Range:1-65535 DEFAULT Setting: OFF=10
This parameter is the minimum number of clock cycles the EtherExpress Flash32
adapter card will remain off the bus between data transfers. For best performance,
this setting should be set to a minimum, thus allowing the Flash32 access as
needed.
FIFO
Range: 2-15 DEFAULT setting: FIFO=12
FIFO defines the threshold for requesting bus access. For systems with high
bus latency, this setting should be increased. For systems with very low
latency, this setting may be reduced. For best performance, this should be set
as low as possible without causing DMA over/underruns.
* Third-party trademarks are the property of their respective owners.
Return to the