G'day Lewin!

 -=> In a message on 05 Apr 96 <=-
 -=> Lewin Edwards said this to John Piper <=-

 JP> to supply them with my profile dump and see what they have to say. If
 JP> the M11F won't report /V.FC, I'll just give up.

 LE> It won't. Now is the correct time to give up. The only 

Yes, I've had it confirmed by NetComm that the "/V.FC" is only appended to
the CONNECT string in V.34 models.

 LE> reason that protocol notification is there is to let you
 LE> distinguish between V.FC and V.34. Since the RC288DPi/VFC 
 LE> doesn't support V.34, the feature is irrelevant and 
 LE> inoperable, at least in the firmware versions I've tested. 
 LE> /VFC is _implicit_ in the fact that you have an M11F.

V.FC may be _implicit_ for speeds of 16800 bps and above in the M11F but
CONNECT 14400 is still ambiguous whereas the M34F leaves no doubt...

CONNECT 14400/LAP-M/V.42bis/V.34  - V.34
CONNECT 14400/LAP-M/V.42bis/V.FC  - V.FC
CONNECT 14400/LAP-M/V.42bis       - V.32bis

BTW I've never forced a "slow" V.34 connection so I don't know if
"/V.34" is
appended to CONNECT 2400, CONNECT 9600, etc.  Have you tried?


BFN
  _
 (_`
 ._)teve



___ E-mail: slennie{at}cin.gov.au
~~~ PGPWave v1.22a Gamma / PGP 2.6.3i
... Windows 95:  The ultimate triumph of style over substance.
___ Blue Wave/386 v2.30

--- Maximus/2 3.01