|Forums | USR (Public) | USR 5610-B modem problem: becomes inactive erratically||Watch|
|Posted - 4/12/2006 4:01:44 PM |
Not so long ago I got a used computer having an internal, US Robotics, 56K, PCI "Performance Pro" modem (model 5610-02 aka 5610-B). In this computer I installed 2 OSs on the single HDD: Win98 1st Edition and Linux. I had the same modem problem with both OSs. The problem is that I can connect to the Net but the modem becomes inactive unpredictably. It can work fine for a minute or two or for a few hours but then suddenly becomes inactive-- I don't know if something I do triggers this inactivity or if it just happens. Nothing freezes up and no crashes occur but I can't send or receive email nor go to any website. When this happens with Win98, my Win98 Net connection icon says the connection is there. Also, when this happens, I found that if I pick up the nearby phone handset (which is on the same phone line as the modem) I hear modem connection sounds. I usually listen to one or two sets of these modem connection sounds, put down the phone handset, and find that the modem is OK again: I can use email and go to any website. [Remember, this same problem occurs *in the same computer* when I used the Linux OS with this modem.]
I recently took out this modem and put it in another computer which runs Win98 1st Edition as OS. The same problem occurs.
I contacted US Robotics about this but all they tell me to do is update my BIOS. I did that but the problem has not gone away.
The init string I have for this modem is simply AT&F.
Does anyone here know what could be wrong and how this is fixed? [I believe I have the latest drivers for this USR modem.] Is there some unusual or common setting that has to be changed or set somewhere? [I have this modem now only for a Win98 1st Edition computer.] I figure that since I had this same exact problem with two different operating systems (when I had these two OSs in the computer which came with this modem), the problem must be with the modem and not something else.
|Posted - 4/16/2006 7:48:52 PM |
You should use init string
AT&F sets the modem differently & is not appropriate for high-speed connections.
With Windows, an init string shouldn't be necessary at all as Windows will do this for you, and putting an init string (Extra setting) will override all the settings that Windows does; if the modem is installed correctly with the USR driver, the init strings given to the modem will be correct/based upon your DUNs connectoid and modem property settings.
The post-call diagnostics
|Posted - 5/15/2006 4:40:55 PM |
I have the very same modem with the very same problem but I'm running Win XP Pro. I have never had this problem before and my modem ran flawlessly for months until just about 3 weeks ago with its start this problem. I even thought that maybe my modem had gone bad so I got a new one and the problem remains. Any help in fixing this would be GREATLY apprecated.
|Posted - 5/16/2006 8:51:32 AM |
Ok, I found the fix for this. This is a problem that a lot of ppl who have this modem are having and this sting seems to fix it.
You can also try these ones too if that does not do it for you.
|Posted - 5/16/2006 1:32:48 PM |
Wonderful! Thanks for your research and help. I'll soon be using my Win98 1st Edition computer and will change the init string for the USR modem. I'll see which one of your init strings solves the problem.
Click Here To Close Thread, Administrators & Moderators Only.
Show All Forums |