View Single Post
Old 09-02-2016, 09:26 AM   #22
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
Just remembered something.

Kobo changed an option in the database. The have changed from journal mode to "WAL". This should mean better performance and I less likelihood of corruption. But, the Windows version of the Python SQLite library that the KoboTouch driver used did not support this journal mode. I needed to change the driver to use a different Python SQLite library that does support this journal mode. This was released in calibre 2.63.0.

What this means is that you cannot use a version of calibre before 2.63.0 on Windows with this firmware. You will also need the latest versions of the Kobo Utilities plugin and KoboTouchExtended driver if you use them.
davidfor is offline   Reply With Quote