I don't have cs4 yet, but what I see on here is that if you uninstall cs3 after installing cs4, it will disable cs4. I believe I read that there will be a fix for this coming out. As long as you don't uninstall cs3, you can have both on your machine with no problems.
It seems we've read the same thread :-)
I think I'll install CS4 in parallel and hope Adobe's fix will come soon...
I now have my CS4 package and will install it without removing CS3 .
Then I will hold off using it "seriously" until the updates are installed ie . I will have a play with it.
There is a known issue where removing CS3 after having both CS3 and CS4 installed together will cause problems with Adobe Media Encoder. As long as you don't have them installed at the same time initially, you're fine. CS4 by itself is fine. If you do get yourself into this situation, the solution is just to uninstall and reinstall CS4.
I installed CS4 on the same drive as CS3 and so far I have had no problems.
You shouldn't, so long as you leave CS3 installed. If you now uninstall CS3, that's when problems occur.
I have the same problem but I don't have CS3 installed (I had it there's some times). Only thing to note is that I had Flash CS4 US trial installed before to install Premiere CS4 trial FR.
I uninstalled all CS4 and reinstalled only Premiere + components, and the problem is yet there.
Any idea ?
I have the same problem with CS4 installed over CS3, then uninstall of CS3.
The net result for me is that in the directory \Documents and Settings\[your user name]\Application Data\Adobe\Premiere Pro there are three directories 2.0, 3.0, and 4.0
I have removed the 2.0 and 3.0 one with their content, and renames 4.0 as old.
I launched again premiere, end then itt surprisinly worked.
Loking at the dictory, it ré-sed the old directory as if it was named 4.0.
What I suspect is that the software does not even looks at the name of the directory, and thkes one of the three, in my case the workgn one.
To be sure I rename 4.0 the directory just in case a change makes premiere look for it.
May be this might work for you! Good luck (it tooks ma a full day to come to that)
I was beleiving to santa clauss!
There stil remain the main problem, Media Encoder receives references that he cannot accept ans the production does not happens.
Amazingly enough, the original question was never answered...
I have CS3 Web Premium Suite installed on my Windows XP Home SP3 machine, plus the upgrade to 3.1 (was only the new version of Acrobat Pro 9). It mostly works fine.
I just bought CS4 Web Premium Suite. The question is: SHOULD CS3 BE UNINSTALLED BEFORE INITIAL INSTALLATION OF CS4.
This turned into a discussion of whether CS3 could be removed AFTER CS4 had been installed in parallel. The real question is: Is is better to have a clean installation of CS4 by completely removing CS3 FIRST.
No, you can use them side by side. You can't use CS3 when you created CS4 projects, there is no backward compatibility. Be aware if you want to continue using Ultra CS3, you need at least one basic component of CS3 installed. The rest can be uninstalled.
Thanks for that. So CS4-created work cannot be opened in CS3? But I assume all CS3-created projects will work fine in CS4?
And why would I want to keep CS3 on my system if I now have CS4? I'm not sure what "CS3 Ultra" is, or if I even have it (never heard of it before), but it sounds like if I install CS4 parallel with CS3, and then remove CS3 later, I may well have trouble...
Is there a compelling reason to leave CS3 programs on my machine if I am now installing CS4??
I assume all CS3-created projects will work fine in CS4?
Mine have all pretty much worked, but there have been reports of difficulty. If you have any open CS3 projects, it may be best to leave CS3 available to work on them.
I'm not sure what "CS3 Ultra" is, or if I even have it (never heard of it before)
Then don't worry about it.
if I install CS4 parallel with CS3, and then remove CS3 later, I may well have trouble...
One avenue of approach would be to install CS4 and leave CS3 in place. When all current CS3 projects are done, or once you know they work fine in CS4, you then wipe the entire System drive, reinstall everything from the OS on up to get a nice, clean fresh install of CS4.
Thanks for that advice, Jim. Perhaps I'll uninstall all CS3 programs except Dreamweaver and Photoshop, and then install full CS4. Those are the main two I use frequently and have tweaked to ongoing projects. Plenty of harddrive, so headroom's not an issue.
A complete harddrive reformat would be rather extreme, but would definitely make for a clean install!
My comments about compatibility relate to Premiere only. Photoshop should have no issues. Check the Dreamweaver forum for further data.
Did everything go ok?
Yes, thanks. CS4 Web Premium Suite was fully installed in parallel with CS3 with nary a burp, though there are a few anolamies here and there. All psd files are now associated with Photoshop CS4 now, but opening them from the file browser inside PS CS4 causes a complete program crash. That's repeatable. So, as the doctor might say, I just don't do that. I think PS CS4 may not like some data associated with PS CS3 files, as least in that opening context. Still playing around with it. Getting the color profile set up and working properly has been the biggest hassle so far. DW CS4 immediately found all my defined sites on my desktop, and everything seems copacetic.
I will probably not use CS3 much anymore, unless the PS CS3 files are really unworkable in CS4. But it seems prudent to leave the entire CS3 Suite alone for the life of this computer, as removal will undoubtedly create some headaches. Too bad there's no guidance whatsoever on this issue from Adobe...
I have discovered a nasty bug:
Fireworks CS4 is installed in parallel to Fireworks CS3, but I have gif files associated with IE, since I want to see them in a browser first. So when I right-click and try to open a gif file with Fireworks, only Fireworks CS3 (and other programs) are listed, NOT Fireworks CS4. When I browse to the Fireworks CS4 executable and click on it, nothing happens.
Same issue when I try to associate all gif files with Fireworks CS4- the executable simply will not associate. If you click on the executable separately, it DOES open the program.
So the only way to open gif files with Fireworks CS4 is now to open the program first, and then use File--> Open. Not the end of the world, but could get pretty annoying.
Anyone see this particular glitch before?
So the only way to open gif files with Fireworks CS4 is now to open the program first, and then use File--> Open.
Personally, I find that the best method regardless of file type.