Path: utzoo!utgpu!watserv1!watmath!att!pacbell.com!ucsd!sdd.hp.com!hplabs!pyramid!infmx!aland
From: aland@informix.com (Colonel Panic)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: 3C503 shared memory conflict
Summary: PC-NFS gives little choice; consider a WD card
Message-ID: <1990Dec11.194526.10121@informix.com>
Date: 11 Dec 90 19:45:26 GMT
References: <1990Dec4.124602.3672@csc.anu.oz.au>
Sender: news@informix.com (Usenet News)
Organization: INFORMIX Client Services ("Peace thru Normalization")
Lines: 23

In article <1990Dec4.124602.3672@csc.anu.oz.au> axt654@csc.anu.oz.au writes:
>Hi,
>I'm running Sun's version of PC-NFS on a 386 PC with a 3C503 card but
>also want to run NCSA Telnet because I need some of it's features. The problem
>is that the NCSA driver (and the packet driver) need a shared memoryt address
>available (eg dc00 or d800) but the NFS software requires this to be disabled
>(PC-NFS version 3.0.1). Is there some way around this? Is there a packet driver
>that runs with shared mem disabled? 

I faced a similar situation when trying to run WIN/TCP from UNIX and
PC-NFS from DOS on the same machine and card.  PC-NFS doesn't give you
a choice of enabling shared memory on those cards that it wants it
disabled by default.

I decided to shift to using the WD8003E instead, for which PC-NFS does
use shared memory mode.

--
Alan Denney      aland@informix.com      {pyramid|uunet}!infmx!aland

"When will Apple get socially responsible and offer separate trash can
 icons for glass, aluminum, and paper?"
  - Lincoln Spector