Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!xanth!mcnc!ece-csc!ncrcae!ncrlnk!uunet!munnari!murtoa.cs.mu.oz.au!wcc!latcs1!ditmela!idm
From: idm@ditmela.oz (Ian Mathieson)
Newsgroups: comp.protocols.appletalk
Subject: Re: AppleShare spooling
Summary: We have had the exact opposite problem.
Message-ID: <4156@ditmela.oz>
Date: 10 Feb 89 02:08:06 GMT
References: <8902021917.AA18189@NMSU.Edu> <5555@bsu-cs.UUCP>
Reply-To: idm@ditmela.oz.au (Ian Mathieson)
Organization: CSIRO, Division of Information Technology, Australia
Lines: 27

In article <5555@bsu-cs.UUCP> mithomas@bsu-cs.UUCP (Michael Thomas Niehaus) writes:
> In article <8902021917.AA18189@NMSU.Edu>, tjh+atalk.errors@ANDREW.CMU.EDU writes:
>> Here's an interesting problem with the AppleShare spooler:
>> 
>> When we set up our Mac AppleShare network for our student Mac Lab, we ran 
>> into a rather annoying bug.  The AppleShare spooler is consistently flushing
>> MacDraw 1.95 documents.
>>	[ ... ]
>	[ ... ]
> This is not a bug with Cricket Draw or MacDraw (in my opinion, assuming that
> my assumptions above are correct).  They will print correctly if you set the
> spooler in direct print (bypass) mode.  It is a matter of opinion if this is
> a bug with the print spooler, or just an oversight (or is there a difference).
> I believe that this should be fixed, though.

Interestingly, we had the exact opposite problem recently.  MacDraw 1.5
on a Mac+ running System 6.0.2 would repeatedly crash (error 28) when
printing direct or spooling via lwsrv/papif, but background printing via
the PrintMonitor worked fine!

----------------------------------------------------------------------
ISD:	+61-3-347-8644			Dr. Ian Mathieson,                 
FAX:	+61-3-347-8987			Division of Information Technology,
ACSnet/CSNET:	idm@ditmela.oz		CSIRO Australia,
ARPA:	idm%ditmela.oz@uunet.uu.net	55 Barry Street,
JANET:	ditmela.oz!idm@ukc		Carlton, Vic 3053, Australia.         
UUCP:	{enea,mcvax,nttlab,ukc,uunet}!munnari!ditmela.oz!idm