PE> In fact, it MAY even bee just the word "RING".  What I really
PE> need to do is set S0=3 and then see what happens when an incoming
PE> call comes.  The RINGs will be garbage, but what about the CONNECT?

BG> Just tried it.  Here's the sequence if you wish to verify it...

BG> 1. Start LW/2 with both the DTE and the USR locked to 57600 bps.

BG> 2. Enter ATS0=2 (before the term's bit rate change, otherwise the
BG> modem will autobaud to the new setting with this command).

BG> 3. Change LW/2's DTE rate to 38400.

BG> 4. Immediately call the modem from an _external_ source.

Yes, thats a valid test.

BG> The modem rings, but gibberish is displayed on the terminal
BG> screen. However, after 2 rings, the modem still answers as
BG> expected, then attempts to negotiate a connect.  I'd need
BG> another modem to confirm that they'd actually connect
BG> properly though, but I'd fully expect them to do so.

Yes, but THEN when your modem tries to send the CONNECT text back
to the software behind it, it will obviously do so at 57600 like
it clearly did with the RING text, and so the software behind the
modem wont be able to do anything useful with the call at all.

Without an AT from the modem, the modem has no way to know what
speed to send the CONNECT out at. Or more strictly, the only one
its seen is the one at 57600, so it will do so at THAT speed.
@EOT:

---