Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!decvax!ittatc!dcdwest!sdcsvax!ucbvax!laser-lovers
From: laser-lovers@ucbvax.UUCP
Newsgroups: mod.computers.laser-printers
Subject: Re: LaserWriter Bargraph
Message-ID: <8602030028.AA13844@adobe.UUCP>
Date: Sun, 2-Feb-86 19:28:00 EST
Article-I.D.: adobe.8602030028.AA13844
Posted: Sun Feb  2 19:28:00 1986
Date-Received: Tue, 4-Feb-86 07:35:58 EST
References: <glacier!mark@mimsy.umd.edu>, <8601
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: laser-lovers@washington.arpa

The problem is that one byte in the EEROM (non-volatile memory) has
gotten corrupted somehow. EEROM clobbering is usually a result of your
LaserWriter having a hardware problem that causes the 68000 to go out
of control; it is not usually a problem with the EEROM device itself.

The parameter that has been clobbered is the "batch" baud rate for the
25-pin channel. The way to fix this is to get control of the machine
somehow, either by using the 9-pin channel or by setting the switch to
the "1200" setting and communicating at 1200 baud. (The 1200 baud
setting is fixed and does not depend on anything in the EEROM.) Then
reset the corrupted baud rate parameter to the desired value, e.g.:

	serverdict begin 0 exitserver
	statusdict begin 25 9600 0 setsccbatch end

Once you have done this, you can switch back to the "9600" setting and
you should be back in business. For more information, see Appendix D of
the PostScript Language Reference Manual.

	Ed Taft
	Adobe Systems, Inc.