Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!tomiii
From: TOMIII@MTUS5.BITNET (Thomas Dwyer III)
Newsgroups: comp.protocols.nfs
Subject: PC-NFS vs. Beame
Message-ID: <90309.170944TOMIII@MTUS5.BITNET>
Date: 5 Nov 90 22:09:44 GMT
References: <3160@jaytee.East.Sun.COM> <2575@gazette.bcm.tmc.edu>
 <3196@jaytee.East.Sun.COM> <2583@gazette.bcm.tmc.edu>
Organization: Computing Technology Services, Michigan Technological Univ.
Lines: 20

>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.

Well, on the other hand, we rather prefer Sun's idea of the NET PRINT *
command.  If I want something to come out of the printer, *I'll* tell it
to come out.  Beame has to guess when you are ready for the queue to be
printed, where as Sun lets *you* decide.  I also like Sun's idea of having
T: U: and V: as "windows" to the print queue; you can watch your file(s)
get printed by using the "dir" command.  Beame does not have anything
similar to this.


Thomas Dwyer III                        Email: tomiii@mtu.edu
Network Programmer                             tomiii@mtus5.BITNET
Computing Technology Services           Voice: (906) 487-2110
Michigan Technological University       Fax:   (906) 487-2787