US Robotics 56k Winmodem problems

Hello, I've had some problems recently with my US Robotics 56k Winmodem. My windows doesn't recognize it as PnP. When I replaced my Win ME (modem worked before) to Win XP Pro, the new windows can't seem to find it. I also installed Win ME on the same machine and it can't recognize it now either. I remember setting up the modem about a year or two ago, and I think COM port was 3. Right now I have only 2 COM ports, 1 and 2. With either one it doesn't work, says modem did not respond. My IRQ ports are all taken from 00 to 15, but 3 and 4 are the Communication Ports. As I said i tried both ports and they didn't work and the error message also says "check for interrupt settings of the modem ". I don't know which the right interrupt settings are.

Since I remember the modem work properly I replaced my old 15gb hd with new 20gb, and bought a new power supply, don't think i've done any other changes.

I've taken the modem in and out, restarted the system many times, both in Win ME and Win XP, and still nothing works. I also updated the driver for Win Me from www.usr.com website, still no help.

If anybody could help me, plz all comments are welcome.

P.S.: I changed my harddrive and power supply because both of them had a "melt down ". I don't know which caused which to break, but I had to change both of them. Not sure if my modem really works because didn't see it working since, but no visible burns or anything of that sort which was visible on my previous hd and power supply. Don't know where I can check if it works at all :/

Thanks in Advance

 

This is a common characteristic of an Internal Winmodem.

Many times they refuse to re setup in a system ( or OS ) other then the original one they were installed in.

A new modem * MIGHT * work. But you may run right smack into the same problem if you decide to change the OS again.

The best cure for this problem is a serial port External Modem. They are 99.5% more reliable and 99.5% less problems when changjing the OS.

BillyBob

 

So what you are saying is that i won't be able to get this modem up and running again? Or is there at least some hope? And how does the change of the OS affect the modem? Would I be able to set it up on another system?

I was still going to buy another modem, but throwing this one out isn't that good idea for me. I like using everything to its max

Thanks....

 

Or is there at least some hope?

You might try going to the device Manager and removing all COMM ports and then shutting down ( power off ) and restarting and see if the System will pick up the modem then.

You could also try going to the Control panel/add new hardware and adding a COMM port from the list.

You could also try getting into the BIOS and disabaling COMM2.

Sometime the above items work and sometimes they don't. But even if they do you could still run into the same problem when you change the OS again.

And how does the change of the OS affect the modem?

It is the Modem that effects the OS.

Each OS has its own way of handling IRQ asignments. Many internal modems ( once installed ) become hardcoded and refuse change to allow PCI IRQ steering to work properly.

Maybe I can not explain it completely but I do know that is the way WinModems behave.

Would I be able to set it up on another system?

Maybe and maybe not. Some will and some won't. And there is no way of telling until tried.

But I must add here that the suggestions above are actually from others that have been posted in the past. I fought with one PCI modem for two hours and will do my best to never fight with one again.

That is why I suggest an External serial Port set on COMM2 and you can be 98.5% relieved of any problems. And I can FULLY vouch for that as I had as many as three Externals at the same time and were used on everything from DOS to Win98 ME, at least 7 completely different systems and have NEVER given me one problem.

And External is well worth the extra initial bucks. And they are also a FULL MODEM. They do not leave half of the work for the CPU to do.

BillyBob

 

I don't believe a bad p/s would just damage the hard drive. More likely it was a bad drive that zapped the p/s. It is possible weaker components could have been affected as well in a "melt down ". There may be a problem originating from this incident, a change of O/S, and/or a flaky modem.

"My windows doesn't recognize it as a PnP. "
If you have a proper functioning PnP device, you shouldn't need to figure available ports or IRQs, as the system should make adjustments if necessary and provide the proper assignments. If there is a problem or an unresolved conflict, You will see a yellow question mark or other signs in your device manager section. It is possible you have a problem with your PnP Software Device Enumerator. You can update the driver or Rollback the driver if necessary. That may correct your PnP problem.

 

From what I've read, XP seems to be more friendly with Lucent.

 

Alright, thanks for all your help guys.

I'm not sure if the modem works at all, and I'm pretty sure I tried all the things possible.

So I will get my friend to check the modem out on his computer and if it works, probably will try to sell it, and get the external one

Thanks again

 

Ummm - Don't think so guys...

Look, before going through all that other nonsense, go to www.modemdriver.com

Here's the information you need to have before you go to the site -- Take a close look at your modem. Find the chipset that it uses. Also locate the manufacturer and the FCC product ID -- write this info down and go to the site to find the appropriate drivers...

I don't know what they're talking about when they say "...usually won't re-setup in another system... Get into the BIOS, etc. etc" -- These answers are wrong... Here's why WinModems have trouble being true "PnP" devices:

Modems require a COM port to run. In a real modem (not a WinModem) you literally hardwire which com port you want the modem to use, either by a jumper setting, a switch or by physically connecting it to an existing com port (external).. When this is done, the computer finds the new port. When the port exists, the computer can query the port and detect the device attached to it...

A WinModem is different... Because the COM port is "software-settable" there is no true physical com port. SO - When the proper drivers are installed, here's what happens:

A virtual com port is created using the first available port number.. When the virtual com port is installed properly, the computer querys it and detects the new modem and begins installing the appropriate drivers -- Hopefully --

