Xref: utzoo comp.sys.ibm.pc:33466 comp.protocols.tcp-ip.ibmpc:1559
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!ucsfcgl!cca.ucsf.edu!wet!epsilon
From: epsilon@wet.UUCP (Eric P. Scott)
Newsgroups: comp.sys.ibm.pc,comp.protocols.tcp-ip.ibmpc
Subject: Re: NFS Support for DOS
Summary: Why is PC-NFS screwing other 3C503 applications?
Message-ID: <457@wet.UUCP>
Date: 20 Aug 89 10:00:38 GMT
References: <606@UALTAVM.BITNET> <409@datran2.uunet> <26558@amdcad.AMD.COM> <653@east.East.Sun.COM> <4554@uhccux.uhcc.hawaii.edu>
Reply-To: epsilon@wet.UUCP (Eric P. Scott)
Followup-To: comp.protocols.tcp-ip.ibmpc
Organization: Wetware Diversions, San Francisco
Lines: 18

In article <4554@uhccux.uhcc.hawaii.edu> richard@uhccux.UUCP (Richard Foulk)
writes:
>Right.  So this must mean that you guys are now supporting the industry
>standard packet-driver interface so that things like NCSA-Telnet and
>FTP Software's stuff will run alongside PC-NFS.  Right?

I'd like to run PC-NFS and Clarkson's TN3270 on a PC/AT with a
3C503 (not at the same time).   Clarkson's Packet Driver requires
the dip-switches set to enable shared memory.  PC-NFS's 3C503
driver will not run when I do this; it wants shared memory
disabled.  I have Geoff Arnold's PC-NFS+Packet Driver Version 2,
but I'd rather not run it if I don't have to, since it's
officially unsupported.  Does enabling shared memory force it to
be used, or just set a power-on default that a driver could
disable?  Why does PC-NFS insist on an inefficient operating mode?
According to the documentation, it doesn't do this on the WD8003!

					-=EPS=-