Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site uw-beaver Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!vax135!cornell!uw-beaver!laser-lovers From: laser-lovers@uw-beaver Newsgroups: fa.laser-lovers Subject: Re: QMS Printers Message-ID: <955@uw-beaver> Date: Mon, 25-Mar-85 18:06:18 EST Article-I.D.: uw-beave.955 Posted: Mon Mar 25 18:06:18 1985 Date-Received: Wed, 27-Mar-85 02:46:11 EST Sender: daemon@uw-beaver Organization: U of Washington Computer Science Lines: 24 From: Mark Johnson Well, I can certainly see a number of problems arising if you get a malicious user screwing up the printer for the next person. We are running with VMS 3.7 & our QMS is on a DMF-32 printer port. Occasionally the printer does get brain damaged. In particular, overloading its font memory, aborting jobs while printing, and hitting the initialize button all rank up there for making a mess of the printer. I would really like to see a V4 style printer spooler for that printer. I have a number of reasons including reprinting pages that were jammed (& burned occasionally!) in the printer, true selection by page, and a more fool proof interface for the printer. Overall, what I have now is fine. It is infrequent that we have serious problems unless the printer itself is marginal. That is when EVERYBODY thinks they know how to re-initialize the printer, reload the fonts, etc. & I have to stop the queue, delete the multiple font load requests, initialize the printer, load the fonts ONCE, and then restart the queue. Good luck with your printer. Perhaps after we get V4.x up on our system we will look at the more general problem. --Mark