anon wrote:
<snip>

Have you ever been able to get faster (ie 48000, 52000, etc)
connections on this phone line with any other modem ??

If not, then this line may not support "56k" operation. Here is a site
with some info to consider:
http://modemsite.com/56k/56kline.asp

I have an internal USR 56k v.92 FaxModem (5660c) which I just purchased a
week ago. Everytime I connect to my ISP (Earthlink) my connect speed is
*always* @ 24000bps. I just had the phone line fixed for line noise a few
weeks ago. I downloaded the latest drivers from the USR site. I put in
various init strings (taken from suggestions for other posts here from users
with similar problems) to no avail. I even tried calling a non-local access
# with the same connect speed. When I download a file from the Web, my d/l
speed starts out at 7k/sec but diminishes to a steady 2.7k/sec. It's like
the modem is capped to download at 2.7k/sec with a capped 24000 connect. As
a test, I connected a 486 running win95 with an ActionTec v90 modem (with
out of date drivers) using the same ISP and it connected at 26400 bps. What
gives? Any help would greatly be appreciated.

Here's the modem log file for the USR modem (sorry if it's too long; I
don't know which parts to snip out):

02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\tapisrv.dll, Version
5.1.2600
02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\unimdm.tsp, Version
5.1.2600
02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\unimdmat.dll, Version
5.1.2600
02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\uniplat.dll, Version
5.1.2600
02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\drivers\modem.sys,
Version 5.1.2600
02-15-2008 21:52:20.430 - File: C:\WINDOWS\system32\modemui.dll, Version
5.1.2600
02-15-2008 21:52:20.440 - File: C:\WINDOWS\system32\mdminst.dll, Version
5.1.2600
02-15-2008 21:52:20.440 - Modem type: U.S. Robotics V.92 PCI Faxmodem
02-15-2008 21:52:20.440 - Modem inf path: oem0.inf
02-15-2008 21:52:20.440 - Modem inf section: ModemX
02-15-2008 21:52:20.440 - Matching hardware ID:
pci\ven_16ec&dev_2f00&subsys_010a16ec&rev_01
02-15-2008 21:52:20.810 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-15-2008 21:52:20.810 - Initializing modem.
02-15-2008 21:52:20.820 - Send: AT<cr>
02-15-2008 21:52:20.820 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:20.820 - Interpreted response: OK
02-15-2008 21:52:20.830 - Send:
AT&F&A0X4E0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
02-15-2008 21:52:20.981 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:20.981 - Interpreted response: OK
02-15-2008 21:52:20.991 - Send:
ATS7=60S30=0M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
02-15-2008 21:52:20.991 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:20.991 - Interpreted response: OK
02-15-2008 21:52:20.991 - Waiting for a call.
02-15-2008 21:52:21.011 - Send: at+vcid=1<cr>
02-15-2008 21:52:21.011 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:21.011 - Interpreted response: OK
02-15-2008 21:52:21.031 - Send: ATS0=0<cr>
02-15-2008 21:52:21.031 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:21.031 - Interpreted response: OK
02-15-2008 21:52:21.031 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-15-2008 21:52:21.031 - Initializing modem.
02-15-2008 21:52:21.041 - Send: AT<cr>
02-15-2008 21:52:21.041 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:21.041 - Interpreted response: OK
02-15-2008 21:52:21.061 - Send:
AT&F&A0X4E0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
02-15-2008 21:52:21.201 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:21.221 - Interpreted response: OK
02-15-2008 21:52:21.241 - Send:
ATS7=60S30=0M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
02-15-2008 21:52:21.241 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:52:21.241 - Interpreted response: OK
02-15-2008 21:52:21.241 - Dialing.
02-15-2008 21:52:21.261 - Send: ATDT###########<cr>
02-15-2008 21:52:37.865 - Recv: <cr><lf>+MCR: V92<cr><lf>
02-15-2008 21:52:37.865 - Interpreted response: Informative
02-15-2008 21:52:37.865 - Recv: <cr><lf>+MRR: 24000<cr><lf>
02-15-2008 21:52:37.865 - Interpreted response: Informative
02-15-2008 21:52:38.576 - Recv: <cr><lf>+ER: LAPM<cr><lf>
02-15-2008 21:52:38.576 - Interpreted response: Informative
02-15-2008 21:52:38.576 - Recv: <cr><lf>+DR: V44<cr><lf>
02-15-2008 21:52:38.576 - Interpreted response: Informative
02-15-2008 21:52:38.576 - Recv: <cr><lf>CONNECT 24000<cr><lf>
02-15-2008 21:52:38.576 - Interpreted response: Connect
02-15-2008 21:52:38.576 - Connection established at 24000bps.
02-15-2008 21:52:38.576 - Error-control on.
02-15-2008 21:52:38.576 - Data compression on.
02-15-2008 21:53:08.579 - Read: Total: 26052, Per/Sec: 865, Written: Total:
2103, Per/Sec: 66
02-15-2008 21:53:21.428 - Hanging up the modem.
02-15-2008 21:53:21.428 - Hardware hangup by lowering DTR.
02-15-2008 21:53:21.728 - Detected CD dropped from lowering DTR
02-15-2008 21:53:21.728 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:21.728 - Interpreted response: OK
02-15-2008 21:53:21.738 - Send: ATH<cr>
02-15-2008 21:53:21.738 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:21.738 - Interpreted response: OK
02-15-2008 21:53:21.748 - Send: at#ud<cr>
02-15-2008 21:53:21.748 - Recv: <cr><lf>DIAG
02-15-2008 21:53:21.748 - Interpreted response: Diagnostic Info
02-15-2008 21:53:21.748 - Recv: <2A4D3263 0=10><cr><lf><cr><lf>DIAG
<2A4D3263 1=7><cr><lf><cr><lf>DIAG <2A4D3263 2=0><cr><lf><cr><lf>DIAG
<2A4D3263 3=0><cr><lf><cr><lf>DIAG <2A4D3263 4=""><cr><lf><cr><lf>DIAG
<2A4D3263 5=""><cr><lf><cr><lf>DIAG <2A4D3263 10=1A 11=11
12=1A><cr><lf><cr><lf>DIAG <2A4D3263 13=1E><cr><lf><cr><lf>D
02-15-2008 21:53:21.748 - Unknown Response
02-15-2008 21:53:21.748 - Recv: 7=0 F8=2><cr><lf><cr><lf>DIAG <2A4D3263
F9=0><cr><lf><cr><lf>DIAG <2A4D3263 FA=60><cr><lf><cr><lf>DIAG <2A4D3263
FB=0 FC=0><cr><lf><cr><lf>DIAG <2A4D3263 FD=FFFF8400
FE=0><cr><lf><cr><lf>OK<cr><lf>
02-15-2008 21:53:21.748 - Unknown Response
02-15-2008 21:53:21.748 - 115200,8,N,1, ctsfl=1, rtsctl=2
02-15-2008 21:53:21.748 - Initializing modem.
02-15-2008 21:53:21.948 - Send: AT<cr>
02-15-2008 21:53:21.948 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:21.948 - Interpreted response: OK
02-15-2008 21:53:21.958 - Send:
AT&F&A0X4E0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
02-15-2008 21:53:22.099 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:22.099 - Interpreted response: OK
02-15-2008 21:53:22.109 - Send:
ATS7=60S30=0M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
02-15-2008 21:53:22.119 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:22.119 - Interpreted response: OK
02-15-2008 21:53:22.119 - Waiting for a call.
02-15-2008 21:53:22.129 - Send: at+vcid=1<cr>
02-15-2008 21:53:22.129 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:22.129 - Interpreted response: OK
02-15-2008 21:53:22.139 - Send: ATS0=0<cr>
02-15-2008 21:53:22.139 - Recv: <cr><lf>OK<cr><lf>
02-15-2008 21:53:22.139 - Interpreted response: OK
02-15-2008 21:53:22.139 - Session Statistics:
02-15-2008 21:53:22.139 - Reads : 30 bytes
02-15-2008 21:53:22.139 - Writes: 106 bytes

