Quote:
Originally Posted by EagleRidgeGal
davidfor said: Yes, I'm sorry, I should have made that clear at the start. The Glo lists the card in the device info. and correctly displays the available memory on the card. The card holds ~2000 books, side-loaded using Calibre 1.3 64-bit, but none of these books are displayed by the Glo. Previously I had a 32Gb microSD card loaded with ~1700 books, all side-loaded using Calibre (though 2 versions of Calibre prior and one version of Glo FW prior) and they were all displayed with no problems.
I'm not familiar with SQL but I'll do some research and give it a go. I'm having a lot of learning since getting the Glo and Calibre. But I'll give your idea's a try.
Ejecting and reinserting the card whilst Glo running makes no difference to books on card being recognised/displayed. Calibre does indeed see all the books on the card and has no problems interacting with them the same as those on the unit's main memory.
Thanks for your help. I'm off to do some reading up on editing SQL and Calibre/Shelves.
|
All that is really weird and I haven't heard of that happening before. I would really like to see the database to try an work out what is happening.
Thinking of possibilities, there might be something in the "Kobo eReader.conf". If you look in it, in the section starting "[ApplicationPreferences]", there should an entry for the SD card. It is an eight digit hexadecimal number with a value of true. Mine has "90164EF8=true". Deleting that line might get the device to reprocess the books. That would mean it deleted all the books on the SD card from the database and then added them as new books. If you try this, remember what the id was in case it doesn't work.
Another way that might work is to insert a different card with just a few books. This should remove the current books from the database and then add the new books. Swapping the cards again should get the books on the card processed.
If you try either of the above and it doesn't work, tell me. Someone suggested a new function for the utilities plugin that should help to fix something like this. I haven't sat down to plan it, but someone with a need like this encourages me to do it.