🚀 go-pugleaf

I recently posted:

>I would like to use ghostscript to preview TeX output with ps graphics
>inclusions.  When I attempt to view a TeX output file I get an
>insufficient memory message.  I am using gs252 on an msdos '486
>machine, 16mb ram, with windows 3.0.  I get the same result with
>gs386.exe, gswin.exe, and gs.exe (expected for 640k version).
>My TeX ps files are produced by ptips (Personal TeX version of dvips).

>Is there any way to get ghostscript to use more memory?

I have some more information (having learned far more about postscript
than I wanted to):

The source of the problem was an "enhancement" Personal Tex Inc. added
to its ps driver, but it points up a ghostscript departure from level 1
practice and level two specs.

Before processing, the PTI postscript file checks to see that free VM
(maximum - used) is greater that 144000--I presume this is to detect a
failed previous job on the printer.  This works on most printers since
most Level 1 devices provide 240000 bytes VM (Appendix B, Postscript
Language Reference Manual (2nd ed.), Adobe Systems Inc.).  Ghostscript
(MSDOS versions) starts up with a VM limit of 105000.  In addition, I
have not been able to find that Ghostscript implements Level 2
interpreter parameters, such as MaxLocalVM (Appendix C, ibid.).

Question (again): is there any way to force Ghostscript to allocate
more VM before running a program.



--
David L. Rector				drector@math.uci.edu
Dept. of Math.				U. C. Irvine, Irvine CA 92717

Colleagues of mine use Rokicki's dvips (now at version 5.493) with
Ghostscript on their 386's and 486's.

On unix, I find that dvips's "-Z" option compresses TeX bitmaps up to
tenfold.  Why not use this on DOS?

Geoffrey Tobin