Xref: utzoo comp.text:3309 comp.lang.postscript:1640
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!sun!pitstop!sundc!seismo!uunet!munnari!goanna!isaac
From: isaac@goanna.oz (Isaac Balbin)
Newsgroups: comp.text,comp.lang.postscript,aus.tex
Subject: Large postscript files to a laserwriter
Message-ID: <1936@goanna.oz>
Date: 17 Feb 89 02:01:39 GMT
Organization: Comp Sci, RMIT, Melbourne, Australia
Lines: 25

I feel sure many others have experienced this, I am curious,
however, how they deal with it --- under Unix.
I use Rokicki's dvi2ps translator from TeX to postscript.
Indeed, the same thing happens for dvi2ps (by Holtz and Senn) in the
standard distribution of TeX and I recall it also happened in the old
days when I had to convert ditroff to postscript.
What happens? After a certain amount of processing, something overflows
and the rest of the large job does not print and finds its way to the great
big bit-bucket in the sky.
Normally, I print a large job (>30-40) pages (it also depends how much
is in each page) in chunks.
Is there a better solution that people use? That is, postscript code
which looks after the laserprinter and doesn't let it proverbially
dump core.
(PS I also have to send a  ^C to the printer to stop it processing 
after lprm'ing the rest of the job)
----------------------------------------------------------------------------
Isaac Balbin,
Department of Computer Science,	         ACSNET: isaac@goanna.oz
Royal Melbourne Institute of Technology,  JANET: isaac%goanna.oz.au@uk.ac.ukc
GPO BOX 2476 V,                            ARPA: isaac%goanna.oz.au@uunet.uu.net
Melbourne, 3001, 		          CSNET: isaac%goanna.oz.au@australia
AUSTRALIA                                  UUCP: ...!uunet!goanna.oz.au!isaac
Phone: +61 3 660 2803		         BITNET: isaac%goanna.oz.au@relay.cs.net
Fax  : +61 3 663 2764		          EARN: isaac%goanna.oz.au@uk.ac.rl.earn