Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!uunet!seas.gwu.edu!timur
From: timur@seas.gwu.edu (The Time Traveler)
Newsgroups: comp.windows.ms
Subject: Re: Debugging PostScript problems in WIN3.0?
Message-ID: <2999@sparko.gwu.edu>
Date: 6 Apr 91 06:18:17 GMT
References: <1991Apr4.224731.23858@odin.corp.sgi.com>
Reply-To: timur@seas.gwu.edu ()
Distribution: na
Organization: The George Washington University, Washington D.C.
Lines: 28

In article <1991Apr4.224731.23858@odin.corp.sgi.com> nelson@bolyard.wpd.sgi.com (Nelson Bolyard) writes:
>There's a whizzy Macintosh program that lets you monitor the data beint
>sent to and messages received from a locally attached PostScript printer
>(e.g. one attached directly to a port on the MAC, not on a net).  The sent
>and received data are shown in real time in two windows on the MAC screen.
>It's great for debugging problems when your printer doesn't like the
>PostScript it's being sent, for some reason.  I sure wish I had a similar
>program that runs under WIN3.0 in 386Enh mode.

Go to the control panel.  Select PRINTERS.  Select a Postscript printer,
and go to the setup menus.  On one of them, hit ALT-E.  This is an
*undocumented* feature that allows you to print an error handler.  

I haven't tried this thing out yet, but I'd like to hear about it.

>I've also heard about a Public Domain file of PostScript commands called
>ERRHAND.PSC that directs the PostScript printer to print out on paper a
>pretty complete analysis of any problem it encounters with a PostScript
>document.
>

I'd like a copy, too.  Perhaps someone could post it?

----------------------------------------------------------- The Time Traveler
I used to love her                                          a.k.a. Timur Tabi
But I had to kill her                            Internet: timur@seas.gwu.edu
I had to put her six feet under                  Bitnet:         HE891C@GWUVM
And I can still hear her complain  - Guns 'n Roses