[Ken Maltby]

ADE (Adobe Digital Editions), ADE SDK (Software Development Kit), the device
developers implementation of Adobe Reader Mobile (using the SDK), are all interrelated
factors. Add to that the fact that the B&N (Barns and Noble) DRM support was not
added to the Adobe Reader Mobile until recently, make for more confusion in these
discussions.

First, while the Adobe Reader Mobile versions that support the B&N DRM are
implemented in conjunction with ADE, the ability to read B&N DRM ebook files is a
function of the Reader not ADE. You do not need your device "Authorized" by ADE
or have your B&N .epubs interact with ADE in any way, to be able to read the ebooks.

Disinfecting your ebook purchases is only prudent and is the wisest move even if your
devices can deal with the DRM infection. It can be the only sure way to have the book
that you purchased readable on all the platforms you own, now or in the future.

As to ADE "Authorizing" your devices, the most common situation is that the "Authorization"
has happened, but it is not apparent to the user. Check in the "Library" mode of the ADE
program on your PC and see if there is a "Bookshelf"/listing for your device.

On your device, you can check if there is a hidden (in linux) folder titled ".adobe-digital-
editions" that contains the file "device.xml", in the root of the device's internal storage.
This folder and file are what ADE uses to establish that there is a device that it can
"Authorize" and the file contains data needed in the process.

Having a folder titled "Digital Editions" on your device would also indicate that the ADE
program, on your PC, has already authorized your device, as creating that folder is a part
of the process.

Luck;
Ken