WinCE5.0 - Hive Registry

Tutorials Win: Microsoft Windows Forum

Hai everyone,

Subject: WinCE5.0-Hive Registry

First i built a platform with normal default registry it works fine. then i
tried to configure the hive based registry.
To configure a hive registry i did the following 4 steps, build with 0
errors. but when i try to connect to target machine, image downloaded to
machine, after the i did not get the desktop(no response).I am not sure
about system.hv and user.hv files creation, so i did not placed any such
files in the specified registry directory, but i created the
directory"Storage Card\config". do i have to place sytsem.hv, user.hv file
there, if so how to do that, if not what is the issue?
we are using X86, DiskOnChip2000.
KINDLY help me out.

Regards
Sunny

steps
1)Add hive resgistry from catalog to OS

2)EnvironmentVariables
FILESYS_FSREGHIVE=1
BSP_MSYSTEMS_DISKONCHIP=1

3)common.reg
; @CESYSGEN IF FILESYS_FSREGHIVE
; HIVE BOOT SECTION
[HKEY_LOCAL_MACHINE\init\BootVars]
"SystemHive"="Storage Card\\config\\system.hv"
"ProfileDir"="Storage Card\\config"
; "Flags"=dword:0x00000001 | 0x00000002
"Start DevMgr"=dword:1
"DefaultUser"="TBATM"
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF FILESYS_FSREGHIVE


4)DiskOnChip.reg
@CESYSGEN IF CE_MODULES_DEVICE
; HIVE BOOT SECTION
IF BSP_MSYSTEMS_DISKONCHIP
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS]
"Index"=dword:1
"Dll"="TrueFFS.dll"
"Prefix"="DSK"
"Order"=dword:1
"Ioctl"=dword:4
"WindowBase"=dword:D4000
"IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
"Flags"=dword:1000
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
"Name"="DiskOnChip M-Systems"
"Folder"="Storage Card"
"DefaultFileSystem"="FATFS"
MountAsBootable=dword:1
ENDIF BSP_MSYSTEMS_DISKONCHIP
; END HIVE BOOT SECTION
; @CESYSGEN ENDIF
Top

Re: WinCE5.0 - Hive Registry by Gunnar

Gunnar
Wed Feb 08 10:54:30 CST 2006

Hi,

can you post the debug output on your serial port while booting?


> "SystemHive"="Storage Card\\config\\system.hv"
> "ProfileDir"="Storage Card\\config"

You can try to write

"SystemHive"="\\Storage Card\\config\\system.hv"
"ProfileDir"="\\Storage Card\\config"

I think the path is invalid if you don't start with a backslash, so maybe
that's why the system hangs on startup.

Gunnar


Top

Re: WinCE5.0 - Hive Registry by Anthony

Anthony
Wed Feb 08 11:40:10 CST 2006

Did you rebuild your platform with "clean" flag set? I remember problems of
booting image after adding hive support without performing a "clean"
rebuild.

HTH

--
--
--
----------------------------------------------------------------
Anthony Pellerin
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"Sunny" <Sunny@Sunny.com> a écrit dans le message de news:
usm1b8MLGHA.3496@TK2MSFTNGP14.phx.gbl...
> Hai everyone,
>
> Subject: WinCE5.0-Hive Registry
>
> First i built a platform with normal default registry it works fine. then
> i tried to configure the hive based registry.
> To configure a hive registry i did the following 4 steps, build with 0
> errors. but when i try to connect to target machine, image downloaded to
> machine, after the i did not get the desktop(no response).I am not sure
> about system.hv and user.hv files creation, so i did not placed any such
> files in the specified registry directory, but i created the
> directory"Storage Card\config". do i have to place sytsem.hv, user.hv file
> there, if so how to do that, if not what is the issue?
> we are using X86, DiskOnChip2000.
> KINDLY help me out.
>
> Regards
> Sunny
>
> steps
> 1)Add hive resgistry from catalog to OS
>
> 2)EnvironmentVariables
> FILESYS_FSREGHIVE=1
> BSP_MSYSTEMS_DISKONCHIP=1
>
> 3)common.reg
> ; @CESYSGEN IF FILESYS_FSREGHIVE
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "SystemHive"="Storage Card\\config\\system.hv"
> "ProfileDir"="Storage Card\\config"
> ; "Flags"=dword:0x00000001 | 0x00000002
> "Start DevMgr"=dword:1
> "DefaultUser"="TBATM"
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
>
>
> 4)DiskOnChip.reg
> @CESYSGEN IF CE_MODULES_DEVICE
> ; HIVE BOOT SECTION
> IF BSP_MSYSTEMS_DISKONCHIP
> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS]
> "Index"=dword:1
> "Dll"="TrueFFS.dll"
> "Prefix"="DSK"
> "Order"=dword:1
> "Ioctl"=dword:4
> "WindowBase"=dword:D4000
> "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
> "Flags"=dword:1000
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
> "Name"="DiskOnChip M-Systems"
> "Folder"="Storage Card"
> "DefaultFileSystem"="FATFS"
> MountAsBootable=dword:1
> ENDIF BSP_MSYSTEMS_DISKONCHIP
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF
>


Top

Re: WinCE5.0 - Hive Registry by Bruce

Bruce
Wed Feb 08 11:39:19 CST 2006

Did you do a clean build after switching to HIVE?

> [HKEY_LOCAL_MACHINE\init\BootVars]
> "SystemHive"="Storage Card\\config\\system.hv"
> "ProfileDir"="Storage Card\\config"

Don't specify the "Storage Card" part, it uses the first drive that it finds
with the correct flag set.


--
Bruce Eitman (eMVP)
Senior Engineer
beitman AT applieddata DOT net

Applied Data Systems
www.applieddata.net
An ISO 9001:2000 Registered Company
Microsoft WEP Gold-level Member

