Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[hylafax-users] Premature EOL?

0 views
Skip to first unread message

Thomas -Balu- Walter

unread,
Aug 12, 2002, 9:45:11 AM8/12/02
to hylafa...@hylafax.org
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).

Balu

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

Thomas -Balu- Walter

unread,
Aug 12, 2002, 1:04:07 PM8/12/02
to hylafa...@hylafax.org
I've edited /etc/hylafax/FaxDispatch to attach PDF's:

# cat /etc/hylafax/FaxDispatch
FILETYPE=pdf
SENDTO=FaxMaster

The PDF's get sent, but the tagline is cut off, I can see the last lines
of it, but not complete...

If I view the .tif the tagline looks weird too. Is it possible that this
behaviour has the same base as the Premature EOL I've posted a few hours
ago?

What could cause such crappy taglines?

Tren Blackburn

unread,
Aug 12, 2002, 1:30:20 PM8/12/02
to hylafa...@hylafax.org
Hi;

It might just be me, but you're not converting to a PDF, you're
converting to a Postscript file. Is that what you meant?

Cheers,

Tren

> -----Original Message-----
> From: hylafax-us...@hylafax.org
> [mailto:hylafax-us...@hylafax.org] On Behalf Of Thomas
> -Balu- Walter
> Sent: Monday, August 12, 2002 7:46 AM
> To: hylafa...@hylafax.org
> Subject: [hylafax-users] Premature EOL?

Thomas -Balu- Walter

unread,
Aug 12, 2002, 1:35:49 PM8/12/02
to hylafa...@hylafax.org
On Mon, Aug 12, 2002 at 11:29:59AM -0600, Tren Blackburn wrote:
> It might just be me, but you're not converting to a PDF, you're
> converting to a Postscript file. Is that what you meant?

No, I was thinking of converting to PDF, but that is a two step process
:) tiff2ps | ps2pdf

Lee Howard

unread,
Aug 12, 2002, 3:30:45 PM8/12/02
to Thomas -Balu- Walter, hylafa...@hylafax.org
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.

0 new messages