G'day John!



 -=> In a message on 18 Mar 96 <=-

 -=> John Piper said this to Stephen Lennie <=-



 SL> If you have "S95=47" change it to "S95=0" as
multi-line CONNECT strings

 SL> are rarely needed and tend to confuse most comms and BBS software.

 

 JP> I've already sent you another more detailed message, but in short,

 JP> changing S95 to 0 did the trick. When I dialled a 14400 BBS this

 JP> morning, the modem reported CONNECT 14400/LAP-M/V.42bis. I have not

 JP> connected to a V.FC modem yet, but when I do, I expect that V.FC

 JP> will be added to that connect string.



 JP> Nope -- it wasn't. ARG -- back to the way things were BEFORE I

 JP> upgraded the firmware. I would like to have the /V.FC result code

 JP> appended to my connect string. Currently it only reports CONNECT

 JP> XXXXX/LAP-M/V.42bis. 

 JP> Any ideas? (profile is the same as the one I posted before)



If you have "W2 \V1 %U2 S95=0" in your Active Profile and the
"/V.FC" *still*

isn't appended to the CONNECT message - maybe it never will be.



Perhaps the "/V.FC" and "/V.34" suffixes are only valid
in V.34 modems (M34F)

even though they exist in both the V7 and Z7 SmartModem code.



Just a thought.  I might give NetComm a call myself about this, I'm curious.





BFN

  _

 (_`

 ._)teve







___ E-mail: slennie{at}cin.gov.au

~~~ PGPWave v1.22a Gamma / PGP 2.6.3i

... Seen on hacker's tombstone:  CONNECT 1961, NO CARRIER 1993

--- Blue Wave/386 v2.30