PE> Yeah, 1.5 seconds negotiation is about what everyone else is getting.

RS> Yeah, thats what it looks like from my logs. One real deficiency with
RS> the FroDo log is that its only got a 1 second resolution which is a pity
RS> when looking at that detail. I might Awk the logs and do some stats.

PE> Binkley 2.60 only has 1-second resolution.

RS> What are you adding that was missing from the standard 2.60 ?

PE> 1/100 second resolution in logs.

How dare you ?

PE> AT commands get printed out. Not case folded either.  Case-sensitive
PE> comparison of "ERROR" etc so as to not get a match on
Netcomm's "Error
PE> Correction" string, also more stringent matching on the string, so as
PE> to not match on Netcomm's debug info "OK, trying xxx".

Dunno, I wondered if the general concept of that stuff
is wrong now when we want to get all that status/debug
stuff auto. Havent thought that thru carefully tho.

PE> Fixed bug in Wazoo session with product >255 causing trap.  Protect
PE> against control characters in the log. Also I intend to add
"afterconn".

Yeah, those USR stats are fucking amazing, you certainly
do want to be able to allow the user to just turn them on
and have a decent system of auto stats on every call.

I have also been thinking about just say FREQing a file
you know wont be there, just as a very cheap stats call.

One real deficiency on that currently is that it would be nice if the stats
could interrogate the full model/version/code etc data from the other modem
and include those too. I dont even know if V34 makes any provision for that.

With that lot, you really could then have a fully auto system which fired
of some calls and just told you all there was to know about your phone line.
And you could do another any time you wondered if your line had gone bad etc.

Interesting times modem wise.
@EOT:

---