I have a lot to say here, so let me save anyone else that may be visiting this post an awful lot of un-necessary grief, and to straight to an answer to your problem:
1. Read ALL of these steps carefully before doing anything
2. Do a full back up of your Windows Registry. DO NOT SKIP THIS STEP. If you do not know how to use the registry, give it all you’ve got to find someone to help you through this process. If you run XP, make sure you have a recent restore point. Also make sure you set the local administrative password to something you are sure of just in case you need to boot into safe mode. Even with all this, it will be less effort than the RIDICULOUS suggestion of reformatting your whole hard drive just to get one Ulead program installed.
3. Now, do a search on the entire registry for “Ulead” (without the quotes). VERY CAREFULLY delete any key where you find “Ulead”. The reason you have to be very careful is some registry keys may have information about other programs and Windows functions, and you don’t want to delete these. With a patient eye and good judgment, you should be able to decide when a whole key should be deleted, and when just one value within a key should be deleted. Again, if you are uncomfortable with the Windows Registry, get someone who is comfortable to help you.
4. Most of the areas where entire Ulead keys should be deleted will be found in HKEY_CLASSES_ROOT. Most of the keys where just the value that contains “Ulead” needs to be deleted will be found in the other “Hives” of the registry, such as HKEY_LOCAL_MACHINE.
5. Delete the “Ulead CD & DVD PictureShow 3” folder at C:\Program Files\Ulead Systems.
6. Delete all files and folders at “C:\Documents and Settings\All Users\Application Data\Ulead Systems\Ulead DVD PictureShow”
7. Delete all files and folders at “C:\Documents and Settings\your_username\Application Data\Ulead Systems\Ulead DVD PictureShow”
8. Delete all files and folders at “C:\Documents and Settings\your_username\Local Settings\Temp”
9. Empty your Recycle Bin and reboot.
I rarely throw around credentials, because it is done so often, and too often it ends up sounding stupid. However, I think it is important to back up what I am saying.
I am a network analyst. I have a good number of years of experience repackaging legacy software into Windows Installer (.msi) format for Microsoft Active Directory / Group Policy distribution. I have custom built intranet based software installation systems from scratch. I am a senior member at
www.appdeploy.com , and you can see my contributions there under the same username I have here: craig16229. In other words, I know what I am doing. And I am annoyed at how much of my time was just wasted dealing with this program, and equally annoyed at substance I read upward in this thread.
My experience with PictureShow is this: I downloaded the trial version, and I liked it very much. I went out the same day and bought the full version. When I came home, I went into Control Panel – as has been so stridently advised here – and uninstalled the trial version. When I went to install the full version, the InstallShield routine endlessly offered to uninstall or repair the trial version. I rebooted. Same thing. Then I decided to do a manual cleanup of the produce under Program Files, etc. This made things worse. Then I was also not even able to re-install the trial version so that I could re-attempt a proper un-installation. Whether I tried to install or uninstall the trial or the full product, the InstallShield routine would run for about 1 second and then report it had finished successfully.
In the interest of other users and providing the most accurate information possible, I edited what I originally said in the post about this product being a "setup driven" Windows Installer application. What I discovered after looking at C:\Windows\installer for the cached .msi is that I was incorrect. There was no cached .msi. I ran the install again and watched C:\Documents and Settings\my_user_name\Local Settings\Temp to see what extracted there during the pre-install routine. I can now see that is an install authored purely with InstallShield. I should have noticed that the Windows Installer Service was not running while I was trying to fix this mess before, but it was well past 2:00 a.m. in the morning.
The install was designed to look and act like an .msi installation. But it is not and does not, and I was fooled by appearances.
If it were a well authored .msi installation, it would have the ability to remove itself cleanly. That was one of initiatives of the whole Windows Installer architecture. An .msi is a database file of everything about and installation: folders, files, permissions, registry, sequencing, and on and on. It is the intelligence behind an application's ability to add/modify/repair/remove itself.
Now that I know it is authored completely in InstallShield (and again - for the benefit of others visiting), I will go back and experiment with the folder created by the trial version at "C:\Program Files\InstallShield Installation Information\{C82E1703-ACBB-4015-856B-A8A0E5BAC661}" and see if I can come up with an easier set of instructions than what I have already provided.
Still, someone at Ulead needs to revisit the InstallShield un-install routine for the trial product, because there is something that is not fully right with it.
Craig --<>.