Most Plug-and-Play modems do not work under NT,
so let's assume that your modem isn't one of those,
and that it is not a "winmodem".

Instead, let's hope that it is either a Rockwell-based modem,      
or a 3COM/US Robotics modem.  So, set the jumpers to COM4/IRQ3,
and use 'AT&F' (for the Rockwell) or 'AT&F1' (for the 3COM)
as your modem-initialization string, to set each modem to
its "factory-default" settings.

That's all the "driver" that you really need,
since a modem is just a piece of "hardware",
which really doesn't require any "driver-software" of its own.

Also, check:

Presario 4824
http://www.compaq.com/athome/showroom/classics/4824qs.html

and check:

Presario K56Flex Modem Driver Update
Models Affected: ... 4824, ...
http://www.compaq.com/athome/support/softpaq/pages/sp5836.html

Thanks for your input!  I'm not sure what the chipset is in the 56K-VSC modem...  I suppose I'll just have to pull the card and see what info is on it.  The jumper scenario would work fine, BUT, I also run WIN98 on that same PC; the modem functions fine under this OS.  I also have a Presario 5630 running WIN NT 4.0 Server and WIN98 which has a Rockwell chipset modem, and I was albe to find NT drivers for it... I didn't need to move the jumpers.  It's been like looking for a needle in a haystack to find a "driver" for this 4824 modem, though.

Thanks much!!!

See the above web-pages, which state that it is K56flex.
Use HyperTerminal, and send commands like 'ATI0', 'ATI1',
through 'ATI14' to the modem, and see if it identifies itself.
(Post those results here.)

Like I said, only the "winmodem" class of modems require
software-drivers to make them functional.
So, don't go looking for software which does not *NEED* to exist.
Instead, see which Compaq-brand modems that NT does support,
and pick one, and try it.

I wasn't able to get the modem to identifiy itself... I'd expect that from something made by Compaq.  I triedI pulled out the card and looked at the chipset.  It's a Lucent 1643.  I understand that when Compaq uses other manufacturers chips that the modem may not correctly identify itself anyway.  I tried a few "drivers" for other modems with the Lucent chip but no go... yet.  I wonder if it's worth it?  I've ordered a new modem that's compatible with NT (a cheap one), but I'd still like to conquer the Lucent chip under NT.  The Lucent 1643 chip represents a "winmodem", doesn't it?  That's what I've surmised...

Thanks for the help... this is the most useful exchange I've had thus far regarding this issue.

Sue-Ellen

GREETINGS!

This question was awarded, but never cleared due to the JSP-500 errors of that time.  It was "stuck" against userID -1 versus the intended expert whom you awarded.  This corrects the problem and the expert will now receive these points; points verified.

Please click on your Member Profile and select "View Question History" to navigate through any open or locked questions you may have to update and finalize them.  If you are an EE Pro user, you can also choose Power Search to find all your open questions.

This is the Community Support link, if help is needed, along with the link to All Topics which reflects many TAs recently added.  Also in the Community Support link is a question on how experts can help, if they wish, on the cleaning of old and abandoned questions.

https://www.experts-exchange.com/jsp/qList.jsp?ta=commspt
https://www.experts-exchange.com/jsp/zonesAll.jsp
 
Thank you,
Moondancer
Moderator @ Experts Exchange