Havent seen this one before
This is a discussion about Havent seen this one before in the Windows Hardware category; Alright, for once this is a CD-RW question that doesn't have anything to do with burning CD's. My drive has worked fine for months now, but I decided to uninstall eazy cd creator 3. 5 to install 4. 0.
Alright, for once this is a CD-RW question that doesn't have anything to do with burning CD's. My drive has worked fine for months now, but I decided to uninstall eazy cd creator 3.5 to install 4.0. After reboot my cd drive is gone. I checked under the hardware devices and it has a yellow mark with an error 31 saying windows can not load the drivers for the device, so I uninstall the drive and it detects the HP 8100i, but still the error 31 and no drive, so I changed the driver to a regular cd rom, but again no cd drive. Then I deleted all the files windows reported to be in use by the drive and re loaded the driver from the cd over my network.......still no drive. Lastly I updated my win2k from 2195 to final to see if that would clear things up, but still no drive, and an error 31.......help please..
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Apr 20
Apr 23
0
3 minutes
Responses to this topic

OP
Almost forgot to mention......I also unhooked my CDRW and replaced it with a standard cd rom I had....Boom still same problem error 31. I think that eazy cd deleted some critical cdrom driver file, that even up[censored] the copy of windows didn't replace......Any help is greatly appreciated...
If all else fails you will have to format. I have never seen this error happen before either totally sorry

OP
anyone else have another solution.........i hate reformating........i seem to do it monthly
Exactly what does error 31 meen...?

OP
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
Click Troubleshooter to start the troubleshooter for this device.
Click Troubleshooter to start the troubleshooter for this device.
I've never seen this get screwed up in device manager like this, so there is no guarantee that my recommendations will actually do anything.
Try once again uninstalling EasyCD Creator and reinstalling again. Be sure to get the 4.02 patch from Adaptec's web page. What could have happened is something screwy with the ASPI drivers between uninstalling 3.x and installing 4.0. Maybe one more uninstall/reinstall will fix it.
[This message has been edited by Reidyn (edited 22 April 2000).]
Try once again uninstalling EasyCD Creator and reinstalling again. Be sure to get the 4.02 patch from Adaptec's web page. What could have happened is something screwy with the ASPI drivers between uninstalling 3.x and installing 4.0. Maybe one more uninstall/reinstall will fix it.
[This message has been edited by Reidyn (edited 22 April 2000).]
this may be a stupid question, but is your bios detecting the cd-rw at bootup?
I had a little spell with Win2k actually losing both my cd-rw (Also an HP 8100i) and my Pioneer DVD 6x.
If it is, then I think a reinstall of win2k is the only solution.
evil Homer
------------------
"Screw you guys... I'm going home!"
I had a little spell with Win2k actually losing both my cd-rw (Also an HP 8100i) and my Pioneer DVD 6x.
If it is, then I think a reinstall of win2k is the only solution.
evil Homer
------------------
"Screw you guys... I'm going home!"
If its a hardware problem, start up in safe mode, goto hardware devices, and delete any thing relevant, then reboot, set bios "reset configuration data" to enabled, and restart windows. Win2k may have disabled the device, or its host controller.
Probably its software, so I guess if the systems knackered anyway, a quick look through regedit would be fun. Delete in local machine/system/current hardware/services all the adaptec, aspi, buslogic... then search for the system drivers delete then, then reinstall your current drivers before rebooting. (you don't want win to say missing files) Which you'll probably get anyway.
If it were me I would have used my system backup from a clean install, but I guess most people don't have that.
Probably its software, so I guess if the systems knackered anyway, a quick look through regedit would be fun. Delete in local machine/system/current hardware/services all the adaptec, aspi, buslogic... then search for the system drivers delete then, then reinstall your current drivers before rebooting. (you don't want win to say missing files) Which you'll probably get anyway.
If it were me I would have used my system backup from a clean install, but I guess most people don't have that.