View Single Post
Old 01-07-2011, 06:14 PM   #18
taming
Trying for calm & polite
taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.taming ought to be getting tired of karma fortunes by now.
 
taming's Avatar
 
Posts: 4,012
Karma: 9455193
Join Date: May 2010
Location: Mostly in Canada
Device: kobo original, WiFI, Touch, Glo, and Aura
Is there some history to all of this that we don't know about? For example, some time back there were a couple of Calibre versions for which the Kobo driver pooched the Db. Tim Legge, who does the Calibre development for such things, caught it fairly quickly, but folks found that they had to do a factory reset. Is that a possibility? For me, that was, btw, the only time sideloaded books went to the back of the I'M Reading section and didn't behave themselves.

One of the best parts about the WiFi version of the reader, from my POV, is that no books are stored in the Db. Much easier to keep the Db spiffy that way.

Also, when you show the books in the main memory of the device on Calibre, you should be able to change the status to "read" for any book on the device.

Last edited by taming; 01-07-2011 at 07:01 PM.
taming is offline   Reply With Quote