Modemsite's Forum56 - The Modem Board
Main | profile | register | search | help | Ad-free Login
Forums | Agere (Public) | LT v.92-Disabling Hardware Flow to connect to earthlink    Watch  
Author Topic
llamage
Tl Posts:
5

USA
Posted - 6/7/2004 3:38:42 PM  Show Profile  Email Poster  Edit Message
Hi,
I recently upgraded from Windows ME to Windows XP Professional. For some reason, I cannot connect to earthlink with hardware flow control enabled(along with modem error code and modem compression). I am using driver 8.28 for the LT Winmodem (v.92). When I disable hardware flow control, I connect at 19.2 bps. What's going on here?

Thanks,
Llamage

v.Richard
Tl Posts:
6222

USA
Posted - 6/7/2004 8:33:26 PM  Show Profile  Email Poster  Edit Message  v.Richards Homepage
Try driver version 8.30 -
www.modemsite.com/56k/_ltwin7.asp

What speeds did you get with WindowsMe?

Post your modem log if you still have problem after upgrading driver to 8.30.
www.modemsite.com/56k/modemlog.asp

Aloha! Richard.

llamage
Tl Posts:
5

USA
Posted - 6/7/2004 10:57:10 PM  Show Profile  Email Poster  Edit Message
Hi Richard,
With driver version 8.30 installed, I am still connecting at 19.2 kbps with hardware flow disabled. With Windows Me, I was getting anywhere from 42-46 kbps, depending on the time of day. However, while running Windows ME, I do not remember whether or not I had hardware flow disabled. Here is the modem log :

06-07-2004 22:49:09.291 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600
06-07-2004 22:49:09.291 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600
06-07-2004 22:49:09.291 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600
06-07-2004 22:49:09.291 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600
06-07-2004 22:49:09.301 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600
06-07-2004 22:49:09.301 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600
06-07-2004 22:49:09.301 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600
06-07-2004 22:49:09.301 - Modem type: Agere Win Modem
06-07-2004 22:49:09.301 - Modem inf path: oem2.inf
06-07-2004 22:49:09.301 - Modem inf section: Modem_PNP_DSVD
06-07-2004 22:49:09.301 - Matching hardware ID: pci\ven_11c1&dev_044e&cc_0780
06-07-2004 22:49:10.393 - Opening Modem
06-07-2004 22:49:10.393 - 115200,8,N,1, ctsfl=1, rtsctl=2
06-07-2004 22:49:10.393 - Initializing modem.
06-07-2004 22:49:10.403 - Send: AT<cr>
06-07-2004 22:49:10.413 - Recv: AT<cr>
06-07-2004 22:49:10.413 - Command Echo
06-07-2004 22:49:10.413 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:10.413 - Interpreted response: OK
06-07-2004 22:49:10.423 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
06-07-2004 22:49:11.424 - Recv: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
06-07-2004 22:49:11.424 - Command Echo
06-07-2004 22:49:11.424 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:11.424 - Interpreted response: OK
06-07-2004 22:49:11.444 - Send: ATS7=60S30=0L0M1\N3%C1 +DCS=1,1&K3B0B15B2X4<cr>
06-07-2004 22:49:11.454 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:11.454 - Interpreted response: OK
06-07-2004 22:49:11.454 - Waiting for a call.
06-07-2004 22:49:11.464 - Send: ATS0=0<cr>
06-07-2004 22:49:11.475 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:11.475 - Interpreted response: OK
06-07-2004 22:49:11.515 - TSP(0000): Making Call
06-07-2004 22:49:11.515 - 115200,8,N,1, ctsfl=0, rtsctl=1
06-07-2004 22:49:11.515 - Initializing modem.
06-07-2004 22:49:11.525 - Send: AT<cr>
06-07-2004 22:49:11.535 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:11.535 - Interpreted response: OK
06-07-2004 22:49:11.545 - Send: AT &F E0 &C1 &D2 V1 S0=0\V1<cr>
06-07-2004 22:49:12.556 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:12.556 - Interpreted response: OK
06-07-2004 22:49:12.566 - Send: ATS7=60S30=0L0M1\N1%C0 +DCS=0,0&K0B0B15B2X4<cr>
06-07-2004 22:49:12.586 - Recv: <cr><lf>OK<cr><lf>
06-07-2004 22:49:12.586 - Interpreted response: OK
06-07-2004 22:49:12.596 - Dialing.
06-07-2004 22:49:12.596 - TSP Completing Async Operation(0x00010279) Status 0x00000000
06-07-2004 22:49:12.596 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
06-07-2004 22:49:12.596 - TSP(0000): LINEEVENT: LINECALLSTATE_PROCEEDING
06-07-2004 22:49:12.606 - Send: ATDT#######<cr>
06-07-2004 22:49:35.449 - Recv: <cr><lf>CONNECT 19200 NoEC<cr><lf>
06-07-2004 22:49:35.449 - Interpreted response: Connect
06-07-2004 22:49:35.449 - Receive Connect but CD was low, Waiting for signal to go high
06-07-2004 22:49:35.469 - CD has been raised
06-07-2004 22:49:35.469 - Connection established at 19200bps.
06-07-2004 22:49:35.469 - Error-control off or unknown.
06-07-2004 22:49:35.469 - Data compression off or unknown.
06-07-2004 22:49:35.469 - TSP(0000): LINEEVENT: LINECALLSTATE_CONNECTED
06-07-2004 22:50:05.472 - Read: Total: 16367, Per/Sec: 544, Written: Total: 5434, Per/Sec: 178
06-07-2004 22:52:05.475 - Read: Total: 55379, Per/Sec: 325, Written: Total: 22025, Per/Sec: 138
06-07-2004 22:54:05.477 - Read: Total: 63415, Per/Sec: 66, Written: Total: 25838, Per/Sec: 31


