Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uunet!mcsun!sunic!tut!hydra!pihlaja From: pihlaja@cs.Helsinki.FI (Markku Pihlaja) Newsgroups: comp.lang.postscript Subject: Re: How to resume 'normal' error handling? Keywords: error,undo Message-ID: <4068@hydra.Helsinki.FI> Date: 12 Feb 90 09:08:55 GMT References: <4809@brazos.Rice.edu> Organization: University of Helsinki, Department of Computer Science Lines: 39 In article <4809@brazos.Rice.edu> jrr@ricevm1.rice.edu writes: >I downloaded Adobe's ehandler.ps (downloaded error break-page handler, ... >now I would like to remove it (or its effects) and revert to the >'standard' Apple setup when I am not developing PostScript code. If I got it right, what you want to do is make the ehandler non-resident, i.e. one that does not stay in printer memory after your job is finished. You could do this by simply commenting a few lines (5 to 11 in my version): %! % lib/ehandler.ps -- Downloaded Error Break-page handler % Copyright (c) 1984 Adobe Systems, Inc. All Rights Reserved. % assumes serverloop password is the default one % %/$brkpage where % %{pop(Error Handler in place - not loaded again\n)print flush stop} % %{serverdict begin statusdict begin 0 checkpassword % % {(Error Handler downloaded.\n)print flush 0 exitserver} % % {(Bad Password on loading error handler!!!\n)print flush}ifelse % % end%statusdict % %}ifelse /$brkpage 64 dict def $brkpage begin /prnt ...etc Of course, having done this, you must include the file in every print job you need it with. But at least there won't be any extra error message pages. Our printer server does not seem to add an EOF character (ctrl-D) at the end of each job, so downloading the ehanldler produced lots of pages reporting timeout. Markku ====================================== ======================= Markku Pihlaja Please tell me if my University of Helsinki, Finland English is not perfect. pihlaja@cs.helsinki.fi I'm a perfectionist. ====================================== =======================