Leopard & FCS2

Question

CS2 & Leopard are terribly incompatible.
I struggled with them together for a month and I finally downgraded to Tiger.
I did clean installs, re-installs of software, etc...
I am a 20+ year mac user and very technically adept, but was still unable to reach a solution that was reliable on all fronts.
Here are just SOME of the issues that pop up intermittently:
-Compressor's windows don't open
-Compressor's Batch window will not open
-Compressor does not see the local machine when submitting (local cluster)
-Various FCP6->Compressor issues
-Motion's interface does not open
-Motion goes into a processor-intensive loop of some sort on launch
-Various update issues (including but not limited to):
-Compressor update to 3.0.2 sometimes will not work, beacuse the installer thinks it has been already installed
-The second pro-apps update will not apply sometimes
-FCS2 will sometimes not replace key files when doing a re-install(therefore, a clean install is ALWAYS recommended, but of course it is a huge pain to remove every key file---why does Apple not offer an uninstaller?)
-Various issues with frameworks (this becomes clear when you sort through the console logs)
These are just some of the issues that plague FCS2-Leopard. Of course, downgrading to Tiger fixes everything. This is unacceptable, and will quickly push professional users away. Apple QA is not what it used to be - I'd recommend that Apple Corporate take a look at this.

Answer 1

I must say, your trouble report is unique; none of our editors nor anyone on other forum has your laundry list of complaints. Curious how your installation could be so unstable however, I'd highly recommend submitting a trouble ticket to Apple Pro support. Nobody at Apple is going to read this thread and do anything about it, you need to be pro-active and call in your problems directly.