Hive based Registry support issue

[AnantWakode]

hi,

thanks for looking in to this, I am using win ce 6.0, I need to implement
hive based registry support , for that i have added hive based registry
catlog item along with Rom only file system.

set the the appropriate registry as specified in the msdn documentation,
I am able to boot the system but main scrren does't appear , some times show
blank screen and some times some window (i thing that is related to
activesync) and which size is so bigger that i cant see its close button even
on the PC (if device connected to pc) activesync connection established but
can't explorer files ,remote tregistry

the registry settings.
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Registry\\System.hv"
"ProfileDir"="Registry"
"Flags"=dword:1
"Start DevMgr"=dword:1

then included
nand flash driver registry settings and cepddk settings in hive boot section.
and cepddk

set mount as bootable aswell as mount as root for FlashDisk Profile

please suggest me any solution.

Thanks
-Anant Wakode

[Bruce Eitman [eMVP]]

Did you do a clean sysgen after making the changes?

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

"AnantWakode" <Anant...@discussions.microsoft.com> wrote in message
news:EF3AC057-0AC7-4DDE...@microsoft.com...

[AnantWakode]

TGIS

I have made following changes and its working now, please let me know if
there is any non needed settings are present with this.

I am using WIN CE 6.0

1) Added Hive Based Registry Component
2) Added ROM Only File System
3) Modified Registry

;Common.reg

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FATFS]
"Flags"=dword:00020024

[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Registry\\System.hv"
"ProfileDir"="Registry"
"Flags"=dword:1
"Start DevMgr"=dword:1

this setting was missing. is it really needed ?????
[HKEY_LOCAL_MACHINE\init\BootVars]
"Flags"=dword:3

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS]
"MountAsRoot"=dword:1

this setting was missing. is it really needed ?????

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"MountAsRoot"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk]
"MountAsBootable"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS\Filters\CEFilt]
"Dll"="cefilt.dll"

;Platform.reg
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NAND_Flash]
"Flags"=dword:1000

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CSPDDK]
"Flags"=dword:1000

Thanks
-Anant

[AnantWakode]

Thanks Bruce Eitman.
yes I had clean sysgen, I have solved the issue it was an reg. settings issue.

can you please tell me the settings i have provided are needed ? or any
redundant settings are present.

Thanks again
-Anant

"Bruce Eitman [eMVP]" wrote:

> .
>

[Paul G. Tobey [ eMVP ]]

You ARE NOT modifying common.reg are you? BAD IDEA. Modify platform.reg or
project.reg as necessary, but don't modify common code. Sorry I can't
actually help with the question, but you don't want to modify common.reg EVER.

Paul T.

[AnantWakode]

Thanks !!!

yes really a bad idea,

actualy till now I was just exprementing.

I am going to move these changes to platform or project.

I am doubtful about one thing suppose i moved all the common.reg changes
(related to current topic) in to either platform or project.reg. wheather
those keys will get overridden as already there are few keys already present
in the common.reg. which are not useful to me. like MSFLASH

can I use PRJ_ variables for conditional inclusion of registry settings
present in project.reg or platform.reg

Thanks again.
-Anant

[Bruce Eitman [eMVP]]

I'm not sure that I understand your questions completely. Registry entries
in platform.reg overwrite settings in common.reg. You can use environment
variables in your platform.reg.

Some articles that you might want to read:

http://geekswithblogs.net/BruceEitman/archive/2008/06/04/platform-builder--managing-the-registry.aspx

http://geekswithblogs.net/BruceEitman/archive/2008/05/23/platform-builder-pulling-it-all-together-with-makeimg.aspx

http://geekswithblogs.net/BruceEitman/archive/2008/06/20/platform-builder-fmerge-tips-and-tricks.aspx

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

"AnantWakode" <Anant...@discussions.microsoft.com> wrote in message

news:19C61E19-B9E3-4FB7...@microsoft.com...

[Paul G. Tobey [ eMVP ]]

It's a bad idea even to experiment via common.reg changes. What if you
forget to put them back? Every build you do after that will now have these
experimental changes in it. For that matter, you also have to remember to
copy common.reg from PUBLIC to the release folder, if you changed the
original common.reg. Better to just adjust project.reg or platform.reg from
the beginning.

As I recall the priority order of settings:

common.reg
project.reg
platform.reg
<PB projects>.reg

Paul T.

[Paul G. Tobey [ eMVP ]]

What I listed there was the order in which items are included in the big
registry file which describes the initial registry on the device. Last added
to that file wins in a conflict. I think that I've messed up the order with
respect to subprojects, too; I think that they are included after common.reg,
but before project.reg and platform.reg. Platform.reg wins, is the basic
message.

Paul T.

[AnantWakode]

Thanks !

I have made the changes as per your suggestion and its working,....!

Thanks again !
-Anant Wakode

[Keaven Pineau]

Regarding this issue,

Do we really need to set SYSGEN_FSROMONLY or we can also have a hive
registry using SYSGEN_FSRAMROM that is saving the system.hv file on a
nandflash?

Thank you

"AnantWakode" <Anant...@discussions.microsoft.com> wrote in message
news:19C61E19-B9E3-4FB7...@microsoft.com...

[Paul G. Tobey [eMVP]]

FSROMONLY means that your filesystem will simply contain the 'files' built
into your OS image, nk.bin. FSRAMROM means that a RAM-based filesystem will
also be mounted, allowing you to write files to \, \windows, etc., which
will be stored in RAM. That is, hive-based registry and the filesystem
setting are really not related. You could, for example, have an SD card
mounted as \storage card and set up your registry for the hive to put the
hive files *there*, rather thaan the default location. You could then have
a RAMROM filesystem, while still using hive-based registry. My best
success, however, has been with ROMONLY because it not only allows you to
use hive-based registry with the default settings, but also makes it
possible to persistently put stuff in the \windows folder. This is very
good as most installed items like to be in \windows and allowing them to be
installed to their default locations makes your device more-likey to work
with such things. Not necessary, but, for me, the right thing to do.

Paul T.

"Keaven Pineau" <keavenpineau...@videotron.ca-no-more-spam> wrote
in message news:%23b1F2sN...@TK2MSFTNGP04.phx.gbl...

[Bruce Eitman [eMVP]]

No, you do not need to use SYSGEN_FSROMONLY. That seems to be a common
misconception.

What you do need to do is set the environment variable PRJ_ENABLE_FSREGHIVE
which is documented in common.reg. I beleive that this variable is the work
of the devil becuase it is so obscure and creates a result that is not
usually expected.

--
Bruce Eitman (eMVP)
Senior Engineer
Bruce.Eitman AT Eurotech DOT com
My BLOG http://geekswithblogs.net/bruceeitman

Eurotech Inc.
www.Eurotech.com

"Keaven Pineau" <keavenpineau...@videotron.ca-no-more-spam> wrote
in message news:%23b1F2sN...@TK2MSFTNGP04.phx.gbl...

[Keaven Pineau]

Ok I understand well the difference between the two thank you.

Another one concerning the FLASH hash that is done by the kernel for
checking the integrity of the memory on boot and force a clean hive. Do you
know on which section of the FLASH the hash is done? Is it done only on the
FLASH partition where I want to save the system.hv?

Regards,

"Bruce Eitman [eMVP]" <bruce.eit...@Eurotech.com.nospam> wrote in
message news:eq3zwZQt...@TK2MSFTNGP02.phx.gbl...