I have a Windows NT/modem emergency and would appreciate any help! (I am running NT 4.0, SP6a, on a 500-MHz Pentium-III Arrow PC, with 256 MB of RAM.)
I just purchased and installed an internal 3Com Courier V.Everything 56k internal modem to replace an internal OEM Sportster modem for which my computer manufacturer would offer no support, since they did not install Windows NT on my PC, and for which 3Com nor my ISP could offer help. (It could not sustain a connection with my ISP.)
I installed the Courier (Product Code 002805-00) in the same ISA slot, using the same COM port (2) and IRQ settings (3) as the OEM modem (via the jumpers), but Windows NT 4 (SP 6) fails to recognize it (which was not a problem with the OEM modem, even if it was not reliable).
I tried using the driver on the 3Com Connections CD-ROM, the V.90 driver from the Courier section of their Web site's support section, and the V.Everything V.90 internal driver from Windows NT, 'Courier V.Everything INT (V.90&x2)'.
I deleted and re-entered my ISP information in my Dial-Up Networking address book and even deleted and reinstalled RAS and TCP/IP, and then reinstalled Service Pack 6.
When I try to dial-out with DUN, I get the error message, "Error 692: Hardware failure in port or attached device." I have the base I/O port address and IRQ settings for the Ports control panel set for the default IRQ settings, which worked fine for the OEM modem, and -- as I say -- I do have the jumpers set for COM 2 and IRQ 3 -- which worked for my OEM modem (which NT at least recognized).
I suspect I am making a mistake in the configuration of NT for use with this modem, not that the modem is bad, but I am at a total loss. This situation is a business emergency for me; I went from an unreliable modem to one which NT will not recognize at all. (By the way, I tried using HyperTerminal to test the modem, but it acts as if no modem is installed.)
Could you please offer me some advice? I am in urgent need of a reliable modem for my PC, since I leave to teach a Web-development workshop in Ukraine soon and cannot prepare without a modem!
Finally, I had a corrupted hive in my NT registry several months ago; I had to take the PC into a shop. Although they restored my data, I had many problems with NT and did a fresh installation. When I installed my OEM Sportster modem after installing NT, I had this same problem. After working at it for a week, I finally took the PC back to the shop and they got it working. They said it was set for plug-and-play, which I had discovered before taking it in and had set the jumpers; oddly, when I first installed NT and the old modem in early 1999, NT recognized the modem and I had reliable connections with my previous ISP (even though the modem was in plug-and-play mode at that time)!
Thank you, very much, in advance! I would appreciate prompt responses; I am up against a deadline and am totally frustrated.
I suspect the new modem is okay -- but I have done something to mess up Windows NT and its ability to recognize the modem!
P.S. -- I used the 3Com Knowledgebase, but it was of no help. I have also contacted 3Com support via their Web site, but my experience had not been very good with them, and it takes them a while to respond.
I have also searched the Microsoft KnowledgeBase and followed all the recommendations in the documents I found.