Windows Mobile 6.5 File Sync Folder Structures

This article examines the file synchronization architectures used in Windows Mobile 6.5 to enable seamless offline file access. It details the directory mapping between host PCs and mobile devices, the role of primary and secondary storage hierarchies, and the synchronization mechanisms managed by ActiveSync and Windows Mobile Device Center (WMDC).

The Primary Synchronization Mapping: \My Documents

Windows Mobile 6.5 relied on a paired-folder model to maintain local copies of files for offline access. The core of this system was the device’s root \My Documents directory, which mirrored a dedicated folder on the host computer.

  • Host PC Path (Windows Vista / 7 via WMDC): C:\Users\<Username>\Documents\<DeviceName> My Documents
  • Host PC Path (Windows XP via ActiveSync): C:\Documents and Settings\<Username>\My Documents\<DeviceName> My Documents
  • Device Target Path: \My Documents

When synchronized, files placed into the desktop folder were duplicated directly to the mobile device's internal flash storage. Because the files physically resided within the device's local memory, users could view, edit, and create Office Mobile documents without an active cellular, Wi-Fi, or tethered connection. Changes made offline were tracked via a file state database and synchronized back to the host PC upon the next connection.

Subfolder Structures and Depth

ActiveSync and WMDC supported nested directories beneath the root sync folder:

  • Structure: \My Documents\<ProjectName>\<FileName>
  • Behavior: Subfolders created on the PC were replicated exactly within \My Documents on the device. Windows Mobile 6.5 maintained directory parity, allowing structured file categorization (e.g., \My Documents\Personal or \My Documents\Work) to carry over offline.

Files saved outside of \My Documents on the device root (such as directly in \Windows or \Program Files) were ignored by the standard automated file synchronization service.

Removable Storage Hierarchy: \Storage Card

Because internal memory on Windows Mobile 6.5 devices was often limited, file synchronization could be redirected or expanded to external memory (typically microSD cards).

  • Target Path: \Storage Card\My Documents
  • Implementation: Within ActiveSync or WMDC partnership settings, users could designate the storage card as the default file sync target. This preserved internal non-volatile memory for application installations while keeping large documents, media files, and spreadsheets accessible offline.

Application Caching and Email Attachments

For enterprise data accessed via Exchange ActiveSync (EAS) or SharePoint Workspace Mobile, dedicated application-specific structures handled offline availability:

  • Email Attachments: Downloaded attachments were decoupled from the message payload and stored locally in protected system directories, typically within \Application Data\Volatile or the mail client's local store, permitting offline review through Pocket Office applications.
  • SharePoint Workspace Mobile: Offline document libraries created cached copies within \Application Data\Microsoft\Office Mobile\, maintaining checkout states and metadata locally until an active connection permitted synchronization back to the SharePoint server.

Synchronization State Engine

Offline functionality succeeded because the system used true bidirectional replication rather than network file streaming. The Windows Mobile 6.5 replication engine maintained an internal change log. When a device was offline:

  1. Files were manipulated directly on the local FAT or proprietary flash file system.
  2. The operating system marked modified files with an updated timestamp and archive flag.
  3. Upon reconnecting via USB, Bluetooth, or over-the-air sync, the synchronization partnership compared hashes and timestamps to resolve conflicts, applying changes to the desktop or server copy automatically.