Hive Based Registry Tip

Hi all,

I am working on a system that uses Hive Based Registry over IDE/ATAPI. When
the Compact Flash is plugged in the system everything works fine. However,
my guess is that the system could work fine when the Compact Flash is not
attached to the device; obviously with the original registry stored inside
the NK.BIN.

I've been "playing" with Platform Builder and I've realized of the
following: when the system boots up, DEVICE tries to load the IDE driver. As
the Compact Flash is not attached the driver initialization fails and the
driver gets unloaded.

However, when the system continues booting it seems that FILESYS gets locked
waiting for a DEVICE notification. I assume that FILESYS is waiting for a
DEVICE notification, and the notification waited is the succesfull load of
the driver responsible of storing the registry.

My question is the following :

# Is the system able to detect the failure in the loading of the driver
responsible of storing the registry hives?

# Is there any place in the sources of the Platform (x86) where I can tailor
my system to detect this situation, and work on as configured in the
original NK.BIN?

Thanks in advance,

Ten
Wed Feb 11 10:07:16 CST 2004

To me, the use of a persistent registry is a contract with the kernel. You
either use it and allow the kernel to rely on it or you don't. That's not
to say what you want to do can't be done but it seems to me that it would be
a vast undertaking.

Do you have another store that you can use? For example, I have a 2 MB NOR
and a 64 MB NAND that are built on the SBC. With the FLASH drivers, these
are seen as \NOR FLASH and \NAND FLASH. My registry is configured to use
\NAND FLASH for the persistent store. My registry hives are about 130 k
each (for user.hv and system.hv).

My boot loader (on NOR) occupies < 300K and my CE image is about 7 MB
compressed on NAND so there is plenty of room for the hive on either. I
realize your situtation may be different, but since the SBC usually has some
sort of storage for the boot loader and os image, you may be able to use
something like this instead of the removable media.

Nick.


"Roberto Bernardo Cagigal" <rbernardoATingeteamDOTes> wrote in message
news:uDGb7mK8DHA.2576@TK2MSFTNGP11.phx.gbl...
> Hi all,
>
> I am working on a system that uses Hive Based Registry over IDE/ATAPI.
When
> the Compact Flash is plugged in the system everything works fine. However,
> my guess is that the system could work fine when the Compact Flash is not
> attached to the device; obviously with the original registry stored inside
> the NK.BIN.
>
> I've been "playing" with Platform Builder and I've realized of the
> following: when the system boots up, DEVICE tries to load the IDE driver.
As
> the Compact Flash is not attached the driver initialization fails and the
> driver gets unloaded.
>
> However, when the system continues booting it seems that FILESYS gets
locked
> waiting for a DEVICE notification. I assume that FILESYS is waiting for a
> DEVICE notification, and the notification waited is the succesfull load of
> the driver responsible of storing the registry.
>
> My question is the following :
>
> # Is the system able to detect the failure in the loading of the driver
> responsible of storing the registry hives?
>
> # Is there any place in the sources of the Platform (x86) where I can
tailor
> my system to detect this situation, and work on as configured in the
> original NK.BIN?
>
> Thanks in advance,
>
>
>