On Sat, 9 Jun 2001, Michael Lindner wrote:
> I agree, it IS wierd, and I spoke too soon - not having repeated all the tests
> I made. What I did was to run "gs ... file.ps" into a file, and send the file
> directly to /dev/lp0 in 1000 byte chunks at 1/10 second intervals. That worked,
> whereas "lpr file.ps" did not, so I assumed it was parport's fault. What I
> didn't try again, and should have, was "gs ... file.ps > /dev/lp0". Voila, it
> works! So, the problem now appears to lie with lpd and NOT parport. My
> apologies. Any clues on what to do now?
If I had to guess, I'd say you had gs-6.50 installed and were printing
a PostScript file produced by the Acrobat reader. If so, you have a
known problem. If you look at the command that lpd executes, it is
gs ... -
i.e., the input is coming from stdin. gs has a bug with certain files
coming on stdin, in particular those produced by Acrobat reader. If
you do the same command line with a filename argument (as you did), it
works just fine. I would try upgrading to gs-7.00 (although that has
its own collection of bugs) and see if that works.
I'm not sure this explains everything you're seeing, but it may be
part of it.
-- J. Scott Berg email@example.com 12 ROLLING HILLS DR (631) 924-8613 RIDGE NY 11961
-- To unsubscribe, send mail to: firstname.lastname@example.org -- -- with the single word "unsubscribe" in the body of the message. --
This archive was generated by hypermail 2b29 : Mon Jun 11 2001 - 22:24:17 EDT