Quote:
Originally Posted by jhowell
... Perhaps calibre produces azw3 files that are subtly incompatible with recent kindle firmware. I have never experienced this problem, but I use kindlegen for conversion. Or that could just be a coincidence.
|
I haven't used Calibre for a while. Everything I've read in the past several months has been hand-edited via an HTML editor; validated and zipped into an epub using Pagina EPUB-Checker; run through KindleGen via Terminal command on Mac; then Send-to-Kindle via Send-to-Kindle app on Mac or iOS. If you think any of those steps could be suspect, let me know and I'll see if I can figure out an alternative to test.
Quote:
|
The kindle firmware is pretty good about reporting internal problems. I suggest that someone who does experience this problem use the ";dm" search command to dump the kindle's log files whenever it occurs. The the ends of these logs should be checked to see if there is a common error message that could point to the cause of the problem.
|
Cool. Thanks for the tip. I will try that.
Is there a list somewhere of these ";" commands that can be used? I remember there was one to reset the "time-left-reading" feature. What other nifty commands am I missing? :)
Quote:
Originally Posted by shalym
Hmmm...odamizu, are you on a Mac? It looks like the other user is. Maybe that's the issue?
|
I am indeed on a Mac, which is an interesting coincidence. But I'm not sure what about the Mac would cause this.
KindleGen on Mac should be the same as KindleGen on PC.
Could the Send-to-Kindle app for Mac be wonky? Hmmm ... maybe I'll try sending it via email to my Kindle's address and see if that makes a difference ...