"Sunny" <Sunny@Sunny.com> wrote in message
news:usm1b8MLGHA.3496@TK2MSFTNGP14.phx.gbl...
> Hai everyone,
>
> Subject: WinCE5.0-Hive Registry
>
> First i built a platform with normal default registry it works fine. then
> i tried to configure the hive based registry.
> To configure a hive registry i did the following 4 steps, build with 0
> errors. but when i try to connect to target machine, image downloaded to
> machine, after the i did not get the desktop(no response).I am not sure
> about system.hv and user.hv files creation, so i did not placed any such
> files in the specified registry directory, but i created the
> directory"Storage Card\config". do i have to place sytsem.hv, user.hv file
> there, if so how to do that, if not what is the issue?
> we are using X86, DiskOnChip2000.
> KINDLY help me out.
>
> Regards
> Sunny
>
> steps
> 1)Add hive resgistry from catalog to OS
>
> 2)EnvironmentVariables
> FILESYS_FSREGHIVE=1
> BSP_MSYSTEMS_DISKONCHIP=1
>
> 3)common.reg
> ; @CESYSGEN IF FILESYS_FSREGHIVE
> ; HIVE BOOT SECTION
> [HKEY_LOCAL_MACHINE\init\BootVars]
> "SystemHive"="Storage Card\\config\\system.hv"
> "ProfileDir"="Storage Card\\config"
> ; "Flags"=dword:0x00000001 | 0x00000002
> "Start DevMgr"=dword:1
> "DefaultUser"="TBATM"
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
>
>
> 4)DiskOnChip.reg
> @CESYSGEN IF CE_MODULES_DEVICE
> ; HIVE BOOT SECTION
> IF BSP_MSYSTEMS_DISKONCHIP
> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS]
> "Index"=dword:1
> "Dll"="TrueFFS.dll"
> "Prefix"="DSK"
> "Order"=dword:1
> "Ioctl"=dword:4
> "WindowBase"=dword:D4000
> "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
> "Flags"=dword:1000
> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
> "Name"="DiskOnChip M-Systems"
> "Folder"="Storage Card"
> "DefaultFileSystem"="FATFS"
> MountAsBootable=dword:1
> ENDIF BSP_MSYSTEMS_DISKONCHIP
> ; END HIVE BOOT SECTION
> ; @CESYSGEN ENDIF
>


Top

Re: WinCE5.0 - Hive Registry - LOG MESSAGE i got in DEBUG WINDOW of platform in DEBUG MODE by Sunny

Sunny
Thu Feb 09 06:38:50 CST 2006

Hi eveyone,

Thanks for replying.
Yes i did clean build after adding hive catatlog item to OS.
now i have added '\\' slashes in fornt of storage card as follows
"SystemHive"="Storage Card\\config\\system.hv" changed as
"SystemHive"="\\Storage Card\\config\\system.hv"
"ProfileDir"="Storage Card\\config" changed as "ProfileDir"="\\Storage
Card\\config"
the following is LOG MESSAGE i got in DEBUG WINDOW of platform in DEBUG
MODE. In the next reply post, i will post the message i got through

DEBUG_SERIAL port(COM1).
Any help is appreciated

Regards
Sunny

0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 g_dwCPUFeatures = 00808131
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
0 PID:0 TID:0 &pTOC = 802279d8, pTOC = 8177911c, pTOC->ulRamFree =
81808000, MemForPT = 00024000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 10160, Secondary pages: 0,
Filesystem pages = 5080
0 PID:0 TID:0
Booting kernel with clean memory configuration:
0 PID:0 TID:0 Memory Sections:
0 PID:0 TID:0 [0] : start: 8182d000, extension: 00003000, length:
027b0000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023dc78.
0 PID:0 TID:0 Windows CE KernelInit
4294767297 PID:3fdf002 TID:3fdf1de Updated eptr->e32_vsize to = 00090000
4294767298 PID:3fdf002 TID:3fdf1de Scheduling the first thread.
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: KernelInit2:
pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit =
80260d90
4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00005000
4294767309 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00022000
4294767310 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00007000
4294767311 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to =
00018000
4294767311 PID:3fdf002 TID:3fdf1de 0x83fdf030: Starting kernel debugger
software probe (KdStub) - KD API version 18
4294767312 PID:3fdf002 TID:3fdf1de 0x83fdf030: Calling KDEnableInt (FALSE,
NULL) without previously calling KDEnableInt (FALSE, p)
4294767321 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module NK.EXE at
address 0x80220000-0x802B0000 (RW data at 0x8177B000-

0x817E91FF)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is X86).
Target name: M1
Probe name: KdStub
Binary Image should be loaded at 0x80220000 / Data relocated at 0x8177b000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\NK.EXE'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\KD.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\OSAXST1.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\OSAXST0.DLL'
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\HD.DLL'
4294767358 PID:3fdf002 TID:3fdf1de 0x83fdf030: first = 01eb0000, last =
02000000, SharedDllBase = 02970000
4294767369 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-

0x01FFF5E5)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\COREDLL.DLL'
4294767381 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation code
for x86... using floating point hardware.
4294767510 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-

0x01FFF5E5)
4294767522 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
filesys.exe at address 0x04010000-0x04081000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\FILESYS.EXE'
4294767535 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: CertMod.dll not found,
using old OEM Trust Model
4294767540 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FileSystem Starting -
starting with clean file system
4294767542 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: initializing ROM/RAM
file system
4294767542 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: SC_CreateAPIHandle: pvData
== NULL
4294767543 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file system
ROM, index 2, flags 0x00000031
4294767543 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Mount complete (ROM,
index 2, flags 0x00000031)
4294767546 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: OEMIoControl: Unsupported
Code 0x101008c - device 0x0101 func 35
4294767552 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Opening existing
volume
4294767554 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Volume heap already
initialized
4294767554 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSREG: Mounted ROM portion
of boot registry
4294767555 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Creating clean
virtual volume
4294767556 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Initializing volume
heap
4294767575 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSREG: Mounted RAM portion
of boot registry
4294767575 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: PCIReg(key:
Drivers\BuiltIn\PCI\Instance\KITL, device: 0/15/0)
4294767590 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
SYSTEM/DevMgrApiSetReady
4294767591 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
SYSTEM/PowerManagerReady
4294767591 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
SYSTEM/GweApiSetReady
4294767592 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
ReleaseFSD
4294767592 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
SYSTEM/NLedAPIsReady
4294767593 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Starting storage
manager.
4294767600 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
fsdmgr.dll at address 0x03D30000-0x03D53000 (RW data at 0x01FDD000-

0x01FDD810)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\FSDMGR.DLL'
4294767613 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file system
StoreMgr, index 3, flags 0x00000001
4294767615 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: InitSharedHeap: 46200000
10000 c
4294767616 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: InitSharedHeap: return
46200060
4294767617 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Restarting storage
manager.
4294767624 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
relfsd.dll at address 0x03E70000-0x03E79000 (RW data at 0x01FEB000-

0x01FEBADC)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\RELFSD.DLL'
4294767643 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file system
Release, index 4, flags 0x00000000
4294767643 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: Mounted ReleaseFSD volume
'\Release'
4294767658 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: size of 'dbglist.txt' =
00000000
4294767660 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Mount complete
(Release, index 4, flags 0x00000000)
4294767661 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Starting device
and waiting for boot file system.
4294767672 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-

