Flash driver for wince 5.0

Hi,

I am going to design flash driver of 128MB size for a handset. So I
need to persist my data in the flash every time it's updated. My doubt
is,

Whether I have to use HIVE BASED REGISTRY or RAM based registry?

The hive-based registry is most efficient on target devices that cold
boot often but rarely or never warm boot.(this info is from platform
builder). I think as a handset, it will need considerable number of
warm boot also.

So can you suggest a suitable registry type?

My second doubt is selecting the internal file system. The available
file systems are ROM only file system and RAM and ROM file system.

It is mentioned in Platform builder that, the RAM and ROM file system
is most useful in target devices that continuously power RAM because
the object store is lost when RAM is not refreshed, and in the case of
ROM only file system, it does not allow applications to place files in
the object store. So can anybody suggest a suitable internal file
system among this?

Thanks in advance.

Bruce
Thu Aug 16 07:39:10 CDT 2007

The only thing that we know about your device is that it has 128MB flash and
you are asking us for specific information.

--
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

<princyf@gmail.com> wrote in message
news:1187236035.719809.162140@j4g2000prf.googlegroups.com...
> Hi,
>
> I am going to design flash driver of 128MB size for a handset. So I
> need to persist my data in the flash every time it's updated. My doubt
> is,
>
> Whether I have to use HIVE BASED REGISTRY or RAM based registry?
>
> The hive-based registry is most efficient on target devices that cold
> boot often but rarely or never warm boot.(this info is from platform
> builder). I think as a handset, it will need considerable number of
> warm boot also.
>
> So can you suggest a suitable registry type?
>
> My second doubt is selecting the internal file system. The available
> file systems are ROM only file system and RAM and ROM file system.
>
> It is mentioned in Platform builder that, the RAM and ROM file system
> is most useful in target devices that continuously power RAM because
> the object store is lost when RAM is not refreshed, and in the case of
> ROM only file system, it does not allow applications to place files in
> the object store. So can anybody suggest a suitable internal file
> system among this?
>
> Thanks in advance.
>

Gary
Thu Aug 16 13:48:48 CDT 2007

When you make registry changes and cold boot the device, do you want the
registry changes to still be there?
If yes, use hive
If no, use RAM (reverts to original registry)

Regards,
Gary

<princyf@gmail.com> wrote in message
news:1187236035.719809.162140@j4g2000prf.googlegroups.com...
> Hi,
>
> I am going to design flash driver of 128MB size for a handset. So I
> need to persist my data in the flash every time it's updated. My doubt
> is,
>
> Whether I have to use HIVE BASED REGISTRY or RAM based registry?
>
> The hive-based registry is most efficient on target devices that cold
> boot often but rarely or never warm boot.(this info is from platform
> builder). I think as a handset, it will need considerable number of
> warm boot also.
>
> So can you suggest a suitable registry type?
>
> My second doubt is selecting the internal file system. The available
> file systems are ROM only file system and RAM and ROM file system.
>
> It is mentioned in Platform builder that, the RAM and ROM file system
> is most useful in target devices that continuously power RAM because
> the object store is lost when RAM is not refreshed, and in the case of
> ROM only file system, it does not allow applications to place files in
> the object store. So can anybody suggest a suitable internal file
> system among this?
>
> Thanks in advance.
>

Bruce
Thu Aug 16 14:45:20 CDT 2007

Not completely acurate.

You can use RAM and persist the registry. With RAM based you can implement
pWriteRegistryToOEM and pReadRegistryFromOEM in the kernel to persist the
registry.

--
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

