Thread: Adobe Digital Editions Authorization
View Single Post
Old 04-22-2022, 10:19 PM   #17
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by anacreon View Post
I was extremely surprised recently when I couldn't read any PDF on the Sage - supposedly they weren't authorized by ADE - while there had been no change whatsoever to F/w and such. There was no problem with the kepubs (I don't read plain epubs).
I checked that the same PDFs had no problem on Elipsa, and decided to turn off the Sage.
I was happy that after turning it back on, all PDFs became readable again.
I wonder what type of problem would "de-authorize" reading PDFs but not kepubs, and would be solved by turning a device off then on.

EDIT: I strip DRMs on all books (PDFs or epubs or kindle files) as soon as bought, so ADE shouldn't have a say on them anyway. It is particularly necessary for PDFs since a higher proportion do not have TOCs than epubs'.
Firstly, the DRM mechanisms for ePub and PDF is completely different from and unrelated to the DRM mechanism for kepubs. For ePub and PDF, the Adobe RMSDK is used. And is used for ePubs and PDF with and without DRM. So a failure on one doesn't mean a failure for the other.

The DRM error is something that has been around a while. It isn't obvious what is happening. And rebooting the device usually solves it. That suggests it could be a problem with one of the processes used for reading. It could be that a process has hung, or has crashed and not restarted properly. Restarting the device clears those problems as everything gets started anew.
davidfor is offline   Reply With Quote