My CE6.0 image is set to hive-based registry, and I want to storage
hive files in Hard Disk(FAT file system). But the NK.bin boot failed, and
halt at "FILESYS: Waiting for bootable file system to be mounted." I don't
know why.

1. Add "RAM and ROM File System", "FAT File System", "Hive-based
Registry","ATAPI PCI Support" from catalog.

2. I added the following settings to platform.reg:
=======================================
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Documents and Settings\\system.hv"
"ProfileDir"="Documents and Settings"
"Flags"=dword:3
"DefaultUser"="Administrator"
"RegistryFlags"=dword:2

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"MountAsBootable"=dword:1
; END HIVE BOOT SECTION
=======================================

2. I set the environment variable PRJ_ENABLE_FSREGHIVE = 1, which would
affect settings in common.reg:
=======================================
; @CESYSGEN IF FILESYS_FSYSRAM
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ObjectStore]
IF PRJ_ENABLE_FSREGHIVE !
; Only mount ObjectStore FS as bootable if PRJ_ENABLE_FSREGHIVE is NOT set
; in order to preserve backwards compatibility (hive files go on
; ObjectStore FS by default).
"MountAsBootable"=dword:1
ENDIF
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF FILESYS_FSYSRAM
===========================================

Now, I copy some debug message as follows:
===========================================
FSDMGR!DllMain: DLL_PROCESS_ATTACH
CertMod.dll not found, using old OEM Trust Model
FileSystem Starting - starting with clean file system
FSDMGR!STOREMGR_Initialize
FSDMGR!InitializeStoreAPI
FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index
2FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2
(Name="StoreMgr", MountFlags=0x1)FSDMGR!InitializeROMFileSystem: File
System=ROM
FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
(Name="ROM", MountFlags=0x71)FSVOL: Opening existing volume
FSVOL: Volume heap already initialized
FSREG: Mounted ROM portion of boot registry
FSVOL: Creating clean virtual volume
FSVOL: Initializing volume heap
FSREG: Mounted RAM portion of boot registry
Override Serial Driver: No COM port selected for serial KITL transport, no
override necessary.
FS: Creating signal event SYSTEM/DevMgrApiSetReady
FS: Creating signal event SYSTEM/PowerManagerReady
FS: Creating signal event SYSTEM/GweApiSetReady
FSREG: Unable to read value "Start DevMgr" under
HKEY_LOCAL_MACHINE\init\BootVars
FILESYS: Starting boot phase 0.
FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
FSDMGR: File security disabled.
FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0,
RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore
FILESYS: RAM File System FSD_MountDisk registering folder "Object Store"
FSDMGR!MountTableFSDMGR!PNPThread: Using PNPUnloadDelay of 4096
FSDMGR!PNPThread: PNPThread starting!
_t::RegisterVolumeName: Registered "Object Store" at index
4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="",
MountFlags=0x44)
FILESYS: Starting boot phase 1.
FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
FILESYS: Starting device and waiting for boot file system.
*** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
Filesys: Loaded device.dll
FILESYS: Waiting for device manager to signal BootPhase1 completion.
+InitDeviceFileSystems
...
...
PCIBUS!PCIRequestResources: I/O Resource Manager request for I/O range
0x0-0x3 failed
PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1 failed
DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 3800 Ticks
FILESYS: Waiting for bootable file system to be mounted.
FILESYS: Waiting for bootable file system to be mounted.
FILESYS: Waiting for bootable file system to be mounted.
...
===========================================

Could you help me please?
Thanks and best regards.

Re: CE6.0 Hive-based registry in Hard Disk by Mike

Mike
Fri Mar 14 02:34:17 PDT 2008

=?Utf-8?B?emhpemk=?= <zhizi@discussions.microsoft.com> wrote in
news:DF162850-567E-4664-AB28-F770ED1E227D@microsoft.com:

