![]() |
On 4/12/06, Lee Howard <faxguy@xxxxxxxxxxxxxxxx> wrote: > What you're probably seeing is the effect of what a non-zero > time-per-scanline setting does to the sender. In non-ECM mode receivers > have the option of specifying a scanline-time setting (5 ms, 10 ms, or > 20 ms) that limits the sender as to how much time communication time > must be consumed by each scanline (to add time to a scanline the > scanline is padded with zero-bits)... at least this is the only time > that I can reproduce the smaller transmission datasets. I verified this issue is only with scanline > 0; with scanline=0 I get the usual 102x bytes. I verified that with a 4.2.1-cvs20050305 I get 102x bytes with scanline > 0. All the machines I manage with 4.2.5 have RHEL3, while older HylaFAX versions are with rh6x, can this be a compiler issue? Today I'll try reverting a rhel3 machine to a previous HylaFAX version and test again. -- giulioo@xxxxxxxxx ____________________ 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@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*