Xml Provisioning Vs. Regmerge And Copy File - Motorola MC3000R - Win CE 5.0 Core 312 MHz Integration Manual

XML Provisioning vs. RegMerge and Copy File

Prior to Windows Mobile 6.1, Motorola used two drivers (RegMerge and CopyFiles) to update the registry and to
copy files during a cold boot. With Mobile 6.1, Motorola recommends using XML provisioning instead. RegMerge
and CopyFiles are supported for backward compatibility but Motorola may eliminate support in the future. The
following sections provide examples of how RegMerge and CopyFiles were used, and how to perform the same
function using XML provisioning.
RegMerge
RegMerge.dll is a built-in driver that allows updating the registry during a clean boot. RegMerge runs very early in
the boot process and looks for registry files (.reg files) in certain Flash File System folders (i.e., \Application) during
a clean boot. It then merges the registry changes into the system registry located in RAM.
The following example uses RegMerge to set a registry key:
SampleReg.reg
[HKEY_LOCAL_MACHINE\Hardware\DeviceMap\Backlight]
"BacklightIntensity"=dword:00000036
The following example uses XML provisioning to perform the same task:
SampleReg.xml
<wap-provisioningdoc>
<characteristic type= "Registry">
<characteristic type= "HKLM\Hardware\DeviceMap\Backlight">
<parm name= "BacklightIntensity" value= "54" datatype= "integer" />
</characteristic>
</characteristic>
</wap-provisioningdoc>
CopyFiles
CopyFiles copies files from one folder to another on a clean boot. During a clean boot CopyFiles looks for files with
a .CPY extension in the root of the Application FFS partition. These files are text files containing the source and
destination for the desired files to copy, separated by ">".
The following example uses CopyFiles to copy a file from the \Application folder to the \Windows folder:
SampleCpy.cpy
\Application\example.txt > \Windows\example.txt
The following example uses XML provisioning to perform the same task:
Application Deployment for Mobile 6.1 5 - 7