At 05:01 PM 2/15/01 -0500, Dave Lovelace wrote:
>Lee Howard wrote, in part:
>> 
>> I've also experienced the same trouble with LPRng-3.6.something (before I
>> upgraded).  I see this when printing from any Windows system
>> (NT/2000/98/95/ME).  It usually occurs in the middle of a graphic (as in
>> the example), and sometimes the error only surfaces as a line on the page
>> rather than a bunch of characters.
>> 
>> Could someone be so kind as to point me in the direction of where to look
>> for a solution?
>> 
>Well, it's just a guess, but ... is the print job going to a raw print queue,
>ultimately?  If not, I'd suspect that some character is being translated
>(say, newline -> CR+newline, when the newline really means its ASCII value
>of 10) in the middle of a graphics sequence, making hash of stuff for a
while.
>
>We've certainly seen that in a different environment (SYSV lp/lpsched,
>long ago, about SVR3).  In that case, making sure the queue was raw (doing
>no translations, implemented by making sure that "-o stty=raw" was always
set)
>was the cure.

I don't mean to sound ignorant, but do I set these options in lpd.conf, or
how do I tell if I'm already using a raw print queue?  I'd be happy to read
documentation, only I don't know which documentation to read.

Thanks.

Lee Howard


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to