0x01FFF5E5)
4294767696 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module pm.dll
at address 0x03F00000-0x03F1D000 (RW data at 0x01FF6000-

0x01FF6708)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\PM.DLL'
4294767708 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
devmgr.dll at address 0x03F40000-0x03F55000 (RW data at 0x01FFC000-

0x01FFC6B4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\DEVMGR.DLL'
4294767721 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
device.exe at address 0x06010000-0x06013000
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\DEVICE.EXE'
4294767736 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InitSharedHeap: 46200000 0
c
4294767737 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InitSharedHeap: return
46200060
4294767738 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Waiting for device to
signal BootPhase1 completion
4294767790 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: *** DLL_PROCESS_ATTACH -
Current Process: 0x42, ID: 0xc3f912b2 ***
4294767819 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: +InitDeviceFileSystems
4294767820 PID:23fc8c1a TID:c3f91282 0x83fc8cf0: FS: Registering file system
$device, index 5, flags 0x00000001
4294767820 PID:23fc8c1a TID:c3f91282 0x83fc8cf0: FS: Registering file system
$bus, index 6, flags 0x00000001
4294767821 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: -InitDeviceFileSystems:
status is 1
4294767823 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
ceddk.dll at address 0x03CD0000-0x03CD7000 (RW data at 0x01FD5000-

0x01FD50CC)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\CEDDK.DLL'
4294767837 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
Ceddk!CalibrateStallCounter: Enter
4294767839 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
Ceddk!CalibrateStallCounter: Could not find stall counter
4294767839 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Ceddk!BeginCalibration:
min(1194) max(1326)
4294767854 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Ceddk!BeginCalibration:
Elapsed is 1316
4294767854 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Ceddk!BeginCalibration:
Delay is 18
4294767875 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: DEVICE!DevloadInit
4294767876 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: DEVICE!InitDevices: Root
Key is Drivers\BuiltIn.
4294767877 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix)
returned 2
4294767877 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix)
returned 2
4294767888 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
busenum.dll at address 0x03F20000-0x03F27000 (RW data at 0x01FF8000-

0x01FF850C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\BUSENUM.DLL'
4294767935 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\TrueFFS\BusPrefix) returned 2
4294767944 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
trueffs.dll at address 0x01EB0000-0x01EE7000
Loaded 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\TRUEFFS.DLL', no
matching symbolic information found.
4294768560 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: TFFSdiskEntry: TrueFFS
DLL_PROCESS_ATTACH
4294768560 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: initPcmciaDll [START]
4294768560 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: initPcmciaDll: loading
DLL...
4294768567 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
pcmcia.dll at address 0x029C0000-0x029D0000 (RW data at 0x01EFA000-

0x01EFA56C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\PCMCIA.DLL'
4294768605 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CardBus.DLL
DLL_PROCESS_ATTACH
4294768605 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: initPcmciaDll [END],
returning TRUE
4294768606 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: TFFSdiskEntry: calling
flInit
4294768607 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init [START]
Drivers\Active\4294967281
4294768607 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init: flinitialized
= 0
4294768608 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig [START]
4294768609 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig:
windowBase=0xd4000
4294768609 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig [END]
4294768609 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: checkRFA[START]
4294768610 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init: After setting
builtIn flinitialized = 0
4294768610 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init: After setting
builtIn = 1
4294768611 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
getBuiltInHandleByActivePath[START]
4294768612 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
getBuiltInHandleByActivePath() Drivers\BuiltIn\TrueFFS
4294768612 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
getBuiltInHandleByActivePath(): len1 = 23 , len2 = 23
4294768612 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
getBuiltInHandleByActivePath()- HANDLE = 0
4294768613 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init: Before
flInit()
4294768613 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: updateSocketParams()
start for volNo = = 0...
4294768614 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskBaseAddres
[START] WindowBase
4294768615 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig:
windowBase=0xd4000
4294768615 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig [END]
4294768616 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: updateSocketParams
[END], flashBase=0xd4000
4294768616 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768617 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(ADDRESS_SHIFT) failed, returned 2
4294768617 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768618 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(AddressShift) failed, returned 2
4294768619 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768619 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(DOC_ACCESS_TYPE) failed, returned 2
4294768620 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768621 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(DocAccessType) failed, returned 2
4294768621 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768622 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(SetPolicy) failed, returned 2
4294768623 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768623 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(RamCheck) failed, returned 2
4294768624 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768625 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(UseCache) failed, returned 2
4294768625 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768626 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(ChainsLength) failed, returned 2
4294768627 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768627 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(MarkDelete) failed, returned 2
4294768628 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768629 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(CustomizeAccess) failed, returned 2
4294768629 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768630 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(Use8Bit) failed, returned 2
4294768631 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:flRegisterComponents():
Registry entry found, windowBase = 0xd4000
4294768631 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: customizeSocket()
customizing cache use, value is 1.
4294768631 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: customizeSocket()
customizing RAM check usage, value is 0.
4294768632 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: customizeSocket()
customizing mark delete, value is 0.
4294768632 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: updateSocketParams()
start for volNo = = 1...
4294768633 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskBaseAddres
[START] DocBase10
4294768634 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig-
RegQueryValueEx(Sckt) returned 2 (87 means no key, it's ok)
4294768634 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flGetDiskConfig Failed
[END]
4294768634 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: flRegisterComponents:
[end]
4294768696 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init:
pgDisk=0x1ee17a0
4294768696 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init:
pgDisk->hSocket.uSocket = 0
pgDisk->builtIn = 1
, pgDisk->activePath = Drivers\Active\4294967281
4294768696 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294768697 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(AutoDPDMode) failed, returned 2
4294768758 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
===============================
4294768758 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: DSK_Init [END] pgDisk =
0x1ee17a0
4294768758 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
===============================
4294769149 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294769150 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(VerifyWrite) failed, returned 2
4294769153 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #:
################################
4294769153 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: mountDisk [START] pDisk
= 0x1ee17a0
4294769154 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: mountDisk(): before
flAbsMountVolume Handle = 0x0
4294769542 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue [START]
4294769543 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: getRegValue:
RegQueryValueEx(VerifyWrite) failed, returned 2
4294769544 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: mountDisk(): After
flAbsMountVolume
4294769544 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: mountDisk [END],
returning 0
4294769605 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: InitFSD [START]
4294769606 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: #: InitFSD [END] -
RegQueryValueEx(FS) returned 2, returning FALSE
4294769607 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix)
returned 2
4294769607 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix) returned 2
4294769616 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
pcibus.dll at address 0x02AF0000-0x02B09000 (RW data at 0x01F0A000-

0x01F0A7B4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\PCIBUS.DLL'
4294769628 PID:c3f912b2 TID:a3f98db2 0x83fca800: #: getRegValue [START]
4294769629 PID:c3f912b2 TID:a3f98db2 0x83fca800: #: getRegValue:
RegQueryValueEx(Profile) failed, returned 2
4294769637 PID:23fc8c1a TID:a3f98db2 0x83fca800: >>> Loading module
mspart.dll at address 0x03D20000-0x03D29000 (RW data at 0x01FDB000-

0x01FDB4B4)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\MSPART.DLL'
4294769707 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769708 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294769708 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769709 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/0/0, Host / PCI Bridge
4294769709 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x1078,
DeviceID = 0x0001, Command = 0x0007, Status = 0x0280
4294769709 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x00, ProgIf
= 0x00, SubClass = 0x00, BaseClass = 0x06
4294769710 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294769710 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294769711 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
4294769711 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294769712 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294769712 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x00,
InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294769713 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769713 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/0/0.
4294769713 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294769717 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769718 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294769718 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769718 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/16/0, VGA Compatible Display Adapter
4294769719 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x102C,
DeviceID = 0x00C0, Command = 0x0083, Status = 0x0280
4294769719 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x64, ProgIf
= 0x00, SubClass = 0x00, BaseClass = 0x03
4294769719 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294769720 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294769720 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0xD0000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
4294769721 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x102C, SubSystemID = 0x00C0
4294769721 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294769722 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x09,
InterruptPin = 0x01, MinGrant = 0x00, MaxLatency = 0x00
4294769722 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769723 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/16/0.
4294769723 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294769725 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769725 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294769725 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769726 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/18/0, PCI / ISA Bridge
4294769726 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x1078,
DeviceID = 0x0100, Command = 0x000F, Status = 0x0280
4294769727 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x30, ProgIf
= 0x00, SubClass = 0x01, BaseClass = 0x06
4294769727 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294769728 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294769728 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0x00000000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
4294769728 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294769729 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294769729 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x00,
InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294769729 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769730 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/18/0.
4294769730 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294769732 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769732 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294769733 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769733 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/18/1, Other Bridge
4294769733 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x1078,
DeviceID = 0x0101, Command = 0x0002, Status = 0x0280
4294769734 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x00, ProgIf
= 0x00, SubClass = 0x80, BaseClass = 0x06
4294769734 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294769734 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294769734 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0x40012000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
4294769735 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294769735 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294769735 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x00,
InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294769735 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769736 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/18/1.
4294769736 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294769738 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769738 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294769738 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294769739 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/18/2, IDE Controller
4294770859 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x1078,
DeviceID = 0x0102, Command = 0x0005, Status = 0x0280
4294770870 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x00, ProgIf
= 0x00, SubClass = 0x01, BaseClass = 0x01
4294770871 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294770871 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294770872 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0x00000000 0x00000000
0x00000000 0x00000000 0x0000F001 0x00000000
4294770873 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294770873 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294770874 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x00,
InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294770874 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294770875 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/18/2.
4294770875 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294770878 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770878 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Warning: No Match template
is found for following PCI Device
4294770878 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294770879 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: Bus/Device/Function =
0/18/3, Audio Multimedia Device
4294770879 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: VendorID = 0x1078,
DeviceID = 0x0103, Command = 0x0006, Status = 0x0280
4294770879 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: RevisionID = 0x00, ProgIf
= 0x00, SubClass = 0x01, BaseClass = 0x04
4294770880 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CacheLineSize = 0x00,
LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294770880 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: BaseAddresses:
4294770881 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: 0x40011000 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000
4294770881 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294770882 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: ROMBaseAddress =
0x00000000
4294770882 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: InterruptLine = 0x00,
InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294770882 PID:c3f912b2 TID:c3f91282
0x83fc8cf0: -------------------------------------------------------------------------------
4294770883 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
WARNING: No matching registry key was found for placed device 0/18/3.
4294770883 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgCheckBARs:
Problems can result if the device is being used while configuring

PCIbus.
4294770885 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgAllocMemSpace:
Failed to place Device resource: Bus 0, Device 18, Function 1
4294770886 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!PCICfgAllocMemSpace:
Failed to place Device resource: Bus 0, Device 18, Function 3
4294770889 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770890 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770896 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770897 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770899 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770900 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770901 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770902 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770904 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770906 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770907 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294770909 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: PCIBUS!RegMatch
RegOpenKeyEx(Drivers\BuiltIn\PCI\Template) returned 2.
4294769740 PID:23fc8c1a TID:a3f98db2 0x83fca800: Loading partition driver
mspart.dll hModule=83F2FA7C
4294770981 PID:23fc8c1a TID:a3f98db2 0x83fca800: Driver mspart.dll loaded
4294770985 PID:23fc8c1a TID:a3f98db2 0x83fca800: Opened the store
hStore=000A5030
4294770986 PID:23fc8c1a TID:a3f98db2 0x83fca800: NumSec=64000
BytesPerSec=512 FreeSec=0 BiggestCreatable=0
4294770987 PID:23fc8c1a TID:a3f98db2 0x83fca800: Partition Part00
NumSectors=63996
4294770987 PID:23fc8c1a TID:a3f98db2 0x83fca800: MSPART!PD_OpenPartition:
dwStoreId=000A5030, PartName=Part00
4294770997 PID:23fc8c1a TID:a3f98db2 0x83fca800: >>> Loading module
fatfsd.dll at address 0x03EB0000-0x03ED1000 (RW data at 0x01FF2000-

0x01FF263C)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\FATFSD.DLL'
4294771197 PID:c3f912b2 TID:c3f91282 0x83fc8cf0:
DEVICE!RegReadActivationValues
RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\KITL\DllName)

