RS> And now that its clear that its become clear that the mindless retrain
RS> behaviour of the Courier goes away if V32terbo is disabled on the Courier,
RS> and the Spirit Thunder ALSO had to have V32terbo disabled to ensure
RS> reliable incoming V32bis connects from NOT JUST A SUPRA, this is just
RS> the usual attempt to point the finger and blame it on the other party.

RB> Are you saying that the BUG in the Courier,
RB> is infact the result of bad V32terbo code

Well, one other possibility is that the design of the V32terbo
protocol is not robust enough to allow for reliable coexistence
with V32bis, particularly as an addon later after V32bis has
become very widely used with hordes of modems implementing it.

In other words a rather crude kludge with some inevitable compromises
in the design of the protocol itself, which mean its got real problems.

RB> (Who invented that, Rockwell?)

Nope, AT&T from memory, but certainly not Rockwell,
as far as I know Rockwell never bothered with it at all.

Corse they did their own relatively crude kludge, VFC, instead.

Both were in fact just attempts to do something more than V32bis while
waiting for the V34 which was taking a long time to be formalised.

RB> Rockwell are not known for backpedalling and fixing their bugs
RB> nor informing other manufacturers when they do chnge something.

Oh sure, no argument there.

RB> USR can hardly be blamed then, if they did not
RB> match Rockwells interpretation of the Turbo code.

Rockwell never bothered with V32terbo.
@EOT:

---