"Gary Swalling" <garret.swalling@spansion.com.nospam> wrote in message
news:etn95XD4HHA.1824@TK2MSFTNGP04.phx.gbl...
> When you make registry changes and cold boot the device, do you want the
> registry changes to still be there?
> If yes, use hive
> If no, use RAM (reverts to original registry)
>
> Regards,
> Gary
>
> <princyf@gmail.com> wrote in message
> news:1187236035.719809.162140@j4g2000prf.googlegroups.com...
>> Hi,
>>
>> I am going to design flash driver of 128MB size for a handset. So I
>> need to persist my data in the flash every time it's updated. My doubt
>> is,
>>
>> Whether I have to use HIVE BASED REGISTRY or RAM based registry?
>>
>> The hive-based registry is most efficient on target devices that cold
>> boot often but rarely or never warm boot.(this info is from platform
>> builder). I think as a handset, it will need considerable number of
>> warm boot also.
>>
>> So can you suggest a suitable registry type?
>>
>> My second doubt is selecting the internal file system. The available
>> file systems are ROM only file system and RAM and ROM file system.
>>
>> It is mentioned in Platform builder that, the RAM and ROM file system
>> is most useful in target devices that continuously power RAM because
>> the object store is lost when RAM is not refreshed, and in the case of
>> ROM only file system, it does not allow applications to place files in
>> the object store. So can anybody suggest a suitable internal file
>> system among this?
>>
>> Thanks in advance.
>>
>
>

ctacke/>
Thu Aug 16 23:22:15 CDT 2007

And with a Hive registry you can still store it to a RAM filesystem that
gets wiped out on a reset...

For registries:
Hive != persistent
RAM != volatile

--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com



"Bruce Eitman [eMVP]" <beitman.nospam@applieddata.net.nospam> wrote in
message news:%231W7R5D4HHA.3916@TK2MSFTNGP02.phx.gbl...
> Not completely acurate.
>
> You can use RAM and persist the registry. With RAM based you can
> implement pWriteRegistryToOEM and pReadRegistryFromOEM in the kernel to
> persist the registry.
>
> --
> 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
>
> "Gary Swalling" <garret.swalling@spansion.com.nospam> wrote in message
> news:etn95XD4HHA.1824@TK2MSFTNGP04.phx.gbl...
>> When you make registry changes and cold boot the device, do you want the
>> registry changes to still be there?
>> If yes, use hive
>> If no, use RAM (reverts to original registry)
>>
>> Regards,
>> Gary
>>
>> <princyf@gmail.com> wrote in message
>> news:1187236035.719809.162140@j4g2000prf.googlegroups.com...
>>> Hi,
>>>
>>> I am going to design flash driver of 128MB size for a handset. So I
>>> need to persist my data in the flash every time it's updated. My doubt
>>> is,
>>>
>>> Whether I have to use HIVE BASED REGISTRY or RAM based registry?
>>>
>>> The hive-based registry is most efficient on target devices that cold
>>> boot often but rarely or never warm boot.(this info is from platform
>>> builder). I think as a handset, it will need considerable number of
>>> warm boot also.
>>>
>>> So can you suggest a suitable registry type?
>>>
>>> My second doubt is selecting the internal file system. The available
>>> file systems are ROM only file system and RAM and ROM file system.
>>>
>>> It is mentioned in Platform builder that, the RAM and ROM file system
>>> is most useful in target devices that continuously power RAM because
>>> the object store is lost when RAM is not refreshed, and in the case of
>>> ROM only file system, it does not allow applications to place files in
>>> the object store. So can anybody suggest a suitable internal file
>>> system among this?
>>>
>>> Thanks in advance.
>>>
>>
>>
>
>

princyf
Thu Aug 16 23:29:25 CDT 2007

Hi,

Thanks for the reply,
We are designing a VOIP handset which uses WinCE 5.0 OS, we have an
Ethernet port to download data, and this data will be stored in flash.
So the contents of flash will be changed every time, these changes
along with previous data should persist after a cold boot. So at this
condition which registry I should use, where I can get more
information about HIVE BASED and RAM based registry other than
platform builder help.

Bruce
Fri Aug 17 07:26:12 CDT 2007

Good catch Chris!

--
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

