🚀 go-pugleaf

I was pretty sure it was mentioned earlier in the post, and as Dave pointed out, in the "Adobe Intel Mac Commitment" post, but the reason behind this is that Version Cue is a low-level process that doesn't abide by the rules of "Rosetta," which is the way that non-intel mac applications can run on intel-based macs. I think somewhere it said that it loads some kernal extensions at boot time, which would be 1) at a much lower level than rosetta operates, and 2) wholly incompatible with any chip that it wasn't written specifically for, i.e. powerpc-based chips.

Version Cue CS2 will not run on intel-based macs, which currently includes Mac Mini and iMac Core Solo and Core Duos, Macbooks, Macbook Pros, and Mac Pros.

That being said, there are ways of taking advantage of Version Cue on these machines, without running Version Cue. Lets say, for example, that you have just upgraded to a macbook pro from another mac that was powerpc-based. You can install just Version Cue on your old powerpc-based machine, and enable Version Cue file handling on your intel-based mac's installed copy of CS2, but not install Version Cue on that machine. This way, your old machine would in effect become a version cue file server.

I know this isn't ideal, since most people don't have multiple machines with which to experiment on, but it is a way of making the most out of an unfortunate situation, that being that version cue CS2 will never run on intel hardware. Its a really fantastic extension of the Creative Suite 2, and I try to advocate it at every turn.