Quote:
Originally Posted by Catlady
I had let my Amazon books pile up for a couple of months and so today decided to strip and convert. I've done this through Calibre ever since the plug-in became available--but today none of the books would convert; I got error messages telling me the books were all locked with DRM. So I updated to the latest version of Calibre, updated to the 5.1 tools and added the plug-in--and STILL got error messages.
All the books had azw extensions. I changed them to mobi extensions, solely on a whim because I couldn't think of anything else to do, and then, lo and behold, Calibre converted them to epub. A few of them turned out to be topaz, but they too converted when they had the mobi extension.
This doesn't make any sense to me, especially since I didn't see anything about a problem with azw files in the readme files. Do I really need to change file extensions now? Weird.
|
I've encountered a variation of this, Catlady. After upgrading to the new version of Kindle 4 PC, I ran a test batch of various newly-purchased .azw3 and .azw files through the 5.1 toolset plugin for Calibre. It looked like all ~12-15 files converted successfully to .epub format, and I was able to open them fine on the same computer that I ran the conversions on, but then when I transferred them to Computer #2 (which does not have the toolset) for extra editing in Sigil, the files refused to open at all, giving an error message about DRM. Brought the files back to Computer #1 and they opened again just fine.
Ultimately I got around it by opening the .epub files on Computer #1, copy-pasting contents into fresh .epub files in Sigil, and then moving these fresh files to Computer #2. Still, I'm a little unsettled by the whole thing - never ran into this problem before, very weird.