Re: [hylafax-users] Bad 1D/2D pixel counts and invalid code words

[Lee Howard <faxguy@deanox.com>]

At 03:55 PM 4/12/01 -0500, Dennis Fellows wrote:
>Well, I upgraded to beta3 with no prob and set my session tracing to 0xFFF.
>I haven't experienced any Faxgetty hangs (yet)!
>
>I've got some questions as to what the errors are. I waited for at least
>three faxes to come in to make sure that the errors were typical (they
>were). Now, I know that I may be dealing with line noise (I've given up
>fighting with my local telco (Ameritech) and am moving to a local T1 from
>another phone company) but I want to make sure these errors are not config
>errors. Here is a typical log with my questions interspersed (**)....

>Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1053, got 0,
>expec
>ted 1728
>Apr 12 14:06:18.16: [ 6035]: RECV/CQ: Bad 1D pixel count, row 1054, got 0,
>expec
>Apr 12 14:06:18.32: [ 6035]: RECV: 31208 bytes of data, 1055 total lines
>
>** This is typical : I get 5 lines in a row at the end of a page that error
>then an "adjusting" statement**
>
>Apr 12 14:06:18.32: [ 6035]: RECV/CQ: Adjusting for RTC found at row 1049

Perfectly normal.  This is just verbosity from HylaFAX's copy quality
checking routine.

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null