For those of you running Adobe CS2 on Leopard...

[tahoedrew]

I'm hoping for some help... anyone out there running CS2 on Leopard and an Intel machine?

Thanks,
~A

[Stephanie]

Yes, I am.

[Mike Sellers]

MacBook Pro. Runs fine. Actually, I did an archive and install with 10.5.

[tahoedrew]

How did you install CS2. I used Migration Assistant, but should I uninstall and start from the install DVDs?

Thanks,
~A

[Stephanie]

I used Migration Assistant too.

At this point, it might not hurt to uninstall and reinstall from the DVDs.

[tahoedrew]

Did you move from a previous install of the OS on an Intel machine (10.4.x)?

~A

[tahoedrew]

Uninstalled and re-installed and it appears to have registered a-ok.

Still, WTF?! Adobe tells you over the phone you can't activate CS2 on Leopard and then I load it up and it works.

Bunch of f*ing idiots!

~A

[gabester]

I think it's really a disservice when a company determines that, because they don't "support" something anymore that they still won't make a best effort attempt (esp. for one of those phone calls that no doubt presents an option for you to pay a fee with a credit card to speak with an support engineer) to get it to work when it can be done. As in this case.

I also have to question the quality of activation code when it doesn't work after just a couple OS generations - and moreover, when will Adobe deliberately break their activation interface since the product is old and unsupported, forcing folks to upgrade?

After all, you only own a license for the software and in that license I'm sure it says something to the effect of Adobe being able to change the terms of the license as they see fit, including no longer providing activation for the product at all, and better yet, they could probably provide you an update for the software that would disable it completely because it's "too old." They wouldn't put it that way, they'd claim it was to protect you from security problems or some such...
g=

[swampy]

I hate the Adobe activation scheme. I've even managed to 'break' it in the sense that it no longer worked and I could not run CS3

It was last winter when I upgraded from a G5 to a MacPro running Tiger. Early summer I upgraded Tiger to Leopard and that's when the trouble began. For about a month I maintained 4 partitions (Tiger boot/backup and Leopard boot/backup). I was always careful to deactivate CS3 on all boot partitions before cloning thier backup. After the clone process I would boot from the clone to verify it was a good clone, Launch CS, activate then deactivate before returning to the regular boot partition.

One day I started getting messages that I could no longer deactivate CS3, note the error code and call Adobe techsupport. Turns out that Adobe keeps a count of your activations and deactivations. I got bumped up through the tech support chain of command until I reached a software engineer who said that the programers put no limit on the number of activations, but for some reason had written in a limit of 21 for deactivations! He didn't know why they did that, but the fix was for Adobe to reset my 'count' numbers. In that process their 'fix' process had a limit of 5 so I was told that I could only deactivate 5 more times. After that, I'd have to buy a new copy of CS3!!!! That's BS!!

[MysteryGuest]

The dark side of activation schemes.

There is no light side...