DD>> I initialised my modem with AT&F1&W - I reset my modem with
DD>> ATZ
PE> "I set up my modem with AT&F1&W - I use ATZ as my
PE> initialization string".
DD> Initialise - from "initial", meaning first. ATZ resets a
USR modem to it's
DD> stored settings, it says so in the documentation
And I bet they don't recomment "&W" in an initialization string.
And initialization string is what you send to your modem EVERY
time after power up, before usage.
DD>> Both of these commands have been/are issued at the SAME
DD>> port speed.
PE> Yeah, good idea. It avoids the problem of the USR not doing
PE> auto-baud-detect on ATZ like every other modem in the world.
DD> The USR also does HST unlike every other modem in the world. It is unique,
DD> it's ATZ command behaves EXACTLY as documented,
Where is it documented that it won't auto-baud-detect on the ATZ
command, although it auto-baud-detects on every other command?
Reality to David, reality to David. It isn't even documented
that it auto-baud-detects AT ALL, nevermind that it does, and that
ATZ is the one and only command that fails to auto-baud-detect.
EVEN AT&F auto-bauds.
DD> unlike every other modem in the world.
I've never seen any other-brand modem document that ATZ won't
auto-baud-detect, whilst every other command will.
Which is pretty fortunate really, since there are NO terminals,
and NO comms programs, which will automatically detect that you
just issued an ATZ command, and are thus expecting the baud rate
to change, and so quickly change port speed to cope with this,
the port speed which they saved away on hard disk when they last
saw you issue an "AT&W" command. Sorry David, there is NOT
terminal, NO comms program and NO reason to NOT auto-baud-detect
on the ATZ like every other modem. BFN. Paul.
@EOT:
---
* Origin: X (3:711/934.9)
|