Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!agate!violet.berkeley.edu!izumi
From: izumi@violet.berkeley.edu (Izumi Ohzawa)
Newsgroups: comp.lang.postscript
Subject: Re: Printer memory size
Message-ID: <24228@agate.BERKELEY.EDU>
Date: 10 May 89 07:03:36 GMT
References: <4961@pt.cs.cmu.edu>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 22

In article <4961@pt.cs.cmu.edu> tsf@PROOF.ERGO.CS.CMU.EDU (Timothy Freeman) writes:
>We've been having problems with files that print on one postscript
>printer failing on other postscript printers.  The difference between
>the printers may be the size of VM, the size of the execution stack,
>Tim Freeman

Perhaps, the printer that fails gets things permanently stored in VM
by programs which sends 'exitserver' to the printer.
Depending on the size of items permanently stored (until power off)
this way, subsequent jobs may run out of VM space.

I don't know of any good solution to this except for (1) resetting
the printer periodically (you can do this via software commands), or
(2) looking out for programs which tries to store something via
'exitserver', and modifying them so that they don't do that.

All PS programs should work on the original Apple LaserWriter,
which has probably the least amount of VM.  On ours, we have
181488 bytes on power-on.
Are there any other PS printer which has less free VM?

Izumi Ohzawa, izumi@violet.berkeley.edu