Quote:
Originally Posted by knc1
Although geekmaster seems to imply in his last post here that he thinks the device is not repairable; what he actually points out is not proof to the contrary, just interesting observations.
|
I did not say that, nor did I intend to "imply" what you are "inferring" about my comments. In fact, in a previous post I already mentioned that vfat supports bad-block mapping (if you do NOT select "quick" format) so the bad areas can be mapped out during a high-level format command. Running windows CHKDSK on the mounted USB drive can also map out bad sectors. There is no limit to how many bad blocks can be mapped out this way (unlike the 64MB device-driver spare blocks limit).
But even with bad block mapping, as I mentioned previously, there may be OTHER blocks that are near "end of life" that will not be mapped out and can reduce data retention and reliability. Just make sure you backup anything you want to keep to a reliable storage device and keep only COPIES on this mmc, and you should be fine.
Quote:
Originally Posted by knc1
In the datasheet we should be able to learn where (if) they put the erase-block(s) that serve as the bad block table, the details for unlocking it and updating it.
The erase-blocks used for the internal bad block table are usually on their own dedicated lock chain. And sometimes the read/erase/re-program commands are different.
|
As I mentioned previously, this information is all in the GPL source code, which is more accurate than any "datasheet". It is actually what the kindle USES to access the device.
Quote:
Originally Posted by knc1
At the moment, I have lost interest in this subject.
|
So this was a "disinterested" reply?
