Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!emory!kd4nc!n4hgf!wht
From: wht@n4hgf.uucp (Warren Tucker)
Newsgroups: comp.unix.i386
Subject: Re: 386ix and Parallel Printers
Message-ID: <685@n4hgf.uucp>
Date: 7 May 90 20:43:58 GMT
References: <15427@bfmny0.UU.NET> <1990May3.111446.2879@oct1.UUCP> <1990May6.152012.14804@ddsw1.MCS.COM> <7813@dmshq.mn.org>
Reply-To: wht@n4hgf.UUCP (Warren Tucker)
Organization: Amateur Radio Station N4HGF
Lines: 23

In article <7813@dmshq.mn.org> pnessutt@dmshq.mn.org (Bob Monio) writes:
>In article <1990May6.152012.14804@ddsw1.MCS.COM> karl@mcs.MCS.COM (Karl Denninger) writes:
>>In article <1990May3.111446.2879@oct1.UUCP> mason@oct1.UUCP (David M. Mason) writes:
>>>In article <15427@bfmny0.UU.NET> tneff@bfmny0.UU.NET (Tom Neff) writes:
>>>>My advice: If you're not really running multi-user, ditch the spooler.
>>>>It's a pain in the caboose.  Just pump to /dev/lp and have a nice day.
>It's not just accounting.  The company I do some work for has a
>wholesale distribution package that does both; write directly to the
>serial printer and also use the spooler.  I'm not sure why it was
>originally done this way, but we are in the process of changing it.

Most of the check writing programs I have run into want more a
better feeling that check # blah-dee-blah has been printed than
just knowing it has been spooled, especially when printing on
checks with preprinted numbers.

Now as to the usual MIS daily/weekly detail tomes people rarely look at,
spoolers are more trusted :-).
 
------------------------------------------------------------------
Warren Tucker, TuckerWare gatech!n4hgf!wht or wht%n4hgf@gatech.edu
McCarthyism did to cinema what ANSI did to C,  cast a great number
of characters into the void.