<br><br><div><span class="gmail_quote">On 8/29/07, <b class="gmail_sendername">David Hazel</b> <<a href="mailto:david.hazel@enchaine.com">david.hazel@enchaine.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><span class="q"><br><div><font color="#0000ff" face="Arial" size="2"></font> </div></span>
<div><span><font color="#0000ff" face="Arial" size="2">It's
possible that cards experiencing this problem are not completely corrupted
"beyond repair", but that they've simply had their FAT tables damaged to
the point where most software can't deal with them. FAT32 devices seem to have a
particular problem, in that if certain elements of the FAT table get corrupted,
they appear to be completely unusable. This kind of damage can be
repaired using the Disk Manager on Windows XP or 2000. If you use this to
reformat such a device, it will come back to life quite successfully (but be
prepared for a bit of a wait while the Disk Manager decides that the device is
not properly formatted and that it can't therefore show its current
format).</font></span></div></div></blockquote><div><br><br><span class="q"><div><div><br></div></div></span>I didn't mean to turn
this into a discussion of the bug, but from what I've read there are
some apparently very technically capable people who have tried to
low-level format cards after the failure using Windows and they refuse
to be fixed.
<br><br>Anyway it's just a caution, it hasn't happened to me personally. </div><br></div><br>