View Single Post
Old 10-26-2010, 02:36 PM   #141
tomsem
Grand Sorcerer
tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.tomsem ought to be getting tired of karma fortunes by now.
 
Posts: 6,959
Karma: 27060153
Join Date: Apr 2009
Location: USA
Device: iPhone 15PM, Kindle Scribe, iPad mini 6, PocketBook InkPad Color 3
Quote:
Originally Posted by KarlB View Post
I'm having a similar problem. I've been using the Feedbooks Guide for a long time on my Kindle 2, but when I went to update it yesterday I got the above-described error message and a file that my Kindle won't open. I can download the Feedbooks Guide on my Mac, and even open and view it using the Macintosh Kindle client, but when I manually move it to my Kindle, the Kindle still won't open it. Multiple attempts produce the same results.

This is really frustrating. The Feedbooks catalog has been an excellent resource; its public domain books are almost always better-formatted than the same book available through Amazon's Kindle store.
I had the same problem. I think there's some problem with their web server prematurely terminating the download and thus corrupting the file. Eventually I got a 'good' copy, which I won't be updating for awhile, or at least I won't replace it until I'm sure the new one is good. The 'good' copy (19Oct2010) is 1,952,488 bytes. One of the bad ones (supposedly successfully downloaded) was only about 450KB. Presumably newer ones should be larger than 1,952,488 bytes.

I checked their Facebook feed and someone else had also reported this problem, which also mysteriously disappeared.
tomsem is offline   Reply With Quote