LaserWriter and VAX: How To Fix An EEROM Problem (3/94)

Some users, especially those with networks, have experienced peculiar situations wherein a LaserWriter (connected via AppleTalk to a Macintosh) works, while another LaserWriter (connected on a serial line to a VAX that spools its print jobs) won't. Quite often, an EEROM problem is involved. (The EEROM is where persistent parameters are stored.)

When a failure to print across the serial line occurs, the problem can be that the EEROM was left in a state that the VAX is unable to deal with. This can happen if the LaserWriter was serially connected to a non-Macintosh machine before being connected to the VAX. For example, there are a number of MS-DOS programs that leave a LaserWriter EEROM in a non-standard state.

Two common problem areas are improper setting of the "setdefaulttimeouts" persistent parameter in EEROM and the corruption of the EESCRATCH section of the EEROM. The EESCRATCH is the area of EEROM used to extend PostScript. It is also the area most likely to have been set up in a non-standard way.

Initializing (by running a print job) over AppleTalk is a good, simple way to correct the problem. When the LaserWriter is initialized over AppleTalk, the EEROM is set in a state that the VAX can work with. Thereafter, the VAX should be able to print the file.

The AppleTalk LaserWriter drivers can deal with this situation, because they communicate with the LaserWriter as it is printing. When the LaserWriter has an EEROM problem, the driver can set the EEROM up properly. Because the VAX is spooling the document, it cannot maintain this type of back and forth dialog with the LaserWriter.

Article Change History:
18 Mar 1994 - Corrected title which contained errant characters.

Support Information Services


Published Date: Feb 18, 2012