Xref: utzoo comp.windows.ms:4843 comp.protocols.nfs:1237 comp.dcom.lans:5830
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!munnari.oz.au!uhccux!uhunix1.uhcc.Hawaii.Edu!pilger
From: pilger@uhunix1.uhcc.Hawaii.Edu (Eric Pilger)
Newsgroups: comp.windows.ms,comp.protocols.nfs,comp.dcom.lans
Subject: Re: Windows 3.0 and PC-NFS?????
Keywords: Software for pcnfs
Message-ID: <9192@uhccux.uhcc.Hawaii.Edu>
Date: 2 Sep 90 19:43:06 GMT
References: <852@iiasa.UUCP> <926@massey.ac.nz>
Sender: news@uhccux.uhcc.Hawaii.Edu
Followup-To: comp.windows.ms
Organization: University of Hawaii
Lines: 17

In article <926@massey.ac.nz> ABishop@massey.ac.nz (A.G. Bishop) writes:
>If you can find ANYTHING in the way of mainstream PC software that is
>aware of PC-NFS I'd love to hear about it!

I successfully installed Paradox as "other network."  It doesn't know
about PC-NFS specifically, but it does know about DOS networking.
PC-NFS appears to do a proper job of supporting DOS networking because
everything SEEMS to work just fine.  I haven't tested it rigorously,
but the basic support is obviously there (record locking, even the
name of who did the locking.)

If PC-NFS is doing a proper job of supporting DOS networking, then my
guess is that any mainstream PC software that is aware of DOS
networking will be indirectly aware of PC-NFS.

				   Eric Pilger
				   NASA Infrared Telescope Facility