Quote:
Originally Posted by joblack
Ok, I just removed my registry and reactivated with the new version of ADE. Script works fine so far.
So they haven't changed the key saving scheme. Very strange - could be that some have more than one key in the registry (the key retrieval gets the first it finds).
People who have problems with this bookkey thing, inspect your registry for more than one entry like
privateLicenseKey
in the
[HKEY_CURRENT_USER\Software\Adobe\Adept]
(To open the registry -> Start -> Execute -> regedit (under XP don't know if that works for Vista)).
PS: I've got another suspicion: Have the ladies/gentlemen changed their hardware in the past and had to reactivate the ADE?
|
My impression is that if you already had your adeptkey.der file, and had to upgrade DE, DE uses your old authorization key. So we have no problems decrypting with the new script.
It seems that people having problems are those that are running the key file for the first time after having upgraded to the latest version of DE. For some reason adeptkey.pyw does not find the key in the latest version, supporting your theory that Adobe may have moved the key to a different register within DE. Therefore, the script that needs possible modification now would be the adeptkey.pyw (or ineptkey.pyw) script, once someone can identify where the key in the new version is stored.
Does that may sense to your way of thinking?
cheers