Thread: Kobo Patcher
View Single Post
Old 05-03-2014, 07:55 PM   #697
Nick_1964
Bookworm
Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.Nick_1964 ought to be getting tired of karma fortunes by now.
 
Nick_1964's Avatar
 
Posts: 975
Karma: 768585
Join Date: Aug 2010
Location: Netherlands
Device: Sony prs-650, Kobo Glo HD (2x), Kobo Glo
Quote:
Originally Posted by PeterT View Post
Calibre does NOT care about the f/w release level; rather it goes by the database version # from the database itself.

99% of the time there are no changes in the database itself, and configuring the driver in calibre to "attempt to support newer f/w levels" is all that is required.
Tried the patch yourself ?
Because then you must have noticed that after some reboots of the reader after the patch, when you attach it to usb again, windows doesn't even recognised the Aura HD anymore, say that a new device is detected, tries to install new drivers for the kobo 99.10 like when you use a new usb stick that never attached to the system,then Calible doesn't recognise the patched reader and say that it has no driver for the "kobo 99.10" and can't recognise the database.. Alternative 2 and 3 does similar things and tried to sync 3 times but that didn't work also anymore.. , tried it several times but Calibre keeps saying that it doesn't know the type of Kobo attached and therefore can't support it, the database can be the same,but Calibre doesn't even bother try to read it.
Tried configuring the driver the way you say.. but nope...
Just thinking as a noob it almost look like the new firmware is injected in the place that the reader uses to identify itself,like it is not changing the firmware version,but the model version,possible during reboot and implementing the changes you made.
Nick_1964 is offline   Reply With Quote