RS> That doesnt actually prove a damned thing. Clearly it would
RS> negotiate a V34 or VFC session. The problem is with V32bis
RS> sessions, and the weird way that a Courier attempts to see if
RS> V32terbo is possible. It aint ever gunna even contemplate V32terbo
RS> when its called by a V34 or VFC capable modem.

RL> OK, then my v32bis Avtek also connected without fault (and still
RL> does). Wouldn't this come down to a problem with the Supra, if it is the
RL> only v32bis modem to have this problem??

No more than the fact that the Supra V32bis being able to connect
to a Netcomm and Viper without problem is due to a USR bug.  We
simply don't know who, if anyone, is violating protocol.  Given
that we are almost dead certain that it's a V32terbo protocol
problem, it's a bit rich to be guaranteeing that it's a Supra 
V32bis problem, no?  Not QUITE true, we still need to know whether
the Supra is obeying every bit of V32bis and not doing anything
wrong at all, which we don't know.

BTW, I have a problem against the Netcomm, with respect to Avtek
V32bis calls.  Should I take that off the Netcomm problem list, just
because it's the only modem?  No way, hose!  BFN.  Paul.
@EOT:

---