Prev: Newegg cult
Next: IC9R Raid5 array rebuild question
From: Bob M on 4 May 2008 13:48
Jon Danniken wrote:
> <letterman(a)invalid.com> wrote:
>
>>I'm running Win98se. Neither modem is recognized.
>
>
> Uninstall the software, the drivers, turn off the computer, and physically
> remove the modem.
>
> Reboot. Reboot again for fun.
>
> Install the software/driver. Reboot.
>
> Turn off the computer, install the physical modem, turn the computer back
> on.
>
> It should find the modem and apply the previously installed driver. You
> might have to reboot again.
>
> Jon
>
>

In addition to what was suggested abobe, try another PCI slot. When I
was using Win 98 I ran into modem problems from time to time. Using
another PCI slot would sometimes work.
Bob
From: "nobody >" on 4 May 2008 15:39
Bob M wrote:
> Jon Danniken wrote:
>> <letterman(a)invalid.com> wrote:
>>
>>> I'm running Win98se. Neither modem is recognized.
>>
>>
>> Uninstall the software, the drivers, turn off the computer, and
>> physically remove the modem.
>>
>> Reboot. Reboot again for fun.
>>
>> Install the software/driver. Reboot.
>>
>> Turn off the computer, install the physical modem, turn the computer
>> back on.
>>
>> It should find the modem and apply the previously installed driver.
>> You might have to reboot again.
>>
>> Jon
>>
>
> In addition to what was suggested abobe, try another PCI slot. When I
> was using Win 98 I ran into modem problems from time to time. Using
> another PCI slot would sometimes work.
> Bob

I've alway put the modem in the slot farthest away from the video card,
be the modem ISA or PCI after having troubles with closer slots (1 or 2
away). No real good reason, just that video cards do tend to radiate a
lot of noise in the case.
From: mike on 4 May 2008 17:41
hey I feel like it's 1998 again...
From: Flasherly on 4 May 2008 22:51
On Apr 30, 11:47 pm, letter...(a)invalid.com wrote:
> I have always used external modems. I think internal modems are the
> curse of the universe. I swore I would never use another internal,
> but my 56K external is running real slow and only connecting at 24K. I
> suspect the phone lines, since we are having some flooding. To verify
> that is in fact the phone lines, I thought I'd try another modem.
> Unfortunately I only had 3 some spare internals. One already went in
> the trash because it had a loose part. The others appear to be ok,
> for whatever that's worth. I do suspect they are ok, since I took
> them out of other working, but slow computers that I stripped for
> parts. They are PCI card types.
>
> One is a US Robotics model 0637
>
> Two is a Cyber Star CY-MDM-Cyber 10 56K data-fax modem (whoever makes
> that thing). And that one contains a MIC and SPK jack, so I assume it
> contains a built in sound card.
>
> I hesitated to plug in that Cyber Star, but the USR modem seems like
> it would be the ticket, since USR makes good modems.
>
> I'm running Win98se. Neither modem is recognized. I tried 2
> different PCI slots. If I try to use the manual settings, and select
> "Standard Modem", it always gives me COM 1 and COM 2. Shouldn't it
> give me com 3 and 4? After all, both com1 and com2 are assigned to
> the com ports, even though they are no in use with my ext modem
> disconnected.
>
> No matter what I try, neither modem is even found, and I tried to
> allow windows to find it, and did it manually. I even booted to dos
> and tried to run an old dos version of Telix for dos. Nothing finds
> the damn things. Internal modems are the curse of civilization and
> likely the reason we have so much violence in this world, because AI
> am darn near ready to take a hammer to all of them.

There's a com port it's assigned to along with an IRQ. They're
expected and have default values. You may have your MB overmapping it
in the BIOS (active with nothing connected to the port). Try turning
it off. HIREMS or a DOS level diagnostics util may help. Pin jumper
the board for its defaults, then. External generally is the way to go
but I've also had good luck with a software-driven datapumps at V90 --
Lucent and others. Been awhile - I've a couple nice new externals in
boxes that may end up the trash can. Nobody can stand running them
anymore. Getting the hardware ID'd is only the first part -- then
you've all the command strings specific to a chipset and combinations
best for hitting on a entirely different one you're dialing into.
Results from the correct INF file for Windows to provide actual
connection information. Similar to controlling a printer with control
codes, except printers don't necessary reach out in a blizzard to make
a connection into Canada.
 | 
Pages: 1
Prev: Newegg cult
Next: IC9R Raid5 array rebuild question