Xref: utzoo comp.text:3338 comp.lang.postscript:1672
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!amdcad!sun!pitstop!sundc!seismo!uunet!munnari!bruce!trlluna!trlamct!goanna!cidam!mg
From: mg@cidam.rmit.oz (Mike A. Gigante)
Newsgroups: comp.text,comp.lang.postscript,aus.tex
Subject: Re: Large postscript files to a laserwriter
Summary: VMError
Message-ID: <3660@cidam.rmit.oz>
Date: 21 Feb 89 20:02:12 GMT
References: <1936@goanna.oz>
Organization: RMIT Mech & Prod Eng, Melbourne, Australia.
Lines: 20

In article <1936@goanna.oz>, isaac@goanna.oz (Isaac Balbin) writes:
> 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.

Watching the messages that come back from the Laserwriter shpows that
the casuse is a VMerror. I suspect that the dvi*ps programs are not as
careful as they might be w.r.t. postscript data space (or code space?)

The same documents print flawlessly with MicroTeX's laser package (and spr).

I have a single page that I cannot print using dvi2ps! Very frustrating indeed!

Mike