Under Windows 7, Lightroom 3.2 left a legacy folder called c:\program files\adobe\adobe photoshop lightroom 3\resource, and Lightroom 3 left a legacy folder named c:\program files\adobe\adobe photoshop lightroom 3.2\resource. Both folders are empty. However, it raises a question of whether anything else is being left on the machine.
This issue arises because Nik Software, despite an hour's work on my machine, cannot get a plug-in for HDR Efex Pro to work, and the install program is unable to install seven files that have to do with this plug-in. They are wondering if the install program is seeing past versions of the program and doesn't know where to put things.
One proposed solution is to complete remove LR3 from my system and start over with a clean install of LR3.3. Will this remove my catalogue?
Thanks.
Uninstalling LR will not remove the catalog. Removing everything associate with the application obviously would as this would include the catalog. All uninstallers leave loads of stuff behind in the registry (this is a problem with how windows works rather than anything to do with applications) and you can go through the registry and remove these or try a registry cleaner such as ccCleaner first. However the installer application for any plug in should be smart enough too recognise which is the active application and install itself to that. I would contact the makers of the plug in software asking that they ensure their plug in installs correctly for LR 3.3 as files will be left behind every time a update is made and they plug in designer should be aware of this and discuss the matter with Adobe rather than suggesting you start to mess with the registry or remove files that may be required by LR. If ccCleaner doesn't correct the problem.
By the way, I too have legacy files on my system and I too have a Nik plug in (not the one you mention but Silver Efex). It has successfully transferred from LR 3.0 to 3.2 to 3.3 RC to 3.3 without this problem. However it did require a reinstall of the plug in (not the application) to function in CS 5 after the upgrade from CS 4, now it is in both versions as I have not yet removed CS 4 from my machine. If Nik can get it right for one plug in, then it would seem they should be able to get it right with another. I do, however, regularly clean my registry using ccCleaner.
North America
Europe, Middle East and Africa
Asia Pacific