BL> The phone rings, Paul picks up, there is a sub-second's pause,
 BL> and then I get BUSY. If I ring straight back, it's BUSY.

 BG> Yep, that's EXACTLY the same symptom that I was seeing here,
 BG> although I seem to recall that it started happening during the
 BG> final 2 weeks of his running the Viper, and went away once the
 BG> M34F was on-line.

  It did it once with the Viper (on the last day, I think), and with
the Netcom it's worse. It's something to do with the timing of the
rings.

  This morning It gave me BUSY twice, and then worked. The phone rings
(brrt, brrt), there is a pause and the phone begins to ring again, and
then it disconnects and I get BUSY. The time it worked, the phone only
rang once (brrt), paused and rang again (brrt, brrt)... and picked up
normally when Paul sent the signals.

  I've changed nothing at this end, but it sounds like *my* problem.
The Sportshoe isn't waiting long enough for something to happen, but
S7 is set at 60 seconds, and what else is there? Is it possible that
my 0.6 second carrier recognition (S9) is too long, or S10 at 0.7 is
too short?

  It's been working that way for 3 years, though.

 BG> The really unfortunate aspect from your POV is that you will
 BG> have been charged for those calls, whereas I won't (at least I
 BG> hope that's the case), because the charging doesn't begin until
 BG> the STD pips have ceased, and mine never gets that far. Oh
 BG> well, the bloody phone bill is almost due, so I guess I'll soon
 BG> find out...

  Yair! I'm averaging two-for one. It's like Russian roulette; I never
know if it'll go off.

 BL> From that I assumed it might be me hanging Paul's modem.

 BG> No, I think you can safely apportion the blame to somebody else
 BG> here. :) 

  What would make the Sprortie think it was BUSY when it wasn't?

Regards,
Bob
___ Blue Wave/QWK v2.12
@EOT:

---