Paul, at 18:12 on Jan 30 1996, you wrote ...

PE>> I loaded the software from DOS using a baud rate of 57600.
PE>> When booting under OS/2, despite my bt.cmd having a mode
PE>> command setting it to 38400, and my binkley.cfg with a 
PE>> baud rate of 38400, the bloody thing writes junk instead
PE>> of "RING".  I had to set the mode command and binkley.cfg
PE>> to 57600, and now it is getting a "RING" through.  This
PE>> means that the USR isn't doing auto-baud rate detect.  I
PE>> mean, the bloody thing is accepting my ATZ etc, and even
PE>> responds with "OK", it's just the "RING"
that it decides
PE>> to send at a different baud rate.  Bizaare!  BFN.  Paul.

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.

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

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

The locked speed stored is the speed of the _LAST_ AT&W command.  That
is how one sets the LOCKED speed.

David
@EOT:

--- Msgedsq/2 3.10