I have tried four v92 modems on two ISPs and the post call diagnostics show
V44 negotiations took place. Further down it says "compression on". In all
cases the win XP modem status indicator says there is no compression.

Using the V90 lines with the same ISPs results in compression being shown in
the modem status indicator.

One of these ISPs advertises V44 compression is supported and I do not have
an answer from the other.

Is anyone getting compression with V92 without signing up for the broad
dial, Propel or other speedup options?

"J.M. Burns" <highline@ispwest.com> wrote in message
news:belsje02nmq@enews2.newsguy.com...
It sounds like the "driver" (inf file) is incorrect so XP's DUN does not
understand the connection report from the modem. Look in the modem log file
and see what is reported by the modem.

--

Hooda Gest
"The only thing I do immediately is procrastinate."

"Hooda Gest" <Be@One_With.Calm> wrote in message
news:LzyPa.50140$3o3.3325254@bgtnsc05-news.ops.worldnet.att.net...

I did not mean to email this to you Hooda...I hit the wrong button.

If that is the reason for the problem, the inf files for four different
brands of modems would all have to be giving bum information to the DUN.
Here is a clip from the modem log for this call:

07-11-2003 10:54:55.125 - Recv: <cr><lf>+DR: V44<cr><lf>
07-11-2003 10:54:55.125 - Interpreted response: Informative
07-11-2003 10:54:55.125 - Recv: <cr><lf>CONNECT 115200<cr><lf>
07-11-2003 10:54:55.125 - Interpreted response: Connect
07-11-2003 10:54:55.125 - Connection established at 49333bps.
07-11-2003 10:54:55.125 - Error-control on.
07-11-2003 10:54:55.125 - Data compression on.

From this one could that V44 compression is being used although it's not
explicitly stated.

Now I will hang up and grab the post-call diagnostics with AT#UG. Do you
see anything suspicious other than the outlandish number for s/n? On one
occasion the s/n was resonable at around 35 dB but it's been stuck on 249
ever since


<#UG VERSION=2>
<UNIMODEM VERSION=10>
<DRIVER VERSION=212.173.010.000>
<CALL SETUP RESULT=Detected V.8bis Tone>
<MULTIMEDIA MODE=Data Only>
<DTE-DCE MODE=Async data>
<V.8 CM octet string="">
<V.8 JM octet string="">
<RX SIG POWER DB=16, TX SIG POWER DB=15, S/N RATIO DB=249>
V.34 INFO bit map =1073742848>
<TX MOD=V.92, TX SYMBOL RATE=3200, TX CARRIER FREQ=1829>
<RX MOD=V.92, RX SYMBOL RATE=8000, RX CARRIER FREQ=0>
<TX FIRST DATA RATE=26400, RX FIRST DATA RATE=49333>
<CARRIER LOSS=0, RATE RENEG=1>
<RETRAINS REQ=0, RETRAINS DET=0>
<TX FINAL RATE=26400, RX FINAL RATE=48000>
<PROTOCOL NEGOTIATION=LAPM>
<EC FRAME SIZE=80>
<EC LINK TIMEOUTS=0>
<EC LINK NAKS=4>
<COMPRESSION NEGOTIATION=V44>
<COMPRESSION DICTIONARY SIZE=800>
<TX FLOW CONTROL=2>
<RX FLOW CONTROL=2>
<TX CHARS SENT FROM DTE=1EFF>
<RX CHARS SENT TO DTE=4318>
<TX CHARS LOST=0>
<RX CHARS LOST=0>
<TX FRAME COUNT=1F0>
<RX FRAME COUNT=99>
<TX FRAME ERROR COUNT=4>
<RX FRAME ERROR COUNT=4>
<TERMINATION CAUSE=DTR drop>
<CALL WAITING EVENT COUNT=0>
<LSD Vdd=49, Power Bits=C0>
<DIB ERROR COUNTERS=0, 0, 0, 0, 0, 0, 0, 0>
<V8BIS FLEX VERSION=0, V8BIS DSP VERSION=0>
<RATE RENEG REQ=1, RATE RENEG DET=0>
<ROBBED BIT PATTERN=1>
<DIGITAL PAD DETECTED=0, DIGITAL LOSS ESTIMATE=3F07>
<Cnt1=0, Det1=0, Res1=0>
<EQM=2213, TRAINING EQM SUM=A2FD>
<RETRAIN/HDLC RESET=0>
<LAST DPDOWNLOAD FAILURE MODULE=0>
<TRN TIME=12843, NEG TIME=520>
<DP HANDSHAKE STATE CHANGE= >
<LAST DP STATE=1>
<ANSPCM0=0037 0074 10E8 107E 110B 109F>
<ANSPCM1=006C 002F 1089 101E 10AB 103F>
<ANSPCM2=006C 0031 1093 1029 10B6 104A>
<ANSPCM3=006E 0031 1088 101E 10AB 103F>
<ANSPCM4=006F 0030 108B 1020 10AD 1041>
<ANSPCM5=006E 0031 108B 1020 10AD 1041>
<ANSPCM6=0001 003E 0000 0000 0000 0000>

OK

"J.M. Burns" <highline@ispwest.com> wrote in message
news:bemusm0v8g@enews3.newsguy.com...
Not a problem.

It is explicitly stated, however. First line reports the modem negotiated
V.44 data compression. The last line says that DUN understood this.

That would leave me to believe it is just a bug in XP's modem status
indicator.


I saw nothing suspicious or unreasonable. SNR's are very subjective and
unreliable in modems, I'm afraid.


--

Hooda Gest
"The only thing I do immediately is procrastinate."

| Is anyone getting compression with V92
Isn't compression noticeable whenever SystemMonitor reports more
bytes per second than DCE speed can give ( e.g. 49333 ÷ 9 = 5481 byte
per second ) ?

| The last line says compresssion was used but does not explicity state
| what kind of compression.
Win98se & DUN1.4 report the compression std used, e.g. :-
07-17-2003 00:11:20.76 - Recv: COMPRESSION: V.42BIS
07-17-2003 00:11:20.76 - Interpreted response: Informative
07-17-2003 00:11:20.76 - Recv: <cr>
07-17-2003 00:11:20.76 - Interpreted response: Informative
07-17-2003 00:11:20.76 - Recv: <lf>
07-17-2003 00:11:20.76 - Interpreted response: Informative
07-17-2003 00:11:20.76 - Recv: <cr>
07-17-2003 00:11:20.76 - Interpreted response: Informative
07-17-2003 00:11:20.76 - Recv: <lf>
07-17-2003 00:11:20.76 - Interpreted response: Informative
07-17-2003 00:11:20.76 - Recv: CONNECT 44000
07-17-2003 00:11:20.76 - Interpreted response: Connect
07-17-2003 00:11:20.76 - Connection established at 44000bps.