View Single Post
Old 12-05-2016, 07:19 AM   #5
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Sir Loyne View Post
As I had said from the start, this WAS just after a factory reset.

If you do a search for a Kobo Touch plugin you will find that there's no such thing, that there's only the Kobo Touch Extended plugin. I was just saving time by shortening the name. That one is on me. For reference... I added the word "Extended" to the original post
Yes, there is a Kobo Touch plugin. But, it is not a user installed plugin, it is part of the calibre installation. And it is usually referred to as a driver. If you hadn't installed the extended driver, this would have been used. Of course, the extended driver subclasses the KoboTouch driver and most of the function comes from it.
[/QUOTE]
I wasn't blaming anyone here. How did you get that? And I wasn't really asking for help. It was more of an updated report of what it took to actually get a book on the reader.[/QUOTE]

From your description the database is corrupt. The problem is why. If it is only happening when the Windows 7 machine, then there is something wrong with it. What, I have no idea. If it is happening with more than one PC, then it is more likely the device. If it happened immediately after the factory reset, it might be faulty internal memory. You could try the factory reset again and see what happens. Or the less drastic act of signing out of the Kobo account. That removes the database and you get a new one when you sign in again. If it corrupts quickly, it's probably a hardware fault and you should exchange it.
davidfor is offline   Reply With Quote