Xref: utzoo comp.sys.mac.programmer:21431 comp.sys.mac.system:3071 Path: utzoo!attcan!uunet!wuarchive!usc!snorkelwacker.mit.edu!ira.uka.de!smurf!urlichs From: urlichs@smurf.sub.org (Matthias Urlichs) Newsgroups: comp.sys.mac.programmer,comp.sys.mac.system Subject: Re: MultiFinder Programmer's Guide question 4 Message-ID: Date: 12 Jan 91 23:28:13 GMT References: <3724@uakari.primate.wisc.edu> Organization: University of Karlsruhe, FRG Lines: 20 In comp.sys.mac.programmer, article <3724@uakari.primate.wisc.edu>, < < Just what is PrintMonitor's problem anyway? Isn't it following Apple's < guidelines? Is there some resource that can be edited to get it to < be a little more cooperative? Or is this behavior simply something < to do with waiting for a response from the printer at certain times < such that it can't let go until the printer says something back? PrintMonitor uses the LaserWriter's AppleTalk/PAP code, which probably wasn't designed with background printing in mind. The problem is more or less inversely proportional to the quality of the wire(s) to your LaserWriter. Give it a thousand PINGs with InterPoll -- what's the round trip time and how many packets get lost? What LaserWriter model are you using? -- Matthias Urlichs -- urlichs@smurf.sub.org -- urlichs@smurf.ira.uka.de /(o\ Humboldtstrasse 7 - 7500 Karlsruhe 1 - FRG -- +49+721+621127(0700-2330) \o)/