BG> You and Paul better get together and argue the point,

RS> No thanks, we are BOTH saying the same thing.

He's right.

BG> as he reckons it WASN'T the lines, but dodgy code in the USR.

RS> Nope, we are both saying that the code is clearly the problem if the rom
RS> change fixed that, and we are both saying that with the less than the fixed
RS> code, that particular fault is much worse on a poor line, evidenced by the
RS> fact that only you were seeing it with the V32bis Sportster. You were also
RS> getting quite obscene results calling CHH from your poor home line, but
RS> not when using the much better line you used when working there.

Translated and modified:

1. The problem may only be seen on the combination of line conditions
seen with both you and me.  I am not sure that we have enough test
results to know whether this problem only happens on 2 bad lines, 1
bad line, or 0 bad lines.

2. When the problem was happening, it was a sign of AT LEAST 1 modem
violating protocol, and BOTH modems having deficient code.

3. USR either stopped violating protocol, or they provided more robust
code.  Most likely the former.  Only they and Netcomm can answer that
for sure, and they are both a bunch of wankers so we'll never know.

BFN.  Paul.
@EOT:

---