returned 2
4294771197 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: DEVICE!I_ActivateDeviceEx:
can't find all required activation values in
'Drivers\BuiltIn\PCI\Instance\KITL'
4294771199 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Starting device
and waiting for boot file system.
4294771224 PID:23fc8c1a TID:a3f98db2 0x83fca800: FSD_MountDisk: mounting
volumes for hDsk=000A4DB0
4294771224 PID:c3f912b2 TID:a3f98db2 0x83fca800: #: getRegValue [START]
4294771225 PID:c3f912b2 TID:a3f98db2 0x83fca800: #: getRegValue:
RegQueryValueEx(Profile) failed, returned 2
4294771227 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!MountDisk:
BPB_HiddenSectors(4) != 0
4294771229 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: access
time updates disabled
4294771229 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: event
logging enabled
4294771229 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: automatic
scanning disabled
4294771230 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: write
verify disabled
4294771230 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: extra FAT
on format disabled
4294771231 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: force
write through enabled
4294771232 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: Codepage
= 1
4294771233 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!OpenVolume: Number of
path cache entries = 50
4294771235 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!InitVolume: driver
disagrees with BPB (BPB CHS=999:16:4)
4294771246 PID:23fc8c1a TID:a3f98db2 0x83fca800: >>> Loading module
diskcache.dll at address 0x03EA0000-0x03EA6000 (RW data at 0x01FF0000-

0x01FF04EC)
Loaded symbols for
'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\DISKCACHE.DLL'
4294771285 PID:23fc8c1a TID:a3f98db2 0x83fca800: CreateCache: Successful.
Cache Size: 31 KB, Start: 1, End: 126.
4294771285 PID:23fc8c1a TID:a3f98db2 0x83fca800: CreateCache: Successful.
Cache Size: 63 KB, Start: 127, End: 63995.
4294771286 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!InitVolume: FAT
version: 16
4294771286 PID:23fc8c1a TID:a3f98db2 0x83fca800: FATFS!InitVolume: Cluster
Size (Sectors): 4
4294771291 PID:23fc8c1a TID:a3f98db2 0x83fca800: FS: Registering file system
Storage Card, index 0, flags 0x00000000
4294771292 PID:23fc8c1a TID:a3f98db2 0x83fca800: FS: Mount complete (Storage
Card, index 0, flags 0x00000000)

