Re: [hylafax-users] [hylafax-devel] Re: No response to MPS again

[Lee Howard <faxguy@deanox.com>]

At 08:31 PM 3/28/01 +0400, Vyacheslav Frolov wrote:
>You can fix that by 3 ways.
>
>1. On the receiver's side where the receiver is a ZyXEL Class2.0
>disable modem copy quality checking. For example by
>
>Class2CQQueryCmd:      AT+FCQ=0,0;+FCQ=?

Wouldn't "!(0),(0)" provide the same results?

>2. On the sender's side disable page chopping.
>
>3. On the sender's side patch HylaFAX:
>
>-------------[cut]--------------
>--- faxQueueApp.c++.old Wed Mar 28 20:06:24 2001
>+++ faxQueueApp.c++     Wed Mar 28 19:51:29 2001
>@@ -841,6 +841,12 @@
>        u_int topMargin = 1*98;                 // 1" at 98 lpi
>        if (params.vr == VR_FINE)               // 196 lpi =>'s twice as many
>            topMargin *= 2;
>+
>+       /*
>+        * Skip at least 200 rows. ZYXELs like it.
>+        */
>+        if( topMargin < 220 ) topMargin = 220;
>+
>        do {
>            (void) decodeRow(NULL, rowpixels);
>        } while (--topMargin);
>-------------[cut]--------------

Is this something that should be applied to HylaFAX codebase as a whole, or
only applicable in the case of Zyxel modems?  If the latter, then perhaps
we should make a config option,

ModemTopMargin:	topMargin

and commit the above patch allowing for variable topMargin value?

Lee.



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