MobileRead Forums - View Single Post - Font, ScreenSaver & USBNetwork Hacks for Kindle 2.x, 3.x & 4.x

NiLuJe · 06-16-2015, 07:36 PM

Well, at least the reason why legacy packages fail to show up on FW 3.4.1 isn't mystical anymore:

The legacy Python packager used the max value of a *signed* 32bit integer, instead of the *unsigned* value of such an integer (i.e., 2147483647 vs 4294967295) as the target OTA version, and since the OTA version of FW 3.4.1 (2540470001) passed that halfway mark, anything packaged with the legacy packager fails the version check.

(KindleTool does things right, FWIW, which is why I linked to the repacking post

).

----

Spending so much time staring at the data types used in OTA headers paid off once again ;p.

06-16-2015, 07:36 PM	#3536
NiLuJe BLAM! Posts: 13,478 Karma: 26012494 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	Well, at least the reason why legacy packages fail to show up on FW 3.4.1 isn't mystical anymore: The legacy Python packager used the max value of a signed 32bit integer, instead of the unsigned value of such an integer (i.e., 2147483647 vs 4294967295) as the target OTA version, and since the OTA version of FW 3.4.1 (2540470001) passed that halfway mark, anything packaged with the legacy packager fails the version check. (KindleTool does things right, FWIW, which is why I linked to the repacking post ). ---- Spending so much time staring at the data types used in OTA headers paid off once again ;p. Last edited by NiLuJe; 06-16-2015 at 07:47 PM.