Paul, at 23:06 on Jan 25 1996, you wrote to All...

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. 

Not at all.  What's happened is that because you loaded the SDL with a
locked baud rate of 57600, that has also been written to NVRAM.  If you
attempt to run it at 38400, you'll get a baud rate mismatch until you issue
any AT command to match the speeds.

PE> I 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.

Not really.  It's a strange quirk with the USRs (dunno if it applies to
Rockwells, I've never checked).  All you need to do is run up your
favourite comms app with the baud rate set to whatever you prefer - I
strongly recommend at least 57600 for the V.34+ 33k6, as it transfers
compressed files at around 4000 cps (which is too fast for a port speed of
38400 anyway) - then do an AT&W to write this baud rate to NVRAM.

BTW, all you need as an init$ is AT&F1&W.  Then ATZ as your Terminit.

Regards, Bill

--- Msgedsq/2 3.20