|
Thank you for the interest.
I don't have TOO many books on the reader.. a couple of essentials on the reader itself, about 200 small works of fiction on an SD card, and about two dozen reference books (the largest is about 20mb) on a 256 meg memstick produo. So over-filling is not likely. Also, while it can and does crash from time to time, this last time I lost some tags there were no intermediate steps between loading the books onto the reader, (properly) unplugging the device, and trying to open the books on the reader. They simply weren't there! Until I did an alphabetical search.
Umm, I followed the advice from the bug report, which was: delete everything on that memory card (so far it has only happened on a memcard, not an SD card or the device itself, but that is where I usually write and remove stuff from) and replace them. I did so, and it seemed to happen again (to just one of them. Let me just check this..
Ok yeah, I have been able to replicate it. The same file lost it's tags twice in a row. The first time I deleted the file from the card and the replaced it. I checked the tags before I unplugged the device and after the device finished reloading I browsed by tag but couldn't find it. Reconnecting the device showed it missing it's tags. As mentioned in the bug report, it may be from too many caps in the filename. Let me check THAT now...
Yeah, I removed anything that might be considered remotely "abnormal" from the file's title, and it is still doing it. I dunno.
So I have spent an hour or so trying to figure this out, but I am running out of "spare" time, so I will have to return to this problem tomorrow or something. It is pretty irritating, but I can deal.
Thanks for your help,
Andrew
|