| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 47876 | 2004-08-08 02:58:00 | Modem Driver | B.M. (505) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 259357 | 2004-08-08 04:50:00 | Sounds like you have done all the right things to identify it. I would shutdown, pull the modem, reboot, shut down, reinstall the modem and reboot, feed it the driver when the modem is recognised and asks for one. Even try a different slot. |
godfather (25) | ||
| 259358 | 2004-08-08 05:36:00 | Yes GF, Ive done the physical modem removal and reboot trick, even cleaned the registry with Nortons SystemWorks and Microsoft Reg cleaner between installation attempts, but I guess I just havent found the correct driver . Mind you, windows refers to the modem as a PCI Serial Controller and when I point Windows to the folder Ive unzipped the driver into I get the message Windows was unable to locate driver for this device etc etc . Is there a programme that will get the electronic identification of the modem? I havent changed slots yet so Ill give that a try . Can't help thinking I've missed something obvious . |
B.M. (505) | ||
| 259359 | 2004-08-08 05:43:00 | > I assume you've been through all the cruft that came > with the computer? |
whiskeytangofoxtrot (438) | ||
| 259360 | 2004-08-08 05:44:00 | Get your magnifying glass out again and try here at Modem Help (www.modem-help.com). I've yet to come across a working modem that this site or links within it can't ID and point to drivers, if available. They also give good info about known problems with particular modems, chips and drivers. Cheers Murray P |
Murray P (44) | ||
| 259361 | 2004-08-08 06:01:00 | Try here www.modemsite.com There may be some leads that you haven't tried |
PaulD (232) | ||
| 259362 | 2004-08-08 07:44:00 | Well guys the good news is its all go now and the answer was??????? OK, the telepermit reference said it was a Aztech MDP3858 Internal fax modem, fine and theres heaps of drivers available for that type of modem but alas none worked. The board itself said the modem was MDP38586P-A and there was a couple of drivers for this type of modem that didnt work. However, as I replied to GF it occurred to me that checking the Modem with Everest might be worthwhile and that revealed that Electronically it was in fact a Aztech MDP3858SP-A SVD Modem. Loading the correct drivers for this type of modem fixed things. I guess the moral of the story is dont put too much faith in what is registered with Telepermit or written on the board. Good work Everest !!!!!!!! So thanks everyone for your input. Bob |
B.M. (505) | ||
| 1 2 | |||||