Hive based registry

Hi all,
I wanted to implement hive based registry in an x86 based board, i am using
wince 6.0(We have done the same in wince 5.0 successfully).
I wanted to get hive registry in compact flash(I am using atapi driver). I
could able to boot the system with "ram based reg", but for hive it is not
coming up. i tried with setting PRJ_ENABLE_ FSREGHIVE as 1, no use. So here
is the debug output, i deleted something. I have selected RAM and ROM file
system also tried with ROM only file system.(See the last few lines)

Thanks and Regards,
Sankarraj



Microsoft Windows CE BIOS Bootloader Version 2.3 (Built Apr 4 2005)INFO:
code=0x4.
INFO: code=0x4.
INFO: code=0x4.
Jumping to image (address=0x226DF0)

Debug Serial Init

SysInit: GDTBase=82474000 IDTBase=8247e8c0 KData=82479800
Windows CE Kernel for i486 Built on Feb 6 2007 at 14:58:03
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
PCIBIOS:: BIOS Address static map to addr=a00e0000
GetPicRoutingIrqTable: Start
search_pci_bios start
CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00f0000
bios32_call_offset=10010 for CE/PC
Return from First BIOS EAX=49435000

EBX=f0000,ECX=10000 EDX=31
32 PCI BIOS offset located.addr=10031
32 PCI BIOS Present EDX=20494350,EAX=1 EBX=f0210,ECX=10001
+GetRoutingOption
search_pci_routing
search_pci_routing found entry =a00f3e50 CE/PC
GetRoutingOption, found ROM version for Routing table.
GetRoutingOption return SUCCESS .AH=0
ScanConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =0
ScanConfigureIrq: BufferSize = 144 @ address 824777ea


OSAXST0: Platform Name = Geode Platform
OSAXST1: >>> Loading Module 'kd.dll' (0x83FDC57C) at address
0xC0010000-0xC003E000 in Process 'NK.EXE' (0x8247BC80)
KD: Starting kernel debugger software probe (KdStub) - KD API version 22
Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt
(FALSE, p)
OSAXST1: >>> Loading Module 'NK.EXE' (0x8247BC80) at address
0x80220000-0x80233000 in Process 'NK.EXE' (0x8247BC80)
Message Queue support initialized, g_hMsgQHeap = d0040750
OSAXST1: >>> Loading Module 'filesys.dll' (0x83FBA198) at address
0xC0170000-0xC01EA000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x83FBA2D0) at address
0xC0520000-0xC0556000 in Process 'NK.EXE' (0x8247BC80)
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
OSAXST1: >>> Loading Module 'romfsd.dll' (0x83FA43E4) at address
0xC01F0000-0xC01F6000 in Process 'NK.EXE' (0x8247BC80)
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
FS: Creating signal event SYSTEM/BatteryAPIsReady
FS: Creating signal event SYSTEM/NLedAPIsReady
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=FSDMGR!PNPThread: Using
PNPUnloadDelay of 4096
FSDMGR!PNPThread: PNPThread starting!
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!MountTable_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.
OSAXST1: >>> Loading Module 'device.dll' (0x83F889EC) at address
0xC0380000-0xC0384000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'devmgr.dll' (0x83F88B24) at address
0xC0390000-0xC03AF000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x83F88C5C) at address
0xC0600000-0xC060A000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'pm.dll' (0x83F88DA4) at address
0xC03E0000-0xC0400000 in Process 'NK.EXE' (0x8247BC80)
*** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
Fil+InitDeviceFileSystems
FSDMGR!MountTable_t::RegisterVolumeName: Registered "$device" at index
5FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5
(Name="$device",

MountFlags=0x1)FSDMGR!MountTable_t::RegisterVolumeName: Registered "$bus" at
index 6FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 6

