Modem test ? Test number?

[amdkt7]

It really did not like the S95=1 setting. I also found that it is unable to use the error control setting and data compression. Error control is grayed out and the log file reflects this problem. I'm sure this because the driver is not correct for this modem.
Here is the last log:

04-07-2002 08:02:10.12 - Standard 56000 bps V90 Modem in use.
04-07-2002 08:02:10.22 - Modem type: Standard 56000 bps V90 Modem
04-07-2002 08:02:10.22 - Modem inf path: MDMUSRK1.INF
04-07-2002 08:02:10.22 - Modem inf section: Gen2
04-07-2002 08:02:10.46 - 115200,N,8,1
04-07-2002 08:02:10.46 - 115200,N,8,1
04-07-2002 08:02:10.46 - Initializing modem.
04-07-2002 08:02:10.46 - Send: ATZ<cr>
04-07-2002 08:02:10.46 - Recv: ATZ<cr>
04-07-2002 08:02:10.59 - Recv: <cr><lf>OK<cr><lf>
04-07-2002 08:02:10.59 - Interpreted response: Ok
04-07-2002 08:02:10.59 - Send: ATE0V1&C1&D2S0=0<cr>
04-07-2002 08:02:10.59 - Recv: ATE0V1&C1&D2S0=0<cr>
04-07-2002 08:02:10.72 - Recv: <cr><lf>OK<cr><lf>
04-07-2002 08:02:10.72 - Interpreted response: Ok
04-07-2002 08:02:10.72 - Send: ATM0X4<cr>
04-07-2002 08:02:10.84 - Recv: <cr><lf>OK<cr><lf>
04-07-2002 08:02:10.84 - Interpreted response: Ok
04-07-2002 08:02:10.84 - Dialing.
04-07-2002 08:02:10.84 - Send: ATDT;<cr>
04-07-2002 08:02:12.32 - Recv: <cr><lf>OK<cr><lf>
04-07-2002 08:02:12.32 - Interpreted response: Ok
04-07-2002 08:02:12.32 - Dialing.
04-07-2002 08:02:12.32 - Send: ATDT#######<cr>
04-07-2002 08:02:36.63 - Recv: <cr><lf>CONNECT 45333/ARQ/V90/LAPM/V42BIS<cr><lf>
04-07-2002 08:02:36.63 - WARNING: Unrecognized response. Retrying...
04-07-2002 08:02:36.63 - Connection established at 115200bps.
04-07-2002 08:02:36.63 - Error-control off or unknown.
04-07-2002 08:02:36.63 - Data compression off or unknown.
04-07-2002 08:04:52.99 - Hanging up the modem.
04-07-2002 08:04:52.99 - Hardware hangup by lowering DTR.
04-07-2002 08:04:53.10 - Recv: <cr><lf>NO CARRIER<cr><lf>
04-07-2002 08:04:53.10 - Interpreted response: No Carrier
04-07-2002 08:04:53.10 - Send: ATH<cr>
04-07-2002 08:04:53.23 - Recv: <cr><lf>OK<cr><lf>
04-07-2002 08:04:53.23 - Interpreted response: Ok
04-07-2002 08:04:53.23 - 115200,N,8,1
04-07-2002 08:04:53.23 - Session Statistics:
04-07-2002 08:04:53.23 - Reads : 23897 bytes
04-07-2002 08:04:53.23 - Writes: 3263 bytes
04-07-2002 08:04:53.23 - Standard 56000 bps V90 Modem closed.

Sure looks like there is a problem here. Don't know if I should worry about it.

The s95 hangs the modem up and I have to powerdown before it will work again.

[amdkt7]

I tried again, this time I used the MS USR 56K voice INT driver. Windows bitched of course, but it seems to work great.

I got the standard connect speed I am use to and download speeds seemed to be normal.

I checked the log and did not find any errors. Error control and data compresion were all working.

http://www.modemsite.com/56k/index.asp is a great source for modem info.

[BFlurie]

Glad to hear it. Put W4 in the modem string to report correct speed.

I've experimented quite a bit, but modem benchmarking is difficult 'cause you never know if line/connection conditions are a cause of variance. My "extra" settings are simple:

W4S10=30S11=60

Error-control & both software compression in Dial-up TCP properties & modem compression in modem properties are enabled. Point-to-point & IPX-header compression are disabled in Dial-up adapter properties. I use a "large" packet size (1500), an RWIN of (1500-40) x 5 = 7300, tho much larger multiples apparently work OK. MTUdetect is disabled in the registry -- MTU autodetection doesn't seem to work as well.