File System Migration
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/28/2008
This topic contains information about migrating the functionality from earlier versions of Windows Embedded CE.
**For general migration information, see Migrating from an Earlier Version of Windows Embedded CE.
Migrating from Windows CE 5.0
Windows CE 5.0 added the file system replication filter to fix ActiveSync problems, and this filter is present in Windows Embedded CE 6.0 and later. Now, you must include the file system replication filter in your OS design to ensure that ActiveSync works correctly when you mount a file system as the root directory.
The FILECHANGEINFO/MyFSD_RegisterFileSystemFunction support is no longer in CE 6.0 and later releases. Support for call-back file notifications is obsolete.
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:- 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, Storage Manager enumerates partitions and loads file systems. For more information, see Storage Management. - 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.
With either method, the actual file system is loaded multiple times with Storage Manager, and you need to call FSDMGR_RegisterVolume only once per instance of an FSD.
- 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.
- Database incompatibility:
Changes made to the database engine in Windows CE .NET 4.2 and in later versions prevent it from reading database volume files that are 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 Embedded CE. - M-Systems TrueFFS:
Effective with Windows CE .NET 4.2, M-Systems TrueFFS is no longer supported in Windows Embedded CE.
Migrating from Windows CE 2.12
In Windows CE 5.0, if a database is open when CeSetDatabaseInfoEx (CEDB) 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 4.2. 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 they are used by an unprivileged application.
Migrating from Windows CE 2.0
The BOOL and floating-point record properties are available only in Windows CE 2.0 and later.