Path: utzoo!utgpu!news-server.csri.toronto.edu!torsqnt!hybrid!robohack!eci386!clewis
From: clewis@eci386.uucp (Chris Lewis)
Newsgroups: comp.lang.postscript
Subject: Re: Printing bitmaps in postscript
Message-ID: <1990Jul6.202241.7182@eci386.uucp>
Date: 6 Jul 90 20:22:41 GMT
References: <1990Jul5.172746.10305@dvinci.usask.ca>
Reply-To: clewis@eci386.UUCP (Chris Lewis)
Organization: Elegant Communications Inc.
Lines: 21

In article <1990Jul5.172746.10305@dvinci.usask.ca> eric@dvinci.usask.ca (Eric Neufeld) writes:
> I am experimenting with halftoning algorithms, ...
 
> But the printer frequently *just doesn't print* and leaves me no clues.
 
> Any ideas of where to start troubleshooting?

Most postscript printers will transmit back up the serial line to the
computer various diagnostics.  Eg: if you had a postscript printer hung off
/dev/ttyab, you could spawn a "cat /dev/ttyab > /tmp/logfile" in
the background and examine /tmp/logfile after your file blackholes.
Note: depending on a number of things, you may have to write this
as a C program that setbuf's output as unbuffered or something so
that you see the output as soon as the printer spits it back.

Alternately, you can use "ehandler.ps" which will print a stack
traceback onto paper on error.  This gets posted frequently, so
you should be able to find it.
-- 
Chris Lewis, Elegant Communications Inc, {uunet!attcan,utzoo}!lsuc!eci386!clewis
Ferret mailing list: eci386!ferret-list, psroff mailing list: eci386!psroff-list