Quote:
Originally Posted by dreams
Welcome (officially) to MobileRead and glad you were able to solve your problem.
Now we have one more problem area and solution to check if something happens to our reader.
|
Thanks for the welcome,
dreams and sorry for the delay in replying.
For those interested in going into this further, found out that the infinite-Loading-loop was caused when the Reader tried to rebuild the index after being disconnected from my PC -- the media.xml file. Entries which normally look like "/media/books/xyz.lrf" were coming out as "/tmp/tmp/tmp/tmp/tmp.." -- the number of "tmp"s growing the longer I led the "Loading" continue.
My ending's not as happy as I'd thought. My Reader seemed to be working perfectly till I started transferring more books -- only to discover that, as per it, the total internal memory is now only 37MB. Approximately 190MB has simply disappeared.
Therefore a warning to anyone who tries my "erase everything in the root directory" solution -- you'll lose a lot of your memory!
Strangely enough, 37 MB is roughly the amount of memory I had free when my Reader started going into the infinite-Loading-loop. All the previously used memory now off-limits, apparently.
I'm not complaining, honestly. It's better than having a bricked-up Reader. But thought that anyone who has this problem and tries this solution should be forewarned --
you will probably lose access to all the memory which had been in use!
I'm hoping that adding an SD card will give me more space -- will post here if that works!
Any of the resident geniuses have any idea how I could try to get back my lost memory, by the way??