On (17 Jul 95) Paul Edwards wrote to Roy McNeill...



 RM> When my Sweatsock gives this response, it normally means that the

 RM> line was too foul for the modems to negotiate an MNP/v42 (whatever)

 RM> error correction. After this, the modem invariably starts receiving

 RM> almost pure junk. I get several connections like this per year, and

 RM> some time ago told the modem to &M5 to save me the trouble of

 RM> hanging up.



 PE> Can you give me some idea of the % of MONITORED calls that you have

 PE> had in the past 6 months that connected successfully?  BFN.  Paul.



Not really, I vaguely remember only one in six months, maybe four

more before that. I have had a problem with the fossil driver,

though - if I use it to talk to Drip on com1, then I have to power

down the pc before I can use it on com3 for the modem (i don't have

a reset button, that's on the tuit list). I've probably done that

wrong five or six times this year - the modem dials out, connects,

goes quiet, and sits there like a stuffed dummy. I guess the receive

interrupt is stuffed up somehow. You can probably see it in your

logs - connect, no id, hangup, then me connecting a couple of

minutes later. I never actually confessed to it because every time

it happened I would swear on a stack of dead cats that I wouldn't

do it again.



cheers



... 25/13



--- PPoint 1.88