• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Modem added on every cold boot

Ryland

Platinum Member
My friends computer keeps adding a new modem every time she boots it up. After awhile it takes 40 minutes for the computer to start because it has to time out all of the non-used modems. Is there anyway to turn off the new hardware detection?
 
I'd try Safe Mode,F8, and then Uninstall all the modems in the list in Device manager. Then I'd reboot to either the regular OS or Safe Mode and let it detect the modem. I would either feed the darn thing the correct driver or Disable it in Device manager.

Larry
 
I have deleted all of the modems (sometimes up to 40) and then reinstalled the one single modem that should be there. FYI this is under Vista and the subsequent modems always end up with a wrong COM port number. I can't disable the modem since she needs it for faxing.
 
Originally posted by: techmanc
Are you using the latest chipset drivers for that computer?

^ + 1

Also, are you letting bios designate the ports, irq's etc? Another thought is to manually set the port for the modem.

Larry
 
Hmm...I think I installed the latest chipset drivers for it when I set it up but I will verify that. The bios is automatically setting the irq and port for the pci slots. Great point on that. Guess I have something to do next time I goto her house.
 
You can download Crossloop and install it on both computers then you can do remote desktop if needed. This wont help to check BIOS issues tho. Here a link pretty east to setup and use you dont need to make a account to use it either..........................

http://www.crossloop.com/
 
When this happened to me, on Win95, it was because the registry structure was corrupted. A "SCANREG /FIX" fixed the problem.

I have no idea if it has the same cause on XP, or how you would scan and fix the actual registry structure under an NT-based OS.
 
Well this is a fresh install of Vista so it shouldn't be a registry corruption but I guess I could try doing a fix on it.
 
Back
Top