Do you think it's a v.92 compatibility issue with Earthlink? If so, howcome it worked fine with ME, and not XP Professional?

Thanks

Tony

llamage
Tl Posts:
5

USA
Posted - 6/7/2004 11:04:02 PM  Show Profile  Email Poster  Edit Message
Hi again,
Correction. When I turn off Modem Compression and modem error correction, then I am able to connect at 19.2 kpbs. Obviously, without modem compression, its going to run slower, but with it turned on, I get error 721, and the earthlink ISP does not respond.

Thanks again

Tony

v.Richard
Tl Posts:
6222

USA
Posted - 6/8/2004 8:47:21 AM  Show Profile  Email Poster  Edit Message  v.Richards Homepage
You really don't want to make a connection without error correction...

Try the modem in a different PCI slot
www.modemsite.com/56k/pci.asp

Try connecting with error correction & compression, and only the following init strings (try each one )
+MS=V90
+MS=V90;+DS44=0
+MS=V34

Also, try dialing in with Hyperterminal with AT&F; then the above init strings. What connect rates do you get with Hyperterminal? Copy/paste the Earthlink RAS sign-in id/sign-in prompt you get with Hyperterminal in a reply.
www.modemsite.com/56k/x2-hyperterm.asp
www.modemsite.com/56k/v92l3.asp

Aloha! Richard.

llamage
Tl Posts:
5

USA
Posted - 6/8/2004 1:21:41 PM  Show Profile  Email Poster  Edit Message
With Mode Compression and Error control Codes enabled:

I tried dialing in with and without all the different INIT Strings individually, and I still could not connect.
I then proceeded to dial in with Hyperterminal, but each connection waits for some response from Earthlink, but doesn't reply:

AT&F
OK
ATDT2185100
CONNECT 19200 NoEC
?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?~?....

For some reason, even with Error Control Enabled, it still connects with it disabled, and at a low speed, before going into this infinite ?.

Yet when I disable it manually before dialing, I am able to connect at the low 19.2 kpbs.

On a side note, with error correction disabled, and with the init string +MS=V34, I am able to connect at a slightly higher connection rate of 26.4-28.8 kbps.

