|Forums | USR | Win 2k doesn't recognize USR 56K WinModem as 56k||Watch|
|Posted - 1/9/2003 10:57:14 PM |
I have a USR/3com ISA 16 bit 56k Winmodem model #00568301 that Windows 2000 recognizes as a 33.6 modem. Win2k loads drivers for it that only allow it to be 33.6. Here's a hyperterminal log:
Level 3 Comm nas51.lax1 UQKT2
U.S. Robotics 33.6K Win INT Link Diagnostics...
I've tried setting the modem up with the different drivers that USR has on their site, but nothing seems to work. They don't have a driver set for Win 2000. Damn Win2k! POS. This modem was running perfect on my Win 98 machine. It's been with me for a long time and I've never had problems. Now I put it in my other box, Win2k loads 33.6 associates 33.6 drivers for it. Help.
|Posted - 1/10/2003 12:55:07 AM |
SNR (dB) 0.1 still showing phone line problem,should be higher like 30 or 40.Might want to try ATI6 for more info on line in hyperterminal.
What is the driver version that is installed now.
325683-02 - Canada
005683-00, 005683-01, 005683-03 - USA
Might try this driver.
|Posted - 1/10/2003 8:44:19 AM |
In the W2K Compatibility Guide it is showing your modem as a U.S. Robotics 56K Winmodem ISA.Might reinstall modem and pick it from the list and not let windows install it on its own choose U.S. Robotics 56K Winmodem ISA from the list.
|Posted - 1/12/2003 6:03:11 PM |
I've tried reinstalling that modem a number of times. It first recognizes it as a 56k modem, but then it installs it as 3COM Windows Modem ISA ADI. The driver for it is 5.0.2167.1.
I tried out that 568301w.exe file. I removed the modem and went to that file. When I double clicked the setup icon after unzipping it, computer just freezes up. Mouse works, but that's it. I have to Ctrl-Alt-Delete and end the task to get back control. I even have the Service Pack 3 installed for Win2k. Odd, huh? :-(
|Posted - 1/20/2003 6:25:30 PM |
I think you have to prevent Win2k from installing the driver it 'thinks' the modem should have.
Remove the modem from System-/HW Device Mgr; then
One way to do this may be to remove the appropriate files from the windows/inf folder. (Look for any USR .inf files that start with oem#### - these are files not included with Win2k; if it's installing a driver included in Win2k, you may need to locate the .inf file and remove that - text search PCI ID info may help find the file. This should prevent Win2k from finding and installing driver when you reboot and allow you to specify the driver.
Click Here To Close Thread, Administrators & Moderators Only.
Show All Forums |