"Anthony Pellerin" <apellerin@nospam_adeneo.adetelgroup.com> wrote in
message news:ujid6aNLGHA.2668@tk2msftngp13.phx.gbl...
> Did you rebuild your platform with "clean" flag set? I remember problems
> of booting image after adding hive support without performing a "clean"
> rebuild.
>
> HTH
>
> --
> --
> --
> ----------------------------------------------------------------
> Anthony Pellerin
> ADENEO (ADESET)
> Windows Embedded Consultant
> <apellerin AT adeneo DOT adetelgroup DOT com>
> http://www.adeneo.adetelgroup.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
> "Sunny" <Sunny@Sunny.com> a écrit dans le message de news:
> usm1b8MLGHA.3496@TK2MSFTNGP14.phx.gbl...
>> Hai everyone,
>>
>> Subject: WinCE5.0-Hive Registry
>>
>> First i built a platform with normal default registry it works fine. then
>> i tried to configure the hive based registry.
>> To configure a hive registry i did the following 4 steps, build with 0
>> errors. but when i try to connect to target machine, image downloaded to
>> machine, after the i did not get the desktop(no response).I am not sure
>> about system.hv and user.hv files creation, so i did not placed any such
>> files in the specified registry directory, but i created the
>> directory"Storage Card\config". do i have to place sytsem.hv, user.hv
>> file there, if so how to do that, if not what is the issue?
>> we are using X86, DiskOnChip2000.
>> KINDLY help me out.
>>
>> Regards
>> Sunny
>>
>> steps
>> 1)Add hive resgistry from catalog to OS
>>
>> 2)EnvironmentVariables
>> FILESYS_FSREGHIVE=1
>> BSP_MSYSTEMS_DISKONCHIP=1
>>
>> 3)common.reg
>> ; @CESYSGEN IF FILESYS_FSREGHIVE
>> ; HIVE BOOT SECTION
>> [HKEY_LOCAL_MACHINE\init\BootVars]
>> "SystemHive"="Storage Card\\config\\system.hv"
>> "ProfileDir"="Storage Card\\config"
>> ; "Flags"=dword:0x00000001 | 0x00000002
>> "Start DevMgr"=dword:1
>> "DefaultUser"="TBATM"
>> ; END HIVE BOOT SECTION
>> ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
>>
>>
>> 4)DiskOnChip.reg
>> @CESYSGEN IF CE_MODULES_DEVICE
>> ; HIVE BOOT SECTION
>> IF BSP_MSYSTEMS_DISKONCHIP
>> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS]
>> "Index"=dword:1
>> "Dll"="TrueFFS.dll"
>> "Prefix"="DSK"
>> "Order"=dword:1
>> "Ioctl"=dword:4
>> "WindowBase"=dword:D4000
>> "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
>> "Flags"=dword:1000
>> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
>> "Name"="DiskOnChip M-Systems"
>> "Folder"="Storage Card"
>> "DefaultFileSystem"="FATFS"
>> MountAsBootable=dword:1
>> ENDIF BSP_MSYSTEMS_DISKONCHIP
>> ; END HIVE BOOT SECTION
>> ; @CESYSGEN ENDIF
>>
>
>


Top

Re: WinCE5.0 - Hive Registry - LOG MESSAGE i got through DEBUG_SERIAL port by Sunny

Sunny
Thu Feb 09 06:42:47 CST 2006

Hi eveyone,

Thanks for replying.
in my last reply i have posted the log i got form Debug window of Platform
in DEBUG MODE and the following is the LOG MESSAGE i got through
DEBUG_SERIAL port(COM1) of target in DEBUG MODE.
Any help is appreciated

Regards
Sunny

