Thanks, you guys rock!!! My PD9 Burns now and hopefully I can finish the DVD's by my daughter's soccer team party by Monday. Love this forum and its knowledgeable folks.
@NicolasNY & JL_JL - Not a burning issue since PowerProducer has no issues on my machine.
@SeptimusFry -Thanks for pointing me in the right direction. With msconfig I re-enabled at startup CTASIO.SLL in SYSWOW64. %SYSTEMROOT%\SYSWOW\REGSVR.EXE /S %SYSTEMROOT%\SYSWOW64\CTASIO.SLL
I disabled it earlier because PD9 would crash when I clicked on Creat Disc. I disabled everything at startup to determine if anything was conflicting which turns out I had a menu template installed that was for PD7 that was causing the problem.
I also per below, disabled the Windows Desktop Search or the Search Indexer per below. I can now burn!!! But I don't know which solved it or if it was both.
http://www.sharepointassist.com/2009/01/07/searchmapi2handler1-cannot-be-loaded/
http://social.msdn.microsoft.com/Forums/en/windowsdesktopsearchdevelopment/thread/c0c5561d-c972-4da2-ab22-48d97e69439e
This was also an issue on 64-bit Vista and we made a fix for it, but it looks like the fix did not correctly
address 64-bit XP.
The background on this issue is that there are two process that can index on 64-bit machines. One process
is 64-bit and can load 64-bit protocol handlers and the other is a 32-bit process which can load 32-bit
protocol handlers. In this case, since mapi (which is used to index outlook email) is 32-bit only, when
the 64-bit protocol handler process starts, it tries to load the 64-bit version of the non-existent mapi
protocol handler. It should call into the WOW64-32 layer to determine that this handler is correctly
registered in the other CLSID hive and not display the error. For some reason this check is not passing,
most likely due to some incompatible vista only flag we are using when calling to WOW64.
The good news is that this error message will not impact email indexing, but will create event messages
every time the protocol handler starts up.