CD ROM Drive Not Working in XP

[mhubbard]

I am working on a Dell PC brought to me with a cd drive problem. When windows comes up, the cd drive letter never comes up. I checked device manager, exclamation point beside the drive, I uninstalled, let Windows reinstall. Same problem. When you check the properties, it says that there was a problem loading the driver.

So I install a new cd drive. Same problem. So it has to be in Windows I would think.....

BIOS recognizes the drives just fine.

Any ideas??

[AlienDyne]

Have you tried SP2? Most of the times, problems of this kind are solved by it.

[confus-ed]

.. uninstalled, let Windows reinstall. Same problem. When you check the properties, it says that there was a problem loading the driver..

What's it say exactly please ?

[Gabriel]

Hi,
Try connecting the drive as standalone (dell usually ships computers when HDD and CDROM are on the same data ribbon).
To do so -> open the case , locate IDE ribbon, disconnect the CDROM and connect it to secondary IDE (sometimes you will not find extra DATA ribbon inside the coomputer case so be preapered).

Cheers - and good luck,
Gabriel

[mhubbard]

The exact error message:

Windows was unable to load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

The cd drive is on the secondary ide port all by itself. I disconected reconnected just for fun.

I just noticed that it does have sp1 so I will put sp2 on it to see if that helps.

I appreciate the responses.

[confus-ed]

I had to look up what code 39 in device manager meant .. that's an ususual one !

Code 39
Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)


Recommended resolution

Reasons for this error include a driver that is not present; a binary file that is corrupted; a file I/O problem, or a driver that references an entry point in another binary file that could not be loaded.

Uninstall the driver, and then click Scan for hardware changes to reinstall or upgrade the driver.

On the General Properties tab of the device, click Troubleshoot to start the Troubleshooting Wizard..

M$ don't help themselves sometimes .. but that message is apparently on about one of my 'favourite' subjects .. Class filter drivers.

So that makes the resolution 'wrong' in that burning software is what adds these (along with emulation software like virtual CDs such as daemon tools or alcohol 120) & no amount of re-decting in device manager will help !

SP2 can come into the equation here too as that updates some of the standard files windows uses when reading cd's e.g. atapi.sys

So I guess install sp2, & then uninstall/re-install all your burning apps (that's what seems to invariably fix 'filter class issues' ) one at a time & test between each.

[MAXIMUS2111-SPQR]

ive run into this issue twice in the last month

so basically what you are saying is that a corrupt burner app clobbered the driver?

i think the driver that goes bad or gets corrupted is asdm.sys IIRC

i tried doing a repair on one system & it got all the way up to a point where it was looking for asmd.sys & it couldnt find it on the cd drive because it could no longer access it...we did try dumping that file on the hdd but that proved pointless & in the end we had to wipe the system.

Ill give your suggestions a shot next time i see this issue
thx

[confus-ed]

..so basically what you are saying is that a corrupt burner app clobbered the driver? ..

Yes & no he answers confus-ed-ly ... Class filter drivers are things which interact with a device driver to add functionality.

So they don't 'clobber the driver' as they don't actually change it, but as they are linked to it by function, every time you try & use windows for any cd/dvd operation they try & interact.

If you remove all your burning applications & reinstall the latest versions windows will rebuild all the dependencies hopefully right - I guess you need to understand the notion of 'encapsulation' like used in programming to fully get the idea as this is all to do with class inheritance ..

[MAXIMUS2111-SPQR]

as a wise man once put it....ah so

[gheidenr]

Try this: http://support.microsoft.com/kb/q270008/

I've had this occur several times with other software than Adaptec, and it always seems to fix the problem.