PE> If it is, it's fucked by design.  Name one bit of software
PE> that will wait for the modem to respond at 38400, and then
PE> quickly switch up to 57600 in case a ring comes through?

DD> Name one sane person who would lock their modem at 57,600 and then
DD> promptly set their software to 38,400 to communicate with it . . .

They may well issue a &W command and MONTHS later change their port speed
tho, and expect the RINGs to be displayed at the speed of the last AT
command, even if thats an ATZ command. Just like all the other modems do.

PE> The modem was never locked at 57600, it merely happened
PE> to be the speed the com port was set at at the last &W.

DD> That is how you lock the speed into the Courier . . . .

Fucked by design, when there is no good reason for doing it like
that, differently how ALL the other modem manufacturers do it.
Let alone not even bothering to document that the ATZ command *ALONE*
does it differently to how all the other modem manufacturers do it.

PE> That actually happened on my DOS system, and on my OS/2 system
PE> the rate was set to 38400 (which is what I wanted).  Then I had
PE> planned on changing it to 57600, and perhaps 115200 one day, as
PE> an experiment. So now I've told you the reason why I chop and
PE> change baud rates as required.  Now you name the software that
PE> jumps up from 38400 to 57600 after issuing an ATZ.

DD> None that I know of.  I still want to know why you would set your
DD> software to 38,400 after you have locked your modem speed to 57,600?

Because people do change their port speed at times, and it doesnt make
the slightest sense for USR modems ALONE to be fanging your arse in that
situation, ONLY when you have ATZ for a modem init string. FOR NO GOOD REASON.
@EOT:

---