(Name="$bus", MountFlags=0x1)-InitDeviceFileSystems: esys: Loaded device.dll
FILESYS: Waiting for device manager to signal BootPhase1 completion.
status is 1
Ceddk!CalibrateStallCounter: Enter
Ceddk!CalibrateStallCounter: Could not find stall counter
Ceddk!BeginCalibration: min(1194) max(1326)
Ceddk!BeginCalibration: Calibration timed out (51 tries). Defaulting to 1 ms
resolution.
PlatformValidatePMRegistryreturningGDA::Chennai::Power Thread Started
RunningDEVICE!DevloadInit
DEVICE!InitDevices: Root Key is Drivers\BuiltIn.
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix)
returned 2
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix)
returned 2
OSAXST1: >>> Loading Module 'busenum.dll' (0x83F7C0C0) at address
0xC03D0000-0xC03D8000 in Process 'NK.EXE' (0x8247BC80)
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\CgcePrep\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'cgceprep.dll' (0x83F75BAC) at address
0xC0E10000-0xC0E15000 in Process 'NK.EXE' (0x8247BC80)
ERROR!!! Calling SetKMode
ERROR!!! Calling SetKMode
DeviceFolder::LoadDevice(Drivers\BuiltIn\CgcePrepDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2.
DEVICE!I_ActivateDeviceEx: can't find all required activation values in
'Notify'
) last 90 TicksDEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix) returned 2
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'pcibus.dll' (0x83F75CE4) at address
0xC0C60000-0xC0C7A000 in Process 'NK.EXE' (0x8247BC80)


ATAPI:PCIConfig!DeviceConfig+(1)
PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device
31, Function 3
ATAPI:PCIConfig!DeviceConfig+(1)
ATAPI:PCIConfig!DeviceConfig+(1)
ATAPI:PCIConfig!DeviceConfig+(1)
ATAPI:PCIConfig!DeviceConfig+(1)
ATAPI:PCIConfig!DeviceConfig+(1)
OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
ATAPI:PCIConfig!DeviceConfig+(2)
OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
ATAPI:PCIConfig!DeviceConfig+(3)
OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\BusPrefix) returned 2
OSAXST1: >>> Loading Module 'atapi.dll' (0x83F6609C) at address
0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device0\BusPrefix)
returned 2
DEVICE!LaunchDevice: Init() failed for device 0xd004ae70
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
atapi.dll, context 0xd029cf20
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device1\BusPrefix)
returned 2
DEVICE!LaunchDevice: Init() failed for device 0xd004b070
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
atapi.dll, context 0xd029cf20
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device2\BusPrefix)
returned 2
FILESYS: Waiting for device manager to signal BootPhase1 completion.
DEVICE!LaunchDevice: Init() failed for device 0xd004b270
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
atapi.dll, context 0xd029cf20
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device3\BusPrefix)
returned 2
DEVICE!LaunchDevice: Init() failed for device 0xd004b470
DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
atapi.dll, context 0xd029cf20
DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\ALI14531) last 6365
TicksDeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 10275

TicksDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2.
DEVICE!I_ActivateDeviceEx: can't find all required activation values in
'Notify'
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.
FILESYS: Waiting for bootable file system to be mounted.

Michel
Thu Jun 07 16:41:37 CDT 2007

Well, if you look at the debug output, ATAPI wasn't able to load a
driver for any of the harddisk (iow, the HD did not respond to
initialization!). So, there is NO HD mounted that can store the hive,
and thus CE stalls waiting for it to come online.

Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com