Microsoft Windows CE Ethernet Bootloader Common Library Version 1.0 Built
Jan 31
2002 15:27:26
Copyright (c) 2000-2001 Microsoft Corporation
Microsoft Windows CE Ethernet Bootloader 3.3 fo
Boot Args @ 0x1DD26
PCI Device Configurations (1 PCI bus(es) present)...
========================================================
Bus, Device, Function = 0, 15, 0
Vendor ID, Device ID = 0x10EC, 0x8139
Base Class, Subclass = 2, 0 => NETWORK_CTLR
Interrupt = 15
BaseAddress[0] = 0xE000 (I/O)
BaseAddress[1] = 0xD2000000 (Memory)
========================================================
Bus, Device, Function = 0, 16, 0
Vendor ID, Device ID = 0x102C, 0x00C0
Base Class, Subclass = 3
Interrupt = 9
BaseAddress[0] = 0xD0000000 (Memory)
========================================================
FindAllPCINetCard: Searching for PCI Ethernet NIC ...
FindALLPCINetCard(0): Found Ethernet NIC (IRQ=15, IOBase=0xE001, Type=4).
FindALLPCINetCard(1): Found Ethernet NIC (IRQ=0, IOBase=0x40012000, Type=2).
FindPCINetCard:Argument IOBASE=0, IRQ=0,TYPE=2
FindPCINetCard:Found 2 PCI Ethernet NIC ...
FindPCINetCard: Found Ethernet NIC (IRQ=15, IOBase=0xE000).
RTL8139InitDMABuffer():: Start[0x200000]-[0x200000] - Size[0x20000]
Tx[0x200000] - Rx[0x201800] - RxLength[0x10000] - RxLengthBit[0x1800]
RTL8139Init():: BaseIO[0xE000] : MemOffset[0x1]
RTL8139Init():: TxBuff[0x200000] - RxBuff[0x201800] - LastRx[0x2117FF]
RTL8139Init:: MAC = 00-07-32-01-9B-D8
RTL8139 ethdbg library: AutoNegotiate..
RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
Returned MAC Address:00:07:32:01:9B:D8
System ready!
Preparing for download...
Using device name: CEPC39896
Using static IP address: 1
+EbootSendBootmeAndWaitForTftp
Sent BOOTME to 255.255.255.255
Locked Down Link 1
Src IP 192.100.0.22 Port 0400 Dest IP 192.100.0.170 Port 0CB5
EthDown::TFTPD_OPEN::boot.bin
-EbootSendBootmeAndWaitForTftp
TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:3, DestAddr.wPort: 3253, SrcAddr.wPort: 1024
TftpReceiver, port: 0x00008900, wkp: 0x0000D403

TFTP link[0]: State:0, DestAddr.wPort: 0, SrcAddr.wPort: 0
TFTP link[1]: State:3, DestAddr.wPort: 3253, SrcAddr.wPort: 1024
TftpReceiver, port: 0x00008900, wkp: 0x0000D403

Found pTOC signature.
ROMHDR at Address 00220044h
RomHdr.ulRAMStart=8177B000h RomHdr.physfirst=80220000h.
Download successful! Jumping to image at 0023DC58h...
Got EDBG_CMD_JUMPIMG
Got EDBG_CMD_CONFIG, flags:0x00000000
Debug Serial Init

SysInit: GDTBase=8177b0e8 IDTBase=817cd340 KData=817ed800
Windows CE Kernel for i486 Built on Jun 24 2004 at 18:28:19
g_pPageDir = 81808000
PCIBIOS:: BIOS Address static map to addr=a00e0000
GetPicRoutingIrqTabl
search_pci_bios start
CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00fa950
bios32_call
_offset=1add0 for CE/PC
Return from First BIOS EAX=49435000
EBX=f0000,ECX=b258 E
DX=ae00
32 PCI BIOS offset located.addr=1ae00
32 PCI BIOS Present
EDX=20494350,EAX
=11 EBX=f0210,ECX=b200
+GetRoutingOption
search_pci_routing
search_pci_routing found entry =a00fddf0 CE/PC
GetRoutingOption, found ROM
vers
ion for Routing table.
GetRoutingOption return SUCCESS .AH=8200
canConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =8200
ScanConfigureIrq: BufferSize = 48 @ address 817d0daa
ScanConfigureIrq: for Bus=0 ,Device=14 SlotNumber=1
INTA_LinkValue=1,INTA_IrqBitMap=deb8
INTB_LinkValue=2,INTB_IrqBitMap=deb8
INTC_LinkValue=3,INTC_IrqBitMap=deb8
INTD_LinkValue=4,INTC_IrqBitMap=deb8
ScanConfigureIrq: for Bus=0 ,Device
INTA_LinkValue=2,INTA_IrqBitMap=deb8
INTB_LinkValue=3,INTB_IrqBitMap=deb8
INTC_LinkValue=4,INTC_IrqBitMap=deb8
INTD_LinkValue=1,INTC_IrqBitMap=deb8
ScanConfigureIrq: LinkNumber=2 associated with irq=15
ScanConfigureIrq: for Bus=0 ,Device=16 SlotNumber=3
INTA_LinkValue=4,INTA_IrqBitMap=deb8
INTB_LinkValue=1,INTB_IrqBitMap=deb8
INTC_LinkValue=2,INTC_IrqBitMap=deb8
INTD_LinkValue=3,INTC_IrqBitMap=deb8
ScanConfigureIrq: LinkNumber=4 associated with irq=9
InitKitlNIC: Searching for PCI Ethernet NIC (dwIrq = F, dwIoBase = E000,
dwDfltT
ype = 4) ...
InitKitlNIC: Found PCI Ethernet NIC (type = 4, IRQ=15, IOBase=0xE000).
RTL8139InitDMABuffer():: Start[0x817D1040]-[0x817D1040] - Size[0x10000]
Tx[0x817D1040] - Rx[0x817D2840] - RxLength[0x8000] - RxLengthBit[0x1000]
RTL8139:: built on [Feb 9 2006] [13:16:23]
RTL8139Init():: BaseIO[0xE000] : MemOffset[0xE000]
RTL8139Init():: TxBuff[0x817D1040] - RxBuff[0x817D2840] - LastRx[0x817DA83F]
RTL8139Init:: MAC = 00-07-32-01-9B
RTL8139 ethdbg library: perform auto negotiate.
RTL8139:: RTL8139HWSetMCRegs():: Set all to 0x00
x86KitlCreateName: Using Device Name 'CEPC39896'
OALKitlCreateName: Using Device Name 'CEPC39896'
KITL: *** Device Name CEPC39896 ***
VBridge:: built on [Feb 9 2006] time [13:16:25]
VBridgeInit()...TX = [16384] bytes -- Rx = [16384] bytes
Tx buffer [0xA17E11E0] to [0xA17E51E0].
Rx buffer [0xA17E5200] to [0xA17E9200].
VBridge:: NK add MAC: [0-7-32-1-9B-D8]
KITL: Connected host IP: 192.100.0.170 Port: 3251
KeyIndex
KeyIndex 1 = -1
KeyIndex 2 = -1
KeyIndex 3 = -1
KeyIndex 4 = -1
KeyIndex 5 = -4194305
KeyIndex 6 = -4194305
KeyIndex 7 = -1
+KITLRegisterDfltClient, service:0
+KITLRegisterDfltClient, service:1
KITLGlobalState == 0x61
Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service PPSH
ProcessAdminMsg: Receive Config message for service DBGMSG
ProcessAdminMsg: Receive Config message for service PPSH
ProcessAdminMsg: Receive Config message for service DBGMSG
+KITLRegisterDfltClient, service:2
ProcessAdminMsg: Receive Config message for service KDBG
ProcessAdminMsg: Receive Config message for service KDBG
MarshalProcessesAsModules: Process ID 0x03FDF002 (NK.EXE) not using
CoreDll.dl
l, may be in startup or shutdown.
MarshalProcessesAsModules: Process ID 0x03FDF002 (NK.EXE) not using
CoreDll.dl
l, may be in startup or shutdown.
MarshalProcessesAsModules: Process ID 0x03FDF002 (NK.EXE) not using
CoreDll.dl
l, may be in startup or shutdown.
GetProcessDebugInfo: Process ID 0x03FDF002 (NK.EXE) not using CoreDll.dll,
may
be in startup or shutdown.
KITL: Leaving polling mode...
KITL Checking client registrations
+RegisterClientPart2: Id 0x00000000
KITL Timer thread started, (hTh: 0x03FDBF96, pTh: 0x83FD0800)
-RegisterClientPart2
+RegisterClientPart2: Id 0x00000001
-RegisterClientPart2
KITL Creating IST
KITL Interrupt thread started (hTh: 0x83FD0F9E, pTh: 0x83FCE800), using
SYSINTR
31
Enabling adapter ints...
+RTL8139EnableInts()..
-RTL8139EnableInts()..


