On Mar 21, 1996 at 07:03, David Drummond of 3:640/305 wrote:

 db>> The next line begins with "error" (for error-correction), so
 db>> Bink sees that and hangs-up;  unless you're using an
 db>> unmodified version of Bink (likely) that stops reading the
 db>> "connect string" after 50 characters or so...
 DD>
 DD> Ah so - one must hack Binkley to work with the M34F?  Gosh I just love
 DD> stuff that conforms to standards . . .

Well, there are two parts to this - Binkley 2.50 had a hard-coded
50-character limit (see my message to Paul) that stopped "extended
response codes" of this type, regardless of modem.

In this case, though, it's more than likely the fact that the next line has
the word "Error" which Bink sees as a dial/connection fault, and
hangs up.  If you can tell Bink not to bother with it in BINKLEY.CFG, then
great.

Otherwise, if you're just after simple EC/COMPR stats, just use the
one-line \V1 and be done with it.

Cheers..

    - dave
    d.begley{at}ieee.org

---