View Single Post
Old 03-07-2008, 03:10 PM   #17
tompe
Grand Sorcerer
tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.tompe ought to be getting tired of karma fortunes by now.
 
Posts: 7,452
Karma: 7185064
Join Date: Oct 2007
Location: Linköpng, Sweden
Device: Kindle Voyage, Nexus 5, Kindle PW
Quote:
Originally Posted by delphidb96 View Post
How?

And riddle me this. The \eBooks folder was *EMPTY* - I had problems with the Gen3 remembering my font choices. Then I moved the mobipocket.param file BACK. Suddenly, the Cybook remembers my choices. Note that the Cybook did NOT re-create the mobipocket.param file on its own...

And this is a brand-spanking-new (well, okay, a month old) Cybook! I've done nothing to it but add in a few ebooks and delete a few ebooks. No dropping it on the floor, no sitting on it by mistake, no dunking it in water - nothing at all that could be considered harmful. So when, where, why and how would this 'file system corruption' occur?
Excuse me for coming with good suggestions.

If you know something about debugging programs you know that you have to test things. You can theorize how much you want but often you miss something and you are lead in the wrong direction.

I have confirmed that with a working Cybook it recreates the file. Your file was not recreated so there is a problem and the symptom is that the file was not recreated.

And it is easy to have a theory for your observations (it might be wrong). The cybook tries to create the file. It fails and remounts the file system read only. When you moved the file back maybe you copied it to another place on the file system that worked.

I have once ot twice forgotten to unmount before removing the cable. I assume that can happen for other people also so there is not hard to explain how a file corruption can occur.

Trivial googling give you from Wikipedia:
Quote:
The Microsoft equivalent programs are scandisk and chkdsk. In DOS, chkdsk was used to check file system integrity, but later versions also featured a tool called scandisk for checking disk surface for bad sectors. Windows 95, Windows 98 and Windows Me featured a version of scandisk which ran natively in the Windows environment. The Windows NT series, including NT 4, Windows 2000, Windows XP, and Windows Vista all use a modern, updated version of chkdsk which performs both disk surface and file system scanning, though its disk-surface check is less thorough than scandisk's.
tompe is offline   Reply With Quote