This is totally a stumper to me... I got a new modem to use for a build for my friends computer, and he decided that he didn't want one right now, so I decided to use it. After all, the modem was free anyway, and better than my previous one, seeing as it supports V.92. Anyway, I loaded the drivers and everything, and when I attempted to dial up to my ISP in Windows 2000, my dialer froze when 'initializing modem.' I did a little bit of checking... no IRQ, or resource conflicts. It should be working perfectly. So I tried it on a Windows 98 install, and it works. This is rather puzzling. The modem in Windows 2000 is on COM3, and I can't change it because it freezes every time I attempt to do so.
Confusing modem issue...
-
Please click the link below for your operating system to download the TSG SysInfo Utility. Click on "Save File" then double-click the file to run it. Copy and paste the report in your initial post. Windows 7 and later (downloads a file named tsginfo.exe) | Windows XP (downloads a file named SysInfo.exe)
- Status
1 - 9 of 9 Posts
Joined
·
754 Posts
Hi,
I don't know about your Win98 drivers, but I can tell you that the drivers in Win XP and Win2K are not V.92 drivers. I was told by a USRobotics tech that they were only V.90 drivers and would not work correctly without the newest modems that are V.92. You can download the latest drivers from your website and I can tell you that you will have to force feed them. Win will tell you that the drivers they have are O.K. and it is working properly.....NOT!
Specify the location and load them even if not digitally signed (that is another story) by Microsoft.
Also, as a precaution, put the modem in slot three or the third PCI slot from the AGP port. I have had a couple that required this to properly work.
I don't know about your Win98 drivers, but I can tell you that the drivers in Win XP and Win2K are not V.92 drivers. I was told by a USRobotics tech that they were only V.90 drivers and would not work correctly without the newest modems that are V.92. You can download the latest drivers from your website and I can tell you that you will have to force feed them. Win will tell you that the drivers they have are O.K. and it is working properly.....NOT!
Specify the location and load them even if not digitally signed (that is another story) by Microsoft.
Also, as a precaution, put the modem in slot three or the third PCI slot from the AGP port. I have had a couple that required this to properly work.
That would work except, I don't recall ever saying that I had a USRobotics modem. In fact it's a Hi-Val Soft Modem, and the chipset was made by Montblanc. Also, I looked, and found no drivers for it online. The only ones I had were on the CD that came with the modem. Mind you this was brand new, I bought it at Office Max no more than three weeks ago. I'd really appreciate any suggestions.
Joined
·
754 Posts
Hi,
Did not mean to implly that it was a USRobotics, but that even major brands such as USRobotics are having problems with XP and Win2K drivers. If new, your drivers might be the best, but even a new Best Buy USRobotics modem does not have the latest drivers as I found out. Hope you get it going.
Did not mean to implly that it was a USRobotics, but that even major brands such as USRobotics are having problems with XP and Win2K drivers. If new, your drivers might be the best, but even a new Best Buy USRobotics modem does not have the latest drivers as I found out. Hope you get it going.
Ah, I see. Well, I just did a little bit of work and disabled almost all of the devices that use the 9th IRQ. (IRQ that the new modem uses) It still froze. One thing I did notice is that under system devices, Windows 2000 lacked IRQ steering. Could that be an issue? Might I need chipset drivers, or is this just another thing built into Win2k? I also might mention that I want the modem to coexist with another modem, so I have it plugged in there as well. Might seem strange, but the modem I have is a modem/sound card combo, as said in my specs below. So I figured that if I just disabled the other modem and kept the sound, everything would work out. Guess not, eh? 
As for the V.92 modem drivers, the WinXP/2K driver comes with the Modem-On-Hold application that is used by V.92, so it would only make sense that the driver support it.
As for the V.92 modem drivers, the WinXP/2K driver comes with the Modem-On-Hold application that is used by V.92, so it would only make sense that the driver support it.
Joined
·
754 Posts
Most modems come factory default to use port 3. If you want to keep the other modem/sound card....go in and disable it and do not delete it. That should let them co-exist. Also, you might want to try your PnP in the off postion in the Bios Setup menu. That might let it set up correctly.
I looked through my BIOS to do exactly that. Turning off PnP. Of course, when Phoenix made my stupid HP BIOS, they neglected to add that feature...
The closest thing was choosing your OS. So I chose a non-PnP os from the list and all I got out of that was booting problems. I had to restore the factory default settings out of the extremely limited BIOS. Just a note, I should have mentioned that I took the other modem/sound card out, but it still failed to work. Tried switching PCI slots (Of which there is only two... stupid MicroATX..) to no avail. Definetely an annoying problem.
The closest thing was choosing your OS. So I chose a non-PnP os from the list and all I got out of that was booting problems. I had to restore the factory default settings out of the extremely limited BIOS. Just a note, I should have mentioned that I took the other modem/sound card out, but it still failed to work. Tried switching PCI slots (Of which there is only two... stupid MicroATX..) to no avail. Definetely an annoying problem.
I've seen other posts on the net saying that the COM port the mouse uses conflicts with the modem. I have a USB mouse at the moment, and I'm about ready to give it a try. Still doesn't make sense that Windows 98 works and 2K doesn't but I'll give it a shot.
1 - 9 of 9 Posts
- Status
Join the discussion
