PE> Pity you saw the problem when I had a Spirit Viper
PE> here too.  And a Spirit Thunder for that matter.

BG> I'm not convinced that I did see 28800/NONE with the Viper
BG> (and I certainly couldn't have with the Thunder anyway).

RS> You have always seen /NONEs tho.

BG> 1 in 10 calls to the Thunder at V.32bis, 50% of calls
BG> to the NetComm at V.34 (all before the ROM change which
BG> completely solved the problem), but not at all to the Viper.

Thats not my recollection of the Viper story, but I could well be
remembering it wrong, and we will no doubt see the Viper story now anyway.

BG> Just slower V.34 connects, that's all (26400 typically).
BG> Always with EC though, regardless of the ROM in use here.

Thats certainly what should happen, an EC connect at a lower speed.

BG> Furthermore, everybody has been blaming my poor
BG> lines for that problem, yet now that David is seeing
BG> it, that theory has gone straight out the window.

RS> Nope, it was clearly the reason you alone were
RS> seeing /NONEs with a variety of V32bis USRs when NOT
RS> A SINGLE OTHER PERSON WAS with a USR and his Thunder.

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

No thanks, we are BOTH saying the same thing.

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

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

BG> Can't have it both ways, you know.

If you cant get your 'brain' around the more complex
fault situations thats entirely YOUR problem.

BG> Funny thing is that it hasn't happened
BG> here since I replaced the EPROM.  Not once.

RS> They fixed what was dud in the earlier roms. Bet they would come
RS> back if you return to the earlier rom. It doesnt, your line has
RS> changed. The reason I will bet that it will return was because
RS> your obscene problems with CHH went away with the rom change too.

BG> Now that Paul's using the Viper again, I bet it doesn't return,
BG> as it never happened in the first place with that modem.

Proves nothing useful at all about whether the V34+ Sportster
had less than ideal code in all but the last rom Bill. Which
is made VERY visible when used on your rather poor line, so
you got those utterly obscene results when calling CHH too.

BG> Maybe both the USR and NetComm have slightly incompatible
BG> code which when combined, caused the problem?

Doesnt explain the obscene results you got calling CHH.
Which vanished completely with a rom change in the Sportster.

Or why you alone saw /NONE connects using a V32bis Sportster when
calling his Spirit either. The USR code clearly had a deficiency
when used on a relatively poor line, producing a /NONE results
when it should have dropped the speed a bit and got an /EC connect.

BG> Be interesting to see how the Courier performs when it arrives.

Yeah, tho as Paul says, its a pity he happened to change to
the Viper at the same time, complicates the story considerably.
@EOT:

---