Windows Mobile 6.5 Native Search Capabilities
The native Search utility in Windows Mobile 6.5 provided users with a centralized tool to locate files, personal information, and system data stored directly on their device and removable storage. This article outlines the specific capabilities of this built-in feature, detailing the types of data it indexed, its filtering options, and how it handled system-wide and localized queries.
Cross-System Data Querying
The primary function of the native Search tool was to query the Personal Information Manager (PIM) databases alongside the file system. Rather than requiring users to open individual applications, the utility allowed a single keyword query to simultaneously retrieve matching records from:
- Contacts: First names, last names, company names, and contact details.
- Calendar: Appointment titles, locations, and descriptions.
- Messaging: Subject lines and message bodies across SMS, MMS, and configured Outlook/Exchange email accounts.
- Tasks: Pending and completed task titles and associated notes.
- Notes: Standalone text and handwritten memo files.
Category Filtering
To prevent cluttered search results, the utility featured a drop-down menu that allowed users to constrain searches to specific areas. By default, the search was set to scan "All Data," but users could selectively target:
- Calendar
- Contacts
- Help (indexing native offline help documentation)
- Messages
- Notes
- Tasks
- Larger than 64 KB (a preset filter designed to find storage-consuming files)
File and Storage Search
Beyond database records, the Search utility functioned as a file
locator. When set to search files or "All Data," it scanned both the
device’s internal flash storage and external microSD cards. It matched
queries against file names and extensions, allowing users to find
documents (such as Word Mobile .doc or Excel Mobile
.xls files), audio files, and system utilities without
manually browsing the File Explorer tree.
Keyword Matching Logic
The search engine relied on text-string matching. It supported partial matching, meaning entering a partial string would yield results containing that sequence of characters. Results were hyperlinked, allowing users to tap on a result to directly open the item in its native application (e.g., opening an email in Outlook Mobile or a task in the Tasks app).