🚀 go-pugleaf

In article <Bv56s0.BtJ@newcastle.ac.uk> Andrew.Hilborne@newcastle.ac.uk 
(Andrew Hilborne) writes:
>...I am forced to support the pre-loading of a whole slew of PS prologs...
>[which insist on living outside the server loop --jdlh]
>To "pop" an un-wanted prolog I create my own save object outside
>the server loop first.  I then send a couple of CTRL-D's...
>and wait for the job to complete.  The prolog is concatenated with the 
>user's input and sent as a separate PS job.  I can use the save object
>later to pop the prolog.  ... I am getting
>examples of prologs which are inadequately loaded.

It is very important that "save" and "restore" operators be balanced when
used outside the server loop.  That is, if you send a "save" then be sure
to send a corresponding "restore" before you end that job (send your CTRL-D).

PostScript Level 2 interpreters enforce this balance when they resume 
their server loop.  They issue an implicit "restore" for each unmatched
"save".  This would have the effect of throwing out the save object you are
storing away.  PostScript Level 1 interpreters didn't enforce this balance.

Could it be that the technique you are using happened to work on a 
PostScript Level 1 printer but doesn't on a PostScript Level 2 printer?

I don't know of a good technique for selectively purging prologs, except 
rebooting the printer.  The following code should work on most printers:
	serverdict begin 0 exitserver	% exit server loop
	systemdict /quit get exec	% run systemdict's "quit"
	%%EOF

Write your application suppliers and ask for a version of the software 
which doesn't require a prolog outside the server loop.  If they don't 
know how to do that, send them to Adobe Developer Support!

>Andrew Hilborne

	--Jim DeLaHunt, Developer Support, Adobe Systems Incorporated	
delahunt@adobe.com	...!{apple,decwrl}!adobe!delahunt      +1-415-962-3790