I it were me i would do a clean install.
I installed the trial (multiple programs from the Production Suite), then simply entered my retail serial number. Part of that process was the download and installation of the codecs not included in the trial.
Having said that, I am now encountering a problem with the 5.01 updater for the electronic download version of the suite for PC. It does appear to be a problem with the update file itself and not my installation, but it is unresolved at the moment.
I don't think there is any downside to just entering your serial number in the trial version..... then when time allows, and if you have any issues, install from your discs.
Thanks, Ann... I think you're correct. What's a few hours, anyway?
The problem is, I'm going from JUST Premiere Pro (well, and OnLocation and Encore) to Premiere Pro plus all of the other application in the Production Premium suite (i.e. After Effects, SoundBooth, Photoshop, etc.). I'll HAVE to install from the discs, no matter what, but my question was whether it was OK to go over the top of the trial install--I believe the answer is "no" but thought I'd check anyway.
Just like 'Deactivate' is generally suggested, clean installs are generally suggested and especially with suite changes. It is so easy to destroy DL or other advantages of a suite versus indidividual programs, that the install time is negligent, It does not take hours, but mere minutes.
I would be interested to see what the Production Premium Suite takes in terms of disk space, number of files and directories after installation with everything installed.
Maybe slightly off-topic here, but then maybe not. In another thread, you made mention of the duplication of all possible languages, with all programs in a suite installation. The question that I have is if a suite installation allows one to customize to just the required language.
Just wondering about the bloating and duplication (triplication, etc.) of this type of file, when installing all the apps. in a suite.
It could be simple, like Microsoft does with Windows.
Microsoft probably sells in even more countries than Adobe, but they keep a simple rule for OEM installations: ONE language (EN) is required.
Adobe follows a different approach, they install in total 42 languages, completely missing the other 5,000+ languages.
Adobe misses for instance Hindi, Javanese, Punjabi, Wu, Telugu, Tamil, Cantonese, Tagalog, Gujarati, Min, Wolof, Mandinka and numerous others.
I have suggested to use the Common directory for installing the license agreements and other paraphernalia ONLY in the install language and possibly the OS language, if different. That would clean up the installation and reduce clutter and performance degradation.
As I said in another post, cleaning up saves over 1,600 directories and over 2,000 files in the Production Premium Suite alone and reduces my CS5 PPS to less than 3.47 GB.
What, no Javanese?
That answers my question - just clean up afterwards. I would like to see the adoption your suggestion - one common folder for all the extra "stuff."
PS - it's somewhat similar to the way that PrE handles multiple languages in its DVD/BD Library content. Each Menu Set contains PSD's with every supported language. PrE does sort out the installed language and chooses that, when one authors. Still, the PSD's are much larger, than will likely ever be needed, since all languages are included. If I do any work with those Menu Sets, I just Delete all Button Layer Sets, for the other languages and the total file sizes shrink by about 80%.