A strange problem about WriteRegistryToOEM and ReadRegistryFromOEM

hi, all
I am using wince5.0. I get a BSP which have implemented
Read/WriteRegistryToOEM functions, both verify data with a checksum
computed. I use the two functions to complete Data Persistence with the
RAM-based Registry . I restart OS after calling RegFlushKey(), and find
some registry data is lose.
I have debugged all data writed by WriteRegistryToOEM() to flash and
read ReadRegistryToOEM() from flash, but there is no different between data
writed and data read.
thank in advance.

Michel
Sun Jun 10 20:07:55 CDT 2007

It is impossible to save *all* crypt security data using this method of
registry persistence (for instance network passwords). Search this group
for "MasterKeysInRegistry" and "EnableLMHash" to find more info on what
you can and cannot persist.

Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com

Mslrl wrote:
> hi, all
> I am using wince5.0. I get a BSP which have implemented
> Read/WriteRegistryToOEM functions, both verify data with a checksum
> computed. I use the two functions to complete Data Persistence with the
> RAM-based Registry . I restart OS after calling RegFlushKey(), and find
> some registry data is lose.
> I have debugged all data writed by WriteRegistryToOEM() to flash and
> read ReadRegistryToOEM() from flash, but there is no different between data
> writed and data read.
> thank in advance.
>
>

--

Mslrl
Mon Jun 11 04:18:03 CDT 2007

Hi, Michel
Thank you for your reply.
After analyzing the problem of OS which have store Data Persistence
with the RAM-based Registry by WriteRegistryToOEM,
I find a stange problem. My platform.reg have following registry
setting,

[HKEY_LOCAL_MACHINE\Drivers\Builtin\Pio]
"Prefix"="PIO"
"Dll"="gpio.dll"
"Order"=dword:0
"Index"=dword:1
"pinfunction"=dword:0
"tristate"=dword:FFFF

[HKEY_LOCAL_MACHINE\Drivers\Builtin\SMBus]
"Prefix"="SMB"
"Dll"="psc_smbus.dll"
"Order"=dword:0
"Index"=dword:1

The initial load sequence of the both drivers, is Pio, then SMBus, but
after storing registry data by WriteRegistryToOEM, the load sequence is
changed as SMBus, then Pio. Why have the change?

thank you!

"Michel Verhagen (eMVP)" <mverhagen@nospam.embeddedfusion.com>
??????:%23dTE0T8qHHA.4180@TK2MSFTNGP04.phx.gbl...
> It is impossible to save *all* crypt security data using this method of
> registry persistence (for instance network passwords). Search this group
> for "MasterKeysInRegistry" and "EnableLMHash" to find more info on what
> you can and cannot persist.
>
> Michel Verhagen, eMVP
> EmbeddedFusion
> www.EmbeddedFusion.com
> mverhagen at embeddedfusion dot com
>
> Mslrl wrote:
>> hi, all
>> I am using wince5.0. I get a BSP which have implemented
>> Read/WriteRegistryToOEM functions, both verify data with a checksum
>> computed. I use the two functions to complete Data Persistence with the
>> RAM-based Registry . I restart OS after calling RegFlushKey(), and find
>> some registry data is lose.
>> I have debugged all data writed by WriteRegistryToOEM() to flash and
>> read ReadRegistryToOEM() from flash, but there is no different between
>> data writed and data read.
>> thank in advance.
>
> --

Bruce
Mon Jun 11 07:58:21 CDT 2007

The order that registry keys are read is not guaranteed. It is up to you to
set the Order value so that the drivers load in the order that you need them
to load. In this case you are depending on the order that the registry is
read, rather than the Order value.

The order that the registry is saved tends to reverse each time it is saved.

--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Mslrl" <mailyou_mailyou@hotmail.com> wrote in message
news:ObZzrlArHHA.4764@TK2MSFTNGP06.phx.gbl...
> Hi, Michel
> Thank you for your reply.
> After analyzing the problem of OS which have store Data Persistence
> with the RAM-based Registry by WriteRegistryToOEM,
> I find a stange problem. My platform.reg have following registry
> setting,
>
> [HKEY_LOCAL_MACHINE\Drivers\Builtin\Pio]
> "Prefix"="PIO"
> "Dll"="gpio.dll"
> "Order"=dword:0
> "Index"=dword:1
> "pinfunction"=dword:0
> "tristate"=dword:FFFF
>
> [HKEY_LOCAL_MACHINE\Drivers\Builtin\SMBus]
> "Prefix"="SMB"
> "Dll"="psc_smbus.dll"
> "Order"=dword:0
> "Index"=dword:1
>
> The initial load sequence of the both drivers, is Pio, then SMBus, but
> after storing registry data by WriteRegistryToOEM, the load sequence is
> changed as SMBus, then Pio. Why have the change?
>
> thank you!
>
> "Michel Verhagen (eMVP)" <mverhagen@nospam.embeddedfusion.com>
> ??????:%23dTE0T8qHHA.4180@TK2MSFTNGP04.phx.gbl...
>> It is impossible to save *all* crypt security data using this method of
>> registry persistence (for instance network passwords). Search this group
>> for "MasterKeysInRegistry" and "EnableLMHash" to find more info on what
>> you can and cannot persist.
>>
>> Michel Verhagen, eMVP
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> mverhagen at embeddedfusion dot com
>>
>> Mslrl wrote:
>>> hi, all
>>> I am using wince5.0. I get a BSP which have implemented
>>> Read/WriteRegistryToOEM functions, both verify data with a checksum
>>> computed. I use the two functions to complete Data Persistence with the
>>> RA