Apple says a big F U to Final Cut Studio 2 users…
Category: Blog

Not being a Bud Light type person (I virtually always ask “but why?”, especially when something doesn’t make sense), I felt compelled to dig into the issue further causing this to appear when you try to install Final Cut Studio 2 on OS X 10.7 Lion:

following up on my blog post yesterday about how to Install Final Cut Studio 2 on Mac OS X 10.7 (Lion) without resorting to hackily installing Rosetta.

Digging high and low, I could find nothing in the FinalCutStudio.mpkg that would indicate any PPC requirements. Every binary is universal, nothing in any plist, not even a magic resource fork of some type getting in the way. Trying to pull it up in Pacifist crashes Pacifist, so no luck there either. Stumped, I decide to leverage the knowledge I learned yesterday of DTrace via this amazing blog post on the Top 10 DTrace scripts for Mac OS X.

First up I try `iosnoop`. It does help confirm that the system is being executed, but nothing unexpected appears. One thing it does remind me about however is that writes out a log file to /var/log/installer.log that I had overlooked previously. Checking it for any clues, I see the following:

Installer[14684]: @(#)PROGRAM:Install PROJECT:Install-686.3
Installer[14684]: @(#)PROGRAM:Installer PROJECT:Installer-530
Installer[14684]: Hardware: MacPro5,1 @ 2.40 GHz (x 16), 32768 MB RAM
Installer[14684]: Running OS Build: Mac OS X 10.7.3 (11D50b)
Installer[14684]: Final Cut Studio Installation Log
Installer[14684]: Opened from: /Volumes/Final Cut Studio/Installer/FinalCutStudio.mpkg
Installer[14684]: Rosetta required to install (QuickTime MPEG2 [6748520])

Ok, well that makes sense then. I’m obviously looking at the wrong package, I should actually be looking at QuickTimeMPEG2Pro.pkg instead it seems! Shifting my focus to it, I don’t find any obvious signs externally of it requiring PPC, but I do find it has an executable called `CheckMimeTypes` in it’s Resources folder that’s PPC only which is called by the postflight script. Aha! So there’s our issue, but that still doesn’t explain how knows this fact before we even attempt to install. Not willing to just accept this new found knowledge on face value, I press on.

Since iosnoop was a bit light on info, I decide to give `hfssnoop` a shot since it’s significantly more verbose. Running QuickTimeMPEG2Pro.pkg directly now at this point, I check the hfssnoop output and find the following interesting tidbit:

1922348 501 17517 Installer hfs_vnop_read 0 BundleVersions.plist
1922348 501 17517 Installer hfs_vnop_read 2 PPCRequirements.plist
1922351 501 17517 Installer hfs_vnop_write 0
1922352 501 17517 Installer hfs_vnop_write 0 windows.plist
1922352 501 17517 Installer hfs_vnop_read 8
1922352 501 17517 Installer hfs_vnop_read 8
1922353 501 17517 Installer hfs_vnop_write 0 windows.plist

Ooohhh! Something referencing PPC! What might we have here? Doing a quick find for that file (`locate PPCRequirements.plist` for what its worth) lands me at this file: /System/Library/CoreServices/ Opening it up, I find the following contents:

Very very interesting if I do say so myself! It would seem that Apple is intentionally listing the identifiers explicitly of packages related to Final Cut Studio 2! Removing the FCS2 related entries from that file and re-running the installer, everything proceeds as normal and the install completes (albeit with a warning about the postflight failure) just fine.

So it would seem that just because a simple binary which does nothing other than to check mime types in the postflight script of a minor dependent package, Apple is going to say a big F U to FCS2/FCP6 users! W.T.F. !?!? What’s worse, they aren’t explicitly blocking just the package which is borked (albeit slightly), they are blocking multiple packages related to FCS2, even though they run just fine on Lion and furthermore all of Final Cut Studio 2 proper runs without issue!

This is extremely disappointing to say the least… :(

Tags: , , , , , , , , , , , , , , , ,

17 Responses to “Apple says a big F U to Final Cut Studio 2 users…”

  1. Michael H says:

    One of the best posts ever. I used this a couple years ago and still have Final Cut Pro 7 on El Capitan. Excellent! Thanks!

Leave a Comment

Spam Protection by WP-SpamFree