PE> I'm not sure if I described it satisfactorily...
PE> The last &W was done at 57600. I then go and use 38400. I type
PE> in ATZ. It auto-detects the AT and sends the response, "OK" back
PE> to me at 38400. I then proceeds to send the "RING" word to me
PE> at 57600. It's either designed wrong, or it's a bug. There is
PE> absolutely no sense in using two different baud rates to my session.
PE> Didn't happen with my Spirit II either.
PC> I just tried exactly what you explained above, my modem is set to
PC> 57600 normally i changed the terminal speed to 38400 and issued ATZ it
PC> returned OK with the port at 38400, i then rang the number the modem
PC> is on and it returned RING still at 38400.
PC> I'd say the Courier your trying out is a dud :-(
It has been reproduced by both Dave Hatch and Bill Grimsley.
Your result is very interesting. I have been able to
reproduce something that Bill just told me. The auto baud
detect is only screwed after an ATZ. If you then issue
another AT command, it fixes itself up.
If I type in ATZ
the rings come in at 57600
If I type in ATZ, and then type in ATS0=0
the rings come in at 38400
If I type in ATZ S0=0
the rings come in at 57600
Are you sure you didn't do some other AT command after the ATZ?
PC> Supervisor date 07/18/95
PC> DSP date 07/05/95
The problem occurred with those ROMs too.
BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|