Burning a CD using Windows built in program

Maybe everyone knows this already, but if you look into Windows Help for "Copying CD's--overview" you will be told to right click on the DVD/CD write drive|Properties and make a few settings on the Recording tab.
But if you install some third party burning programs you will find no Recording tab.
It seems that some third party burning programs modify the Registry to hide the Recording tab.
I have found the fix for this
"Run regedit and navigate to
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] Check that NoCDBurning is set to 0 to enable Windows burning.

Repeat the process for HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer] "

Not everyone will have the two keys, so fix only the one(s) you have.

This came from BurrWalnut's first post on September 12 here
http://www.webuser.co.uk/forums/sho.../PC/Number/106342/an/0/page/9/view/collapsed/

BurrWalnut thinks that third party burning programs may change the Value to 1.
I am fairly sure BW is correct and that Sonic's RecordNow! did it for me.

 

Hi Jim,

Wanted to see if Roxio did the same which I primarily use to burn DVD's and occasionaly CD-RW's. That recording tab is there in the burner's properties.

Tried a CD-RW burn using XP and it worked.

IMAPI CD-Burning Com is set to Manual in Services which as you know will start and stop the Service at need.

Could not find either one of the Registery items that you listed.

Regards - Charles

 

charlesvar--Thanks for testing other third party burning programs for problems they might cause. Of course I do not know it was Sonic RecordNow and it was an OEM installation.

Do a search in your Registry for NoCDBurning. You might find it elsewhere--like HKUsers.
(I had it only in HKLM.)

 

Thanks.
I guess if everyone has a Recording tab, they have no problem. And maybe then the NoCDBurning key in Registry would be redundant and just is not present.
In my case, since I had no Recording tab, I was glad to find the fix.

 

Hi Jim,

It may be that the presence of Sonic created those reg entries. The fact that its an OEM installation clouds the issue. The only way to know for sure is for someone to install Sonic.

Regards - Charles