> My CE6.0 image is set to hive-based registry, and I want to
> storage
> hive files in Hard Disk(FAT file system). But the NK.bin boot failed,
> and halt at "FILESYS: Waiting for bootable file system to be mounted."
> I don't know why.
>
> 1. Add "RAM and ROM File System", "FAT File System", "Hive-based
> Registry","ATAPI PCI Support" from catalog.
>
> 2. I added the following settings to platform.reg:
> =======================================
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "SystemHive"="Documents and Settings\\system.hv"
> "ProfileDir"="Documents and Settings"
> "Flags"=dword:3
> "DefaultUser"="Administrator"
> "RegistryFlags"=dword:2
>
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "MountAsBootable"=dword:1
> ; END HIVE BOOT SECTION
> =======================================
>
> 2. I set the environment variable PRJ_ENABLE_FSREGHIVE = 1, which
> would affect settings in common.reg:
> =======================================
> ; @CESYSGEN IF FILESYS_FSYSRAM
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ObjectStore]
> IF PRJ_ENABLE_FSREGHIVE !
> ; Only mount ObjectStore FS as bootable if PRJ_ENABLE_FSREGHIVE is
> NOT set ; in order to preserve backwards compatibility (hive files
> go on ; ObjectStore FS by default).
> "MountAsBootable"=dword:1
> ENDIF
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF FILESYS_FSYSRAM
> ===========================================
>
> Now, I copy some debug message as follows:
> ===========================================
> FSDMGR!DllMain: DLL_PROCESS_ATTACH
> CertMod.dll not found, using old OEM Trust Model
> FileSystem Starting - starting with clean file system
> FSDMGR!STOREMGR_Initialize
> FSDMGR!InitializeStoreAPI
> FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at
> index 2FSDMGR!MountTable_t::RegisterVolume: Registered volume at index
> 2 (Name="StoreMgr", MountFlags=0x1)FSDMGR!InitializeROMFileSystem:
> File System=ROM
> FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
> 3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
> (Name="ROM", MountFlags=0x71)FSVOL: Opening existing volume
> FSVOL: Volume heap already initialized
> FSREG: Mounted ROM portion of boot registry
> FSVOL: Creating clean virtual volume
> FSVOL: Initializing volume heap
> FSREG: Mounted RAM portion of boot registry
> Override Serial Driver: No COM port selected for serial KITL
> transport, no override necessary.
> FS: Creating signal event SYSTEM/DevMgrApiSetReady
> FS: Creating signal event SYSTEM/PowerManagerReady
> FS: Creating signal event SYSTEM/GweApiSetReady
> FSREG: Unable to read value "Start DevMgr" under
> HKEY_LOCAL_MACHINE\init\BootVars
> FILESYS: Starting boot phase 0.
> FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
> FSDMGR: File security disabled.
> FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
> FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0,
> RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore
> FILESYS: RAM File System FSD_MountDisk registering folder "Object
> Store" FSDMGR!MountTableFSDMGR!PNPThread: Using PNPUnloadDelay of 4096
> FSDMGR!PNPThread: PNPThread starting!
> _t::RegisterVolumeName: Registered "Object Store" at index
> 4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4
> (Name="", MountFlags=0x44)
> FILESYS: Starting boot phase 1.
> FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
> FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
> FILESYS: Starting device and waiting for boot file system.
> *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
> Filesys: Loaded device.dll
> FILESYS: Waiting for device manager to signal BootPhase1 completion.
> +InitDeviceFileSystems
> ...
> ...
> PCIBUS!PCIRequestResources: I/O Resource Manager request for I/O range
> 0x0-0x3 failed
> PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1 failed
> DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 3800 Ticks
> FILESYS: Waiting for bootable file system to be mounted.
> FILESYS: Waiting for bootable file system to be mounted.
> FILESYS: Waiting for bootable file system to be mounted.
> ...
> ===========================================
>
> Could you help me please?
> Thanks and best regards.
>
>
>
>
>

Did you add the hard disk driver also to the hive section thus the can
mount the hard disk to access the hive based regisrty?

regards,

Mike
--
Digi International Inc.
http://www.digi.com

Re: CE6.0 Hive-based registry in Hard Disk by zhizi

zhizi
Mon Mar 17 20:54:06 PDT 2008

"Mike E." wrote:

