Win2K: CD & DVDs dead, error 19 (corrupt registry); longish

[boink]

Not long after doing a complete reinstall of Win2K, I installed the Roxio WinOnCD app software for my CDRW (Plextor) which gave me errors like can't find device, etc. I then found that both the DVD and CDRW had disappeared from Windows Explorer, and are listed as problem devices in System Information, with error code 19 (your registry may be corrupt).

My system drive is on the same IDE channel as my DVD and works fine, and I can boot from the CD, so I don't think it's a h/w error. In any case all h/w is as it was before the reinstall, before which I had no probs.

The only thing I (may) have done differently was installing DirectCD 5. I'm pretty sure I didn't 1st time round.

I have tried...
- Uninstalling and reinstalling and uninstalling (current) the Roxio software
- Uninstalling DirectCD 5
- Uninstalling and reinstalling the 2 devices
- Updating the drivers (redbook.sys, cdrom.sys, and storprop.dll)
- Deleting following keys and their subkeys (PnP brings them right back on reboot):

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\I DE\CdRomPIONEER_DVD-ROM_DVD-105_________________1.22____

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\I DE\CdRomPLEXTOR_CD-R___PX-W1610A________________1.02____

as well as other references like:
HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 0\Scsi Bus 0\Target Id 1\Logical Unit Id 0

and

HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi\Scsi Port 1\Scsi Bus 0\Target Id 0\Logical Unit Id 0

plus the references to e: and f: in

HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\DosDevice s\

I have also run Win2K setup, repair, to no avail, and searched the web high and low for clues.

And worst of all I've run out of cigarettes!!! :mad:

There must be something still lurking in the registry that's screwing things up. Any ideas what it is?

Very happy for advice,
Boink

PS no - I don't have a copy of a known good registry like Microsoft say I should restore from. If I did I wouldn't be writing this, would I? :rolleyes:

[reynolan]

Does your motherboard use a VIA chipset?

I had a similar problem and finally traced it to the VIA IDE driver.
Later versions of this driver were updated to fix a problem with Zip drives, but seem now to have a problem with other types of removable storage devices.

Restoring the original Microsoft IDE driver from the Windows 2000 installation disk fixed the problem.

[boink]

Reynolan,

Thanks for your reply. Yes it does have a VIA chipset, the mb is an Asus A7V266. I uninstalled the drivers for both primary and secondary IDE channels, and replaced them both with the Standard IDE/ESDI driver. I then rebooted and reinstalled the primary and secondary IDE (usual) drivers.

Same problem, though - not seen by Explorer or Disk Administrator.

What I didn't try was replacing the VIA Bus Master IDE controller driver. Maybe that's what you meant?

Will try it tonight and post the results.

Thanks again for your interest.

Boink...

[boink]

Good ol' Technet says...

"Code 31 Messages Occur After Removing Adaptec Easy CD Creator 4.02c (Q270008)

...

Remove the Upperfilters and Lowerfilters values completely from the following registry key:


HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}

NOTE : If you are getting a code 39 message, it may be that additional third-party filter drivers were added to UpperFilters and LowerFilters values in addition to Adaptec filter drivers. In that case, you may try to remove the non-Adaptec filter drivers first, leaving the Easy Creator filters in place to see if the Code 39 goes away. If you still receive an error code 39, 32, or 31 message, remove the Upperfilters and Lowerfilters values completely in the preceding key.


Restart your computer.

..."

And it works (and I was just about to rebuild from scratch, too).

Moral of this story - BACK UP THE SODDING REGISTRY before un/installing ANYTHING.

You know it makes sense...

Regards,
Happy, happy Boink

[boink]

Recently I`ve found that the UpperFilters and Lower Filters subkeys get reinserted by the OS when the system boots. To get round this, after deleting the two values, open the registry with Regedt32 (not regedit) and change the permissions for the key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}

If you deny access to the account SYSTEM to write subkeys, the values won`t be replaced, but you will get an error or two in the event log.

I haven`t found this gives rise to other problems... yet.

Will post again if this is the case

bye bye

boink