RS> All the calls on Thurs am were with MNP4 only enabled and allowing a
 RS> fallback to no protocol if MNP4 couldnt be obtained. In contrast to the
 RS> previous calls which have demanded MNP4 else hangup.

Hopefully you have seen my Binkley log and can match up connects.

 RS> If anything the new approach is worse, mainly because the non protocol
 RS> calls dont work for some reason and it takes longer to drop out for a
 RS> retry.

Probably because my end thinks it's connected with MNP4 and takes a while
before it hangs up, unlike previously when it was your end hanging up.

 RS> Not too clear why the non protocol calls dont work. Presumably the line
 RS> noise is to great and Binkley or your modem gives up.

I doubt that there is any line noise.  I never see the MR light flashing
either - I presume it is supposed to flash for MNP4 as well as V42.

So I'm still proposing the theory that the problem is some timings of the
MNP negotiation.  My end thinks it has MNP4 and yours doesn't.  Can you
tell me what the sequence of MNP negotiation is, and which S-register
settings would govern that.  Thursday morning after you had called
successfully the first time, you called again and I got a lot of straight
14400 connections.  What did you get???  MNP4?  You should have been able
to log on, I would have expected both to be 14400.  Anyway, why don't you
try forcing MNP4, and if you don't get it, disable it completely, and see
what happens.  Presumably you will log on, do a file transfer, and find not
a single Zmodem error, which means the problem is not line noise.  BFN.

Paul

--- GoldED 2.40