Rod, at 09:07 on Feb 22 1996, you wrote to Bill Grimsley...

TR> Yep, definitely sounds like a poor V32bis implementation on the Supra.

RS> You might care to try to explain why, if the Supra is at fault,
RS> why that problem is never seen when a USR Sportster V34 is called.

BG> And YOU might care to try explaining why the Supra is apparently the ONLY
BG> V.32bis modem to exhibit this peculiar behaviour when calling a Courier...

RS> We dont actually know that it is Bill, particularly when other V32bis
RS> modems have had problems with Spirit Thunders with the V32terbo mode 
RS> enabled.

Which "other" modems might these be then ?  I know that your
Supra has always had problems connecting with any V.32ter-capable modem,
but given that Dave has several V.32ter callers (and hundreds of V.32bis
callers) who connect with no problems whatsoever, the evidence would
clearly suggest that the problem lies in the old V.32bis Supra's
implementation of that protocol.

RS> Basically, V32terbo is very kludgy hack to V32bis, just fiddling with
RS> the constellation pattern, and not properly integrated into V32bis at
RS> the level of the session negotiation. Its hardly very surprising that
RS> that approach can bite with hordes of V32bis modems already in the field.

But it doesn't.  It apparently only bites with YOUR old Supra modem.  Can't
you grasp that simple fact ?  The world has moved on over the past 5 years.

RS> Its also interesting that the Supra has NO problem whatever with
RS> the rather less kludgy approaches like VFC and V34. Which both
RS> happen to have the session negotiation stuff done properly.

The need for decent backward compatibility is no surprise to me.

RS> Kludges can bite. Thats no news whatever.

As you wish.  They sure haven't bitten me though.

Regards, Bill

--- Msgedsq/2 3.20