Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!mrspoc!starnet!mzellers
From: mzellers@starnet.uucp (Mark Zellers)
Newsgroups: comp.lang.postscript
Subject: Re: Postscript printing small and mirrorimaged!!
Message-ID: <1990Dec10.191056.5456@starnet.uucp>
Date: 10 Dec 90 19:10:56 GMT
References: <7699@hub.ucsb.edu> <1971@fcs280s.ncifcrf.gov>
Reply-To: mzellers@starnet.UUCP (Mark Zellers)
Organization: Starnet Connections---Public Access UNIX
Lines: 29

In article <1971@fcs280s.ncifcrf.gov> toms@fcs260c2.ncifcrf.gov (Tom Schneider) writes:
>Yes, that happend to me before we installed 'transcript'.  To get around it
>you should be able to simply:
>   initgraphics
>before (or between) each job.  This should get you going quickly.  Of course,
>the better solution is to get the control-D solution working.
>

I would definitely advise against using initgraphics as a solution to
this problem.  If you take this approach, there is a good chance that if
you send many jobs to the printer one after the other that you will run
out of virtual memory.  That is because the VM consumed by the previous
job will not be reclaimed by the server loop unless it sees the end of
the job.  One alternative method that will work is to surround the job
with something along the lines:
    /SaveMe save def
    ..
    ..
    ..
    SaveMe restore

This will not only get the coordinate system back to the default but
also reclaim the VM.


Mark H. Zellers
1550 Cowper St
Palo Alto, CA 94301
decwrl.dec.com!batgirl!bwayne!mark