DD>> Read the docs VERY carefully.  Upon connect, the modem (com 
DD>> port) reverts to the baud rate set at the last AT&W or 
DD>> equivalent.

PE> For starters, the rings happen BEFORE a connect.  Secondly,
PE> the RINGs should indeed come in at 57600 BEFORE I send an
PE> AT command at 38400!  That's what auto baud rate detect is
PE> all about.  BFN.  Paul.

DD> OK, upon an incomming call . . . . the comport speed reverts to the speed 
DD> stored in NVRAM (which was set by the last AT&W or eqiv).

If it does that by design, the design is fucked.

DD> Auto baud rate detect is a phenomenom that is experienced on the PHONELINE 
DD> side of the modem.  When the "comport" speed is locked it
DOES NOT ALTER 
DD> FROM THE STORED SPEED.

There are two different things called "Auto baud detect".  One is
adjusting the port speed after a connect.  The other is syncing on
the "AT" command to figure out what speed the terminal is.  Try
it for yourself.  Go into Telix at 57600 and type "ATZ", no problem,
right?  Now change Telix to 38400 and type in "ATZ".  It works,
doesn't it?  That's because the modem AUTO BAUD DETECTED.

DD> The locked speed stored is the speed of the _LAST_ AT&W command.  That is 

NO IT ISN'T.  Try dialling out at 38400 (as above).  You got
the "CONNECT" back at 38400 too, didn't you?  And lo and
behold, you got your DATA back at 38400 ALSO.  Despite the
fact that 57600 is what did the AT&W.  Even if you get a 2400
bps connection, the &B1 will keep the com port locked (at the
speed of the last AT command) even AFTER a connect.  See now?
You might want to try reading this again, with the possibility
in mind that I might be right (because I am right).

DD> how one sets the LOCKED speed.

It's CERTAINLY not the way you set the locked speed on an
outgoing call.  It's CERTAINLY not the way you set the locked
speed for responses to AT commands.  The ONLY thing that I have
seen that uses the speed from the AT&W is the RINGs.  It is a
bug.  BFN.  Paul.
@EOT:

---