View Single Post
Old 04-17-2016, 10:11 PM   #166
geekmaster
Carpe diem, c'est la vie.
geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.geekmaster ought to be getting tired of karma fortunes by now.
 
geekmaster's Avatar
 
Posts: 6,433
Karma: 10773670
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
Quote:
Originally Posted by NiLuJe View Post
@geekmaster: otaup might indeed require otav2 packages, but MRPI certainly doesn't, so that's intriguing. Could you take a look at its log, to see how it actually complained.
Code:
Package 'Update_autorun_k5g_0.1.GM_install.bin' (autorun k5g 0.1.GM I) is not an MR package, skipping . . . :(
That was the OTA (not OTA2) update package I mentioned previously. It works on my K1 if I selecdt k1 instead of k5g. Kindletool creates OTA packages just fine, it seems, but on win32 the OTA2 package creation attempts get that temp file error (moving a file onto itself?).

Are you sure MRPI still supports OTA packages?

Last edited by geekmaster; 04-17-2016 at 10:14 PM.
geekmaster is offline   Reply With Quote