Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Sed posuere consectetur est at lobortis. Vestibulum id ligula porta felis euismod semper. Donec ullamcorper nulla non metus auctor fringilla. Aenean lacinia bibendum nulla sed consectetur. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Cras mattis consectetur purus sit amet fermentum. Morbi leo risus, porta ac consectetur ac, vestibulum at eros. Sed posuere consectetur est at lobortis. Etiam porta sem malesuada magna mollis euismod. Cum sociis natoque penatibus et magnis dis parturient montes, nascetur ridiculus mus. Duis mollis, est non commodo luctus, nisi erat porttitor ligula, eget lacinia odio sem nec elit. Cras justo odio, dapibus ac facilisis in, egestas eget quam. Aenean eu leo quam. Pellentesque ornare sem lacinia quam venenatis vestibulum. Curabitur blandit tempus porttitor. Sed posuere consectetur est at lobortis.
Thanks Jim. This is great data. I'll be working with the N360 product manager to forward to the correct dev teams for review & resolution.
Robert Reynolds
There's a compatibility problem between Norton System Works' WinDoctor and the Roxio Easy Media Creator suits 9 and 10. It also shows up when using the WinDoctor variation in the Norton 360 1 & 2 registry cleaner. I fell victim to it, and I though it might help others with the problem if I described my experience and some workarounds:
The Roxio suite installed and worked here on XP Pro as expected until the next time I ran WinDoctor which determined that more than 40 Items, most with either Roxio or Sonic in the title, needed fixing. After letting WinDoctor fix everything, I discovered that neither the Roxio suite nor any of its components would launch. Neither could it be reinstalled. As it turned out, Roxio knew about the problem and had instructions available to restore the suite using what they call a "Clean Install" procedure (actually an exhaustive uninstall and reinstall). The "Clean Install" is decidedly not a fun procedure, but it restores the suite's functionality. (At present, Roxio doesn't appear to have any utility like the Norton Removal Tools.) Afterward, I set WinDoctor to ignore all the Roxio-related items.
Later I learned that the only cause of the problem was WinDoctor modifying the registry key
HKEY_CLASSES_ROOT\CLSID\{3E867EE6-00C0-40FA-95C0-C9CCB3BA7692}
of which I found one instance among the 40+ items. So, leaving only the key "ignored" in WInDoctor, I was able to "unignore" and clean up the rest of the registry errors without again disabling the Roxio suite.
For those with a disabled Roxio suite from using Norton System Works' WinDoctor, I suggest:
1. Uninstall the Roxio suite using the Roxio Clean Install instructions that can be found at
http://kb.roxio.com/content/kb/Creator/000086CR?set-locale=en for XP users, or
http://kb.roxio.com/content/kb/Creator/000127CR?set-locale=en for Vista users
(Note: There are links in the instructions for other tools you will need - e.g., Windows Installer Cleanup Utility.)
Restart the system.
2. Create a system restore point. If something goes wrong, it's a lot easier to restore the system than have to run through Clean
Install again.
3. Reinstall the Roxio suite and restart the system. Check to make sure it works.
4. For insurance, run another restore point.
5. Run WinDoctor. When it completes the scan, DO NOT FIX THE ERRORS. Instead, open each detailed error list and search for
all instances of the above registry key. Right click the mouse on each instance, and select "ignore." Then let WinDoctor fix the
remaining errors. Restart the system again.
6. Run the Roxio suite to verify that it still works. If it does, you now can safely run WinDoctor or One Button Checkup without it
disabling Roxio.
Unfortunately the WinDoctor "ignore" option is not available with Norton 360 registry cleaner. So, if you have the same problem with N360, your options, for now, are more limited. If Roxio has been disabled, you still have to go through the Clean Install obsticle course to restore its function, but if you want to keep using it, you esentially have to avoid using the reg cleaner scan for a while. The Symantec development team is aware of the problem and are working it. Also, acording to rumors posted on the Roxio Community discussion group (see http://forums.support.roxio.com/ ) Roxio is woring on some sort of utility that will reenable the above registry key when presented with a valid Roxio suite CD key and thus aviod the Clean Install exercise. However, I've found no verification or schedule of its release to us victims. For the time being, It looks like we'll just have to make do. As an aside, evidentally WInDoctor is not the only registry cleaner that does this sort of thing. I guess it goes with the territory.
I hope this helps.
-- Jim
I forgot to add something that could be helpful, especially to N360 users:
While the Roxio suite is working, export the problem registry key
HKEY_CLASSES_ROOT\CLSID\{3E867EE6-00C0-40FA-95C0-C9CCB3BA7692}
to a holding location. Then, if the suite gets disabled during a reg cleaner scan, you should be able to reenable the suite by importing the key back into the registry. Alledgedly, the value of the key is specific to each system, so this would not work between systems.
I haven't tried it yet, but someone using N360 might try it to verify. This would be a way to run N360 registry cleaner and keep Roxio functional. And don't forget to run a restore point before experimenting.
-- Jim