View Single Post
Old 10-07-2007, 10:16 PM   #3
porkupan
Fanatic
porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.porkupan ought to be getting tired of karma fortunes by now.
 
porkupan's Avatar
 
Posts: 556
Karma: 1057213
Join Date: Sep 2006
Location: North Eastern U.S.
Device: Sony Reader
Don't think so. Well, at least not totally right. This same file would read fine after you recovered and re-loaded the file. So, the premise is correct - this seems to happen with more complex files, but the file itself is not always the issue. I am afraid we get some data corruption, perhaps in the process of repaginating (indexing) the file, which is done by eBookLib. I wonder if when the "Eject button" is pressed, the eBookLib kills the repaginating thread while it's in the middle of doing its job.
porkupan is offline   Reply With Quote