If you download the appropriate driver for your WinModem Chipset, the setup should take care of all this for you -- If not, use the "Add New Hardware" wizard, and when it asks for a driver location, point it to the directory where you saved your download...

If the modem is in working conditions, this will work -- Good luck and I hope this helps!!

By the way -- I agree that if you have the extra cash, it IS worth the expense to get a "real" modem.. WinModems have always been plagued by problems -- Indeed, I just fixed my Aunt's computer 'cause she upgraded the OS and had a WinModem in the system..

 

I would suggest that someone be a little more carefull about calling things either nonsense or wrong.

They are not dealing with some still wet behind the ears newcomers to the world of computing and the problems that WinModems can cause.

Not getting picked up and setup properly by the OS is just one of several problems they can cause.

When dealing with WinModems there is no "One fix that fixes all." It can be a very machine/OS specific problem. Different SYSTEMS may require a different fix. And SYSTEM means everything from the MB and hardware on up to and including the the OS.

And that is what this BB is all about. To get different ideas in hopes that at least one of them will work.

And when anybody makes a reply USING EXPERIENCE as a base they are not wrong. Neither is it nonsense.

BillyBob

 

Obviously a hardwired modem or (external modem? if there is a dedication) have attributes that avoid software setting protocol. But is it always the modem's problem if it is not detected or can it also be the software that searches for and installs the driver?

Back when I had another PC with a 98 system I had problems with the modem. At the time I was playing around with 95 and 98 on one partition and there was an obvious conflict!! I solved the modem re-installation problem by manually searching and extracting the correct driver from its cab and installed it on a floppy, and when there was a modem problem, and using the add/delete hardware system program, I prevented unsuccessful searches or incorrect driver installation by inserting the floppy when asked. It didn't prevent having a problem with the modem, but it enabled a re-installation without a problem!

 

Your question

But is it always the modem's problem if it is not detected

My answer.

Everybody keeps referring to just the Modem. ( including me I guess ) But there may be numerous other factors involved. Such as what other cards etc. are installed.

The fix that may work for say KenKeith, or Donniesito may either not work at all or may cause different problems for me.

And the fix that works is the one that is right for that system.

When you get an ISA modem that will stop the machine from booting ( not even to a floppy ) then you have some real hair pulling problems.

And the darn thing worked fine untill I tried to re-install the OS ( 98 FE )

I disabled COMM2 ( after enabling and disabling with the old modem with no success ) in the BIOS. Pulled the old and plugged in an ancient Boca Research ISA 33.6, turned the machine and away we went full speed ahead. It has since been replaced by one of my old Externals only in order to get up to 56K.

Internal Modems can be one very tough piece of hardware to deal with.

WOW !!! I just looked and the temperature outside is reading 89 degrees. NO wonder I am getting a little warm. Guess I need to get out of here and uncover the AC before this PC gets a little too warm. If I am uncomfortable so is the PC.

BillyBob

 

My quote as part of your response is a rhetorical question and in context the answer would be there are other considerations! As clear as I can read, you are agreeing with my last post. Your general answer does not enlightened nor add anything we on this thread do not already know. My assumption

We all know an internal modem is a communication component of the PC system. It is not a stand alone device, therefore, the proper integration into the O/S or lack thereof can be or not be the modem.

In my opinion a hardwired or external modem has stand alone features in the sense there is dedicated connectivity, and the reliability and functionality has more to do with the modem's attributes and its failure or success has less to do with software that its counterpart the internal modem.

 

If you are saying that it would have been better if I had stayed with my first choice of an answer which would have been much shorter and more to the point, I do sort of agree.

That would have been.

From my standpoint of experience, NO. Not always. Just most of the time.

But it does depend a great deal on the Modem itself. Some will take the system changes and some won't.

BTW. The temp is down to a more comfortable 70 degrees.

 

I will try www.modemdriver.com tonight, but don't think it is going to help, since I got the latest drivers and even the driver that I had before doesn't work now with Win ME where I had the modem running properly earlier.

I'm not sure if the modem is working, so I will take it to a friend and try to set it up on win NT system. We'll see what it'll do....

 

Apology

After reading the other replies and my own posting, I feel it necessary to apologise. I hadn't realized when I was typing last night how arrogant I sounded, and again I'm sorry ;-)

 

When I was having modem problems, I found there was difficulty for my 98 system to detect and/or identify the correct Win Modem's driver. The modem itself was OK.

My conclusion is based on the following: There is a cab of drivers with every O/S and included in that group is a general driver that was substituted some of the time for the more appropriate driver with a re-installation. Sometimes the correct driver was installed and there weren't any problems until I switched to a different system that was installed on the same partition. This indicated to me the Win Modem was not properly indentified at times and on a re-installation the sometimes installed substituted driver caused problems. Granted having two different systems on the same partition induced the problem.

I don't totally agree that it is the modem itself that is the problem a great deal of the time, but it has much more to do with the O/S software that comes into play with certain modems; specifically identifying the address of the modem and the modem itself, and then properly installing the correct driver and not a substitute driver. An external modem would not present any such problems because the address is fixed and modem is easily identified.

Regarding the theory that some modems become hard-coded for its address and then not easily changed, if true, this phenomenon would be a software problem and not due to any electronic configuration of the modem card.