Re: Hive-based registry setting

Dear Luca, nice to see your reply.

I fixed my problem. I followed your tips, and forgetting any manual
modification in my .reg files I just included the enviroments variables by
Platform\Settings\Enviroments menus.

Now is perfect.

Thank you very much.

Luca, I have a question about the bootloader:

Can you write alls steps to make new BLDR after modification of in fat.h
because I saw some problems. My sequence is that:

- Modification
- By the right mouse button selecting the project root "loader" I build
this project. BLDR is new. For confirmation I change version in serial
debug outlet. OK
- I move manually the new BLDR in my floppy disk created by SETUPDISK.144
because launching the creator (setupdisk.144) is loaded an older version
dated April 22 2004. I don't how upgrade the utility
- I make all operations on my CF, fdisk + format + mkdisk c:, last one copy
my new BLDR in c:
- Copying NK.bin, splash.bmx, boot.ini;
- I change in boot.ini "BinFile" value from eboot.bix to nk.bin;

this no work !!! But I think is my method of building BLDR, Loader project,
or how I copy the release to floppy disk.

I hope you have a soluction !!

thank you, Tiziano Fabbri


PS: where you live ??


"Luca Calligaris" wrote:

> Dear Tiziano, suppose for a moment you're using the PS Geode BSP:
>
>
> In you common.reg you should have:
>
> IF PRJ_ENABLE_FSREGHIVE
> ; @CESYSGEN IF FILESYS_FSREGHIVE
> ; HIVE BOOT SECTION
> IF PRJ_BOOTDEVICE_MSFLASH
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "Flags"=dword:1
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash]
> "MountAsBootable"=dword:1
> ELSE
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "Flags"=dword:3
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "MountAsBootable"=dword:1
> ENDIF
> ; @CESYSGEN ELSE
> #error PRJ_ENABLE_FSREGHIVE defined without including HIVE based component.
> Add SYSGEN_FSREGHIVE to your configuration
> ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
> ; END HIVE BOOT SECTION
> ENDIF
>
> after CEFILTER this should reduce to:
>
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "Flags"=dword:3
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "MountAsBootable"=dword:1
>
> which means:
> start storage manager & device manager in boot phase 1 for hive-based
> registry;
> HD may contain system registry;
>
> In platform.reg you should have a line like this:
> #include "$(DRIVERS_DIR)\block\atapi\geodeide.reg
>
> if you look at the included .reg file you should found
>
> IF PRJ_ENABLE_FSREGHIVE
> ; HIVE BOOT SECTION
> [$(PCI_BUS_ROOT)\Template\GeodeIDE]
> "Flags"=dword:1000
> [$(PCI_BUS_ROOT)\Template\GeodeIDE\Device0]
> "Flags"=dword:1000
> ; END HIVE BOOT SECTION
> ENDIF PRJ_ENABLE_FSREGHIVE
>
> which tells the Device Manager to loadatapi.dll in the first boot phase with
> the boot registry.
>
>
> As you can see setting PRJ_ENABLE_FSREGHIVE introduce exactly the registry
> entries explained in 'Using the Hive-Based Registry'
>
>
> "tiziano fabbri" wrote:
>
> > Hi Sue Loh, Hi Jimbo,
> >
> > thank you for your reply. I'm writing from my home, is night now.
> >
> > Before I want clearing my situation: today I had first suspect about
> > something
> > wrong on my platform builder, only yestarday I thong that was a mistake in
> > the msdn help.
> >
> > In the help the referement is for platform .reg in each step of "Using
> > Hive-based registry" instructions. But in my project all register keys
> > declared in the help are in common.reg.
> >
> > That is big buzz in my mind. Story of my project start from a cloning of a
> > Geode BSP and after I create my image. No more. Version is 5.0 September 2004
> > and I upgrade just yestarday with the package dated december 2004.
> >
> > Do you have some ideas about it ? Is same thing or not ? If not, how I can
> > change this situation ?
> >
> > Dear Sue, about keypad problem and also the impossibilty to create some new
> > connections I verified that are in the same moment that I call these two
> > command by .reg file, common or platform is not important:
> > "Start DevMng"=dword:1
> > "MountFlags"= dword:2
> > These two commands, after their calling, permits to save by hive registry
> > and that work: I tryed to make some modification in the desktop likes hiding
> > the toolbar, showing hiding files, etc.. Rebooting alls modifications are
> > saved and are avaible. But I have two, or more, big problems.
> >
> > My sensation is a twice launching of driver because, in the keyboard problem
> > you can the its leds flashing, but at displaying of shell nothing run.
> >
> > What I want say is that: if read up the mailing of Luca, he doesn't speaks
> > about Start DevMng or MountFlags, or in general of "Using Hive-based
> > registry", sensation is that simply including in the image right service and
> > enabling the prj enviroment variables everything run. May be not. We wait
> > some confirmation from Luca.
> >
> > What I know is that something strange in my project.
> >
> > thank you alls. Tiziano Fabbri
> >
> > PS: Until now I didn't understood how make some choice about which driver
> > and wich driver not must be tract with "Flags"=dword:1000
> >
> > bye bye, good night
> > "Sue Loh [MS]" wrote:
> >
> > > Hi Tiziano,
> > >
> > > Most of the settings are stored in common.reg, but all the .reg files are
> > > concatenated together into a file called reginit.ini when you make an
> > > image, to create the registry for your device. You should be able to see
> > > reginit.ini in your release directory. The settings from common.reg go
> > > into reginit.ini before the settings from platform.reg. Settings from
> > > later in the file can overwrite settings from earlier in the file. While
> > > you see the settings in common.reg, you should not modify common.reg to
> > > change the settings that go onto your device. You should add the new
> > > settings to platform.reg instead. You will find that if you do this, your
> > > settings from platform.reg come last in reginit.ini and therefore are used
> > > on the device.
> > >
> > > I'm not sure I understood what your problem is. It sounds like your device
> > > boots all right the first time. And that you have verified that if you
> > > make changes, your flush program successfully commits them so that they are
> > > present on the next reboot. But you're having trouble with the keyboard
> > > driver and with the settings for Explorer? For the keyboard driver, I
> > > suggest you build a debug version of that driver and see if it prints any
> > > output that helps you see what is going on. The keyboard driver should not
> > > be started in the first boot phase so I don't know what would cause
> > > problems with it.
> > >
> > > I don't know Explorer very well, but one thought I had is that the settings
> > > may be in the user hive, and your flush program may only be flushing the
> > > system hive. Are you calling RegFlushKey on both HKEY_LOCAL_MACHINE and
> > > HKEY_CURRENT_USER? They are stored in separate keys so you would have to
> > > flush them both. If you are already doing that, then I'm not sure what's
> > > wrong.
> > >
> > > Sue
> > > sloh@xxxxxxxxxxxxx (remove "online" from reply-to address)
> > > http://blogs.msdn.com/sloh/
> > > _____________________________________________________________
> > > This posting is provided "AS IS" with no warranties, and confers no rights.
> > > _____________________________________________________________
> > >
> > > Have an opinion on the effectiveness of Microsoft Embedded newsgroups? Let
> > > us know!
> > > https://www.windowsembeddedeval.com/community/newsgroups
> > >
> > >
.