home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dove!cam!koontz
- From: koontz@cam.nist.gov (John E. Koontz X5180)
- Newsgroups: comp.protocols.nfs
- Subject: Re: PCNFS /3c503 16-bit cards
- Message-ID: <9973@fs3.cam.nist.gov>
- Date: 7 Jan 93 02:15:54 GMT
- References: <C0GJJn.FJ6@dcs.ed.ac.uk>
- Sender: news@cam.nist.gov
- Organization: National Institute of Standards and Technology, Gaithersburg, MD
- Lines: 29
-
- 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
- this VGA card, shared memory has to be disabled to avoid lockups.
- The problem is that the shared memory areas allowed by the Etherlink
- II/16 are all within the Trident's video display buffer. Disabling
- shared memory, as I understand it, makes the Etherlink card place its
- buffer in DOS memory. The apparent alternative is to set a jumper on
- the graphics card that forces it to use 8 bit mode, which effectively
- forces it to limit its graphics modes to modes which use a smaller
- video display buffer, i.e., this approach limits the capabilities of
- the video card. Since the Etherlink card's buffer is fairly small,
- the first approach seems to be the one to take.
-
- I'd be delighted to hear corrections or clarrifications of this
- description!
-
- ----
- John E. Koontz (koontz@bldr.nist.gov)
-
- Disclaimer: Views and recommendations, express or implied, are my own, and
- do not reflect the opinion or policy of my employers.
-