> =?Utf-8?B?emhpemk=?= <zhizi@discussions.microsoft.com> wrote in
> news:DF162850-567E-4664-AB28-F770ED1E227D@microsoft.com:
>
> > My CE6.0 image is set to hive-based registry, and I want to
> > storage
> > hive files in Hard Disk(FAT file system). But the NK.bin boot failed,
> > and halt at "FILESYS: Waiting for bootable file system to be mounted."
> > I don't know why.
> >
> > 1. Add "RAM and ROM File System", "FAT File System", "Hive-based
> > Registry","ATAPI PCI Support" from catalog.
> >
> > 2. I added the following settings to platform.reg:
> > =======================================
> > ; HIVE BOOT SECTION
> > [HKEY_LOCAL_MACHINE\init\BootVars]
> > "SystemHive"="Documents and Settings\\system.hv"
> > "ProfileDir"="Documents and Settings"
> > "Flags"=dword:3
> > "DefaultUser"="Administrator"
> > "RegistryFlags"=dword:2
> >
> > [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> > "MountAsBootable"=dword:1
> > ; END HIVE BOOT SECTION
> > =======================================
> >
> > 2. I set the environment variable PRJ_ENABLE_FSREGHIVE = 1, which
> > would affect settings in common.reg:
> > =======================================
> > ; @CESYSGEN IF FILESYS_FSYSRAM
> > ; HIVE BOOT SECTION
> > [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ObjectStore]
> > IF PRJ_ENABLE_FSREGHIVE !
> > ; Only mount ObjectStore FS as bootable if PRJ_ENABLE_FSREGHIVE is
> > NOT set ; in order to preserve backwards compatibility (hive files
> > go on ; ObjectStore FS by default).
> > "MountAsBootable"=dword:1
> > ENDIF
> > ; END HIVE BOOT SECTION
> > ; @CESYSGEN ENDIF FILESYS_FSYSRAM
> > ===========================================
> >
> > Now, I copy some debug message as follows:
> > ===========================================
> > FSDMGR!DllMain: DLL_PROCESS_ATTACH
> > CertMod.dll not found, using old OEM Trust Model
> > FileSystem Starting - starting with clean file system
> > FSDMGR!STOREMGR_Initialize
> > FSDMGR!InitializeStoreAPI
> > FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at
> > index 2FSDMGR!MountTable_t::RegisterVolume: Registered volume at index
> > 2 (Name="StoreMgr", MountFlags=0x1)FSDMGR!InitializeROMFileSystem:
> > File System=ROM
> > FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
> > 3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
> > (Name="ROM", MountFlags=0x71)FSVOL: Opening existing volume
> > FSVOL: Volume heap already initialized
> > FSREG: Mounted ROM portion of boot registry
> > FSVOL: Creating clean virtual volume
> > FSVOL: Initializing volume heap
> > FSREG: Mounted RAM portion of boot registry
> > Override Serial Driver: No COM port selected for serial KITL
> > transport, no override necessary.
> > FS: Creating signal event SYSTEM/DevMgrApiSetReady
> > FS: Creating signal event SYSTEM/PowerManagerReady
> > FS: Creating signal event SYSTEM/GweApiSetReady
> > FSREG: Unable to read value "Start DevMgr" under
> > HKEY_LOCAL_MACHINE\init\BootVars
> > FILESYS: Starting boot phase 0.
> > FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
> > FSDMGR: File security disabled.
> > FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
> > FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0,
> > RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore
> > FILESYS: RAM File System FSD_MountDisk registering folder "Object
> > Store" FSDMGR!MountTableFSDMGR!PNPThread: Using PNPUnloadDelay of 4096
> > FSDMGR!PNPThread: PNPThread starting!
> > _t::RegisterVolumeName: Registered "Object Store" at index
> > 4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4
> > (Name="", MountFlags=0x44)
> > FILESYS: Starting boot phase 1.
> > FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
> > FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
> > FILESYS: Starting device and waiting for boot file system.
> > *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
> > Filesys: Loaded device.dll
> > FILESYS: Waiting for device manager to signal BootPhase1 completion.
> > +InitDeviceFileSystems
> > ...
> > ...
> > PCIBUS!PCIRequestResources: I/O Resource Manager request for I/O range
> > 0x0-0x3 failed
> > PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1 failed
> > DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 3800 Ticks
> > FILESYS: Waiting for bootable file system to be mounted.
> > FILESYS: Waiting for bootable file system to be mounted.
> > FILESYS: Waiting for bootable file system to be mounted.
> > ...
> > ===========================================
> >
> > Could you help me please?
> > Thanks and best regards.
> >
> >
> >
> >
> >
>
> Did you add the hard disk driver also to the hive section thus the can
> mount the hard disk to access the hive based regisrty?
>
> regards,
>
> Mike
> --
> Digi International Inc.
> http://www.digi.com
>

Hi, Mike,

1) I added the hard disk driver to the hive section, like this:
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
"Name"="IDE Hard Disk Drive"
"Folder"="Hard Disk"

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS]
"EnableCacheWarm"=dword:0
; END HIVE BOOT SECTION

