Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!uunet!pilchuck!jewell From: jewell@Data-IO.COM (Cal Jewell) Newsgroups: comp.protocols.tcp-ip.ibmpc Subject: Re: Clarkson 3C503 & PC-NFS Keywords: Clarkson,3C503,PC-NFS,WINQVT Message-ID: <1728@pilchuck.Data-IO.COM> Date: 14 Mar 91 00:19:03 GMT References: Sender: news@Data-IO.COM Organization: Data I/O Corporation; Redmond, WA Lines: 27 In article gbj@melb.bull.oz.au (Graham Jose) writes: >I am having considerable trouble getting the Clarkson 3C503 packet driver to >work with PC-NFS. [...stuff deleted...] > My ultimate aim is to be able to run WINQVTNET in >Windows 3.0, while still having access to my network drives. I am trying to accomplish the same thing (get WinQVT/NET and PC-NFS to coexist peacefully). But, I haven't been able to pull it off yet. As near as I can tell, what happens is that when you boot the PC, PC-NFS grabs control of the packet driver and won't let go. Then, when you start Windows and start WinQVT/NET, it exits because the packet driver is already in use. I can get PC-NFS to run on the packet driver. I can get WinQVT/NET to run on the packet driver. But, I can't get the two to run together. Am I missing something? If anybody has managed to get WinQVT/NET and PC-NFS to coexist, I'd like to know. I guess that the other possible answer is that Graham and I are trying to do the undoable do. Anybody out there that can offer any clues/insight/answers?