"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message
news:%23m1TTZI4HHA.3900@TK2MSFTNGP02.phx.gbl...
> And with a Hive registry you can still store it to a RAM filesystem that
> gets wiped out on a reset...
>
> For registries:
> Hive != persistent
> RAM != volatile
>
> --
>
> Chris Tacke, Embedded MVP
> OpenNETCF Consulting
> Managed Code in an Embedded World
> www.OpenNETCF.com
>
>
>
> "Bruce Eitman [eMVP]" <beitman.nospam@applieddata.net.nospam> wrote in
> message news:%231W7R5D4HHA.3916@TK2MSFTNGP02.phx.gbl...
>> Not completely acurate.
>>
>> You can use RAM and persist the registry. With RAM based you can
>> implement pWriteRegistryToOEM and pReadRegistryFromOEM in the kernel to
>> persist the registry.
>>
>> --
>> 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
>>
>> "Gary Swalling" <garret.swalling@spansion.com.nospam> wrote in message
>> news:etn95XD4HHA.1824@TK2MSFTNGP04.phx.gbl...
>>> When you make registry changes and cold boot the device, do you want the
>>> registry changes to still be there?
>>> If yes, use hive
>>> If no, use RAM (reverts to original registry)
>>>
>>> Regards,
>>> Gary
>>>
>>> <princyf@gmail.com> wrote in message
>>> news:1187236035.719809.162140@j4g2000prf.googlegroups.com...
>>>> Hi,
>>>>
>>>> I am going to design flash driver of 128MB size for a handset. So I
>>>> need to persist my data in the flash every time it's updated. My doubt
>>>> is,
>>>>
>>>> Whether I have to use HIVE BASED REGISTRY or RAM based registry?
>>>>
>>>> The hive-based registry is most efficient on target devices that cold
>>>> boot often but rarely or never warm boot.(this info is from platform
>>>> builder). I think as a handset, it will need considerable number of
>>>> warm boot also.
>>>>
>>>> So can you suggest a suitable registry type?
>>>>
>>>> My second doubt is selecting the internal file system. The available
>>>> file systems are ROM only file system and RAM and ROM file system.
>>>>
>>>> It is mentioned in Platform builder that, the RAM and ROM file system
>>>> is most useful in target devices that continuously power RAM because
>>>> the object store is lost when RAM is not refreshed, and in the case of
>>>> ROM only file system, it does not allow applications to place files in
>>>> the object store. So can anybody suggest a suitable internal file
>>>> system among this?
>>>>
>>>> Thanks in advance.
>>>>
>>>
>>>
>>
>>
>
>

Bruce
Fri Aug 17 07:27:38 CDT 2007

That really isn't enough information to provide you with assistance.

You should use the one that satisfies your requirements.

--
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

<princyf@gmail.com> wrote in message
news:1187324965.626953.151140@z24g2000prh.googlegroups.com...
> Hi,
>
> Thanks for the reply,
> We are designing a VOIP handset which uses WinCE 5.0 OS, we have an
> Ethernet port to download data, and this data will be stored in flash.
> So the contents of flash will be changed every time, these changes
> along with previous data should persist after a cold boot. So at this
> condition which registry I should use, where I can get more
> information about HIVE BASED and RAM based registry other than
> platform builder help.
>
>
>

Dean
Fri Aug 17 08:17:59 CDT 2007

Also note that registry persistence has nothing to do with preserving the
data you download. Registry persistence is for registry changes only.
You'll need to make sure that whatever *data* you download goes to
persistent storage.

--
Dean Ramsier - eMVP
BSQUARE Corporation


"Bruce Eitman [eMVP]" <beitman.nospam@applieddata.net.nospam> wrote in
message news:ekpxXpM4HHA.5880@TK2MSFTNGP03.phx.gbl...
> That really isn't enough information to provide you with assistance.
>
> You should use the one that satisfies your requirements.
>
> --
> 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
>
> <princyf@gmail.com> wrote in message
> news:1187324965.626953.151140@z24g2000prh.googlegroups.com...
>> Hi,
>>
>> Thanks for the reply,
>> We are designing a VOIP handset which uses WinCE 5.0 OS, we have an
>> Ethernet port to download data, and this data will be stored in flash.
>> So the contents of flash will be changed every time, these changes
>> along with previous data should persist after a cold boot. So at this
>> condition which registry I should use, where I can get more
>> information about HIVE BASED and RAM based registry other than
>> platform builder help.
>>
>>
>>
>
>