All,
I am about 2 months away from our promised DSL activation at our house
(hooray!!!) but last week our dialup modem took a spike or something
and bit the dust.
Not wanting to go buy a new 56K modem to last me two months, I dug
through my box-o-parts and found an ISA USR Sportster modem with the
Product ID 661787-81.
According to USR @
http://www.usr.com/support/product-t...e.asp?prod=oem, this 66
series is an OEM modem classified as generic (i.e. not Dell, Gateway or
Micron), but the only 1787 they list on that page is a 1787E. My label
lists no "E" on it.
I went ahead and installed the modem in our Dell OptiPlex GX1 that is
running Windows XP Pro. Windows recognized the modem just fine, and
reports it as a U.S. Robotics 56K FAX INT PnP, manufactured by 3Com and
located on Intel 82371AB/EB PCI on ISA Bridge ISA. Further diagnostics
state ISAPNP/USR3030 and the modem query returns the expected
responses.
The problem is it connects at 28,800 every single time. The connection
seems solid, no disconnects or anything.
The modem log shows the following:
04-25-2006 15:04:10.800 - File: C:\WINDOWS\system32\tapisrv.dll,
Version 5.1.2600
04-25-2006 15:04:10.800 - File: C:\WINDOWS\system32\unimdm.tsp, Version
5.1.2600
04-25-2006 15:04:10.890 - File: C:\WINDOWS\system32\unimdmat.dll,
Version 5.1.2600
04-25-2006 15:04:11.001 - File: C:\WINDOWS\system32\uniplat.dll,
Version 5.1.2600
04-25-2006 15:04:11.191 - File: C:\WINDOWS\system32\drivers\modem.sys,
Version 5.1.2600
04-25-2006 15:04:11.191 - File: C:\WINDOWS\system32\modemui.dll,
Version 5.1.2600
04-25-2006 15:04:11.361 - File: C:\WINDOWS\system32\mdminst.dll,
Version 5.1.2600
04-25-2006 15:04:11.361 - Modem type: U.S. Robotics 56K FAX INT PnP
04-25-2006 15:04:11.361 - Modem inf path: mdm3com.inf
04-25-2006 15:04:11.361 - Modem inf section: ModemPCMinIBMBad
04-25-2006 15:04:11.361 - Matching hardware ID: *usr3030
04-25-2006 15:04:12.993 - 115200,8,N,1, ctsfl=1, rtsctl=2
04-25-2006 15:04:13.024 - Initializing modem.
04-25-2006 15:04:13.034 - Send: AT<cr>
04-25-2006 15:04:13.164 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:13.164 - Interpreted response: OK
04-25-2006 15:04:13.174 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
04-25-2006 15:04:13.294 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:13.294 - Interpreted response: OK
04-25-2006 15:04:13.304 - Send: ATS7=60S19=0L0M0&M4&K1&H1&R2&I0B0X4<cr>
04-25-2006 15:04:13.434 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:13.434 - Interpreted response: OK
04-25-2006 15:04:13.444 - Waiting for a call.
04-25-2006 15:04:13.454 - Send: AT#CID=1<cr>
04-25-2006 15:04:13.574 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:13.574 - Interpreted response: OK
04-25-2006 15:04:13.594 - Send: ATS0=0<cr>
04-25-2006 15:04:13.715 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:13.715 - Interpreted response: OK
04-25-2006 15:04:14.996 - 115200,8,N,1, ctsfl=1, rtsctl=2
04-25-2006 15:04:14.996 - Initializing modem.
04-25-2006 15:04:15.036 - Send: AT<cr>
04-25-2006 15:04:15.157 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:15.157 - Interpreted response: OK
04-25-2006 15:04:15.167 - Send: AT&F1E0Q0V1&C1&D2S0=0<cr>
04-25-2006 15:04:15.337 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:15.337 - Interpreted response: OK
04-25-2006 15:04:15.347 - Send: ATS7=60S19=0L0M1&M4&K1&H1&R2&I0B0X4<cr>
04-25-2006 15:04:15.477 - Recv: <cr><lf>OK<cr><lf>
04-25-2006 15:04:15.477 - Interpreted response: OK
04-25-2006 15:04:15.477 - Dialing.
04-25-2006 15:04:15.507 - Send: ATDT###-####<cr>
04-25-2006 15:04:50.688 - Recv: <cr><lf>CONNECT
28800/ARQ/V34/LAPM/V42BIS<cr><lf>
04-25-2006 15:04:50.688 - Interpreted response: Connect
04-25-2006 15:04:50.688 - Receive Connect but CD was low, Waiting for
signal to go high
04-25-2006 15:04:50.728 - CD has been raised
04-25-2006 15:04:50.728 - Connection established at 28800bps.
04-25-2006 15:04:50.728 - Error-control on.
04-25-2006 15:04:50.728 - Data compression on.
And then the data transfers begin as expected...
I see no indicators that would dictate a 28,800 connection, but that's
the best we are getting.
Any ideas that might help?
On 25 Apr 2006 18:18:25 -0700, steventhomas42 <steventhomas42@yahoo.com>
wrote:
More information would be helpful. Particularly the output produced by the
AT I5 and I7 commands.
Without those, I can make some guesses:
The modem doesn't support V.90 and your ISP doesn't understand x2. If you
can flash to the latest firmware that would probably fix it.
The modem is set up to disallow x2 and V.90. While the modem is in the
process of connecting, you should hear some assorted noise, followed by a
sort of "bong, bong" sound, followed by more assorted noise. If not, this
is likely the case.
The modem stinks. The 56k Sportsters really weren't the cream of the USR
crop. The external models, at least, could be annoyingly sensitive to bad
phone lines and RF interference (I always suspected replacing the off-hook
relay with a solid state gizmo was the problem but could never prove it).
Popping, crackling, and, in the worst case, humming from the audio
hardware going astable are symptomatic. This is pretty rare, though.
Finally, some digital modems just don't seem to like a Robotics analog at
the other end.
