BG> Init      ATZ|
BG> TermInit  ATZ|
BG> Prefix    ATDT
BG> Answer    ATA|
BG> PreInit   |v``^``
BG> PreDial   `
BG> Aftercall 34 ATI11I6|
BG> [ ... ]
BG> Of course, the fact that the Aftercall commands are issued _before_ the
BG> modem reinitialises may just have something to do with it.

You've still got me puzzled here, after my 2.60 tests, as reported to Poe. 
It takes your PreInit (DTR drop) to even hangup and get back into command
mode.  Why it would then miss your ATZ init, I don't know, unless it's sent
too soon.

 BG> Dunno, I used the same cfg file with 2.59EE, but not with
 BG> earlier versions as I wasn't aware of the Aftercall command
 BG> until relatively recently, and all of my V.34 USRs have had
 BG> their stats logged by Binkley, without any problems.

Well, I believe you - just can't figure out why.  I don't know whether EE
(never heard of a 2.59EE?) had different hangup behaviour, or what?

IS> Hitherto, the PreInit then Init strings were what were always used to
IS> hangup the modem, after which AfterCall was issued, which had meant that
IS> Courier users could not use ATZ in their PreInit or Init.

 BG> Trouble is, there are so many hacked versions of Binkley
 BG> doing the rounds, that one can never really be sure of
 BG> their respective origins.  I'll take your word for it that
 BG> this is how Bink used to function, though.  :)

Well the DOS version hasn't changed, and it's a common code base with the
OS/2 version - you're not using a non-BitBucket version yourself?

IS> Unless of course USR changed the modem to keep the stats after ATZ, which

 BG> No, ATZ definitely clears the last call stats here, and
 BG> this is with the very latest US SDL code dated April 29.
 BG> Looks like Bink has changed instead.

Beats me, then .. I've not heard of any way to get a look into the Rx/Tx
buffers in OS/2, so perhaps it will remain one of those little mysteries.

Cheers, Ian

--- MaltEd 1.0.b5