Sankaraj wrote:
> Hi all,
> I wanted to implement hive based registry in an x86 based board, i am using
> wince 6.0(We have done the same in wince 5.0 successfully).
> I wanted to get hive registry in compact flash(I am using atapi driver). I
> could able to boot the system with "ram based reg", but for hive it is not
> coming up. i tried with setting PRJ_ENABLE_ FSREGHIVE as 1, no use. So here
> is the debug output, i deleted something. I have selected RAM and ROM file
> system also tried with ROM only file system.(See the last few lines)
>
> Thanks and Regards,
> Sankarraj
>
>
>
> Microsoft Windows CE BIOS Bootloader Version 2.3 (Built Apr 4 2005)INFO:
> code=0x4.
> INFO: code=0x4.
> INFO: code=0x4.
> Jumping to image (address=0x226DF0)
>
> Debug Serial Init
>
> SysInit: GDTBase=82474000 IDTBase=8247e8c0 KData=82479800
> Windows CE Kernel for i486 Built on Feb 6 2007 at 14:58:03
> INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
> PCIBIOS:: BIOS Address static map to addr=a00e0000
> GetPicRoutingIrqTable: Start
> search_pci_bios start
> CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00f0000
> bios32_call_offset=10010 for CE/PC
> Return from First BIOS EAX=49435000
>
> EBX=f0000,ECX=10000 EDX=31
> 32 PCI BIOS offset located.addr=10031
> 32 PCI BIOS Present EDX=20494350,EAX=1 EBX=f0210,ECX=10001
> +GetRoutingOption
> search_pci_routing
> search_pci_routing found entry =a00f3e50 CE/PC
> GetRoutingOption, found ROM version for Routing table.
> GetRoutingOption return SUCCESS .AH=0
> ScanConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =0
> ScanConfigureIrq: BufferSize = 144 @ address 824777ea
>
>
> OSAXST0: Platform Name = Geode Platform
> OSAXST1: >>> Loading Module 'kd.dll' (0x83FDC57C) at address
> 0xC0010000-0xC003E000 in Process 'NK.EXE' (0x8247BC80)
> KD: Starting kernel debugger software probe (KdStub) - KD API version 22
> Calling KDEnableInt (FALSE, NULL) without previously calling KDEnableInt
> (FALSE, p)
> OSAXST1: >>> Loading Module 'NK.EXE' (0x8247BC80) at address
> 0x80220000-0x80233000 in Process 'NK.EXE' (0x8247BC80)
> Message Queue support initialized, g_hMsgQHeap = d0040750
> OSAXST1: >>> Loading Module 'filesys.dll' (0x83FBA198) at address
> 0xC0170000-0xC01EA000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x83FBA2D0) at address
> 0xC0520000-0xC0556000 in Process 'NK.EXE' (0x8247BC80)
> 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
> OSAXST1: >>> Loading Module 'romfsd.dll' (0x83FA43E4) at address
> 0xC01F0000-0xC01F6000 in Process 'NK.EXE' (0x8247BC80)
> 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
> FS: Creating signal event SYSTEM/BatteryAPIsReady
> FS: Creating signal event SYSTEM/NLedAPIsReady
> 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=FSDMGR!PNPThread: Using
> PNPUnloadDelay of 4096
> FSDMGR!PNPThread: PNPThread starting!
> 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!MountTable_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.
> OSAXST1: >>> Loading Module 'device.dll' (0x83F889EC) at address
> 0xC0380000-0xC0384000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'devmgr.dll' (0x83F88B24) at address
> 0xC0390000-0xC03AF000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x83F88C5C) at address
> 0xC0600000-0xC060A000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'pm.dll' (0x83F88DA4) at address
> 0xC03E0000-0xC0400000 in Process 'NK.EXE' (0x8247BC80)
> *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x400002 ***
> Fil+InitDeviceFileSystems
> FSDMGR!MountTable_t::RegisterVolumeName: Registered "$device" at index
> 5FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5
> (Name="$device",
>
> MountFlags=0x1)FSDMGR!MountTable_t::RegisterVolumeName: Registered "$bus" at
> index 6FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 6
>
> (Name="$bus", MountFlags=0x1)-InitDeviceFileSystems: esys: Loaded device.dll
> FILESYS: Waiting for device manager to signal BootPhase1 completion.
> status is 1
> Ceddk!CalibrateStallCounter: Enter
> Ceddk!CalibrateStallCounter: Could not find stall counter
> Ceddk!BeginCalibration: min(1194) max(1326)
> Ceddk!BeginCalibration: Calibration timed out (51 tries). Defaulting to 1 ms
> resolution.
> PlatformValidatePMRegistryreturningGDA::Chennai::Power Thread Started
> RunningDEVICE!DevloadInit
> DEVICE!InitDevices: Root Key is Drivers\BuiltIn.
> DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix)
> returned 2
> DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix)
> returned 2
> OSAXST1: >>> Loading Module 'busenum.dll' (0x83F7C0C0) at address
> 0xC03D0000-0xC03D8000 in Process 'NK.EXE' (0x8247BC80)
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\CgcePrep\BusPrefix) returned 2
> OSAXST1: >>> Loading Module 'cgceprep.dll' (0x83F75BAC) at address
> 0xC0E10000-0xC0E15000 in Process 'NK.EXE' (0x8247BC80)
> ERROR!!! Calling SetKMode
> ERROR!!! Calling SetKMode
> DeviceFolder::LoadDevice(Drivers\BuiltIn\CgcePrepDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2.
> DEVICE!I_ActivateDeviceEx: can't find all required activation values in
> 'Notify'
> ) last 90 TicksDEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix) returned 2
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2
> OSAXST1: >>> Loading Module 'pcibus.dll' (0x83F75CE4) at address
> 0xC0C60000-0xC0C7A000 in Process 'NK.EXE' (0x8247BC80)
>
>
> ATAPI:PCIConfig!DeviceConfig+(1)
> PCIBUS!PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device
> 31, Function 3
> ATAPI:PCIConfig!DeviceConfig+(1)
> ATAPI:PCIConfig!DeviceConfig+(1)
> ATAPI:PCIConfig!DeviceConfig+(1)
> ATAPI:PCIConfig!DeviceConfig+(1)
> ATAPI:PCIConfig!DeviceConfig+(1)
> OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> ATAPI:PCIConfig!DeviceConfig+(2)
> OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> OSAXST1: >>> Loading Module 'atapi.dll' (0x83F75EDC) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> ATAPI:PCIConfig!DeviceConfig+(3)
> OSAXST1: <<< Unloading Module 'atapi.dll' (0x83F75EDC) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\BusPrefix) returned 2
> OSAXST1: >>> Loading Module 'atapi.dll' (0x83F6609C) at address
> 0xC04C0000-0xC04E8000 in Process 'NK.EXE' (0x8247BC80)
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device0\BusPrefix)
> returned 2
> DEVICE!LaunchDevice: Init() failed for device 0xd004ae70
> DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
> atapi.dll, context 0xd029cf20
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device1\BusPrefix)
> returned 2
> DEVICE!LaunchDevice: Init() failed for device 0xd004b070
> DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
> atapi.dll, context 0xd029cf20
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device2\BusPrefix)
> returned 2
> FILESYS: Waiting for device manager to signal BootPhase1 completion.
> DEVICE!LaunchDevice: Init() failed for device 0xd004b270
> DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
> atapi.dll, context 0xd029cf20
> DEVICE!RegReadActivationValues
> RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\ALI14531\Device3\BusPrefix)
> returned 2
> DEVICE!LaunchDevice: Init() failed for device 0xd004b470
> DEVICE!I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
> atapi.dll, context 0xd029cf20
> DeviceFolder::LoadDevice(Drivers\BuiltIn\PCI\Instance\ALI14531) last 6365
> TicksDeviceFolder::LoadDevice(Drivers\BuiltIn\PCI) last 10275
>
> TicksDEVICE!RegReadActivationValues RegOpenKeyEx(Notify) returned 2.
> DEVICE!I_ActivateDeviceEx: can't find all required activation values in
> 'Notify'
> 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.
> FILESYS: Waiting for bootable file system to be mounted.
>

