Network Operation
super
MOPS
pro
Copyright
JUMP
tec
Industrielle Computertechnik AG
Page: 70 of 93
TX/RX LED: The yellow LED lights briefly each time the adapter transmits or receives data. (The
yellow LED will appear to "flicker" on a typical network.)
DRIVER SIGN-ON MESSAGES
The sign-on messages reported by the driver and protocol support files when loaded can be helpful in
diagnosing problems. If possible, load the driver and support files manually, one at a time, noting the
messages displayed as they load. (If the files are loaded automatically from a batch or configuration
file, they may scroll by too fast to read.)
RESOLVING I/O-CONFLICTS
An I/O-conflict occurs when two or more adapters use the same ISA resource (I/O address, memory
address, or IRQ). You can usually detect an I/O conflict in one of four ways after installing and or
configuring the CS8900-based adapter:
1) The system does not boot properly (or at all).
2) The driver cannot communicate with the adapter, reporting an "Adapter not found" error message.
3) You cannot connect to the network or the driver will not load.
4) If you have configured the adapter to run in memory mode but the driver reports it is using I/O-
mode when loading, this is an indication of a memory address conflict.
Another common source of install problems is conflicts between EMM386 and the RAM and ROM
areas assigned to the adapter. Please ensure that you exclude the area (RAM and ROM) used by the
adapter from use by EMM386.
If an I/O-conflict occurs, run the CS8900 Setup Utility and perform a diagnostic self-test. Normally,
the ISA resource in conflict will fail the self-test. If so, reconfigure the adapter selecting another
choice for the resource in conflict.Run the diagnostics again to check for further I/O conflicts.