For the authorization see below.
BUT if you have already accessed new books while not authorized check point 2 BEFORE REAUTHORIZATION
otherwise you may regain access to the old books, but lose access to the new ones for ever.
1) ~~~~~
Sometimes ADE gets its registration/activation confused and in a semi-authorized state.
Uninstalling and reinstalling does not help, and indeed installation can even trigger this state.
Unfortunately, it often then gives misleading error messages about what is wrong.
A common incorrect message informs you that the ID is already in use on another computer and cannot be reused.
Another is "E_AUTH_NOT_READY"
This can often be resolved by completely removing any authorization using ctrl-shift-D to the Library screen on ADE (cmd-shift-D if on Mac).
Restart ADE, and then reauthorize with your (old) Adobe ID.
In extreme cases on the mac, the following extra step has helped some people. Navigate to /Users//Library/Application Support/Adobe/Digital Editions and drag the activation.dat file to the trash. If you are using 10.7, see Access hidden user library files | Mac OS 10.7 Lion. http://forums.adobe.com/thread/1265248?tstart=0
2) ~~~~
Running without authorization is a vicious trap that Adobe lays for unsuspecting customers.
They do give very mild warnings, but not nearly strong enough.
When you register 'without ID', ADE creates an anonymous/implicit ID with limited powers (eg can't be used to share with other devices).
Whenever you first load a DRM book, that copy of the book is associated with whatever ID the computer is registered to at the time.
Any book you load while this anonymous ID is active gets associated with that ID, and can't be read on any other device.
When you properly register your computer with a real ID, that old anonymous ID is lost.
Now you don't have any devices that can read the book.
The only way I know round this is to use a DRM stripper such as epubee BEFORE you deauthorize the device.
I do NOT advocate using such code to get around the valid limitations placed on a DRM book.
However, where the problem arises only because of the ineptness of Adobe's ADEPT DRM infrastructure and its implementation,
such a measure is totally justifiable.
AdChoices