Finds new devices (CD) on every restart

[Theo Weber]

Recently WinXP has decided to find both my DVD and CD-RW devices
every time it starts. Then it can't find a driver for them and tells me
I could have problems. Both drives work properly and appear in the
Device Manager. The only thing that seems odd is that there is no
driver information. Both drives are slave drives on the primary and
secondary IDE channels. The problem started when I updated B's Clip to
the XP version. Any thoughts?

ASUS A7V-E
AMD Duron 1.3
Sony CRX320E
Sony CRX1611

 

[Theo Weber]

Since no one seems to have an idea on this issue, would someone be
kind enough to run Device Manager and tell me what the driver properties
for their CD-RW is. Then maybe I could track down the drivers and drop
them onto my system.

 

[Alex Nichol]

Recently WinXP has decided to find both my DVD and CD-RW devices
every time it starts. Then it can't find a driver for them and tells me
I could have problems. Both drives work properly and appear in the
Device Manager. The only thing that seems odd is that there is no
driver information. Both drives are slave drives on the primary and
secondary IDE channels. The problem started when I updated B's Clip to
the XP version.

This happens if a reference to a driver-type file gets left in the
registry after the file itself was deleted (probably because it was not
XP compatible). To tidy up, get a registry patch file, cdgone.reg, from
www.aumha.org/downloads/cdgone.zip, extract it, r-click on it and merge
it into the registry

You will then need to reinstall any burning software that you *do* use.

 

[Theo Weber]

Theo Weber wrote:



This happens if a reference to a driver-type file gets left in the
registry after the file itself was deleted (probably because it was not
XP compatible). To tidy up, get a registry patch file, cdgone.reg, from
www.aumha.org/downloads/cdgone.zip, extract it, r-click on it and merge
it into the registry

You will then need to reinstall any burning software that you *do* use.

In the end the problem was that cdrom.inf had not made it onto to my
system when I upgraded to WinXP. Was a simple matter of expanding it to
the windows\inf directory, search for new hardware, and voila! At least
that problem is sorted.