Rod, at 07:37 on Feb 03 1996, you wrote to Dave Hatch...

DH> After a reset, the modem has no record of the DTE baud rate -

I've been able to reproduce the problem which Paul had detailed re his
serial port mismatch, and have posted it here for a wider distribution...

============================================================================
Well, I believe I've seen the symptom which you describe (at long last) and I 
can seemingly reproduce it at will by starting Livewire/2 with COM2 locked to 
38400 bps, whilst the modem's serial interface has been saved at 57600 bps.

If I induce a RING on the line by dialling 199, the modem responds with garbage 
characters instead of the normal RING result code, and will continue to do so 
until such time as any command (OTHER THAN ATZ) is issued, at which time the 
new speed is "saved" to NVRAM, the modem then reporting RING correctly.

This is certainly peculiar behaviour, I'll agree, although it's not really the 
end of civilisation as we know it.  Especially as I was able to fix the problem 
almost immediately.  Seems that this only occurs when the terminal is first 
started, but once any AT command has been issued (apart from ATZ, for some 
obscure reason), the anomaly disappears permanently from that session.

And now for the strangest aspect of all, re this complete and utter weirdness, 
the one AT command which does NOT auto-baud the serial port is (of all things) 
ATZ !  This basically means that if ATZ is used as a generic initialisation 
string, the very first RING response on an incoming call after starting the 
program, is going to be garbage.

The fix, however, is dead easy.  Rather than use ATZ^M as Livewire's init$, I 
simply changed it to AT&F1^M instead (no &W write command, of
course).  Unlike 
ATZ, AT&F1 allows the serial port to auto-baud correctly, as you'd expect.  The 
same init$ change solved this anomaly in all of my other comms apps too.

PE> Aha, the man suddenly understands what auto baud rate detect is
PE> in this context.

But that's been my understanding all along.  What it DOES do though, is match 
the current and stored baud rates without saving them permanently.  And if I 
read you correctly, you appear to be complaining that the FIRST incoming RING 
is being seen as garbage by the modem, then subsequent RINGs are OK, is that 
correct (because that's precisely what I'm seeing with mine) ?
============================================================================

Regards, Bill

--- Msgedsq/2 3.20