Path: utzoo!attcan!uunet!cs.utexas.edu!usc!wuarchive!bcm!tmc.edu!sob
From: sob@tmc.edu (Stan Barber)
Newsgroups: comp.protocols.nfs
Subject: Re: Enduring PC-NFS Annoyances
Message-ID: <2583@gazette.bcm.tmc.edu>
Date: 5 Nov 90 17:33:52 GMT
References: <3160@jaytee.East.Sun.COM> <2575@gazette.bcm.tmc.edu> <3196@jaytee.East.Sun.COM>
Sender: usenet@bcm.tmc.edu
Organization: Texas Medical Center, Houston, Texas
Lines: 16
Nntp-Posting-Host: tmc.edu

In article <3196@jaytee.East.Sun.COM> geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top) writes:
>Clarification, please? 

Sure. I am talking more about it from the MS/DOS application point of view.
It needs to be more like the printer attached to a PC-LAN. Right now, most
of my users have to go an extra step to print via PCNFS (hot key, or enter
net print to insure that PCNFSD "heard" that there was stuff to print). A
few use the "program exit" and timeout features, but more would rather is
just acted like a printer attached to their PC.

BSD lpr support might get around this, but then again it might not.

-- 
Stan           internet: sob@bcm.tmc.edu         Director, Networking 
Olan           uucp: {rutgers,mailrus}!bcm!sob   and Systems Support
Barber         Opinions expressed are only mine. Baylor College of Medicine