This content has been marked as final. Show 4 replies
I've just spoken to Adobe on the phone. They say they have
no mechanism in place to deactivate a product when the user
is unable to do so.
I'm now in the process of installing a cloned copy of my
OS that I made before I installed CS3 for the first time.
I have been told CS3 should recognize that it's activated
when I start it up as the system ID will be the same. I
have my doubts about this, but I'll try it anyway.
I had a feeling it wouldn't work. It didn't. When I phoned
Adobe again, I was told the advice they'd given me before
was incorrect. Thanks a lot, Adobe. I just reinstalled my
OS for no reason based on your faulty advice.
And now I have to phone up and beg Adobe every time I want
to use my second activation, because they can't delete an
entry in their database that is wrong. Little by little I'm
beginning to hate Adobe.
1. That advice was not necessarily wrong. Unless something had changed on your computer such as a hard drive or a motherboard, or if you had formatted it, the activation should still be recognized.
2. You can still use one activation without problem. If you want to activate another machine, you need to call and explain the situation. There's no need for begging. It takes about 5 minutes and the call is usually free.
> 1. That advice was not necessarily wrong. Unless something had
> changed on your computer such as a hard drive or a motherboard,
> or if you had formatted it, the activation should still be
It was a cloned copy of the OS on an the same machine with no
hardware changes. Perhaps an Apple update I installed after
cloning but before previously installing CS3 changed the
> 2. You can still use one activation without problem. If you
> want to activate another machine, you need to call and explain
> the situation. There's no need for begging. It takes about 5
> minutes and the call is usually free.
Up to a limit of 5 occasions, apparently. But it's more a
matter of principle. The Adobe activation database clearly
doesn't do what a database of this kind should do. That is,
keep a record of the working installed copies there are. It
strikes me as a fundamental flaw that records that are no
longer accurate cannot be removed.
But then, it really doesn't surprise me. Large companies are
often like that. They have rigid systems in place that don't
allow the sensible thing to be done.