File Systems and Data Store Migration (Windows CE 5.0)
This topic contains information about migrating this functionality from earlier versions of Microsoft® Windows® CE.
For general migration information, see Migrating from an Earlier Version of Windows CE.
Migrating from Windows CE 3.0
File system loading
FSD Manager calls the MyFSD_MountDisk function that is exported by MyFSD.dll. You can load a file system driver (FSD) in the following ways:
The Storage Manager loads all partition drivers whose block driver registry keys contain the IClass registry subkey. For an example of the IClass registry subkey, see the ATADISK and ATAPI registry keys.
Using the specified partition driver, the Storage Manager enumerates partitions and loads file systems. For more information, see Storage Manager.
If an FSD is listed under the HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad registry key, it is loaded automatically. These files do not require a block driver under them.
With either method, the actual file system is loaded multiple times with the help of the Storage Manager, and you can only call FSDMGR_RegisterVolume once per instance of an FSD.
Database incompatibility
Changes made to the database engine in Windows CE .NET and later prevent it from reading database volume files created in either Windows CE 2.12 or Windows CE 3.0.
Persistent Storage Manager
Effective with Windows CE .NET 4.2, the Intel Persistent Storage Manager (SYSGEN_IPSM) is no longer supported in Windows CE.
M-Systems TrueFFS
Effective with Windows CE .NET 4.2, M-Systems TrueFFS is no longer supported in Windows CE.
Migrating from Windows CE 2.12
- In Windows CE 2.12, you could change the sort orders of an open database. In Windows CE 5.0, if a database is open when CeSetDatabaseInfoEx is called and a request is issued to change the sort orders, the function fails.
- The database sort flag CEDB_SORT_UNIQUE now implies the CEDB_SORT_NONNULL flag for each sort property. Therefore, it is not valid to write a record that is missing a sort property into a unique-constrained database, as it was in Windows CE .NET. This change was made to prevent conflict between incomplete records.
- When implementing a secure OS, several registry APIs that operated correctly in Windows CE 2.12 fail when used by an untrusted application. For more information, see Trusted APIs.
Migrating from Windows CE 2.0
- The BOOL and floating-point record properties are available only in Windows CE 2.10 and later.
See Also
Send Feedback on this topic to the authors