<br><div><span class="gmail_quote">On 1/25/07, <b class="gmail_sendername">Kimmo Hämäläinen</b> <<a href="mailto:firstname.lastname@example.org">email@example.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;">
> Formatting and then initializing with swap corrupted the card. I<br>> dosfsck'd it under Linux and the report was a corrupted header. If I<br>> fix it and put it back in the N800 it is readable. The N800 is unable
<br>> to format it without corrupting it.<br><br>So the problem is only formatting it in N800, otherwise it's usable?</blockquote><div><br>It seems to be usable until it is accessed with the file manager. At that point all the data disappears and the card registers as 0 bytes available. That's due to it being corrupted. My trick was to format the card in windows, put it in the 800, load the document viewer, and save one of the user guides to the card multiple times. Loading them back was no issue. After then running the file manager, the problems started and the card was corrupted. I will have to investigate further via shell but that's my suspicion right now.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Has anyone else experienced this issue? Could we have a h/w rev or<br>> faulty batch of card readers here?
<br><br>I think we have not tested bigger than 2GB cards in the N800. The<br>formatting needed some tuning for 2GB cards, so it's possible that the<br>kernel has problems with bigger cards as well.</blockquote><div><br>
Thanks, this was what I wanted to hear. I had seen a thread on a forum about possible bad card readers and though this might actually be a real-world hardware-related problem. (almost) Anything can be fixed in software ;-)