On Sun, 17 Feb 2008 01:02:32 -0800, "anon" <user@dialup.com> put
finger to keyboard and composed:

<snip>

These are the Unimodem diagnostic data that I have been able to
extract from your broken modemlog:

DIAG <2A4D3263 0=10>
DIAG <2A4D3263 1=7>
DIAG <2A4D3263 2=0>
DIAG <2A4D3263 3=0>
DIAG <2A4D3263 4="">
DIAG <2A4D3263 5="">
DIAG <2A4D3263 10=1A 11=11 12=1A>
DIAG <2A4D3263 13=1E>
DIAG <2A4D3263 F7=0 F8=2>
DIAG <2A4D3263 F9=0>
DIAG <2A4D3263 FA=60>
DIAG <2A4D3263 FB=0 FC=0>
DIAG <2A4D3263 FD=FFFF8400 FE=0>

This is the decoded information:

Unimodem Diagnostics/W32, version 1.1.0.0, compiled at Mar 14 2002
18:01:05
(c) 2000 Stanislav V. Mekhanoshin (rampitec@tu.spb.ru,
2:5030/172.9@fidonet)
----------------------------------------------------------------------------
Diag Command Specification rev.: 1.0
Call Setup Result code : Data Answering signal detected
Multi-media mode : Data Only
DTE-DCE interface mode : Async data
V.8 CM/JM octet string : ""/""
TX/RX signal power level, -dBm : 17/26
Estimated noise level, -dBm : 26
Normalized Mean Squared error : 30
Manufacturer key : 0


