On Feb 21, 1996 at 22:23, Paul Edwards of 3:711/934.9 wrote:

 PE>> AT\V9
[...]
 PE> Whoops, this was a deadly combination.  After 7 aborted calls, none...

Dunno 'bout BTPE, but other versions of Binkley have a hard-coded limit to
the number of characters they will receive during the initial connection,
and AT\V9 easily overflows that limit.

 PE> AT\V9 and AT%U2 do not return CONNECT anything

Yes they do - as you noted later, Bink was objecting to something in the
\V9 response (the word "error").  I've had no problems outside
Bink with \V9%U2.

 PE> AT\V8 and AT%U2 do not return CONNECT anything

Probably same as above - dunno don't use \V8.

 PE> AT\V1 and AT%U2 seem to produce the best CONNECT string

That's what I use.

 PE> AT\V8 and AT%U0 return a CONNECT string with "REL" in it,
no more info.
 PE> AT\V0 and AT%U0 (default) return just CONNECT xxx

That's what the on-line help says.

 PE> Anyway, one thing this has shown is that I am getting solid
 PE> connects at 26400 instead of 28800.  BFN.  Paul.

I've called you twice since you installed your M34F - both times, first go:

                    Connect 28800/Lap-M/V.42Bis/V.34

The second time was as a bboard user, and for a while I kept +++'ing and
playing around with retrain and rate change options - I also ran AT%Q a few
times to check line quality.  The response was 021 a few times (poor), and
008 a few times (okay).  In response to most "ATO" commands, the
modems retrained back at 28.8Kbps although once they retrained down to
24.0Kbps.

I was using \V9%U2 to check the reconnect/retrain speed.

 PE> P.S. What I was trying to achieve in the first place was a single
 PE> line connect string that told me what EC was used, and whether
 PE> compression was on.

In which case, \V1%U2 is definitely the way to go.

    - dave
    d.begley{at}ieee.org

---