I haven't placed the modem in a different PCI slot yet, because I want to reserve it as the last possible alternative.

Thanks again,

Tony

mainbuss
Tl Posts:
145

USA
Posted - 6/9/2004 8:10:26 AM  Show Profile  Email Poster  Edit Message

Edited by - mainbuss on 7/10/2004 10:24:16 PM
charles
Tl Posts:
5879

USA
Posted - 6/9/2004 10:43:01 AM  Show Profile  Email Poster  Edit Message
Check to see if they have other numbers to connect,like one just for V92. Look like problem with the V92 connection with the V44 comp.Also if you are going to make a V90 or V34 connection do not use the V92 number to connect.
v.Richard
Tl Posts:
6222

USA
Posted - 6/9/2004 11:00:01 PM  Show Profile  Email Poster  Edit Message  v.Richards Homepage
I think it's time to try another PCI slot.
The modem shouldn't require changing flow control to connect; and, the modem shouldn't connect with NoEC....

Aloha! Richard.

mainbuss
Tl Posts:
145

USA
Posted - 6/10/2004 12:38:16 AM  Show Profile  Email Poster  Edit Message

Edited by - mainbuss on 7/10/2004 10:24:36 PM
charles
Tl Posts:
5879

USA
Posted - 6/10/2004 10:45:50 AM  Show Profile  Email Poster  Edit Message
Try disabling the firewall or any other software that is running in the background and try connection again. Have you installed any of the updates from window update.

http://help.stargate.net/dialup/winxp.shtml
http://help.stargate.net/dialup/winxp-check.shtml

llamage
Tl Posts:
5

USA
Posted - 6/10/2004 1:40:03 PM  Show Profile  Email Poster  Edit Message
Hi Guys,
I've done everything thats been posted on this forum. I've also tried other possibilities with INIT Strings, dialed different access numbers, and none seem to work. Time to get a new modem? Man, it sucks to go from campus wireless in college to come home and have to deal with this crap. Any more suggestions before I head to frys?

Thanks all

charles
Tl Posts:
5879

USA
Posted - 6/11/2004 8:15:57 AM  Show Profile  Email Poster  Edit Message
You will Find that you will have allot less problems if you do a clean install of XP,not the upgrade. Remove the modem before doing this then install after XP is up and running. You can try this also,run ltremove.exe,shut down remove modem,boot up and check for any left over files to the modem.Remove the dial up connectoid,shut down,put modem back in,boot up and install modem.
mainbuss
Tl Posts:
145

USA
Posted - 6/11/2004 11:54:17 AM  Show Profile  Email Poster  Edit Message

Edited by - mainbuss on 7/10/2004 10:24:55 PM
charles
Tl Posts:
5879

USA
Posted - 6/12/2004 10:40:44 AM  Show Profile  Email Poster  Edit Message
The below has help alot with the 721 error. Remove the old dun connectoid,make a new one and do the below. Is this a HP pc?

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q318009


Right Click the connection icon
Left click Properties
Click the Networking tab
Click on the Settings button.
In the pop-up, uncheck Negotiate Multi-link for Single-link Connections.

charles
Tl Posts:
5879

USA
Posted - 6/12/2004 4:05:39 PM  Show Profile  Email Poster  Edit Message
If the above will not work might try this.
Reset the tcp/ip stack to the defaults.
Dial-up Networking and TCP/IP cannot be uninstalled on Windows XP. However, you can use the NetShell (netsh) utility to reset TCP/IP.
Click Start > Run.
In the Run box, type command and click OK.
At the DOS prompt, type netsh int ip resetc:\tcpipreset.txt and press the Enter key.
The system will pause for up to a minute while the TCP/IP stack is reset.
Once the cursor returns type exit and press Enter.
Restart your computer

Make sure agere is listed in the connect using window,not lucent or othe modems.

Click Here To Close Thread, Administrators & Moderators Only.

Show All Forums |