You can get *much* more complete and useful information by editing the
Properties key in your registry as described here:
http://modemsite.com/56k/diag.asp

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.

"Reed" <reedh@rmi.net> wrote in message
news:13rfpc1a5ctuc8d@corp.supernews.com...
When I used the ActionTec v90 modem it never connected above 26400 bps.
The website you provided was very helpful. I found out that I have a 'soft'
modem and unfortunately that my phone line doesn't support a 56K connect.
Thanks for your help!

p.s. i accidentally replied directly to your email instead of replying to
group :P

Thanks for your reply. I don't know what the diagnostic data you extracted
mean. Following the instructions on the website I was able to obtain the
following info using the at6 and at7 commands:

U.S. Robotics V.92 PCI Faxmodem Link Diagnostics...

TERMINATION REASON..........No previous call
LAST TX rate................16800
FIRST TX rate...............16800
LAST RX rate................24000
FIRST RX rate...............24000
PROTOCOL....................LAPM
COMPRESSION.................V44
RxLEVEL.....................24
EQM Sum.....................1D
RBS Pattern.................60
Local Reneg Count...........0
Remote Reneg Count..........1
Digital Loss................0
Local Rtrn Count............0
Remote Rtrn Count...........1

U.S. Robotics V.92 PCI Faxmodem Configuration Profile...

Product Type USA FCC D/F
Product ID 5660
Data Options V.32bis,V.34+,V.80,V.90,V.92
Fax Options Class 1
Line Options CallWaiting
Code Date 08/05/2005
Code Rev 7.32.00

the at y11 command doesn't work. It just says ERROR. I don't know what those
numbers above mean.
Is there a chance my modem is defective?

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
newsh1hr31bmqkba4vh1s3c0gccl5lui0s4sq@4ax.com...

Thanks for your reply. I don't know what the diagnostic data you extracted
mean. Following the instructions on the website I was able to obtain the
following info using the at6 and at7 commands:

U.S. Robotics V.92 PCI Faxmodem Link Diagnostics...

TERMINATION REASON..........No previous call
LAST TX rate................16800
FIRST TX rate...............16800
LAST RX rate................24000
FIRST RX rate...............24000
PROTOCOL....................LAPM
COMPRESSION.................V44
RxLEVEL.....................24
EQM Sum.....................1D
RBS Pattern.................60
Local Reneg Count...........0
Remote Reneg Count..........1
Digital Loss................0
Local Rtrn Count............0
Remote Rtrn Count...........1

U.S. Robotics V.92 PCI Faxmodem Configuration Profile...

Product Type USA FCC D/F
Product ID 5660
Data Options V.32bis,V.34+,V.80,V.90,V.92
Fax Options Class 1
Line Options CallWaiting
Code Date 08/05/2005
Code Rev 7.32.00

the at y11 command doesn't work. It just says ERROR. I don't know what those
numbers above mean.
Is there a chance my modem is defective?

"Franc Zabkar" <fzabkar@iinternode.on.net> wrote in message
newsh1hr31bmqkba4vh1s3c0gccl5lui0s4sq@4ax.com...

On Sun, 17 Feb 2008 19:27:08 -0800, "anon" <user@dialup.com> put
finger to keyboard and composed:

Your modem appears to use a Conexant chipset, not USR. AFAIK, the only
diagnostic commands that would be applicable are AT&V1, AT&V2, and
AT#UD. AT&V1 gives you an abbreviated report.

If you edit your registry as described at modemsite.com, then the #UD
data will be automatically appended to your modemlog. Otherwise you
can access it via HyperTerminal and analyse it using Stanislav
Mekhanoshin's utilities.

You wrote previously that "when I download a file from the Web, my d/l
speed starts out at 7k/sec but diminishes to a steady 2.7k/sec". For
an incompressible file such as a ZIP, this would be normal behaviour,
assuming you are relying on your browser for this information. This is
because your browser gives you a rolling average. If you are
downloading a compressible file when this happens, then you *may* have
a problem. One way to verify this is by checking your #UD or &V2
reports for max/min Tx/Rx speeds and Tx/Rx errors.

- Franc Zabkar
--
Please remove one 'i' from my address when replying by email.