View Single Post
Old 09-25-2013, 03:48 PM   #52
parkher
Evangelist
parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.parkher ought to be getting tired of karma fortunes by now.
 
Posts: 467
Karma: 369018
Join Date: Nov 2010
Device: BL Alita/Mimas/Ares, OB Note2/Note, KA One/H2O/HD, S PRS T2/T1, PB 902
This is very strange.
So what you could do next: to save cr3hist.bkm, cr3.ini and cache on your PC and then deliberately cause that problem and try to replace back one-by-one. But probably will not help either.

Backup the whole installation. The whole KoboLauncher directory?
And then replace back bit-by-bit. Or just compare what changed. Nothing likely changed outside the cr3 directory...

Interesting - when you install cr3 - is there an initial cr3.ini generated or is it created only when you run CR? I assume - only when you run CR. Therefore it is a mystery what happened.
I don't think changes are made directly in cr3 elf itself. But it can be checked. Because we are running out of options.

Maybe access rights of some crucial file were somehow modified?
I mean - file permissions.

Last edited by parkher; 09-25-2013 at 04:06 PM.
parkher is offline   Reply With Quote