CDROM not recognized in XP, says needs driver

  • Thread starter Thread starter Dan P
  • Start date Start date
D

Dan P

I have a Gateway with XP on it. One day I booted up and
realized that my CDROM didnt show up in My Computer. I
checked the device manager and it said the driver was
missing. Considering that drives don't really have
drivers, I checked Gateway's support site. They gave me
a driver for the IDE controller because that was supposed
to solve the problem. Well it didn't so I called and
they sent me a new drive under warranty because they
decided that was the problem. However, the problem is
still there. Any ideas on how to get the drive to work?

P.S. I tried to get the driver for the Intel Chipset but
the installer said everything was already updated.
 
Actually, if you check most of the drives on your system,
they DO use drivers. Without drivers, there is no way to
communicate between the PC and the drive.

Did you use the Tracks Eraser feature?

If so, you might have inadvertantly selected the mapped
drives option. If so, and the drive is a mapped drive,
then you might have deleted the entire drive from the
system. You might have to call Gateway and see if they
have an install disk for the drive. Another option is to
remove the CD-ROM and reboot the system. Now shutdown
the system, reinstall the CD-ROM, and reboot. Doing so
might allow Windows to properly detect the drive and
install the appropriate driver. NOTE: Plug-and-Play
MUST be enabled for this to work!

Alan
 
I like both your other answers. Andre's pointed to the right resource, and
Alan's given a good idea. Am I recalling correctly that the CD-Rom doesn't
show up at all in Device Manager, though?

If that's the case, you could also consider removing, in device manager, the
disk controller which controls the CD-drive.

This sounds scary, because it is quite likely that this same controller also
controls your boot drive. In practice, however, I've done this, and it has
worked for me. It may take a couple of boots, but it should all come
back--and the machine will not be rendered unbootable by removing the disk
controller.

I've definitely seen this happen before, and don't believe that it is
related to Microsoft Antispyware at all.
 
Back
Top