Quote:
Originally Posted by Mellobob
I have not changed anything in Calibre ... well, not that is obvious to me.
|
The main thing to check is that the collection/shelf columns setting is correct. It should be a list of the columns you want to build the collections from. If this is not the correct columns, then the collections will be incorrect after the next connection of the device.
Quote:
I wonder, is having both kobo utilities installed a problem? I have the Kobo device interface 2.1.7 and Kobotouch 2.1.7.
|
These are part of calibre. They are the drivers calibre uses to connect to the Kobo devices. The "Kobo device interface" is for the original Kobo ereader and the WiFi. The Kobotouch driver is for all newer devices. That is, the Touch, Glo, Mini, Aura HD, Aura and Aura H2O.
The Kobo Utilites plugin is an addon and has to be installed by you. But, it can be installed though the plugins section of the preferences.
Quote:
When you say "reading status" do you mean all books or the current one? I'm really just concerned about books being marked as "read".
|
Both actually. The plugin can pull the readings status of any book on the device that is in your calibre library. It stores this in some custom columns. The reading status is the percent read (100% = Read), the current position in the book, rating and the timestamp when the book was last read. All are optional, so you can just store the percent read. But, if you store the others, you can restore them to the device after a factory reset or signout and back in. You can also transfer the status to another Kobo ereader.
Quote:
Of course, I don't have a copy of the database
|
Which is another function of the utilities plugin. It can take a backup of the database and configuration when you connect.
It doesn't sound like the database is corrupt. If it was, you would probably be getting errors when calibre connects to it. And f the driver configuration is correct and the collections are wrong, there must be something else going on. I can tell a lot from the log that calibre produces when it is run in debug mode. If you restart calibre in debug mode (right click the preferences button and select the option), connect the device and post the log when it finishes, I'll see what I can see.