DO NOT use the Cache Disk as a method to improve application performance. Analyze applications that perform
slower in persistent storage to optimize disk access. Common areas for optimization include minimizing the
number of reads and writes to a file, removing unneeded debug logging, and minimizing file flushing or closing
Windows Mobile 6 protects all data and applications from power-related loss. Because Windows Mobile 6 mounts
the entire file system and registry in persistent storage (rather than using RAM), MC65 devices provide a reliable
storage platform even in the absence of battery power.
Persistent storage provides application developers with a reliable storage system available through the standard
file system and registry APIs. Persistent storage is optimized for large reads and writes; therefore, applications
reading and writing data in large chunks tend to outperform those applications reading and writing small blocks of
data. Data in persistent storage is lost upon a clean boot.
Persistent storage contains all the directories under the root directory except for Application, Cache Disk, and
Storage Card (if a storage card is installed). Persistent storage is approximately 60 MB (formatted).
The Application folder is a super-persistent storage that is persistent even after a clean boot. Accessing data in the
Application folder is slower than accessing persistent storage. The Application folder is used for deployment and
device-unique data. For example, network profiles can be stored in the Application folder so that connection to the
network is available after a cold boot. The Application folder is approximately 20 MB (formatted).
Enterprise Mobility Developer Kits
The Motorola Enterprise Mobility Developer Kit (EMDK) family of products allows you to write applications that take
advantage of the capture, move and manage capabilities of the MC65. Go to the Support Central
(http://www.motorola.com/enterprisemobility/support) to download the appropriate developer kit.
4 - 9