Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!newstop!eastapps!hinode!geoff
From: geoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Newsgroups: comp.unix.sysv386
Subject: Re: Networking DOS to Unix (Know about commercial products...)
Message-ID: <6013@eastapps.East.Sun.COM>
Date: 8 May 91 13:39:52 GMT
References: <24479@well.sf.ca.us> <833@tiamat.fsc.com> <5940@eastapps.East.Sun.COM> <603@fciva.FRANKCAP.COM>
Sender: news@East.Sun.COM
Reply-To: geoff@east.sun.com (Geoff Arnold @ Sun BOS - R.H. coast near the top)
Organization: Sun Microsystems PC-NFS Engineering
Lines: 23

Quoth dag@fciva.UUCP (Daniel A. Graifer) (in <603@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@East.Sun.COM)   --
------------------------------------------------------------------------------
--     Sun Microsystems PC Distributed Systems ...                          --
--            ... soon to be a part of SunTech (stay tuned for details)     --