cosmos@druhi.ATT.COM (GuestRA) (12/16/87)
We are experiencing an error when printing large jobs on our laserwriter (about 14 pages of viewgraphs). We are running the latest stuff and Multifinder with background printing on a Mac II. PrintMonitor says it got a timeout (this happens after printing about half of the pages) and recommends trying again. However, it tries to start the job over from the beginning and simply times out again in the same place. None of the pages in the vicinity of the timeout have bitmaps. Anyone know what's wrong and if it can be cured? The work around is just to split it into two print jobs, and that works just fine. Ron Guest ihnp4!druhi!cosmos
olson@endor.harvard.edu (Eric K. Olson) (12/18/87)
In a recent article GuestRA writes: > >We are experiencing an error when printing large jobs on our laserwriter >(about 14 pages of viewgraphs). We are running the latest stuff and >Multifinder with background printing on a Mac II. PrintMonitor says it got >a timeout (this happens after printing about half of the pages) and >recommends trying again. However, it tries to start the job over from the >beginning and simply times out again in the same place. I have experienced this when running programs in the foreground that don't give up enough time to other tasks under MultiFinder (the Print Spooler being one of those tasks). So the Laserwriter times out because it doesn't get enough data fast enough. I believe this time constant can be changed in the LaserPrep file (I'll check) using settimeout or setjobtimeout or some such. If you leave PrintMonitor frontmost, it will probably not timeout, but that isn't much fun now that we finally have background printing. -Eric (defun maybe (x) (maybe (not x))) Eric K. Olson olson@endor.harvard.edu harvard!endor!olson D0760 (Name) (ArpaNet) (UseNet) (AppleLink)
cosmos@druhi.ATT.COM (GuestRA) (12/21/87)
In article <3603@husc6.harvard.edu>, olson@endor.harvard.edu (Eric K. Olson) writes: > In a recent article GuestRA writes: > > > I have experienced this when running programs in the foreground that don't > give up enough time to other tasks under MultiFinder (the Print Spooler being > -Eric Actually, the Mac II this happens on is used by our secretary and nothing else is happening when we tried this print. MacWrite is "running" in the foreground, but isn't getting any events (mouse, keyboard, etc.). So, I would think PrintMonitor would get enough time. Is it stil possible that MacWrite is that ill-behaved even when not doing anything? Ron Guest ihnp4!druhi!cosmos