Thread: Kobo Patcher
View Single Post
Old 05-03-2014, 11:40 PM   #699
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: 47303826
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
The calibre driver checks two things: the dbversion number and the firmware version number. If either number is to high, the driver will display the error. Setting the option to "Attempt to support newer firmware" will work as long as you are patching reasonably recent firmware.

The problem is changes in function with the versions. If something has change since the firmware version you have patched, then things might break. The two things I can think of immediately are cover images and series info. The cover image handling changed with 2.9.0, so patching an earlier firmware to a later version number will break that. It won't stop things from working, it will just mean the cover images won't be removed or will be sent to the wrong place. The series info is more serious as that affects the SQL run at various places. They would fail and prevent the driver working properly. That change was somewhere about 2.3.1, so hopefully no one is trying to patch that.

As PeterT suggests, patching the firmware check URL instead of the version number is probably safer.
davidfor is offline   Reply With Quote