🚀 go-pugleaf

In message <36ukdm$n8u@cpcug.org> - kbennett@cpcug.org (Keith Bennett) writes:

>I'm trying to print a long Postscript file onto an HP LJ 4 MP.  I get
>about 7 pages perfectly, but then the printer times out and I have
>to explicitly tell the system to retry.  When I do, I get the
>Postcript error:
[munch]

Ftp over to "wilma.cs.brown.edu" and pick up the postscript faq. It lists
some sources and programs that can help. The one I have in mind
is called "behandler.ps".  It's postscript code that you can download to
your printer. When an error occurs, it prints out something a little more
understandable. To load behandler.ps, just download (print) it to your
printer.

Another thing to try would be to pick up ghostscipt/ghostview and see if
they can display it. It might be that there is an error in the file. Or try it
on another printer.

>
>By the way, if I print via PM, am I supposed to tell PM it's a
>Printer-specific or plain text file?

Tell it Printer-specific (unless of course you want pages and pages of
postscript code ;-).

>Thanks for any help.
>
You're welcome.

Paul Hethmon
Programmer/Analyst & IBM Certified OS/2 Engineer
Agricultural Policy Analysis Center
The University of Tennessee at Knoxville
hethmon@apac.ag.utk.edu  ==  615-974-3666

In article <370q6i$7ql@martha.utk.edu>,
Paul Hethmon <hethmon@apac.ag.utk.edu> wrote:
>In message <36ukdm$n8u@cpcug.org> - kbennett@cpcug.org (Keith Bennett) writes:
>
>>I'm trying to print a long Postscript file onto an HP LJ 4 MP.  I get
>>about 7 pages perfectly, but then the printer times out and I have
>>to explicitly tell the system to retry.  When I do, I get the
>>Postcript error:
>[munch]
>
>Ftp over to "wilma.cs.brown.edu" and pick up the postscript faq. It lists
>some sources and programs that can help. The one I have in mind
>is called "behandler.ps".  It's postscript code that you can download to
>your printer. When an error occurs, it prints out something a little more
>understandable. To load behandler.ps, just download (print) it to your
>printer.

I was having similar problems.  I don't have a printer here at home.  I
use DeScribe and print to a file, which I take to school and print there. 
I simply copy the file to the printer port (lpt1).  In order to avoid
having it crash on large file, I use the MODE command to change the number
of retries on lpt1 to infinite.  I forget the specific syntax (it's
something like MODE LPT1 /B), or even if it would work on an OS/2 machine. 
However, it might be worth looking into. 

JOHN
--
* John M. Martz:  Psychology Dept, UNC-CH  *                            *
|                 CB# 3270, Davie Hall     | B = f(P,E)                 |
|                 Chapel Hill, NC 27599    |          --Kurt Lewin      |
*                 JOHN_MARTZ@UNC.EDU       *                            *

In article <370q6i$7ql@martha.utk.edu>,
Paul Hethmon <hethmon@apac.ag.utk.edu> wrote:
>In message <36ukdm$n8u@cpcug.org> - kbennett@cpcug.org (Keith Bennett) writes:
>
>>I'm trying to print a long Postscript file onto an HP LJ 4 MP.  I get
>>about 7 pages perfectly, but then the printer times out and I have
>>to explicitly tell the system to retry.  When I do, I get the
>>Postcript error:
>[munch]
>
>Ftp over to "wilma.cs.brown.edu" and pick up the postscript faq. It lists
>some sources and programs that can help. The one I have in mind
>is called "behandler.ps".  It's postscript code that you can download to
>your printer. When an error occurs, it prints out something a little more
>understandable. To load behandler.ps, just download (print) it to your
>printer.
>
>Another thing to try would be to pick up ghostscipt/ghostview and see if
>they can display it. It might be that there is an error in the file. Or try it
>on another printer.
>

Well I had the same sort of problem running a LaserJet-IIP with A pAcific Page 
postscript cartridge. It is pretty slow processing the postscript (especially
if bitmap images are being sent) and OS/2 whines about it with its little
pop-up. If I hit "retry" or just ignore it(!!!!!!!!!) it prints fine but the
popup and beep keeps happening every thritysecs or so and it drives me nuts!
I set the timeout to 999 but it doesn't seem to change anything - every 30
secs "BEEEEEEEEP".

In <1994Oct7.085304.29205@cs.sfu.ca>, chapman@cs.sfu.ca (John Chapman) writes:
>I set the timeout to 999 but it doesn't seem to change anything - every 30
>secs "BEEEEEEEEP".

I have the same experience. The timeout setting on the port does not seem
to matter. I get the box every 30 seconds or so. Is this a bug or
a feature ?

************************************************************************
* Stefan Zollner, Assistant Professor and Associate Physicist          *
* Iowa State University/Ames Laboratory, A205 Physics, Ames, IA 50011  *
* zollner@iastate.edu    Phone: (515) 294-7327     FAX: (515) 294-0689 *
************************************************************************

>>>>> "sz" == zollner  <zollner@iastate.edu> writes:

    sz> In <1994Oct7.085304.29205@cs.sfu.ca>, chapman@cs.sfu.ca (John Chapman) writes:
    >> I set the timeout to 999 but it doesn't seem to change anything - every 30
    >> secs "BEEEEEEEEP".

    sz> I have the same experience. The timeout setting on the port does not seem
    sz> to matter. I get the box every 30 seconds or so. Is this a bug or
    sz> a feature ?

Odd. Printing to my HP LJIII (with HP PS cartrige, Level 2) I don't
have these problems. I usually actually print to the IBMNULL driver
(dumping from the command line to lpt1), and yesterday printed a paper
with a 2.6Mb graphics file embedded in it - it took over an hour for
just that one page to print, but I never got a pop up error box.

Richard Stanton