Hello John!

Monday December 02 1996 20:31, John Piper wrote to All:

 > In both cases, I found that rewriting the modem's profile
(AT&F1&K3) did
 > the trick and fixed the problem; the Courier would once again recognise
 > RING and answer the call. I have no idea why this suddenly started
 > happening.

 > Anyone have any explanation for this odd behaviour? Could it be a fault
 > with NVRAM? I'd be interested in hearing people's thoughts on the matter. I
 > don't particularly want to rewrite my modem's profile regularly.

This sounds like it could be a problem Paul Edwards noticed a few months back.
After a reset with ATZ, the modem reverts to whatever port speed was used
to write the profile, rather than whatever speed was used to issue the ATZ.
If you wrote the profile at a different speed, and your init string was
just ATZ in FrontDoor, the modem would change its speed to that other speed
and give you garbage RINGs.

FWIW, I can confirm that my Supra does not have this problem. :-) I just
wrote the profile at 57.6k, then issued an ATZ at 9600, and called the
line; RING came out correctly.

Regards,
Hamish

--- GoldED/P32 2.42.G1219+