FAQs: EtherLink III PCMCIA/PC Card (3C589)

Where can I find drivers for my Etherlink III PCMCIA adapter?

What drivers can I find on the 3c589 Etherdisk?

I have a 3C589B adapter and need to get Windows NT drivers. Where are they located on your EtherDisk?

Where do I get SCO Unix drivers?

I need a promiscuous mode driver for the Etherlink III to use with Novell's Lanalyzer product. Where can I obtain such a driver?

My 3C589 PCMCIA card is not seen by my Laptop?

I'm using the 3C589 in my notebook computer and I keep getting an "adapter not found" error message.

I am trying to load my Netware ODI driver on my IBM ThinkPad 755CE and I am getting "Initialization Failed" messages. What am I doing wrong?

How do I install my PCMCIA adapter into Windows for Workgroups?

I'm using an NDIS driver and I get the following message when booting my notebook computer: "Can't configure card through Card Services, but could be forced with pcmcia_enabler=yes/no in protocol.ini." What's wrong?

Q: Where can I find drivers for my Etherlink III PCMCIA adapter?

A: 3Com adapters ship with many popular drivers. In the event that you did not receive a driver diskette (EtherDisk), equivalent diskettes can be downloaded from 3Com's BBS located at 408-980-8204 or 3Com's FTP site. The EtherDisk for the Etherlink III PCMCIA adapter is contained in a file called 3C589X.EXE.* This file is self extracting and is the current equivalent to the shipping EtherDisk.

To extract the files after downloading, place a newly formatted 3.5" (1.44MB) floppy diskette in your A: drive, locate the newly downloaded file on your hard drive and execute the following command: 3C589X A:

* There is a newer file available which contains the latest patches and fixes for this adapter. The file name is 3C589N.EXE.

Although this is not the shipping version, it contains the latest upgrades and fixes that may resolve some issues which the shipping drivers are unable to resolve. The drivers on this diskette are drivers that have been submitted to the various agencies awaiting certification. 3Com writes drivers to specifications set by the major software vendors and the drivers found in 3C589N.EXE have been tested and are reliable. We recommend that you download this version of the EtherDisk since it will always contain the latest files.

Q: What drivers can I find on the 3c589 Etherdisk?

A: Drivers are available for the following: Netware client, Netware server (v 3.11, 3.12, 4.0x), NDIS, packet driver, WFW3.11 and OS/2. Drivers and any readme files are located in their respective subdirectories on the EtherDisk

Q: I have a 3C589B adapter and need to get Windows NT drivers. Where are they located on your EtherDisk?

A: 3Com does not write NT drivers for the Etherlink III PCMCIA adapter. The drivers are bundled with Windows NT 3.51 and come from Microsoft. Versions of NT prior to 3.51 do not provide support for PCMCIA adapters. NT version 3.51 only supports PCMCIA adapters in point enable mode. Card and Socket services are not currently available with NT.

Q: Where do I get SCO Unix drivers?

A: SCO UNIX drivers are available for 3c509, 3c509B, 3c529, 3c579, 3c589 and 3c589B. The drivers may be downloaded from the BBS at 408-980-8204 or 3Com's FTP site. The filename to download is 5X9SCO.EXE. This file is self extracting and includes the SCO driver and installation instructions.

Q: I need a promiscuous mode driver for the Etherlink III to use with Novell's Lanalyzer product. Where can I obtain such a driver?

A: Although the Etherlink III ODI MLID driver is promiscous, the adapter will not report bad packets. The Parallel Tasking technology incorporated into the adapter increases performance by discarding any bad or illegal packets. This allows the protocol stack to only interface with valid packets. Since this filtering occurs at the hardware level, system performance is increased under normal operations. If you must capture bad or illegal packets, it is suggested that an Etherlink III not be used.

Q: My 3C589 PCMCIA card is not seen by my Laptop?

A: Try using the PCMCIA card with Card and Socket Services (CSS) enabled in your config.sys file. Many problems with installation of PCMCIA cards are resolved with the latest release of CSS from your Notebook manufacturer. After obtaining the latest CSS drivers, load them in your config.sys file and execute the diagnostics program provided on your EtherDisk to verify the functionality of the adapter.

Q: I'm using the 3C589 in my notebook computer and I keep getting an "adapter not found" error message.

A: If your notebook computer uses a Databook PCMCIA controller, make sure you are using version 3.02 of Databook's Card and Socket Services. Versions prior to 3.02 will not find the PCMCIA adapter properly. To obtain the latest version of the Databook Card and Socket Services drivers, contact your notebook manufacturer to obtain the new drivers.

Q. I am trying to load my Netware ODI driver on my IBM ThinkPad 755CE and I am getting "Initialization Failed" messages. What am I doing wrong?

A. Modify the DICRMU01.SYS driver line in the config.sys file on your ThinkPad to include the /SH=1 parameter. The driver line should look like this:

device=c:\thinkpad\DICRMU01.SYS /MA=C800-CFFF /SH=1

The /SH=1 parameter allows for modem interrupt sharing which could resolve some of the initialization conflicts when loading the ODI driver.

Q. How do I install my PCMCIA adapter into Windows for Workgroups?

A:

    1. Click on the Network Icon and enter Network Setup.
    2. Click on Drivers.
    3. Select and click 'unlisted or unsupported adapter'- specify path to your PCMCIA EtherDisk, then [Enter].
    4. The selection box should now read '3Com EtherlinkIII PCMCIA Adapter.' Select it.
    5. Add the protocol(s) for your network support. Your config.sys, autoexec.bat and protocol.ini will be updated and you will need WFW's[VB1] System 7 diskette.
    6. Close the window.
    7. Exit Windows and reboot.

Q: I'm using an NDIS driver and I get the following message when booting my notebook computer: "Can't configure card through Card Services, but could be forced with pcmcia_enabler=yes/no in protocol.ini." What's wrong?

A: Locate your protocol.ini file and edit the file to include an extra parameter. Under the parameter DRIVERNAME=ELPC3$, add this parameter:

PCMCIA_ENABLER=YES