Compaq Presario Modem Problems on Win2k

  • Thread starter Thread starter Pegasus \(MVP\)
  • Start date Start date
P

Pegasus \(MVP\)

I'm puzzled: Why do a lot of research into an incompatible
modem if a new internal or external modem would cost so
little money?

To remove Win2000:
- Boot into Win98
- Rename c:\WinNT to c:\WinNT.old
- Wait a few days
- If all is well, remove c:\WinNT.old
 
I have come across an old(ish) Compaq 1650 that I would like to upgrade to
Win2000. But there's a catch: the modem won't work. I have done a little
(well, quite a lot) of research into this issue, and what I have found is
NOT encouraging.

Both compaq and microsoft Knowledge base tell me it Can't Be Done. Or
rather, get a new modem or go back to Win98 (*Gasp*). a google groups
search also yielded very little helpful info.

Currently I have set up this laptop as a dual boot (98, 2k) until I can
get the modem issue fixed. (modem works just fine under win98)

The gory details:
compaq presario 1650
compaq presario 56k-df modem (or lucent winmodem, or LT winmodem......
depending on which drivers I try next)
96 meg ram

Device manager typically lists the following message under the modem:
"The device is disabled because the firmware of the device did not give
it the reqired resourses. (Code 29)"

MS KB227469 Says bios does not accurately report modem properties to win2k.

If possible I would like to know if there is ANY way to get THIS modem
working under win2k.
If not, is there any way of removing win2k from the dual boot short of
reformatting. If i have to revert, then win2k is just taking up disk
space)

I would also like a better understanding of the problem.....
 
-----Original Message-----
I'm puzzled: Why do a lot of research into an incompatible
modem if a new internal or external modem would cost so
little money?

Well, if it were MY computer....... I would have. It
actually belongs to my step-father. He has an aversion to
Spending Money.

The other half of this is I'm rather stubborn. :)
 
I'm stubborn too . . . I had a similar case like yours and it took
me six months to find a suitable driver (because ultimately I
stumbled over one that worked). www.driverguide.com plus
a lot of patience might help.
 
Back
Top