| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Courier on the fritz |
John, at 20:31 on Dec 02 1996, you wrote to All... JP> In both cases, I found that rewriting the modem's profile JP> (AT&F1&K3) did the trick and fixed the problem; the Courier JP> would once again recognise RING and answer the call. I have JP> no idea why this suddenly started happening. It happened because you altered your terminal's baud (i.e. bit) rate and neglected to save it to your Courier as well with AT&W. What happens is that when ATZ restores the modem's stored bit rate, it no longer matches, and the incoming RING resonse is not displayed correctly (no RING, no answer). JP> Anyone have any explanation for this odd behaviour? Could it JP> be a fault with NVRAM? I'd be interested in hearing people's JP> thoughts on the matter. I don't particularly want to rewrite JP> my modem's profile regularly. Most Courier owners eventually get caught out sooner or later, so don't feel too bad about it. As this anomaly is documented in the manual, it also tells me that there's a lot to be said for suggesting that one needs to RTFM. Regards, Bill --- MsgedSQ/2 3.50* Origin: Logan City, SEQ (3:640/305.9) SEEN-BY: 50/99 620/243 623/630 640/201 206 230 305 306 311 702 820 821 822 SEEN-BY: 640/823 829 711/401 409 410 413 430 808 809 899 932 934 712/515 SEEN-BY: 713/317 714/906 800/1 @PATH: 640/305 820 711/409 808 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™.