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 

 RS> 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



 RS> Well, one other possibility is that the design of the V32terbo

 RS> protocol is not robust enough to allow for reliable coexistence

 RS> with V32bis, particularly as an addon later after V32bis has

 RS> become very widely used with hordes of modems implementing it.



 RS> In other words a rather crude kludge with some inevitable compromises

 RS> in the design of the protocol itself, which mean its got real problems.



Now I come to think about it I agree, and this is where my money is,

 Hurried buggy V32turbo code to get a dollar before

the original V.fast was finished. If memory serves me correctly there was a

lot of uncertainty back in 92-93, when there was talk about V.fast being the

next latest greatest thing but it looked like it would never be ratified, and 

its development was rivelling V32turbo next thing you know, V32turbo appeared

on the scene and was the way to go as V.fast was still not finished, I still

remember the propaganda of the day saying it was better in the long run to

stick with Rockwell rather than go to V32turbo, I thought that it was just

propaganda yet I almost believed them, then out of the blue V.Fc appears and

V.fast was STILL not finalized.





Russell



--- Terminate 3.00/Pro