PE> Rod, you are the first one to hit my new improved debugging info.
PE> I presume at 19:30 it was you that had a bad connect, and then
PE> immediately called again?

Yep, that was the classic very occasional thing I get, it connects fine,
I get CD and 14400 up and it just sits there. FD will eventually time out
and retry but I normally ESC abort it coz its dead obvious that its happened.

PE> On my end I got a connect of 14400, ie no error correction,
PE> and then I started to get garbage. What happened your end?

Thats what I get without any garbage. The modem front panel display
shows that too, a connect, 14400, no error correction. FD never sees
what it wants to see tho, presumably the last CONNECT string, but I
dont know that.

PE> I would expect modems to be able to connect at 14400 with no
PE> error correction and then be able to continue processing!!!

Yes, in fact I have done that on purpose and its worked. Your modem just
appears to go mental. We know it goes mental in other circumstances too.

PE> I don't know what causes the failure to negotiate error-correction in
PE> the first place though (ditto with Bill).  Is it likely to be line noise?

Yes, thats my bet, your modem has an imperfection in the handshaking which
can be made visible by noise at the wrong moment in the negotiation phase.
That early negotiation stuff between V32bis modems is a bit kludgy in some
ways and your modem just appears to have some warts in the code which can
bit it at times.

--- PQWK202