Path: utzoo!attcan!uunet!husc6!bloom-beacon!apple!bionet!agate!ucbvax!RIACS.EDU!davy
From: davy@RIACS.EDU
Newsgroups: comp.protocols.appletalk
Subject: Re: Curious lwsrv behavior with new LaserWriter
Message-ID: <8811052020.AA00393@intrepid.riacs.edu>
Date: 5 Nov 88 20:20:48 GMT
References: <Added.MXPppWy00UkT0Dm08y@andrew.cmu.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 29


     From:  Phil Farrell <farrell@erebus.stanford.edu>
     Date:  Wed, 2 Nov 88 11:04:21 PST
     Subject:  Curious lwsrv behavior with new LaserWriter

	[....]

     The error file on the Vax claimed that one of
     the first lines in the AppleDict file prepended by lwsrv had an
     "OffendingCommand" named "setdefaulttimeouts", so the job was flushed.
     The same file from my Mac printed okay on the first LaserWriter.  I
     verified that the exact same file, including same AppleDict, was being
     sent to the two different LaserWriters by stopping the queues on the
     Vaxes and comparing the spool files that were waiting to print.

     The moral: "break in" your new LaserWriters by printing a file directly
     from a Mac via AppleTalk before trying to access them with lwsrv on a
     UNIX host connected via serial line.  Does anyone have any idea what is
     being set inside the LaserWriter by this procedure?

I don't know what "setdefaulttimeouts" does, but I ran into the same
problem brining up our QMS PS2400 under lwsrv.  I just deleted the
"setdefaulttimeouts" command and the associated if-then-else from the
Appledict files, and it was all happy.

I haven't tried running these files to a LaserWriter, but as near as I
can tell, the deletion of "setdefaulttimeouts" makes no difference.

--Dave Curry