Xref: utzoo comp.lang.postscript:2905 comp.sys.dec:1834 Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!think!bloom-beacon!athena.mit.edu!dkk From: dkk@athena.mit.edu (David K Krikorian) Newsgroups: comp.lang.postscript,comp.sys.dec Subject: Re: Hung DEC Scriptprinter Keywords: PostScript, DEC LN03R, Zombied, Micrographix Message-ID: <14444@bloom-beacon.MIT.EDU> Date: 19 Sep 89 23:11:48 GMT References: <2034@leah.Albany.Edu> Sender: daemon@bloom-beacon.MIT.EDU Reply-To: dkk@athena.mit.edu (David K Krikorian) Followup-To: comp.lang.postscript Organization: Massachusetts Institute of Technology Lines: 28 In article <2034@leah.Albany.Edu> rds95@leah.Albany.Edu (Robert Seals) writes: > >Our DEC ScriptPrinter (LN03R) periodically goes to lunch. I believe >it is caused by the Micrographix PS driver for Microsoft Windows, >but I can't really be sure. ...[symptoms]... > >Has anybody seen ANYTHING like this? Please? The printer gets a lot of >use from our vax and pcs, and my users (and myself) are getting fed up. > >Any comment at all would be appreciated. Except, "Never saw thet before." > Sorry, but I never saw that before. Seriously, I think you're on the right track suspecting your PostScript driver (or printer driver, if you have the same one on all the troublesome printers). (What hardware do you have the printers hooked up to?) The systems I administer have (I'd guess) 75 LN03R's hooked up to DEC hardware in various configurations. We drive them into the ground. Literally. It's truly amazing what those printers will take, and keep on printing. (We have about 10,000 users.) The only problems we have are normal wear on the hardware (even though we run them at an order of magnitude beyond spec.). I understand your desire to downgrade them as a short-term solution for your problem, but isn't that a bit drastic? Is changing the software an option? Hooking up one LN03R in a different configuration than the others (if you haven't yet)? David Krikorian / MIT Project Athena Operations / Systems Programmer