Quote:
Originally Posted by knc1
start with the simplest assumption - only one of the books and/or collections causes the problem . . . .
then do a binary search for the problem -
put 1/2 the books and/or collections back on -
if problem reoccurs, then problem is in that half -
if problem does not reoccur, then the problem is in that half you did not put on -
eleminate the 1/2 which does not cause the problem -
repeat with the half that does cause the problem by choosing only half of it.
repeat ^^^
For 256 books - will take at most 8 tries to find it.
If more than one book and/or collection causes the problem - then when doing the above, be prepared to find more than one "1/2" sample to cause the problem - adapt your search testing in that case.
|
Using binary search I have found the file that was bugging Librerator!
It's name is:
Wisdom from Psychopaths-asin_TWUKDKFYQKO6PVBAVH2EWS5KFB7YI7PG-type_PDOC-v_0.
azw%22;
So, it appears that it was the
bugged extension of the file that caused Librerator to report the "invalid capture index" message. The default Kindle's software simply doesn't see the bugged file, while Librerator can't see the whole directory containing this bugged file.
I have no idea how that extension came to be. When I change the extension to azw the file reappears in Kindle's software and the directory becomes accessible in Librerator. Don't remeber how I created the file unfortunately, it contains only the first page of
this article.
thank you all for assistance
