Windows Mobile 6.5 File System Structure

This article examines the internal file system architecture used by devices running Windows Mobile 6.5. Built on the Windows CE 5.2 kernel, the operating system utilized a single-root unified file structure combined with a persistent storage model. Below is an overview of how the operating system organized directories, handled partitions, and managed file formats across internal memory and removable storage.

The Single-Root Hierarchy

Unlike desktop versions of Windows, Windows Mobile 6.5 did not assign drive letters (such as C: or D:) to distinct drives or partitions. Instead, it used a single-root hierarchical tree originating from a backslash (\). All physical and virtual storage elements—including internal ROM, internal flash memory, and removable storage media—were mounted as subdirectories within this primary root.

Persistent Storage Architecture

Windows Mobile 6.5 relied on the persistent storage architecture originally introduced in Windows Mobile 5.0. Earlier versions of Pocket PC and Windows Mobile used volatile RAM to store user files and the registry, meaning a dead battery resulted in total data loss.

In Windows Mobile 6.5, RAM was dedicated solely to execution memory (program memory), while the file system resided entirely in non-volatile flash memory (storage memory). The operating system partitioned this persistent storage into three primary layers:

  • ROM (Read-Only Memory): Contained the operating system core, standard drivers, and bundled pre-installed applications.
  • Flash Storage (User Store): Handled third-party installed software, system configuration changes, and personal documents.
  • RAM: Provided working memory for active processes and temporary paging.

Underlying File System Formats

Windows Mobile 6.5 utilized several specific file systems depending on the media type and purpose:

  • IMGFS (Image File System): Used primarily for the operating system partition. IMGFS supported block-level data compression and allowed files to be updated or patched individually without having to re-flash the entire ROM image.
  • TFAT (Transaction-Safe FAT): An extension of the standard FAT16 and FAT32 file systems. TFAT was frequently deployed on internal persistent flash memory to prevent data corruption by creating duplicate transaction records before committing file system modifications, ensuring safety during sudden power loss or battery removal.
  • FAT16/FAT32: The standard formats used for removable storage, such as SD and microSD cards.

Core Directory Layout

A standard installation of Windows Mobile 6.5 featured the following standard root directories:

  • \Windows: The core directory housing system binaries, Dynamic Link Libraries (.dll), device drivers, system sounds, and start-up programs. It also contained the \Windows\Start Menu folder, which populated the grid-based Start Menu interface introduced in version 6.5.
  • \Program Files: The default target directory for third-party application installations. Each installed program generally created its own subdirectory containing executables, auxiliary assets, and localized data.
  • \My Documents: The designated storage location for user content, such as photos, ringtones, office documents, and audio recordings. System utilities like camera apps and voice recorders automatically routed files here.
  • \Application Data: Contained application-specific runtime data, configuration caches, browser histories, and connection profiles.
  • \Storage Card: The mount point for secondary media, typically an external microSD card. If multiple storage expansion devices were connected, they were sequentially designated as \Storage Card2, \Storage Card3, and so forth.