Re: .CAB file issue !!
From: K. S. Huang (ks_huang_at_dlink.com.tw.remove.this)
Date: 04/02/04
- Next message: Paul G. Tobey [eMVP]: "Re: Problem migratting from 4.1 to 4.2"
- Previous message: Ten: "Re: APP Still running after Cmd window close"
- In reply to: RF: ".CAB file issue !!"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 2 Apr 2004 21:50:20 +0800
While the platform cold boot, the OS will check if pReadRegistryFromOEM
function pointer is null or not.
If it is not null, the os will invoke this function pointer to restore the
Registry data.
So to prevent the registry read back from Persistent Storage (like IPSM)
during bootup, you may set the pReadRegistryFromOEM
to NULL in your OemInit() OAL funciton
"RF" <rickfang@ms58.hinet.net> ¼¶¼g©ó¶l¥ó·s»D
:71811AD6-428D-4541-B6A4-FC217667225C@microsoft.com...
> Hi,
> I write one simple .CAB file and be executed under WinCE4.2 OS. I find it
will call "RegFlushKey" API to save registry to persistent storage as IPSM
we have. The .inf file of .CAB does not call "RegFlushKey" API during
installation, it seems the WinCE kernel make it. After COLD Boot, there is
one issue that registry do still exist, but program file disappear. Because
COLD Boot doesn't clean the content of Persistent Storage (IPSM), it will
clean all content in DRAM.
> How to prevent this issue by modified .CAB file? Or, it need to clean IPSM
all data once COLD Boot in platform builder.
>
> thanks
> RF
- Next message: Paul G. Tobey [eMVP]: "Re: Problem migratting from 4.1 to 4.2"
- Previous message: Ten: "Re: APP Still running after Cmd window close"
- In reply to: RF: ".CAB file issue !!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
