PE> So the failures to the Spirit do not make the modem count as iffy?
PE> Well if we discount that from the iffy stats, then the Supra only
PE> has the one iffy connect, which is with the Courier. And that fault,
PE> could be either of Supra's or USR's fault, we can't tell.  We can
PE> tell that disabling V32terbo makes that particular problem go away,
PE> which gives a great weight of evidence as to where the problem is.

PC> Well i use to call a Spirit Thunder with my Courier and get good
PC> 19200 v.32ter connects most times "this was on quite bad lines"

That proves nothing at all coz they are both designed to do V32terbo.
Clearly it must basically work on modems designed to do it or it wouldnt
have got out into the field at all. The problem is that those sorts of
kludges can bite you when you try to add them to whats already out in
the field in the full range of V32bis modems. No problem with V34, which
does tend to indicate that doing the protocol properly does allow it
to coexist a hell of a lot better with whats already in the field.

PC> and AFAIK other callers with v.32bis modems
PC> also connected to the Spirit without problem,

They didnt, Maestros also had problems.
Presumably other rockwell V32bis modems as well.

PC> could perhaps the Supra be generating offkey tones

There is NO 'tone' difference between V32bis and V32terbo, they use
the SAME carrier freqs and all V32terbo does is have more points in
the constellation pattern, and thats known to be less than very
satisfactory on the signal to noise demands it makes of the line.

PC> and tricking the Courier into thinking the call was a v.32ter one.

The problem with that theory is that you get perfect 14400 connects
EVERY TIME and then after less than a second the Courier mindlessly
demands a full retrain when V32terbo is enabled on the Courier.
There is no way that 'tones' from the Supra can do that.
@EOT:

---