Conflict with EtherLink III and hardware using I/O address 110h

The EtherLink III (3C509) adapter may experience conflicts with other hardware that uses the 100-1f0h I/O address range. After power-up, the 3C509 enters an ID_WAIT state where it waits to be "woken up" by the ID Sequence State machine. The wake up call comes when a zero is written to the hex I/O address 1y0h. "Y" is any hex value, but is 110h by default. If another piece of hardware is using the address and there is no way to change it, the adapter cannot be moved into a ready state of operation. However, with some adapter drivers, the hex value can be changed to avoid conflicts; those specifics are listed below.

Workaround Solution

Because the 3C509.EXE diagnostics program is hard-coded to use the 110h value, it is necessary to remove the conflicting device, run the diagnostics configuration program, and then re-install the other hardware in the machine before operation.

WSGEN/SHGEN-style IPX drivers: These drivers will use only 110h. Therefore, you must use the ODI driver instead.

NetWare ODI client drivers: These drivers use 110h as default, but they can be changed. To change the address, put this command in the NET.CFG file:

LINK DRIVER 3C509
ID PORT ADDRESS 1y0 (where y = 0-f)

NDIS drivers: These drivers use 110h as default, but they can be changed. To change the address, put this command in the PROTOCOL.INI file:

[ELNK3]
ID_PORT = 0x1y0 (where y = 0-f)

Note: PROTOCOL.INI syntax requires the preceding 0x as in 0x110.