Registry is the worst thing that ol' billybob came up with.

John,

Tech support had me look at the log file which was almost 21Meg in size and look for 'FATAL'. The error code found was loading a color file and was declared by the tech as minor (but happened as many as 20 times). No he did not ask me to send him the file. I have not had an install problem with any other software in the past; I thought XP Pro was fairly stable. I do have a backup with Ghost on DVD'S (two weeks ago)and a duplicate C: HARD DRIVE that I made an image copy onto about a month ago that I may put back in the computer and try installing CS3 on that drive. Meantime, I'm not that excited about all the work of getting CS3 up and running and will use CS2 for my photography. I've been spending too much time with CS3 and need to get some photographic work done. I've given up.....

Ken

I don't understand the reason of Adobe's changing installation routine. What's the purpose? The goal is what?
I remember Photoshop 3.5 and 4 (and so forth untill 10) quick, successful and trouble-free installation procedures...

Still waiting for solution... :(

I've spent two and a half days trying to get rid of the CS3 beta and install the shipped CD--with no luck. CleanScript won't run for me (even as administrator) but maybe it's just as well given some of the above comments. Manual uninstall didn't help--didn't have any of the registry keys they wanted removed to begin with. Only some shared components install from the CD--others don't and Photoshop doesn't--and it takes forever-- only to learn it didn't work. Uninstall of the failed install takes forever, as well. Trying to solve the problem screwed up CS2 and I had to repair that and then had to update the repaired version--took forever. Recent RAW files wouldn't work with the repair until I updated it--needed the updated ACR.) This is a monumental misstep on the part of Adobe--I'm a patient person but this is ridiculous. Each person's solution appears to be different and what works for one doesn't work for another. Why would Adobe assume that we are all so computer-savvy that we can compensate for their bad programming? Will there ever be a way for the average computer user to install Photoshop CS3 and get it up and working without having to invest in hard drive imaging software in case it badly screws up our computers? I back up data to external hard drives, but have no disc image. A friend looked at CleanScript and said that it's a Python script that automatically searches and removes dll's, Adobe files and registry entries that don't allow the new code to work. How about a list from Adobe for those of us for whom the script won't run? When it comes to trying to compensate for Adobe's bad programming, the adage "a little knowledge is a dangerous thing" applies to the average computer user, and some of us just aren't comfortable trying all of the solutions we read in forums, hoping to hit on one that will work for us--and we shouldn't be expected to have to. Adobe should solve the problem--they created it.

After running the clean script at undocumented level 4 and to no avail, like many people I gave up. I decided to reinstall my LightRoom trial and at least get some work done - I have a few days left. As I was re-installing it, I wondered my trail period would now be reset because the clean script removes all traces of Adobe products. To my surprise, the trial period was not reset.

This led me to a theory. These CS3 installation problems revolve around copy protection. Let me come out and say that this is the first copy of Photoshop I've purchased. I always said I'd buy Photoshop if I started making money, and I so I have.

This theory might be wrong, of course.

Eventually however, crack will come out bypassing this nonsense. And the good people who have done the right thing by purchasing a legit copy of CS3 will still be left out in the cold.

Dumping layers and layer of copy protection on a software won't make the 15 year olds that pirate it magically cough up $700 - or the adults that only use the same features for their photos that they could get from Picasa.

People are trying to buy and use this software, myself included, and being punished for it. Or if I'm wrong, this is just the very, very worst major product release in recent history.

Well, soory to dissapoint you.
Here is the Fix to the intallation error.
All other complicated stuff doen't work. I have tried it.

1. Uninstall CS3. Do a search for "caps" in the common folder and delete the files. These files store install info)
1a. Restart
2. Physically disconnect the computer from the internet (preserves network security) Disconnect all networks.
3. Disable the firewall.
4. Install CS3( note: the problem is with the "Bonjour" software that Adobe is trying to use. For some reason if it can't reach the internet the installation will fail)
5. Restart
6. Activate/register

CS3 fixer: Sounds too good to be true--I hope it is the final solution. I'll wait until a few people try it and give us feedback--just can't spend any more hours dealing with failed installation right now.

Please--anyone who tries this, give us feedback on how you make out.

Eventually however, crack will come out bypassing this nonsense.

It would not surprise me that it already has. The bogus copies available in Asia preceeds the actual introduction time, so I am told.

You might want to look at the Event log and see if it's logged as an error. If so, read the error and see if it indicates any missing or faulty modules, like dll's.

Apart from having a relatively well-maintained system, I don't know why I was successful with my CS3 Beta removal and installation of the retail version. However, I will note that I observed the odd-named service related to Bonjour soon after installing the CS3 Beta, and likely even before I began using it. Not knowing what it was yet not liking a service being active that wasn't obviously associated with Adobe, I disabled the service from the start. So, even though I rarely used the CS3 Beta, at least for the times I did explore it or Bridge CS3, the Bonjour service was never active. Ditto upon installing the CS3 retail version...before ever launching it, I disabled Bonjour.

Regards,

Daryl