--

Sankaraj
Thu Jun 07 23:42:04 CDT 2007

Thank you Michel, you are correct, i am having some doubts in that. here is
wat i did to solve...............
; @CESYSGEN IF CE_MODULES_ATAPI
; HIVE BOOT SECTION
; @CESYSGEN IF ATAPI_ATAPI_PCIO_CD
#include-----.reg

; @CESYSGEN ENDIF ATAPI_ATAPI_PCIO_CD
.................
................
(repeated for several individual .reg file)

; END HIVE BOOT SECTION
; @CESYSGEN ENDIF CE_MODULES_ATAPI

I just included HIVE BOOT SECTION and END HIVE BOOT SECTION at each .reg
file. PRJ_ENABLE_FSREGHIVE is set to 1.
If i did not set it to one then the os boots up, but hive is set in ram not
in CF.
I have two doubts
1. Why i need to put the Hive boot sec before all .reg files?
2. If i am not setting PRJ_ENABLE_FSREGHIVE, why it is not reporting error?
Else it should set hive as i am selected hive based reg in my workspace?

Thanks and Regards
Sankarraj

"Michel Verhagen (eMVP)" wrote:

> Well, if you look at the debug output, ATAPI wasn't able to load a
> driver for any of the harddisk (iow, the HD did not respond to
> initialization!). So, there is NO HD mounted that can store the hive,
> and thus CE stalls waiting for it to come online.
>
> Michel Verhagen, eMVP
> EmbeddedFusion
> www.EmbeddedFusion.com
> mverhagen at embeddedfusion dot com
>

