home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!think.com!eplunix!raoul
- From: raoul@eplunix.UUCP (Nico Garcia)
- Newsgroups: comp.protocols.nfs
- Subject: Re: PCNFS /3c503 16-bit cards
- Message-ID: <1338@eplunix.UUCP>
- Date: 7 Jan 93 15:35:29 GMT
- References: <9973@fs3.cam.nist.gov>
- Organization: Eaton-Peabody Lab, Boston, MA
- Lines: 27
-
- In article <9973@fs3.cam.nist.gov>,
- koontz@cam.nist.gov (John E. Koontz X5180) writes:
- >
- > In article <C0GJJn.FJ6@dcs.ed.ac.uk>, jhb@dcs.ed.ac.uk (John Butler) writes:
- > |> The new 3c503 cards (the 16-bit ones with the TP socket on the back in
- > |> particular) cause some PC configurations to hang the moment they actually
- > |> try to access the Ethernet. I cleared this in PC-NFS 4.0a by enabling shared
- > |> memory option 4. I have yet to convince myself WHY this works and that it is
- > |> not doing terrible things elsewhere but you might like to consider it if you
- > |> have similar problems.
- >
- > I just went through something similar with a Trident VGA card with
- > 1MB RAM onboard, and the non TP Etherlink II/16 (3c503 16 bit). With
-
- I have a completely different solution. After talking to Sun technical
- support, they pointed out that the 3c503-16 card needs one of the NDIS
- drivers on the other distribution diskette. The correct driver to use is for
- the 3c507 card, which is called the Etherlink II card in Sun's NDIS listings
- (with file ETHLNKII.DOS). This is screwball, but works correctly on our
- Insight 486DX-50 with MS-DOS 5.0.
-
- Now, why it's listed as the 3c507 instead of the 3c503-16 escapes me
- completely....
- --
- Nico Garcia
- CIRL/MEEI
- eddie.mit.edu!eplunix!raoul
-