"Anthony Pellerin" <apellerin@nospam_adeneo.adetelgroup.com> wrote in
message news:ujid6aNLGHA.2668@tk2msftngp13.phx.gbl...
> Did you rebuild your platform with "clean" flag set? I remember problems
> of booting image after adding hive support without performing a "clean"
> rebuild.
>
> HTH
>
> --
> --
> --
> ----------------------------------------------------------------
> Anthony Pellerin
> ADENEO (ADESET)
> Windows Embedded Consultant
> <apellerin AT adeneo DOT adetelgroup DOT com>
> http://www.adeneo.adetelgroup.com
> Tél : +33 (0)4.72.18.57.77
> Fax : +33 (0)4.72.18.57.78
> ----------------------------------------------------------------
> "Sunny" <Sunny@Sunny.com> a écrit dans le message de news:
> usm1b8MLGHA.3496@TK2MSFTNGP14.phx.gbl...
>> Hai everyone,
>>
>> Subject: WinCE5.0-Hive Registry
>>
>> First i built a platform with normal default registry it works fine. then
>> i tried to configure the hive based registry.
>> To configure a hive registry i did the following 4 steps, build with 0
>> errors. but when i try to connect to target machine, image downloaded to
>> machine, after the i did not get the desktop(no response).I am not sure
>> about system.hv and user.hv files creation, so i did not placed any such
>> files in the specified registry directory, but i created the
>> directory"Storage Card\config". do i have to place sytsem.hv, user.hv
>> file there, if so how to do that, if not what is the issue?
>> we are using X86, DiskOnChip2000.
>> KINDLY help me out.
>>
>> Regards
>> Sunny
>>
>> steps
>> 1)Add hive resgistry from catalog to OS
>>
>> 2)EnvironmentVariables
>> FILESYS_FSREGHIVE=1
>> BSP_MSYSTEMS_DISKONCHIP=1
>>
>> 3)common.reg
>> ; @CESYSGEN IF FILESYS_FSREGHIVE
>> ; HIVE BOOT SECTION
>> [HKEY_LOCAL_MACHINE\init\BootVars]
>> "SystemHive"="Storage Card\\config\\system.hv"
>> "ProfileDir"="Storage Card\\config"
>> ; "Flags"=dword:0x00000001 | 0x00000002
>> "Start DevMgr"=dword:1
>> "DefaultUser"="TBATM"
>> ; END HIVE BOOT SECTION
>> ; @CESYSGEN ENDIF FILESYS_FSREGHIVE
>>
>>
>> 4)DiskOnChip.reg
>> @CESYSGEN IF CE_MODULES_DEVICE
>> ; HIVE BOOT SECTION
>> IF BSP_MSYSTEMS_DISKONCHIP
>> [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\TrueFFS]
>> "Index"=dword:1
>> "Dll"="TrueFFS.dll"
>> "Prefix"="DSK"
>> "Order"=dword:1
>> "Ioctl"=dword:4
>> "WindowBase"=dword:D4000
>> "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}"
>> "Flags"=dword:1000
>> [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
>> "Name"="DiskOnChip M-Systems"
>> "Folder"="Storage Card"
>> "DefaultFileSystem"="FATFS"
>> MountAsBootable=dword:1
>> ENDIF BSP_MSYSTEMS_DISKONCHIP
>> ; END HIVE BOOT SECTION
>> ; @CESYSGEN ENDIF
>>
>
>


Top

Re: WinCE5.0 - Hive Registry - LOG MESSAGE i got in DEBUG WINDOW of platform in DEBUG MODE by Gunnar

Gunnar
Thu Feb 09 07:10:51 CST 2006

Hi,
sorry I mixed a few things up. The \Storage Card is the correct way to
address the storage card, but of course Bruce is right, that in "SystemHive"
you just have to specify the path to and the name of the hive file, so in
your case it's:
"SystemHive"="config\\system.hv"
to store the hive registry settings in the system.hv file in folder config
on your storage card or
"SystemHive"="system.hv"
to store the information in system.hv file in the root directory of your
storage card.
Make sure that the folder config exists on your storage card. I'm not sure
if the folder is created when it's not existing or that might cause an error
as well.
The drive to store the information on (in your case "Storage Card") is
specified by setting the correct flags "MountFlags"=dword:2 in your Storage
Cards Storage Manager profile. So in your case it should be:
[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\TRUEFFS_DOC]
Gunnar


"Sunny" <Sunny@Sunny.com> wrote in message
news:uc1YQUXLGHA.1180@TK2MSFTNGP09.phx.gbl...
> Hi eveyone,
>
> Thanks for replying.
> Yes i did clean build after adding hive catatlog item to OS.
> now i have added '\\' slashes in fornt of storage card as follows
> "SystemHive"="Storage Card\\config\\system.hv" changed as
> "SystemHive"="\\Storage Card\\config\\system.hv"
> "ProfileDir"="Storage Card\\config" changed as "ProfileDir"="\\Storage
> Card\\config"
> the following is LOG MESSAGE i got in DEBUG WINDOW of platform in DEBUG
> MODE. In the next reply post, i will post the message i got through
>
> DEBUG_SERIAL port(COM1).
> Any help is appreciated
>
> Regards
> Sunny
>
> 0 PID:0 TID:0 CEPC Firmware Init
> 0 PID:0 TID:0 RTC - Status Reg B - 0x02
> 0 PID:0 TID:0 g_dwCPUFeatures = 00808131
> 0 PID:0 TID:0 Looking for rom chain
> 0 PID:0 TID:0 Rom chain NOT found
> 0 PID:0 TID:0 Firmware Init Done.
> 0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000
> 0 PID:0 TID:0 Booting Windows CE version 5.00 for (x86)
> 0 PID:0 TID:0 &pTOC = 802279d8, pTOC = 8177911c, pTOC->ulRamFree =
> 81808000, MemForPT = 00024000
> 0 PID:0 TID:0
> Old or invalid version stamp in kernel structures - starting clean!
> 0 PID:0 TID:0 Configuring: Primary pages: 10160, Secondary pages: 0,
> Filesystem pages = 5080
> 0 PID:0 TID:0
> Booting kernel with clean memory configuration:
> 0 PID:0 TID:0 Memory Sections:
> 0 PID:0 TID:0 [0] : start: 8182d000, extension: 00003000, length:
> 027b0000
> 0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023dc78.
> 0 PID:0 TID:0 Windows CE KernelInit
> 4294767297 PID:3fdf002 TID:3fdf1de Updated eptr->e32_vsize to = 00090000
> 4294767298 PID:3fdf002 TID:3fdf1de Scheduling the first thread.
> 4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: KernelInit2:
> pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit =
> 80260d90
> 4294767298 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
> = 00005000
> 4294767309 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
> = 00022000
> 4294767310 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
> = 00007000
> 4294767311 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize to
> = 00018000
> 4294767311 PID:3fdf002 TID:3fdf1de 0x83fdf030: Starting kernel debugger
> software probe (KdStub) - KD API version 18
> 4294767312 PID:3fdf002 TID:3fdf1de 0x83fdf030: Calling KDEnableInt (FALSE,
> NULL) without previously calling KDEnableInt (FALSE, p)
> 4294767321 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module NK.EXE
> at address 0x80220000-0x802B0000 (RW data at 0x8177B000-
>
> 0x817E91FF)
> Kernel debugger connected.
> The Kernel Debugger connection has been established (Target CPU is X86).
> Target name: M1
> Probe name: KdStub
> Binary Image should be loaded at 0x80220000 / Data relocated at 0x8177b000
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\NK.EXE'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\KD.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\OSAXST1.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\OSAXST0.DLL'
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\HD.DLL'
> 4294767358 PID:3fdf002 TID:3fdf1de 0x83fdf030: first = 01eb0000, last =
> 02000000, SharedDllBase = 02970000
> 4294767369 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
> coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-
>
> 0x01FFF5E5)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\COREDLL.DLL'
> 4294767381 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation code
> for x86... using floating point hardware.
> 4294767510 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
> coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-
>
> 0x01FFF5E5)
> 4294767522 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
> filesys.exe at address 0x04010000-0x04081000
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\FILESYS.EXE'
> 4294767535 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: CertMod.dll not found,
> using old OEM Trust Model
> 4294767540 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FileSystem Starting -
> starting with clean file system
> 4294767542 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: initializing ROM/RAM
> file system
> 4294767542 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: SC_CreateAPIHandle:
> pvData == NULL
> 4294767543 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file
> system ROM, index 2, flags 0x00000031
> 4294767543 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Mount complete (ROM,
> index 2, flags 0x00000031)
> 4294767546 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: OEMIoControl: Unsupported
> Code 0x101008c - device 0x0101 func 35
> 4294767552 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Opening existing
> volume
> 4294767554 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Volume heap
> already initialized
> 4294767554 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSREG: Mounted ROM
> portion of boot registry
> 4294767555 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Creating clean
> virtual volume
> 4294767556 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSVOL: Initializing
> volume heap
> 4294767575 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FSREG: Mounted RAM
> portion of boot registry
> 4294767575 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: PCIReg(key:
> Drivers\BuiltIn\PCI\Instance\KITL, device: 0/15/0)
> 4294767590 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
> SYSTEM/DevMgrApiSetReady
> 4294767591 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
> SYSTEM/PowerManagerReady
> 4294767591 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
> SYSTEM/GweApiSetReady
> 4294767592 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
> ReleaseFSD
> 4294767592 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Creating signal event
> SYSTEM/NLedAPIsReady
> 4294767593 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Starting storage
> manager.
> 4294767600 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
> fsdmgr.dll at address 0x03D30000-0x03D53000 (RW data at 0x01FDD000-
>
> 0x01FDD810)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\FSDMGR.DLL'
> 4294767613 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file
> system StoreMgr, index 3, flags 0x00000001
> 4294767615 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: InitSharedHeap: 46200000
> 10000 c
> 4294767616 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: InitSharedHeap: return
> 46200060
> 4294767617 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Restarting
> storage manager.
> 4294767624 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: >>> Loading module
> relfsd.dll at address 0x03E70000-0x03E79000 (RW data at 0x01FEB000-
>
> 0x01FEBADC)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\RELFSD.DLL'
> 4294767643 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Registering file
> system Release, index 4, flags 0x00000000
> 4294767643 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: Mounted ReleaseFSD volume
> '\Release'
> 4294767658 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: size of 'dbglist.txt' =
> 00000000
> 4294767660 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FS: Mount complete
> (Release, index 4, flags 0x00000000)
> 4294767661 PID:23fc8c1a TID:23fc8bea 0x83fc8a3c: FILESYS: Starting device
> and waiting for boot file system.
> 4294767672 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module
> coredll.dll at address 0x03F60000-0x03FF7000 (RW data at 0x01FFE000-
>
> 0x01FFF5E5)
> 4294767696 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading module pm.dll
> at address 0x03F00000-0x03F1D000 (RW data at 0x01FF6000-
>
> 0x01FF6708)
> Loaded symbols for
> 'C:\WINCE500\PBWORKSPACES\HIVE\RELDIR\CEPC_X86_DEBUG\PM.DLL'
> 4294767708 PID:c3f912b2 TID:c3f91282 0x83fc8cf0: >>> Loading modu