Michel
Sun Jun 10 20:25:49 CDT 2007

C inline //

Sankaraj wrote:
> Thank you Michel, you are correct, i am having some doubts in that. here is
> wat i did to solve...............
> ; @CESYSGEN IF CE_MODULES_ATAPI
> ; HIVE BOOT SECTION
> ; @CESYSGEN IF ATAPI_ATAPI_PCIO_CD
> #include-----.reg
>
> ; @CESYSGEN ENDIF ATAPI_ATAPI_PCIO_CD
> .................
> ................
> (repeated for several individual .reg file)
>
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF CE_MODULES_ATAPI
>
> I just included HIVE BOOT SECTION and END HIVE BOOT SECTION at each .reg
> file. PRJ_ENABLE_FSREGHIVE is set to 1.
> If i did not set it to one then the os boots up, but hive is set in ram not
> in CF.
> I have two doubts
> 1. Why i need to put the Hive boot sec before all .reg files?

If you are using hive based registry, you need all drivers you need to
access the store that contains the hive in the "boot" registry. When CE
boots, it boots with a subset of the registry: the boot registry (the
registry keys that are inside HIVE_BOOT_SECTION tags). Using these
registry settings, it loads the "boot-phase" drivers, and then filesys
will load your persisted registry from the store that has the
"MountAsBootable" flag set.

> 2. If i am not setting PRJ_ENABLE_FSREGHIVE, why it is not reporting error?
> Else it should set hive as i am selected hive based reg in my workspace?

If you're using RAM-based registry, you don't need HIVE_BOOT_SECTIONS.
If you do use hive based registry, you DO need them.

Read the docs on Hive Based Registry in MSDN.

Michel Verhagen, eMVP
EmbeddedFusion
www.EmbeddedFusion.com
mverhagen at embeddedfusion dot com


> Thanks and Regards
> Sankarraj
>
> "Michel Verhagen (eMVP)" wrote:
>
>> Well, if you look at the debug output, ATAPI wasn't able to load a
>> driver for any of the harddisk (iow, the HD did not respond to
>> initialization!). So, there is NO HD mounted that can store the hive,
>> and thus CE stalls waiting for it to come online.
>>
>> Michel Verhagen, eMVP
>> EmbeddedFusion
>> www.EmbeddedFusion.com
>> mverhagen at embeddedfusion dot com
>>
>

--