Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!amdcad!sun!pitstop!sundc!seismo!uunet!mcvax!ukc!eagle.ukc.ac.uk!icdoc!qmc-cs!liam From: liam@cs.qmc.ac.uk (William Roberts) Newsgroups: comp.protocols.appletalk Subject: Re: Curious lwsrv behavior with new LaserWriter Summary: Apple LaserPrep writers are completely mad. Keywords: LaserWriter, LaserPrep Message-ID: <751@sequent.cs.qmc.ac.uk> Date: 7 Nov 88 18:34:19 GMT References: Reply-To: liam@cs.qmc.ac.uk (William Roberts) Organization: Computer Science Dept, Queen Mary College, University of London, UK. Lines: 29 Expires: Sender: Followup-To: Distribution: In article farrell@EREBUS.STANFORD.EDU (Phil Farrell) writes: >I found that a new LaserWriter Plus needed "breaking in" before it would >work with lwsrv (CAP 4.0) on a 4.3BSD Vax connected via serial line. >... >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? This must be another example of the insane way that Apple handle PostScript - every new LaserPrep file I see is distinctly more unpleasant than the last, whilst also conforming more precisely to the letter of the Adobe document convention: Example: DSC 2.0 "Every page should be independent of every other page" LaserPrep: Ok, in Document setup we produce a procedure which enumerates the current clip path in device coordinates and use that to completely reset the the printer at the start of every page. I'd send Apple a copy of the PostScript Green Book if I thought it would do any good... -- William Roberts ARPA: liam@cs.qmc.ac.uk (gw: cs.ucl.edu) Queen Mary College UUCP: liam@qmc-cs.UUCP LONDON, UK Tel: 01-975 5250