Re: [hylafax-users] Premature EOL?

[Lee Howard <faxguy@howardsilvan.com>]

On 2002.08.12 06:45 Thomas -Balu- Walter wrote:
> Any idea what causes incorrect(?) tifs? I get some warnings while trying
> to convert my incoming faxes to PDF, like:
> 
> # tiff2ps /var/spool/hylafax/recvq/fax00005.tif > A.ps
> Fax3Decode1D: Warning, /var/spool/hylafax/recvq/fax00005.tif: Premature
>         EOL at scanline 2297 (got 0, expected 1728).
> Fax3Decode1D: Warning, /var/spool/hylafax/recvq/fax00005.tif: Premature
>         EOL at scanline 2298 (got 0, expected 1728).
> Fax3Decode1D: Warning, /var/spool/hylafax/recvq/fax00005.tif: Premature
>         EOL at scanline 2299 (got 0, expected 1728).
> Fax3Decode1D: Warning, /var/spool/hylafax/recvq/fax00005.tif: Premature
>         EOL at scanline 2300 (got 0, expected 1728).
> Fax3Decode1D: Warning, /var/spool/hylafax/recvq/fax00005.tif: Premature
>         EOL at scanline 2301 (got 0, expected 1728).

This ("got 0, expected _____") is a bug from an old viewfax version that 
was perpetuated into libtiff and HylaFAX.  libtiff was fixed a few years 
ago.  HylaFAX was fixed in 4.1.3

You can have yet other "Premature EOL" errors with HylaFAX depending on 
how badly the modem firmware handles corrupt data.  But these errors here 
are fixed now.

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
 On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*