USR 5610B modem problem: becomes inactive erratically
Stan
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 the initial 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 sudden, new, normal modem connection sounds. I usually
listen to one or two sets of these apparently new 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 occurred *in
the same computer* when I used, in the near past, the Linux OS with this
modem.]
I recently removed this modem from the newer IBM computer it was
originally installed in and I installed it inside another, older IBM
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.
[Incidentally, I have no modem problem on this same phone line when I use
a Linux computer which connects to the Net with an external USR
serial modem.]
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 use 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 in which this modem was once installed), the
problem must be with the modem and not something else. [Someone in another
forum told a poster to get an rf filter for the phone line. Since I have
no modem problem with my external, serial USR modem (for the Linux
computer) on the same phone line, wouldn't it be a waste to get such an rf
filter for the internal USR modem which has some problem?]
Thanks
Gary A. Edelstein
wrote:
I understand filters are for DSL enabled phone lines, so that is out.
It appears to be a problem with the modem hardware or how the modem
interacts with your phone line or devices on the line. One way to
test the latter by taking the machine to another location and using a
different phone line. You could also disconnect all devices from the
line, including all handsets and other modems and see if that makes a
difference. It could even be a grounding or line voltage problem.
Different modems interact differently with phone lines, so the fact
your external works doesn't necessarily mean anything. Picking up a
handset returns data transfer is a further clue that it may be your
line.
It could even be a bad modular wire going to the modem, wall jack or
the modem modular plug contacts are corroded.
I don't think it's a software, driver or IRQ/resources problem based
on the fact it behaves the same in different machines.
Gary E
--
|Gary A. Edelstein
|edel...@SPAMyahoo.com.invalid (remove NO SPAM and .invalid to reply)
|"We have met the enemy and he is us." - Walt Kelly's Pogo
Stan
> It appears to be a problem with the modem hardware or how the modem
> interacts with your phone line or devices on the line. One way to
> test the latter by taking the machine to another location and using a
> different phone line. You could also disconnect all devices from the
> line, including all handsets and other modems and see if that makes a
> difference. It could even be a grounding or line voltage problem.
> Different modems interact differently with phone lines, so the fact
> your external works doesn't necessarily mean anything. Picking up a
> handset returns data transfer is a further clue that it may be your
> line.
>
> It could even be a bad modular wire going to the modem, wall jack or
> the modem modular plug contacts are corroded.
>
> I don't think it's a software, driver or IRQ/resources problem based
> on the fact it behaves the same in different machines.
Thanks Gary for the tips and info. I hope to test certain things later. I
have the following question first though.
Regarding the phone wire going to my telephone (which is on the same line
as the internal USR modem): this probably 25' long, flat-type phone line
(so I can carry it to one or another room) does make a great deal of static
when I'm talking to someone and surely causing the wire to move or shake a
bit. But since the wire is not being disturbed or moved when I'm on the
Internet I figured it was not part of the problem. But could it be? Could
some slight break in one of the metal wires inside the phone have, even
when that long phone line is not being shaken or disturbed (such as when
I'm on the Internet), be behind this problem?
Thanks,
Stan
Gary A. Edelstein
wrote:
Well, it's possible a modular wire or the connections on each end of
the wire could cause problems when using the phone and possibly the
modem, especially if the connections are loose or corroded. There
could also be a problem with the phone itself. Again, the way to test
this is to disconnect it from the line and see if it makes a
difference.
As I said, disconnect all devices from the line except the modem. If
that does seem to fix it, then reconnect them one by one and test the
modem each time to try to zero in on the culprit.