View Single Post
Old 08-06-2012, 08:47 PM   #15
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 camiller View Post
Incidentally, I get the exact same error with a Kobo Wireless (version prior to touch) that hasn't had a firmware update in ages. Deletes always worked fine before. I'll probably go the route of configuring the device to attempt to work with the "newest" firmware just to get back to where I was.
Looking back through the thread something hasn't been mentioned:

There have been no changes to the code of the Kobo device driver in calibre that affects the actual function since before February of this year.

The change being discussed here is a simply a warning. This was put in on the 7th of July and went into calibre version 0.8.60. It tests what database version is found on the Kobo device and compares it to the versions that the calibre driver understands. The driver is coded for up to database version 33. Unfortunately, no one has been keeping this up to date. But, luckily there had been no changes to the Kobo database that caused any problems.

I don't know exactly what firmware version DBVersion of 33 is from. From my Kobo Touch, I have copies of the database from various times. I have one from when I recently did a factory reset the device. It has DBVersion 29 for firmware 1.9.11. I also have DBVersion 36 which I came from either 1.9.14 or 1.9.16. The previous firmware I was using was 1.9.17 which DBVersion of 50.

I have had a good look at the different versions of the database and the driver code, and there are no changes in the structure anywhere the calibre uses. So, it is safe to continue using calibre with these firmwares. I don't have a Kobo Wireless, so I can't check it. But, from comments from other people here, it is still OK.

Now the firmware that triggered all this, V2.0.0 for the Kobo Touch, is also safe with the current driver. Again, the database structure has not changed in the areas that the driver touches. But, there have been some changes that the driver doesn't go near and would be great to support. It now needs someone with the time and inclination to update the driver for this. I've had a look at it and have some ideas. But, I would want to split the driver into two. That would be either a Touch and a non-touch, or a pre- and post- firmware 2.0.0 drivers. Both ways have advantages and disadvantages.
davidfor is offline   Reply With Quote