On Dec 02 20:31 96, John Piper of 3:712/841 wrote:

JP> Last week, and just five minutes ago, I discovered that my Courier would 
JP> not answer any inbound calls. Several tests with my other line and mobile 
JP> proved that there was a definite problem. The auto-answer LED on my 
JP> Courier's panel would flash while the line was ringing, but my mailer would 
JP> fail to show any signs of a RING signal. Jumping into terminal mode, I 
JP> dialled my line again. ASCII garbage of equal amounts would echo to the 
JP> screen in place of a RING.

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

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

I used to own a Trailblazer which did exactly this - it would forget,
taking about a fortnight or a month to get it done.  The permanent fix was
a maintenance routine running in the weekly BBS housekeeping cycle.

Theory might be that the number of write cycles for which it's a
"permanent" write has been exceeded.  (My TB didn't worry much
though - ran it like that for years.)

Nothing definitive - but that's what I saw, and did.

Regards,
Dave Hatch.

--- Msgedsq 3.20