mred
asked on
Modem installs; looks good but wont pass diags. Many modems tested on this system. All Bad.
I put a new know good Motorola modem on this system & diags won't pass it.
I had used this system to test about 10 different types of modems and downloaded drivers and NONE have tested good. I thought it was I was just getting screwed up drivers but now am very sure something else is wrong.
I've deleted and reinstalled the network TCP/IP. Client. & other STUFF reloaded the modem & it still comes up with the "Check the modem; not responding" message in modem Diags. I've tried to delete the other modem stuff in the register & now in the modem diags on comm4 where it is, there is no name of the modem it's just blank but I test it anyway (the com4) it takes a while like it sees it but comes up "no luck" just like it did before I deleted the stuff in the registery. It's just a test bed computer so I don't care much if I must reformat it am just wondering if any of you wizzes have any ideas??
I had used this system to test about 10 different types of modems and downloaded drivers and NONE have tested good. I thought it was I was just getting screwed up drivers but now am very sure something else is wrong.
I've deleted and reinstalled the network TCP/IP. Client. & other STUFF reloaded the modem & it still comes up with the "Check the modem; not responding" message in modem Diags. I've tried to delete the other modem stuff in the register & now in the modem diags on comm4 where it is, there is no name of the modem it's just blank but I test it anyway (the com4) it takes a while like it sees it but comes up "no luck" just like it did before I deleted the stuff in the registery. It's just a test bed computer so I don't care much if I must reformat it am just wondering if any of you wizzes have any ideas??
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Have you disabled COM2 in the BIOS. That can sometimes interfere with the system.
Look in C:\Windows\INF and see if you have the following files:
MDMMOTO.INF
MDMMOTO1.INF
MDMMOTON.INF
MDMMOTOU.INF
Look under the headers:
[Manufacturer]
%Mfg% = Models
[Models]
%Modem1% = Modem1,
etc.
MDMMOTO1.INF is the generic motorola driver, while the others are specific.
If they aren't there, then try getting them off the CD and placing them in C:\windows\INF and C:\windows\INF\other
Batch file to extract .inf file to each folder.
Replace the "x" for your CD Rom Drive's Letter.
@echo off
EXTRACT /Y /A x:\win98\BASE4.CAB MDMMOTO1.INF /L c:\windows\INF
EXTRACT /Y /A x:\win98\BASE4.CAB MDMMOTO1.INF /L c:\windows\INF\other
exit
Delete the device manager entry, run this batch file in Windows, and then reboot.
Worth a try?
MDMMOTO.INF
MDMMOTO1.INF
MDMMOTON.INF
MDMMOTOU.INF
Look under the headers:
[Manufacturer]
%Mfg% = Models
[Models]
%Modem1% = Modem1,
etc.
MDMMOTO1.INF is the generic motorola driver, while the others are specific.
If they aren't there, then try getting them off the CD and placing them in C:\windows\INF and C:\windows\INF\other
Batch file to extract .inf file to each folder.
Replace the "x" for your CD Rom Drive's Letter.
@echo off
EXTRACT /Y /A x:\win98\BASE4.CAB MDMMOTO1.INF /L c:\windows\INF
EXTRACT /Y /A x:\win98\BASE4.CAB MDMMOTO1.INF /L c:\windows\INF\other
exit
Delete the device manager entry, run this batch file in Windows, and then reboot.
Worth a try?
Have you looked to see whether it has been registered anywhere in HKEY_LOCAL_MACHINE\Enum\PC
This relates in part to what war1 was suggesting about a different PCI slot.
This relates in part to what war1 was suggesting about a different PCI slot.
ASKER
War1;
Damn, you were right on both counts. #1 all I thought I had to delete was MSTCP. I didn't have the DHCP's and didn't until just now see that there was also the Winsock so I hadn't deleted those (even if I had em.) Upon boot up I got the Password for the first time in so long I had forgot about it. I thought "Yea that's it" but it didn't pass diags again. Upon checking your answer the other thing was change slots. Sooooo I did. Upon boot up it saw the motorola modem (again) . Now I had 2. #2 was installed on com5 & it tested "GOOD"
Thanks a bunch!!
Damn, you were right on both counts. #1 all I thought I had to delete was MSTCP. I didn't have the DHCP's and didn't until just now see that there was also the Winsock so I hadn't deleted those (even if I had em.) Upon boot up I got the Password for the first time in so long I had forgot about it. I thought "Yea that's it" but it didn't pass diags again. Upon checking your answer the other thing was change slots. Sooooo I did. Upon boot up it saw the motorola modem (again) . Now I had 2. #2 was installed on com5 & it tested "GOOD"
Thanks a bunch!!
Glad to help.
The .inf file usually sets up the "init strings" that are used by that modem type to dial, connect, disconnect, etc. They look something like this (truncated for clarity and only extracts):
HKR,Settings,CallSetupFail
HKR,Settings,InactivityTim
;HKR,Responses,"<cr>",1,
;HKR,Responses,"<lf>",1,
HKR,Responses,"<cr><lf>OK<
HKR,Responses,"<cr><lf>RIN
HKR,Responses,"<cr><lf>NO CARRIER<cr><lf>",1,
HKR,Responses,"<cr><lf>ERR
HKR,Responses,"<cr><lf>DEL
HKR,Responses,"<cr><lf>BLA
HKR,Responses,"<cr><lf>DIS
HKR,Responses,"<cr><lf>NO DIALTONE<cr><lf>",1,
HKR,Responses,"<cr><lf>BUS
HKR,Responses,"<cr><lf>NO ANSWER<cr><lf>",1,
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
HKR,Fax\Class1\AdaptiveAns
Was the modem actually recognised by windows as new hardware when you first booted with it fitted?
Have you tried installing it as a "Standard Modem Type" in "Add new Hardware", and pick it from a list rather than allowing a search?
Do you know if it is a WinModem or not?
What are the chipset names and identification on the modem, or even a model. A look at the .inf files on the windows CD and a word search from NotePad/Wordpad might find mention of it.