Persisting Data with the RAM-Based Registry (Windows Embedded CE 6.0)

1/6/2010

You can persist the registry data of your OS with the RAM-based registry when the RAM, which contains the object store, is not powered. With the RAM not powered, you have additional protection against the possibility of invalid data configurations. The preferred method for persisting registry data is to use the hive-based registry. For more information, see Data Persistence with the Hive-Based Registry.

Additional methods for persisting data with the RAM-based registry using the OEM adaptation layer (OAL) are also available. For more information, see Data Persistence with the RAM-based Registry Using the OAL.

Before you can persist the registry data of you OS, you must already have created, built, and downloaded a OS image to your device.

To persist data with the RAM-based registry

1. Copy the Oemregistry sample to your OS. For example, copy the %\SystemRoot%\Public\Common\Oak\Drivers\FSD\Oemfs folder to your platform.

   Filesys.dll attempts to load the Oemregistry.dll file when the registry is initialized. The Oemregistry.dll file must be stored in ROM and should not be stored on external media.

2. Modify the source code for the OEM registry sample to export the ReadRegData, WriteRegData and RegistryOperation functions.

3. To add persistent password support, modify the source code for the OEM registry sample to export the ReadGenericData, and WriteGenericData functions.

4. Initialize the RAM-based registry for your OS.

   For more information about performing this step, see File System Initialization of RAM-based Registry.

See Also

Concepts

Data Persistence with the RAM-based Registry Using the OAL
RAM-Based Registry
Data Persistence with the Hive-Based Registry