<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.smartphonemag.com/cms" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Smartphone &amp;amp;amp; Pocket PC magazine - Comments for &quot;How do I defragment my Pocket PC memory cards? Do I need this at all?&quot;</title>
 <link>http://www.smartphonemag.com/cms/blog/9/how-do-i-defragment-my-pocket-pc-memory-cards-do-i-need-all</link>
 <description>Comments for &quot;How do I defragment my Pocket PC memory cards? Do I need this at all?&quot;</description>
 <language>en-US</language>
<item>
 <title></title>
 <link>http://www.smartphonemag.com/cms/blog/9/how-do-i-defragment-my-pocket-pc-memory-cards-do-i-need-all#comment-2258</link>
 <description>&lt;p&gt;Please note that Pocket Mechanic &lt;strong&gt;Professional&lt;/strong&gt; is a brand new (unavailable/not-yet-announced) at the time of writing of the article), completely rewritten product. In the article, I referred to Pocket Mechanic, not to Pocket Mechanic &lt;em&gt;Professional&lt;/em&gt;. I, along with several other users, did have problems with Pocket Mechanic&#039;s unability to fix errors that the desktop-based, plain &lt;strong&gt;chkdsk&lt;/strong&gt; would have easily fixed.&lt;/p&gt;
&lt;p&gt;I haven&#039;t tested Pocket Mechanic Professional in this respect as yet. Will try to do it soon and will also post the results.&lt;/p&gt;
</description>
 <pubDate> <key>pubDate</key>
 <value>Mon, 10 Jul 2006 03:43:28 -0500</value>
</pubDate>
 <dc:creator> <key>dc:creator</key>
 <value>Werner Ruotsalainen</value>
</dc:creator>
 <guid> <key>guid</key>
 <attributes> <isPermaLink>false</isPermaLink>
</attributes>
 <value>comment 2258 at http://www.smartphonemag.com/cms</value>
</guid>
</item>
<item>
 <title></title>
 <link>http://www.smartphonemag.com/cms/blog/9/how-do-i-defragment-my-pocket-pc-memory-cards-do-i-need-all#comment-2256</link>
 <description>&lt;p&gt;Are you sure the write protection latch isn&#039;t in the &quot;protected&quot; position?&lt;/p&gt;
</description>
 <pubDate> <key>pubDate</key>
 <value>Wed, 10 May 2006 06:59:55 -0500</value>
</pubDate>
 <dc:creator> <key>dc:creator</key>
 <value>Werner Ruotsalainen</value>
</dc:creator>
 <guid> <key>guid</key>
 <attributes> <isPermaLink>false</isPermaLink>
</attributes>
 <value>comment 2256 at http://www.smartphonemag.com/cms</value>
</guid>
</item>
<item>
 <title></title>
 <link>http://www.smartphonemag.com/cms/blog/9/how-do-i-defragment-my-pocket-pc-memory-cards-do-i-need-all#comment-2254</link>
 <description>&lt;p&gt;As promised, I&#039;ve continued researching this subject; File Store uses FAT and, under certain circumstances, can be formatted. I&#039;ll publish a tutorial on all this really soon.&lt;/p&gt;
</description>
 <pubDate> <key>pubDate</key>
 <value>Sat, 11 Feb 2006 04:50:03 -0600</value>
</pubDate>
 <dc:creator> <key>dc:creator</key>
 <value>Werner Ruotsalainen</value>
</dc:creator>
 <guid> <key>guid</key>
 <attributes> <isPermaLink>false</isPermaLink>
</attributes>
 <value>comment 2254 at http://www.smartphonemag.com/cms</value>
</guid>
</item>
<item>
 <title></title>
 <link>http://www.smartphonemag.com/cms/blog/9/how-do-i-defragment-my-pocket-pc-memory-cards-do-i-need-all#comment-2253</link>
 <description>&lt;p&gt;I&#039;m absolutely sure there&#039;s wear levelling in all built-in ROM&#039;s. If there wasn&#039;t, then, even the smallest bit error would cause tremendous problems and would render all ROM&#039;s practically useless.&lt;/p&gt;
&lt;p&gt;In most cases levelling works on the bit level. I don&#039;t think the file system controller sees these problems and allocates the blocks used to avoid them â€“ with most flash memories, the outer world only sees a homogenous address range, of which every single bit is usable. At the flash controller level, there&#039;s some kind of mapping out of bad bits (that is, 4-8 bytes in general), of course. &lt;/p&gt;
&lt;p&gt;As the operating system, however, doesn&#039;t see anything of them, it won&#039;t repartition a file while it&#039;s written to the file store and, therefore, no performance degradation will occur (because it won&#039;t need to update the file allocation table to leave out dead bits).&lt;/p&gt;
&lt;p&gt;As far as formatting the built-in, user-writable flash ROM is concerned, there&#039;re two cases: pre-WM5 and WM5 devices.&lt;/p&gt;
&lt;ol&gt;&lt;li&gt;	pre-WM5 devices need special key combinations at boot time to format (initialize) their File Store; it&#039;s not formatted during &quot;standard&quot; hard resets. A lot of these devices allow for these.&lt;/li&gt;
&lt;li&gt;	WM5 devices, on the other hand, automatically &quot;format&quot; their entire ROM (they don&#039;t have anything like File Store, except for Pocket PC Phone Edition devices with their unlockable and, therefore, for the user available Extended ROM). When you hard reset a WM5 device, the operating system initializes the storage. The ROM in the HTC Wizard even calls this &quot;Format FAT partition&quot; (of course, this doesn&#039;t mean it must be using the traditional FAT file system.)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;As far as the file system format of the ROM is concerned, to my knowledge, it&#039;s not FAT. I may be wrong though â€“ I will check out the related docs some time.&lt;/p&gt;
</description>
 <pubDate> <key>pubDate</key>
 <value>Wed, 08 Feb 2006 11:30:33 -0600</value>
</pubDate>
 <dc:creator> <key>dc:creator</key>
 <value>Werner Ruotsalainen</value>
</dc:creator>
 <guid> <key>guid</key>
 <attributes> <isPermaLink>false</isPermaLink>
</attributes>
 <value>comment 2253 at http://www.smartphonemag.com/cms</value>
</guid>
</item>
</channel>
</rss>


