TIP: Click on subject to list as thread! ANSI
echo: locsysop
to: Rod Speed
from: Bill Grimsley
date: 1996-02-10 07:42:46
subject: USR Courier

Rod, at 10:22 on Feb 09 1996, you wrote to Bill Grimsley...

DD> For a bug it seems well documented.

BG> Furthermore, only Paul Edwards thinks it's a bug,

RS> Nope, the ATZ quirk is clearly a bug, and ISNT documented AT ALL.

Dunno, I've played around with that some more since last time, and I can't
repeat that sequence at all.  I'm sure I'm not doing anything differently
either (maybe the first example was flawed?).  The only time I get
gibberish on an incoming RING is if I change the port speed in my comms app
without issuing an AT command (other than ATZ) to the modem.  I can't even
use ATI4 to check the modem's port speed, as that immediately auto-bauds
the modem and then shows the same as the app's altered speed.

I don't accept that the failure of ATZ to auto-baud the modem is a fault or
a bug at all.  In fact, I'm more inclined to suspect that it's been done
that way intentionally for some obscure reason (but yes, it should be
documented).

BG> whilst the other 5 million Courier owners are obviously too thick to 
BG> realise it...

RS> Well, if you never change the port from the speed used for
RS> the &W you wont see the bug, so thats hardly very surprising.

Can you give me just one valid reason for even needing to alter the port
speed on the fly?  Not these days, although USRs have been around since the
days that EC (i.e. bit-stripping) was the exception rather than the rule
(my own Courier is date-coded 1988).

RS> And since it only affects ATZ, even those who do use a port speed thats
RS> not the one that was used in the &W wont see it unless they only have an
RS> ATZ modem init string. And presumably most of those dont use their modem
RS> for incoming calls so wont notice the RING effect even if they do either.

Aside from the gibberish response, the mode still works though.

RS> Its an absolutely classic genuine bug, not documented AT ALL.

Nope, I can't believe that USR aren't aware of that behaviour, as fixing it
would be a trivial exercise in their flash-ROM code.

Regards, Bill

--- Msgedsq/2 3.20
* Origin: Logan City, SEQ (3:640/305.9)
SEEN-BY: 640/305 711/934

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.