Discussion Locked

CD ROM PROBLEMS!!!!!

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have an acer computer w/an acer 32x cd rom.
My cd rom isn't being recognized. It says that their is no driver on the system. It done this before but showed up later, but now I can't find it at all. Beside the Secondary IDE Controller in the Device Manager there is a yellow ! beside it and it says the bios in the device is reporting the resources for the device incorrectly. I use windows 98. I installed windows w/a cdrom so I cant reinstall windows because the cd rom insn't working. I don't know what else to do. It seems I've tried everything. It says to get an updated bios too. How would I do that? What could've caused this problem?

15 replies

by parbo

First thing i would do is do a virus scan with an updated antivirus program. if there is no virus found remove the secondary controller and reboot and let the system find it again.

by a15624

If all your equipment is original, you should get both BIOS and CDROM driver from the Acersupport web site " http://www.acersupport.com/ " Click on the downloads section for your type of computer.
Your first step is to make sure you have the correct BIOS. Other suspects are loose data cable (you bumped or moved the computer lately), power cable (do you see a light on the CDROM or do you hear it spin up?), IRQ, Memory conflict get your software updated and then sort through the other issues.

by jctech

Sure sounds like a boot sector virus as answer #1 suggests. If you do have a boot sector virus, it will load into memory every time you boot the machine and infect any floppy disk your insert that isn't write protected. You would need to clean boot with a write protected floppy disk, then run a DOS based antivirus capable of cleaning boot sector viruses. That should take care of your problem.

by gregory pleau

Go to support.intel.com and make sure you are using the correct INF files for your IDE controller. I have seen this a bazillion times on Windows. The file you are looking for is called the INF setup utility. You will need to know what kind of motherboard is in your system ( ie SE440BX-2 ).

I have also seen this when the Primary hard disk was on the secondary controller instead of the primary controller.

by willisae

Wow, some creative answers to a problem there guys.
I have one other suggestion. Do you have it jumpered correctly? If it's on the secondary drive, it must be set to 'slave' and not 'master' on the back of the cd-rom itself. Check that out.
-willis

by mad max

Check for a virus as stated in previous answer.. But I would be forewarned by the 'it happened previously but went away ' event. It sounds like a failure of the CDRom drive. Try installing the dos driver and see if you can get a response in DOS if not then the drive/cabling is faulty.. If yes.. Copy Win98 directory to harddrive and use this to re-install windows.

by abinashpadhi

To reinstall or refresh the CD-ROM drivers when the drive is not functioning or being detected, follow these steps:

1. Start the computer in Safe Mode by tapping the F8 key on the keyboard when Windows starts. Ignore the keyboard error message.
2. At the Startup menu, choose Safe Mode.
3. Right-click My Computer icon on the Desktop, and choose Properties.
4. Click the Device Manager tab
5. Click the "+" sign next to CDROM.
6. Click once on any CD-ROM drive listed, and click the Remove button
7. Repeat step 6 until the all devices under CDROM are removed.
8. Click OK and restart the computer.

If that does not solve the issue, alternately try these steps:

1. Click Start, Run, type "regedit" without the quotes and click OK.
2. In Edit menu, click Find, type in "NOIDE" without the quotes and click Find Next.
3. When the search stops, it should have NOIDE highlighted.
4. Press the Delete key on the keyboard, and confirm the deletion. Press F3 to continue the search.
5. Repeat steps 2 through 4 till all "NOIDE" entries are deleted.
5. Click Registry, and then select Exit.
6. Restart the computer.

This discussion is closed to new replies.