IF PRJ_ENABLE_FSREGHIVE
; HIVE BOOT SECTION
[$(PCI_BUS_ROOT)\Template\ICH2]
"Flags"=dword:1000
[$(PCI_BUS_ROOT)\Template\ICH2\Device0]
"Flags"=dword:1000
; END HIVE BOOT SECTION
ENDIF PRJ_ENABLE_FSREGHIVE

IF PRJ_ENABLE_FSREGHIVE
; HIVE BOOT SECTION
[$(PCI_BUS_ROOT)\Template\ICHx]
"Flags"=dword:1000
[$(PCI_BUS_ROOT)\Template\ICHx\Device0]
"Flags"=dword:1000
; END HIVE BOOT SECTION
ENDIF PRJ_ENABLE_FSREGHIVE

2) If I didn't set environment variable PRJ_ENABLE_FSREGHIVE, the NK.bin
will boot successfully, and the "Hard Disk" can be seen in "My Device". But
the hive files contained in the directory "Documents and Settings" is not in
the hard disk, in "My Device" instead.

Could you explain why? Thanks and best regards.





Re: CE6.0 Hive-based registry in Hard Disk by Mike

Mike
Tue Mar 18 05:25:00 PDT 2008

=?Utf-8?B?emhpemk=?= <zhizi@discussions.microsoft.com> wrote in
news:B1CA4B89-537F-460B-9489-862F4237D10E@microsoft.com:

> "Mike E." wrote:
>
>> =?Utf-8?B?emhpemk=?= <zhizi@discussions.microsoft.com> wrote in
>> news:DF162850-567E-4664-AB28-F770ED1E227D@microsoft.com:
>>
>> > My CE6.0 image is set to hive-based registry, and I want to
>> > storage
>> > hive files in Hard Disk(FAT file system). But the NK.bin boot
>> > failed, and halt at "FILESYS: Waiting for bootable file system to
>> > be mounted." I don't know why.
>> >
>> > 1. Add "RAM and ROM File System", "FAT File System", "Hive-based
>> > Registry","ATAPI PCI Support" from catalog.
>> >
>> > 2. I added the following settings to platform.reg:
>> > =======================================
>> > ; HIVE BOOT SECTION
>> > [HKEY_LOCAL_MACHINE\init\BootVars]
>> > "SystemHive"="Documents and Settings\\system.hv"
>> > "ProfileDir"="Documents and Settings"
>> > "Flags"=dword:3
>> > "DefaultUser"="Administrator"
>> > "RegistryFlags"=dword:2
>> >
>> > [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
>> > "MountAsBootable"=dword:1
>> > ; END HIVE BOOT SECTION
>> > =======================================
>> >
>> > 2. I set the environment variable PRJ_ENABLE_FSREGHIVE = 1, which
>> > would affect settings in common.reg:
>> > =======================================
>> > ; @CESYSGEN IF FILESYS_FSYSRAM
>> > ; HIVE BOOT SECTION
>> > [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\ObjectStore]
>> > IF PRJ_ENABLE_FSREGHIVE !
>> > ; Only mount ObjectStore FS as bootable if PRJ_ENABLE_FSREGHIVE
>> > is NOT set ; in order to preserve backwards compatibility (hive
>> > files go on ; ObjectStore FS by default).
>> > "MountAsBootable"=dword:1
>> > ENDIF
>> > ; END HIVE BOOT SECTION
>> > ; @CESYSGEN ENDIF FILESYS_FSYSRAM
>> > ===========================================
>> >
>> > Now, I copy some debug message as follows:
>> > ===========================================
>> > FSDMGR!DllMain: DLL_PROCESS_ATTACH
>> > CertMod.dll not found, using old OEM Trust Model
>> > FileSystem Starting - starting with clean file system
>> > FSDMGR!STOREMGR_Initialize
>> > FSDMGR!InitializeStoreAPI
>> > FSDMGR!MountTable_t::RegisterVolumeName: Registered "StoreMgr" at
>> > index 2FSDMGR!MountTable_t::RegisterVolume: Registered volume at
>> > index 2 (Name="StoreMgr",
>> > MountFlags=0x1)FSDMGR!InitializeROMFileSystem: File System=ROM
>> > FSDMGR!MountTable_t::RegisterVolumeName: Registered "ROM" at index
>> > 3FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3
>> > (Name="ROM", MountFlags=0x71)FSVOL: Opening existing volume
>> > FSVOL: Volume heap already initialized
>> > FSREG: Mounted ROM portion of boot registry
>> > FSVOL: Creating clean virtual volume
>> > FSVOL: Initializing volume heap
>> > FSREG: Mounted RAM portion of boot registry
>> > Override Serial Driver: No COM port selected for serial KITL
>> > transport, no override necessary.
>> > FS: Creating signal event SYSTEM/DevMgrApiSetReady
>> > FS: Creating signal event SYSTEM/PowerManagerReady
>> > FS: Creating signal event SYSTEM/GweApiSetReady
>> > FSREG: Unable to read value "Start DevMgr" under
>> > HKEY_LOCAL_MACHINE\init\BootVars
>> > FILESYS: Starting boot phase 0.
>> > FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1)
>> > FSDMGR: File security disabled.
>> > FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1
>> > FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0,
>> > RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore
>> > FILESYS: RAM File System FSD_MountDisk registering folder "Object
>> > Store" FSDMGR!MountTableFSDMGR!PNPThread: Using PNPUnloadDelay of
>> > 4096 FSDMGR!PNPThread: PNPThread starting!
>> > _t::RegisterVolumeName: Registered "Object Store" at index
>> > 4FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4
>> > (Name="", MountFlags=0x44)
>> > FILESYS: Starting boot phase 1.
>> > FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0)
>> > FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1
>> > FILESYS: Starting device and waiting for boot file system.
>> > *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
>> > Filesys: Loaded device.dll
>> > FILESYS: Waiting for device manager to signal BootPhase1
>> > completion. +InitDeviceFileSystems
>> > ...
>> > ...
>> > PCIBUS!PCIRequestResources: I/O Resource Manager request for I/O
>> > range 0x0-0x3 failed
>> > PCIbus!PCIEnum: WARNING: Resource request for device 0:31:1 failed
>> > DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 3800 Ticks
>> > FILESYS: Waiting for bootable file system to be mounted.
>> > FILESYS: Waiting for bootable file system to be mounted.
>> > FILESYS: Waiting for bootable file system to be mounted.
>> > ...
>> > ===========================================
>> >
>> > Could you help me please?
>> > Thanks and best regards.
>> >
>> >
>> >
>> >
>> >
>>
>> Did you add the hard disk driver also to the hive section thus the
>> can mount the hard disk to access the hive based regisrty?
>>
>> regards,
>>
>> Mike
>> --
>> Digi International Inc.
>> http://www.digi.com
>>
>
> Hi, Mike,
>
> 1) I added the hard disk driver to the hive section, like this:
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile]
> "Name"="IDE Hard Disk Drive"
> "Folder"="Hard Disk"
>
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS]
> "EnableCacheWarm"=dword:0
> ; END HIVE BOOT SECTION
>
> IF PRJ_ENABLE_FSREGHIVE
> ; HIVE BOOT SECTION
> [$(PCI_BUS_ROOT)\Template\ICH2]
> "Flags"=dword:1000
> [$(PCI_BUS_ROOT)\Template\ICH2\Device0]
> "Flags"=dword:1000
> ; END HIVE BOOT SECTION
> ENDIF PRJ_ENABLE_FSREGHIVE
>
> IF PRJ_ENABLE_FSREGHIVE
> ; HIVE BOOT SECTION
> [$(PCI_BUS_ROOT)\Template\ICHx]
> "Flags"=dword:1000
> [$(PCI_BUS_ROOT)\Template\ICHx\Device0]
> "Flags"=dword:1000
> ; END HIVE BOOT SECTION
> ENDIF PRJ_ENABLE_FSREGHIVE
>
> 2) If I didn't set environment variable PRJ_ENABLE_FSREGHIVE, the
> NK.bin will boot successfully, and the "Hard Disk" can be seen in "My
> Device". But the hive files contained in the directory "Documents and
> Settings" is not in the hard disk, in "My Device" instead.
>
> Could you explain why? Thanks and best regards.
>
>
>
>
>

When the hive based registry appears in RAM (Documents and Settings)
taht means the system didn't load your hard disk driver boot to loacte
the hive registry on your hard disk. Did you include teh PCIBus driver
also into the boot hive? You need to include any driver that is
necessary to access your hard disk.

regards,

Mike
--
Digi International Inc.
http://www.digi.com