Printable View
Have a Win95 machine, device manager shows conflict with primary and secondary ide controller, device not found or not working error message, no conflict in the resources, tried removing then redetecting devices, did not help, no new drivers available (opti controller).Any ideas on how to fix this.
I'd check for a virus. Also if you don't need both channels try disabling one.
Have a Win95 machine, device manager shows conflict with primary and secondary ide controller, device not found or not working error message, no conflict in the resources, tried removing then redetecting devices, did not help, no new drivers available (opti controller).Any ideas on how to fix this.
--------------------
Take everything off the second channel and see if that helps and then you could go into the BIOS and "reset configuration data" and reboot and see if t finds a new IRQ. The drive may very well be going bad as well.......
Tried all that, virus scan, moving everything to one channel and reconfig. , still no good.
Tried controler card and disabling on board IDE incase they are defective yet?
nope have not tried that yet, I have found out that the maker of the onboard controller recomends upgrading to 98 or a fresh install of 95. Surely there is a better way.
Surely there are drivers available for your motherboard at the manufactures website?
Find them and install them. This is a controller issue, not a disk drive issue. Without the drivers for your system, those exclamations will remain put. Are the USB drivers installed?
Win95 is definately not clever enough to inform you of a bad drive or virus via the Device Mananger.
The maker of the board states that Windows basic drivers for the controllers are to be used and that is why they do not provide them. No fix that way.
Can you give me some info on the board?
If I can remember right,
There is a way to get that fixed through the registry
It has something to do with the NOIDE value
It's been a long time since I had to do it, but I believe you have to put a value of "1" in that entry.
Thanx a million everyone, Eagle was correct, this is the answer:
Symptoms:
- CDROM drive disappears
- In device manager, both "Primary IDE controller" and "Secondary IDE controller" appear with a yellow exclamation mark
- In device manager under "performance", all HD's appear in compatibility mode.
Solution:
Click Start, then Run... , and type regedit
Go to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\IOS
You should see a value named "NoIDE". Delete it, close regedit and reboot!
LATE POST: Coulda been done another way. Going in the registry is a bad idea unless neccesary. And always back up before you do!
Here's another way, during bootup, watch the bios to see what type motherboard you have. I440LX, I440BX, blahh, blahh, blahh. You'll know what the chip set is then. The most popular is Intell of course. Start windows in safe mode, go to device manager and delete all parent devices for H/Ds, you may actually have many listings that dont show up in protected mode. Assuming you now have a copy of the right drivers, run the install then re-boot. Windows should come up and detect them and load the drivers for you. If you have problems with the IDE controllers, you will not see a CD-ROM drive nor can you access the H/Ds in protected mode.
Actually SBlive, the noide value will stay, and continue to cause problems, you must search for and delete it from the registry.
Gee, I have never had to before and I image about 20 PCs a month with the same image all with different chipsets. wo always me (sigh) I have had to wipe out all the devices listed under system before, but go into the registry? Never for a hardware problem. Usually only for those wonderful un-installs that never un-install everything.
when you remove a device from device manager, it removes it from the registry key under
hkeylocalmachine\enum\
the noide value is under HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\VxD\IOS and has to be manually deleted
edited by Sowulo
SBLive, rrockey, calm it down now. SBLive, your "solution" will solve the problem if it is only one of a damaged or inappropriate driver. In this case your solution will usually do the trick. However, if an error condition has caused Windows to enter the "NOIDE" value in the registry as indicated by rrockey, then the best solution is to delete the NOIDE value and redetect the hardware as rrockey described.
Very well put!
No prob Sowulo.