trevor, check out my post 12 in this thread of the cs forum. not specifically about adobe activation, as i’m not sure what they’re up to, but describes the way ms does it with the rolling/aging hardware changes… my GUESS is this is how adobe does it. so you might get some info from this until someone from adobe responds. 🙂
dave milbut "Activation of Single Product in CS Premium?" 11/5/03 6:53am </cgi-bin/webx?14/11>
Thanks Dave that does help answer some of the questions.
‘Welcome Trev.
Honestly, I’d like to see Adobe fully lay it out, like MS did when they first breached the Activation bubble. What exactly is being cataloged? How much weight is given to each componant? What is the aging strategy? How many activations are allowed in a given time frame? Is that time frame rolling or static? Sounds like good fodder for a well thought out FAQ. Security by obscurity is a bad policy. By spelling out everything clearly and in one place, Adobe can go a long way towards good customer relations on this issue.
While the subject of Activation does not bother me in the slightest (perhaps because I did not have any problems with it ;-)), I agree with you 100%. Enquiring minds want to know!
Well, it only makes sense so that we can properly administer our systems and understand cause/effect, thereby anticipating disaster BEFORE it strikes (sounds like a TV commercial don’t it?)
Cause/effect?
No, you sound more like the Merovingian (from the Matrix ;-))
(Sorry, I just got back from seeing Revolutions.)
If there are temp files as the result of activation, then it is #1, non standard, and #2, should be clarified as to the importance of these files.
My boot routined deletes all *.tmp files on boot. You?
these aren’t standard tmp files tony. (although in the grand scheme, if you clean up and remove all tmp files i suppose they could get wiped out. probably get recreated automagically). they’re executables DISGUISED as tmp files. very sneaky and underhanded IMO. If they’re executable, call them by a standard extention, Gosh Blankity Blang Blammit!!! (EXE, DLL, OCX, etc.) Don’t hide executable code behind an extention that’s not normally used for it! I believe it’s not Adobe’s fault. I think they’re part and parcel of the macrovision thing.
Gee, we do not have enough threads about activation, does anybody care to start a few more?
I already did, so you go ahead and start another one.
Seriously though, I am really looking for a reply – hopefully from someone at Adobe – with regards to the questions I asked at the beginning of this thread. Thanks.
I’ve got questions out to our activation folks about the hardware question. I agree, the FAQ should be more specific here.
I’m not sure there is any limit on re-activations on the same machine. I supposed if you re-activated 100 times a day that it might raise some eyebrows, but AFAIK, there is no re-activation limit.
For changing machines, if you do it once or twice a year, you shouldn’t have any problems. At worst, you can call to get the old machine deactivated.
-Scott
Thanks so much Scott! I really appreciate the answers!
Note that the FAQ on the web has been updated as well.
-Scott
Great, thanks. I will check it out.
BTW, kudos on CS, it rocks!
