|My T3604 (RAM expanded to 2M) uses Power2Go as a DVD/CD writing method; while my computer will recognize a blank CD and will allow Power2Go to open up and burn the CD, whenever I try to burn a data disc on a blank DVD+R, the system spits out the disc and prompts me to put in a blank DVD. Even when Power2Go is not opened up, a blank DVD placed inside the CD/DVD drive will not open up (will not have a box come onscreen asking what I want to do next). Blank CD's are no problem. Therefore, I'm completely unable to burn DVD data discs for my mp3's. The system used to work; it's only been "blind" to blank DVD's recently. I've obviously closed down and restarted the computer repeatedly, to no avail. Control Panel tells me that the drive and the IDE Controllers are working properly. The blank DVD's aren't at fault, as they open up on my other computers. And my computer still recognizes and plays recorded DVD's, both professional and DVD-R.|
I have tried a number of cures, based on advice given at various sites. None have worked. These include:
1) Uninstalling my cd/dvd burner, rebooting and allowing Windows to reinstall the drivers. No change.
2) Going into "regedit", going to 4D36E965-E325-11CE-BFC1-08002BE10318 and deleting UpperFilters and LowerFilters. No change.
3) Going into "regedit" to HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies and creating a new 32-bit DWORD, naming it NoCDBurning and assigning the value data to 1. No change.
4) Opening up my computer, checking to see that all the cables and connections to my burner are properly seated, then unplugging the burner from the motherboard, restarting the computer, allowing for a full boot-up, turning the computer off, plugging the burner back in, and restarting the computer. No change.
5) Reinstalling itunes, which I had recently uninstalled. I was told that sometimes some shared files get deleted and cause trouble with the burner. No change.
Again, this doesn't look like a hardware problem, and I'm beginning to suspect that some recent update from Windows Vista may fouled something up. Have others been experiening this problem lately, and has Windows had anything to suggest?