Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 01-30-2015, 09:10 PM   #885
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 Leonatus View Post
Haha, it went quicker than expected! I slightly remembered that there should be, somewhere on the computer, a backuped database from the times when there was no error message. So I copied it and replaced the present database on the device - including the zipped folder with the files "affiliate.conf", "KoboeReader.conf" and "version".

And voilą: After the processing done, I opened Calibre and made "check database" with the result "ok".

Thank you, David, once more!

P.S.: The settings remained as they had been, only in the books I had on the hard drive, I have to look where I had been.
Good to hear it is working.

Quote:
May I utter a suggestion: Could the automatic storage of a corrupt database be suppressed? I was about to replace the present corrupt database by another that I had stored before at first.
The automatic backup copies the database to the disk and then does a check. If it is corrupt, it renames the backup file to have "CORRUPT" in its name. That file shouldn't be counted when the backup is working out if any files can be removed. But, I did make changes in that area recently and I didn't explicitly test that if there was a corrupt database it worked correctly. I'll have a look.
davidfor is offline