3C523X.EXE V3.3 EtherDisk for ELMC/TP (8193-04)
3C523N.EXE EtherDisk, 3C523 family w/latest patches, V3.4.
LANscope.rar LAN Datascope For Ethernet [file]
Intel 82586 datasheet
3c523 Technical Reference
LAN Datascope For
J1 System Configuration Jumper
J1 allows the adapter to be enabled even though the host system's Configuration RAM contains no entry for it. The only time J1 should be moved from "A" to "B" is if the adapter has been installed in a computer that has no floppy disk drives and there as no provision for temporarily installing one to run the configuration utility on the system's reference diskette.
When the jumper is installed in position "B", the Card Enable feature of POS is overridden so that the adapter's Start ROM program can be accessed during the ROM scan that occurs during the power-up sequence. This Card Enable override is necessary when the host system's configuration RAM doesn't contain an entry for the adapter. Without the jumper, if there isn't an entry in the system's CMOS RAM for the adapter, the system will leave the adapter in the disabled state and its ROM won't be found during the ROM scan.
When using the adapter in this specialized configuration, care must be taken that no bus conflicts will occur because the adapter will be enabled before it is configured. The power-up default configuration for the adapter is as follows: I/O base address = 0300H, memory base address =0C0000H, interrupt level = 12 and the on-board transceiver will be selected.
For general operation, the jumper should be in position "A".
RECEIVE THRESHOLD, LINK BEAT, EQUALIZATION, TRANSMIT LEVEL, and DC SIGNAL jumpers, refer to Table 1.
Table 1. Jumper Settings for 10BASE-T and Non-10BASE-T Hubs
I found two of these in a 3172 Interconnect
Controller. Marked "(C) 1990 3Com" on the front.
Versions not Compatible with 486+
Symptom: they worked fine as long as they
were used in Mod. 70/80 - but when the customer swapped
them to the new bought 76/77 they went belly up and did
not even pass the DOS-based diags test.
These are older ones produced before 1990 - but ironically not all old cards are automatically affected. There was a diagnostic program available from 3COM (I think it came with the revised E/MC) which checks the microcode level and warns for possible incompatibilities. In addition some of the setup / diags and driver software had a problem with later OS-versions (did not run properly under PC-DOS 4.x and above due to "version conflict"). Whatever.
Component Differences, Old vs.
The original 3C-523 has a limitation - the later ones (3C-523B) hasn't. Roughly the two can be differed by looking on the board:
The old one will most likely not run with anything
bigger than a 386DX - the new one hasn't got this
problem. Works with 486 and Pentium. Both cards have the
same card-ID and use the same ADF, so you cannot tell
which is which by the ID only.
LAN Datascope For Ethernet
AdapterId 6042 3Com EtherLink/MC Ethernet Adapter
I/O Address Range
Packet Buffer RAM Address
The computer containing the EtherLink/MC adapter to be tested must be running DOS. If this computer is an operating server, notify all users of the server to save their work and log out from the network. The diagnostic program disrupts the normal operation of the server, and work that is not saved may be lost. The diagnostic tests do not function properly if you run them after booting your system with NetBIOS installed. Please start your computer with a standard boot diskette that does not contain a network driver.
If Group 3 tests are running while computer is connected
to an active network, intermittent packet exchange
failures may occur before the tests are done.
These failures can be avoided by running Group 3 tests
on an inactive network in which only the computer being
tested and the echo server are connected.
ELMC Fails Diagnostics
If the diagnostic tests fail, the adapter may not be defective. Check the following:
1. Make sure adapter is completely seated in
2. Inspect all cables and connections.
3. For Group 2 tests, make sure adapter is
securely connected to a loopback plug (coax version
only) or to a properly cabled inactive network.
4. For Group 3 tests, make sure adapter is
securely connected to a properly cabled inactive network
and that an echo server is set up on the network.
5. Make sure that no settings conflict with any
other peripheral or software program (such as 3Com's
Extended Memory Manager) installed in computer.
For a list of system resources commonly used by other
peripherals, select "Additional Adapter Information"
from the main menu, then "System Resources" from the
7. Running tests while connected to an active
network can cause intermittent failures. These
failures can be avoided by using an inactive network on
which only the computer being tested (and an echo server
if running the Group 3 tests) is connected.
8. For an EtherLink/MC TP adapter, check LEDs on
back-plate. Yellow (ACT) LED is on when there is
data transmission activity on adapter. This light
will go on during Group 2 and Group 3 tests. Green (LNK)
LED will be on when there is a correct connection
between adapter and hub. If link pulse jumper is
OFF, the green LED is on, connection or not.
9. If you have installed an EtherLink/MC TP
adapter, make sure that the settings for the following
jumpers are correctly configured for the hub:
10. Computer slot may be defective. Install adapter in
another slot and run tests again.
11. Computer that adapter is installed may be
defective. Install adapter in known functioning computer
and re-run tests.
12. Loopback plug may be defective. Try a
different loopback plug.
13. Replace failed adapter with known good EL/MC
adapter with same jumper settings. If second
EL/MC adapter fails, something is wrong with test
environment, not with adapter.