Networking DOS to Unix (Know about commercial products...)
Geoff Arnold @ Sun BOS - R.H. coast near the top
geoff at hinode.East.Sun.COM
Wed May 8 23:39:52 AEST 1991
Quoth dag at fciva.UUCP (Daniel A. Graifer) (in <603 at fciva.FRANKCAP.COM>):
#I know this is caused by the brain-damaged way that DOS applications do
#printer I/O. Since they assume they own the entire system, they finish a
#print job by failing to send any more characters. At most, an option is
#provided to send a formfeed to clear the last page out of the printer.
#Networks designed to support DOS deal with this by setting a timeout.
#Output to the LPTn device is spooled, and after a period with no activity,
#the contents are queued for printing, and the spool file reset. Both Novell
#(in this case Portable Netware) and Locus Computing's PC-Interface can do
#this. My point is that this is much cleaner and more obvious to your existing
#DOS users.
For PC-NFS it has always (since 1986) been the case that you have the
options of print-on-timeout, print-on-process-exit, print-on-hotkey and
print-on-special-command. It has never been necessary to print to file, except
for a few oddball apps.
I'll let FTP, Wollongong and B&W discuss their schemes.
-- Geoff Arnold, PC-NFS architect, Sun Microsystems. (geoff at East.Sun.COM) --
------------------------------------------------------------------------------
-- Sun Microsystems PC Distributed Systems ... --
-- ... soon to be a part of SunTech (stay tuned for details) --
More information about the Comp.unix.sysv386
mailing list