Xref: utzoo comp.windows.ms:4817 comp.protocols.nfs:1231 comp.dcom.lans:5821
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!uflorida!travis!hardy!leoh
From: leoh@hardy.hdw.csd.harris.com (Leo Hinds)
Newsgroups: comp.windows.ms,comp.protocols.nfs,comp.dcom.lans
Subject: Re: Windows 3.0 and PC-NFS?????
Message-ID: <866@travis.csd.harris.com>
Date: 31 Aug 90 19:46:51 GMT
References: <852@iiasa.UUCP> <26DE184C.28496@ics.uci.edu>
Sender: news@travis.csd.harris.com
Reply-To: leoh@hardy.hdw.csd.harris.com (Leo Hinds)
Followup-To: comp.windows.ms
Organization: Harris Computer Systems, Fort Lauderdale, FL
Lines: 15

In article <26DE184C.28496@ics.uci.edu> milne@ics.uci.edu (Alastair Milne) writes:

>   			<text deleted>
>   But then run File Manager, and sure enough, your remote drives not 
>   only appear but are marked with the NET drive icon.  And they are 
>   fully usable -- or at least, I've encountered no restriction so far.


Though this is true under FM, whenever I try and use the setup/add new 
applications it does not seem to know about ALL my nfs drives ... just the 
first one (E).  The next nfs drive (F) is ignored, as well as G, H, & P.

leoh@hdw.csd.harris.com         	Leo Hinds       	(305)973-5229
Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n
creireg ?!!!!!!? ... znlor arkg gvzr