jrr@uncle-bens.rice.EDU (J.R. Richardson) (02/08/90)
I downloaded Adobe's ehandler.ps (downloaded error break-page handler,
1986 vintage) into our Apple LaserWriter II NTX (revision 1 version
47.0) via AppleTalk. It works fine for debugging my PostScript work but
now I would like to remove it (or its effects) and revert to the
'standard' Apple setup when I am not developing PostScript code.
What is bothersome is that we get an occasional error page (about 5 per day)
that say ERROR: ioerror
OFFENDING COMMAND: restore
STACK:
Just resetting the LaserWriter doesn't remove ehandler.ps's effects.
Any help will be appreciated. P.S. Can someone give me some guidance on
ftp sites for PostScript items and Adobe's materials on the network? Thanks.
/----------------------------\ /---------------------------------------\
| J.R. Richardson | Consultant, Computing Resource Center |
| Rice University - OCIS | BITNET: jrr@ricevm1 |
| P.O.Box 1892 | Internet: jrr@ricevm1.rice.edu |
| Houston, TX 77251-1892 | MaBellNet: 713-527-4980 |
\----------------------------/ \---------------------------------------/pihlaja@cs.Helsinki.FI (Markku Pihlaja) (02/12/90)
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. ====================================== =======================
woody@rpp386.cactus.org (Woodrow Baker) (02/13/90)
In article <4068@hydra.Helsinki.FI>, pihlaja@cs.Helsinki.FI (Markku Pihlaja) writes: > In article <4809@brazos.Rice.edu> jrr@ricevm1.rice.edu writes: > >I downloaded Adobe's ehandler.ps (downloaded error break-page handler, > ... > ...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. > end your code with stop That should stop the timeout errors Cheers Woody
cplai@daisy.UUCP (Chung-Pang Lai) (02/13/90)
In article <4809@brazos.Rice.edu> jrr@ricevm1.rice.edu writes: >I downloaded Adobe's ehandler.ps (downloaded error break-page handler, >1986 vintage) into our Apple LaserWriter II NTX (revision 1 version >47.0) via AppleTalk. It works fine for debugging my PostScript work but >now I would like to remove it (or its effects) and revert to the >'standard' Apple setup when I am not developing PostScript code. For us, we just turn the printer off and on again to erase its effect. You can also comment out the first block of the code to make it to run on a job to job basis. You can prepend the (one time only) ehandler in front of your regular ps file. the printer will return to normal after the current job.
ivanlan@urbana.mcd.mot.com (Ivan Van Laningham) (02/16/90)
woody sez (Message-ID: <17921@rpp386.cactus.org>): >>end your code with >>stop >>That should stop the timeout errors dont do that; if you run unix (sysV expecially) that stops the batch mode; your spooler will try to send the next job to the printer, and the printer will ignore it. if you dont run unix, you can do whatever you want. -- ----------------------------------------------------------------------- ivanlan@urbana.mcd.mot.com (Ivan Van Laningham) motorola MCD urbana UDC 1101 e. university urbana IL 61801 39N 88W ----------------------------------------------------------------------- signature under construction, watch this space -----------------------------------------------------------------------
cplai@daisy.UUCP (Chung-Pang Lai) (02/22/90)
In article <4068@hydra.Helsinki.FI> pihlaja@cs.Helsinki.FI (Markku Pihlaja) writes: > 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. You can keep the error handler resident without reporting the time-out message pages. You only need to add one line to it. It works for us. known{nl nl(STACK:)prnt nl nl $error/ostack get aload length{==}repeat}if % errorname (timeout) eq {erasepage} % don't show timeout errors {systemdict/showpage get exec}ifelse Just add the line beginning with % to your ehandler, it will screen off all the time-out error.