|
|||||||
![]() |
|
|
LinkBack | Thread Tools | Search this Thread |
Rating:
|
Display Modes |
|
|
#1 |
|
Member (10 bit)
Join Date: Oct 2002
Location: Central Virginia
Posts: 780
|
external modem problems....Attn. reboot
Anyone who can help would be fine, it's just that reboot gave me some instructions in another thread so I titled this thread this way. Here is where I stand with this problem. I've bought a US Robotics External 56k data/fax modem. It works fine on my Dell but not on my new build with windows XP. I have totally removed everything, both modem and drivers from Safe mode, and restarted and checked and all was gone. I reconnected the modem and installed the latest drivers from USR, removed old and setup new dial-up connection. It will not work. I checked the modem log and here is what it says, I know it's long but does it help? It's as if the serial port doesn't see the modem. It's setup just like on my other pc. I can unhook from my new one and hook it up to my Dell and it works fine.?????
11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\tapisrv.dll, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\unimdm.tsp, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\unimdmat.dll, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\uniplat.dll, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\drivers\modem.sys, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\modemui.dll, Version 5.1.2600 11-20-2002 23:08:24.406 - File: C:\WINDOWS\System32\mdminst.dll, Version 5.1.2600 11-20-2002 23:08:24.406 - Modem type: U.S. Robotics 56K FAX EXT PnP 11-20-2002 23:08:24.406 - Modem inf path: oem9.inf 11-20-2002 23:08:24.406 - Modem inf section: Modem_2082 11-20-2002 23:08:24.406 - Matching hardware ID: serenum\usr2082 11-20-2002 23:08:24.406 - 115200,8,N,1, ctsfl=1, rtsctl=2 11-20-2002 23:08:24.406 - Initializing modem. 11-20-2002 23:08:24.406 - DSR is low while initializing the modem. Verify modem is turned on. 11-20-2002 23:08:24.406 - CTS is low while initializing modem. 11-20-2002 23:08:24.421 - Send: AT 11-20-2002 23:08:26.421 - Timed out waiting for response from modem 11-20-2002 23:08:26.421 - The modem failed to respond to the initialization command, Retrying one more time 11-20-2002 23:08:26.421 - 115200,8,N,1, ctsfl=1, rtsctl=2 11-20-2002 23:08:26.421 - DSR is low while initializing the modem. Verify modem is turned on. 11-20-2002 23:08:26.421 - CTS is low while initializing modem. 11-20-2002 23:08:26.421 - Failed to send command because of WriteFile() Failure, Error=000003e3. 11-20-2002 23:08:26.437 - Send: AT 11-20-2002 23:08:28.437 - Timed out waiting for response from modem 11-20-2002 23:08:28.437 - The modem failed to respond to the initialization command, Retrying one more time 11-20-2002 23:08:28.437 - 115200,8,N,1, ctsfl=1, rtsctl=2 11-20-2002 23:08:28.437 - DSR is low while initializing the modem. Verify modem is turned on. 11-20-2002 23:08:28.437 - CTS is low while initializing modem. 11-20-2002 23:08:28.437 - Failed to send command because of WriteFile() Failure, Error=000003e3. 11-20-2002 23:08:28.453 - Send: AT 11-20-2002 23:08:30.453 - Timed out waiting for response from modem 11-20-2002 23:08:30.453 - Failed to send command because of WriteFile() Failure, Error=000003e3. 11-20-2002 23:08:30.453 - Session Statistics: 11-20-2002 23:08:30.453 - Reads : 0 bytes 11-20-2002 23:08:30.453 - Writes: 0 bytes |
|
|
|
|
|
#2 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
It seems the port is not active.
Are you sure it's enabled in BIOS? Are you sure Windows "sees" the port in device manager, and it's working correctly? Are you sure the cable to the modem is installed and working properly? Are you making sure the modem is turned on BEFORE the computer is started? Are you sure the physical port on the back of the computer is attached to the motherboard? (the port will be active, and windows will show it to be working, but there's no physical connection from the board to the port). This could be an indication of a faulty solder joint at the actual port. |
|
|
|
|
|
#3 |
|
Member (10 bit)
Join Date: Oct 2002
Location: Central Virginia
Posts: 780
|
Thanks alot reboot for taking the time to help me address this.
"Are you sure it's enabled in BIOS?" In BIOS I'm given the option to enable/disable, auto, or change the add. and IRQ. It is enabled. "Are you sure Windows "sees" the port in device manager, and it's working correctly?" In device manager it shows up and says working correctly and no conflicts. "Are you sure the cable to the modem is installed and working properly?" I can turn everything off, unplug it and turn and plug it into my Dell which is right next to my new PC, boot up and it works fine. "Are you making sure the modem is turned on BEFORE the computer is started?" Yes I am. "Are you sure the physical port on the back of the computer is attached to the motherboard? (the port will be active, and windows will show it to be working, but there's no physical connection from the board to the port). This could be an indication of a faulty solder joint at the actual port." I have not done this. However, When I first installed the modem, which was one of the first things I did after windows loaded, Windows recognized it but didn't like the software. At that time, being unable to get online and download updated drivers, I was stopped. At that point I removed the internal modem (conxtant) from my Dell and installed it and it worked. I downloaded updated drivers from USR and did the "update drivers" to no avail. Let me say that the modem did work for awhile. My son-in-law contacted my ISP to help setup the dialup thinking that was the problem. He did get the modem to connect to the ISP but it was so slow that you couldn't do anything with it. So I uninstalled all the modem stuff and started over. I even did what you said in your earlier post but nothing seems to make windows see the serial port. I've even tried to update the port drivers but it says they are the best available. Microsoft does not list the modem as compatible but USR says that they've tested it in XP and its ok.?? I wish I had some other serial hardware to test the port to make sure windows wasn't just refusing to recognize the modem. And last, I read that you shouldn't "uninstall PnP hardware in XP, just unplug it. They kinda made it sound like you could end up with the kind of mess I'm dealing with. |
|
|
|
|
|
#4 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
OK, here's my next thoughts:
You installed the Conexant from your Dell, and Windows still thinks that's the modem you're using. Until you rid Windows of the Conexant drivers, and uninstall anything that came with those drivers, THEN start fresh installing the 3com, it won't work. Using "Update drivers" simply forced the USR/com drivers to apply themselves to the Dell/Conexant modem. In Explorer, browse to c:\windows\inf\other and see if there's anything there related to your Dell modem, delete (or rename) them all. Boot to safe mode, remove the modem(s), and all com ports in device manager. Restart, with the modem NOT attached to the computer. Shutdown. Plug the modem in, turn it on, restart. If Windows doesn't detect it, run the Add Hardware wizard. Once it's finished installing, you must go into IE, Connections tab, and specify the new modem to use for your connection. If that doesn't work, remove all connections from dial-up-networking, restart, then go to Start > Run > and type in:inetwiz Make a new connection to your ISP. I think that you may have read that last bit wrong...if you don't uninstall PnP hardware in XP, you can run into this mess. You could put the Dell modem back in, then uninstall it, and shutdown, remove it, restart, and start fresh again. |
|
|
|
|
|
#5 |
|
Member (8 bit)
Join Date: Jul 2002
Posts: 217
|
Just out of curiuosity is this modem USB or ehternet external??
I had trouble with my modem I switched ethernet cards to a difffrent slot and it worked fine.
|
|
|
|
|
|
#6 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
It's an external serial, as he said in his other post.
|
|
|
|
|
|
#7 |
|
Member (10 bit)
Join Date: Oct 2002
Location: Central Virginia
Posts: 780
|
Thanks alot reboot, you've had a lot of patience with me. I'll try it again.
|
|
|
|
|
|
#8 |
|
Member (8 bit)
Join Date: Jan 2002
Location: Oz
Posts: 195
|
XP does have issues with some modems..
See if theres updated XP modem drivers available off the manufacturers site... |
|
|
|
|
|
#9 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
Drivers won't help a modem that's not recognized at the port (hardware) level...
|
|
|
|
|
|
#10 |
|
Member (10 bit)
Join Date: Oct 2002
Location: Central Virginia
Posts: 780
|
You're right reboot and thats my problem right now. No matter what I've done it will not recognize the modem. I've tried everything you wrote above and nothing makes the pc find the modem. I can install it anyway and it will actually show up in device manager and in modems in control panel but evidently windows will not recognize it. That says drivers to me. Sooooo..... I restored clear back to the point that I installed xp, but it still will not recognize it. Short of reinstalling windows I'm afraid it isn't going to. It did recognize it the first time I booted with it hooked up. But it wouldn't dialup. When I installed the updated 5686e.inf it conned but download and upload was excruciatingly slow. When I tried to do it all over again the problems started. And now no matter how I remove/uninstall the modem, drivers, serial ports/drivers, and reboot, it never recognizes the modem. I wish I had some other serial port hardware to make sure it isn't the ports. I don't think it is because as I said it recognized it the first time it booted with it connected. To note, this is very similar to the problem I had with my old Thrustmaster wheel when I got my Dell. I wouldn't recognize it no matter what I did, new drivers or not. I'm back with the Dell modem in here now so I can post this. I'm about ready to give up. I had to on the wheel because there was no support for making it compatible with ME. Don't you think that it is a driver issue?
|
|
|
|
|
|
#11 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
No, that should say "hardware" if windows can't autodetect it.
The problem arises by manually installing a card. Resources get shared that don't want to share, and it MAY still be in device mangler, and may even say it's working, but it won't. Maybe install it on com 2, and remove com 1 from device mangler and disable com 1 in BIOS, activate com 2, and see what happens... I still think this is a hardware issue. The modem may work, but because it's sharing resources with something more important (video, IDE bus, etc.) it's got it's problems. Last thought; go into device mangler, System devices, PCI bus, IRQ steering tab, and DISable IRQ steering. restart see what happens. You can always set a restore point before this, and/or go back and turn IRQ steering back on if it craps out. |
|
|
|
|
|
#12 |
|
Member (10 bit)
Join Date: Oct 2002
Location: Central Virginia
Posts: 780
|
I'll try it. Are the serial ports on the PCI BUS? When I let windows search for new hardware it says it hasn't found any. Key word is "new". Couldn't windows still be seeing the modem as connected even when it isn't? I know I can disable the ports in BIOS, but I think it can be done in Windows also?? My MOBO manuel shows the six PCI ports in a graphic that shows them sharing with ?? whatever. I'm sure you're familar with what I'm trying to describe. I don't have a clue. Thats why I asked if the serial ports are on the PCI bus. Thing is, I don't have anything installed on the PCI bus except the Dell modem, which I removed prior to trying to get windows to recog. the USR. Here's something. After restoring, I still had mouse, printer, scanner, keyboard, all that stuff conned. When it finished restoring it began automatically finding new devices. All of which it loaded drivers for automatically, except the scanner. It needs to get them online. Now through all reboots to try and make this thing work, it keeps coming up "new device found scanner", because, I presume, that the drivers have not been installed?? Once the drivers are installed of course windows no longer sees it as a "new" device. So when I restored, it should have left behind the drivers I installed for the USR modem the first time, right? Just like it did the scanner. And with it connected without drivers, it should be coming up "new device found modem" each time I boot. Man, this could have you under the bed reciting the Greek alphabet!!. So you believe that it is hardware related and the problem lies in the IRQs and addresses.
|
|
|
|
|
|
#13 |
|
Member (14 bit)
Join Date: Mar 1999
Location: Kelowna, B.C., Canada
Posts: 9,138
|
I guess what I'm trying to get at, is the com port active and working properly? If you switch com 1 off and com 2 on in BIOS, does windows detect that, and make the changes in device mangler?
If that is all working right, then it's time to get windows to see the modem. Even if it can't install drivers, it should notice a device on the com port, and try to do something. In device manager, the modem may be showing up under "Other Devices", or even "Human interface devices"... If you boot to safe mode, and remove anything that might be sharing with the com port, even sound cards, etc., then new devices should be detected on restart, and resources assigned for each. |
|
|
|
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|