Hello,

We have a WinCE 5.0 Core system running on a 1 Ghz x86 platform. The
hard disk drive is set up as a CF card. Our program previously ran on
WinCE 4.x with no problems, but now we repeatedly get errors when
writing to the disk drive. GetLastError() returns 4309 (resource
required).

I suspect there is some security issue. We have the NoDefaultUser
registry setting set to 0 by default. The platform was started from
an internet appliance base and we have omitted all items we dont use
in order to adhere to the core licensing agreement.

We have no use for any "user" security. We need to be certain it is
defeated, yet I haven't yet determine a successful solution.

Any suggestions would be appreciated.

Thanks,
Ken

Re: Error 4309 returned when writing files by Michel

Michel
Tue May 13 14:13:04 PDT 2008

I doubt it is a security issue. Can you run a debug version of the
kernel (or at least debug version of filesys) and enable all debug zones
for filesys, then show us the debug output?


Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Ken Hill wrote:
> Hello,
>
> We have a WinCE 5.0 Core system running on a 1 Ghz x86 platform. The
> hard disk drive is set up as a CF card. Our program previously ran on
> WinCE 4.x with no problems, but now we repeatedly get errors when
> writing to the disk drive. GetLastError() returns 4309 (resource
> required).
>
> I suspect there is some security issue. We have the NoDefaultUser
> registry setting set to 0 by default. The platform was started from
> an internet appliance base and we have omitted all items we dont use
> in order to adhere to the core licensing agreement.
>
> We have no use for any "user" security. We need to be certain it is
> defeated, yet I haven't yet determine a successful solution.
>
> Any suggestions would be appreciated.
>
> Thanks,
> Ken
>

Re: Error 4309 returned when writing files by Ken

Ken
Mon May 19 06:59:50 PDT 2008

On May 13, 5:13 pm, "Michel Verhagen (eMVP)" <mic...@nospam.box>
wrote:
> I doubt it is a security issue. Can you run a debug version of the
> kernel (or at least debug version of filesys) and enable all debug zones
> for filesys, then show us the debug output?
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog:http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>
> Ken Hill wrote:
> > Hello,
>
> > We have a WinCE 5.0 Core system running on a 1 Ghz x86 platform. The
> > hard disk drive is set up as a CF card. Our program previously ran on
> > WinCE 4.x with no problems, but now we repeatedly get errors when
> > writing to the disk drive. GetLastError() returns 4309 (resource
> > required).
>
> > I suspect there is some security issue. We have the NoDefaultUser
> > registry setting set to 0 by default. The platform was started from
> > an internet appliance base and we have omitted all items we dont use
> > in order to adhere to the core licensing agreement.
>
> > We have no use for any "user" security. We need to be certain it is
> > defeated, yet I haven't yet determine a successful solution.
>
> > Any suggestions would be appreciated.
>
> > Thanks,
> > Ken

Thanks, Michel. I have the kernel debugger running but I cannot start
any programs with it. I can ping my platform but services.exe is not
yet running so I cannot start telnet to access the file system
manually. When I select "services.exe" to start from the "Run
Programs" menu it never shows up in the process view. I'm not
certain what is hanging the debugger up. Any suggestions?

BTW, your blog was quite helpful. As a precaution, I reinstalled PB
and all QFEs. The problem I am observing still persists nevertheless
- I cannot copy a file from the CF card to another location (e.g. Usb
Disk or RAM drive). Moreover, I cannot delete a file on the CF card.

Cheers,
Ken



Re: Error 4309 returned when writing files by Michel

Michel
Mon May 19 16:41:02 PDT 2008

Hi Ken,

You need to show us the debug output. Without it there's no way we can
help you.

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

Ken Hill wrote:
> On May 13, 5:13 pm, "Michel Verhagen (eMVP)" <mic...@nospam.box>
> wrote:
>> I doubt it is a security issue. Can you run a debug version of the
>> kernel (or at least debug version of filesys) and enable all debug zones
>> for filesys, then show us the debug output?
>>
>> Good luck,
>>
>> Michel Verhagen, eMVP
>> Check out my blog:http://GuruCE.com/blog
>>
>> GuruCE Ltd.
>> Microsoft Embedded Partner
>> http://GuruCE.com
>> Consultancy, training and development services.
>>
>> Ken Hill wrote:
>>> Hello,
>>> We have a WinCE 5.0 Core system running on a 1 Ghz x86 platform. The
>>> hard disk drive is set up as a CF card. Our program previously ran on
>>> WinCE 4.x with no problems, but now we repeatedly get errors when
>>> writing to the disk drive. GetLastError() returns 4309 (resource
>>> required).
>>> I suspect there is some security issue. We have the NoDefaultUser
>>> registry setting set to 0 by default. The platform was started from
>>> an internet appliance base and we have omitted all items we dont use
>>> in order to adhere to the core licensing agreement.
>>> We have no use for any "user" security. We need to be certain it is
>>> defeated, yet I haven't yet determine a successful solution.
>>> Any suggestions would be appreciated.
>>> Thanks,
>>> Ken
>
> Thanks, Michel. I have the kernel debugger running but I cannot start
> any programs with it. I can ping my platform but services.exe is not
> yet running so I cannot start telnet to access the file system
> manually. When I select "services.exe" to start from the "Run
> Programs" menu it never shows up in the process view. I'm not
> certain what is hanging the debugger up. Any suggestions?
>
> BTW, your blog was quite helpful. As a precaution, I reinstalled PB
> and all QFEs. The problem I am observing still persists nevertheless
> - I cannot copy a file from the CF card to another location (e.g. Usb
> Disk or RAM drive). Moreover, I cannot delete a file on the CF card.
>
> Cheers,
> Ken
>
>

Re: Error 4309 returned when writing files by Ken

Ken
Tue May 20 07:12:58 PDT 2008

On May 19, 7:41 pm, "Michel Verhagen (eMVP)" <mic...@nospam.box>
wrote:
> Hi Ken,
>
> You need to show us the debug output. Without it there's no way we can
> help you.
>
> Good luck,
>
> Michel Verhagen, eMVP
> Check out my blog:http://GuruCE.com/blog
>
> GuruCE Ltd.
> Microsoft Embedded Partner
> http://GuruCE.com
> Consultancy, training and development services.
>
> Ken Hill wrote:
> > On May 13, 5:13 pm, "Michel Verhagen (eMVP)" <mic...@nospam.box>
> > wrote:
> >> I doubt it is a security issue. Can you run a debug version of the
> >> kernel (or at least debug version of filesys) and enable all debug zones
> >> for filesys, then show us the debug output?
>
> >> Good luck,
>
> >> Michel Verhagen, eMVP
> >> Check out my blog:http://GuruCE.com/blog
>
> >> GuruCE Ltd.
> >> Microsoft Embedded Partner
> >> http://GuruCE.com
> >> Consultancy, training and development services.
>
> >> Ken Hill wrote:
> >>> Hello,
> >>> We have a WinCE 5.0 Core system running on a 1 Ghz x86 platform. The
> >>> hard disk drive is set up as a CF card. Our program previously ran on
> >>> WinCE 4.x with no problems, but now we repeatedly get errors when
> >>> writing to the disk drive. GetLastError() returns4309(resource
> >>> required).
> >>> I suspect there is some security issue. We have the NoDefaultUser
> >>> registry setting set to 0 by default. The platform was started from
> >>> an internet appliance base and we have omitted all items we dont use
> >>> in order to adhere to the core licensing agreement.
> >>> We have no use for any "user" security. We need to be certain it is
> >>> defeated, yet I haven't yet determine a successful solution.
> >>> Any suggestions would be appreciated.
> >>> Thanks,
> >>> Ken
>
> > Thanks, Michel. I have the kernel debugger running but I cannot start
> > any programs with it. I can ping my platform but services.exe is not
> > yet running so I cannot start telnet to access the file system
> > manually. When I select "services.exe" to start from the "Run
> > Programs" menu it never shows up in the process view. I'm not
> > certain what is hanging the debugger up. Any suggestions?
>
> > BTW, your blog was quite helpful. As a precaution, I reinstalled PB
> > and all QFEs. The problem I am observing still persists nevertheless
> > - I cannot copy a file from the CF card to another location (e.g. Usb
> > Disk or RAM drive). Moreover, I cannot delete a file on the CF card.
>
> > Cheers,
> > Ken

Michel,

I enabled KITL and the kernel debugger in my retail build and set
BSP_ICS_PUBLIC_VMINI=1 and the system comes all the way up. But when
I run the debug build I get the following:

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 = afe9fbff
0 PID:0 TID:0 g_nMtrrCnt = 8
0 PID:0 TID:0 MTRR PhysMask0: 0000000fe0000800
0 PID:0 TID:0 MTRR PhysBase0: 0000000000000006
0 PID:0 TID:0 MTRR PhysMask1: 0000000ffe000800
0 PID:0 TID:0 MTRR PhysBase1: 000000001e000000
0 PID:0 TID:0 MTRR PhysMask2: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase2: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask3: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase3: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask4: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase4: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask5: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase5: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask6: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase6: 0000000000000000
0 PID:0 TID:0 MTRR PhysMask7: 0000000f00000000
0 PID:0 TID:0 MTRR PhysBase7: 0000000000000000
0 PID:0 TID:0 PhysMask0: 0000000fe0000800
0 PID:0 TID:0 PhysMask1: 0000000ffe000800
0 PID:0 TID:0 PhysMask2: 0000000f00000000
0 PID:0 TID:0 PhysMask3: 0000000f00000000
0 PID:0 TID:0 PhysMask4: 0000000f00000000
0 PID:0 TID:0 PhysMask5: 0000000f00000000
0 PID:0 TID:0 PhysMask6: 0000000f00000000
0 PID:0 TID:0 PhysMask7: 0000000f00000000
0 PID:0 TID:0 g_nMtrrInuse = 2
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 = 80227b58, pTOC = 81c3bf00, pTOC->ulRamFree
= 81cce000, MemForPT = 00004000
0 PID:0 TID:0
Old or invalid version stamp in kernel structures - starting clean!
0 PID:0 TID:0 Configuring: Primary pages: 8970, Secondary pages:
0, Filesystem pages = 4485
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: 81cd3000, extension: 00003000,
length: 0230a000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023edb8.
0 PID:0 TID:0 Windows CE KernelInit
4294767297 PID:3fdf002 TID:3fdf1de Updated eptr->e32_vsize to =
00092000
4294767297 PID:3fdf002 TID:3fdf1de Scheduling the first thread.
4294767299 PID:3fdf002 TID:3fdf1de 0x83fdf030: KernelInit2:
pCurThread=83fdf030 hCurThread=03fdf1de hCurProc=03fdf002, KernelInit
= 80261ed0
4294767300 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize
to = 00005000
4294767301 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize
to = 00022000
4294767303 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize
to = 00007000
4294767304 PID:3fdf002 TID:3fdf1de 0x83fdf030: Updated eptr->e32_vsize
to = 00018000
4294767305 PID:3fdf002 TID:3fdf1de 0x83fdf030: Starting kernel
debugger software probe (KdStub) - KD API version 18
4294767307 PID:3fdf002 TID:3fdf1de 0x83fdf030: Calling KDEnableInt
(FALSE, NULL) without previously calling KDEnableInt (FALSE, p)
4294767317 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
NK.EXE at address 0x80220000-0x802B2000 (RW data at
0x81C3E000-0x81CAC2DF)
Kernel debugger connected.
The Kernel Debugger connection has been established (Target CPU is
X86).
Target name: CE Device
Probe name: KdStub
Binary Image should be loaded at 0x80220000 / Data relocated at
0x81c3e000
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\NK.EXE'
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\KD.DLL'
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\OSAXST1.DLL'
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\OSAXST0.DLL'
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\HD.DLL'
4294767357 PID:3fdf002 TID:3fdf1de 0x83fdf030: first = 01db0000, last
= 02000000, SharedDllBase = 022b0000
4294767359 PID:3fdf002 TID:3fdf1de 0x83fdf030: >>> Loading module
coredll.dll at address 0x03F50000-0x03FF3000 (RW data at
0x01FFE000-0x01FFF785)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\COREDLL.DLL'
4294767374 PID:3fdf002 TID:3fdf1de 0x83fdf030: Did not find emulation
code for x86... using floating point hardware.
4294767488 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: >>> Loading module
coredll.dll at address 0x03F50000-0x03FF3000 (RW data at
0x01FFE000-0x01FFF785)
4294767501 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: >>> Loading module
filesys.exe at address 0x04010000-0x04084000
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\FILESYS.EXE'
4294767514 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: CertMod.dll not
found, using old OEM Trust Model
4294767514 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FileSystem Starting -
starting with clean file system
4294767515 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: initializing ROM/
RAM file system
4294767515 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: SC_CreateAPIHandle:
pvData == NULL
4294767515 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Registering file
system ROM, index 2, flags 0x00000031
4294767515 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Mount complete
(ROM, index 2, flags 0x00000031)
4294767516 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: OEMIoControl:
Unsupported Code 0x101008c - device 0x0101 func 35
4294767516 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSVOL: Opening
existing volume
4294767517 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSVOL: Volume heap
already initialized
4294767517 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSREG: Mounted ROM
portion of boot registry
4294767517 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSVOL: Creating clean
virtual volume
4294767517 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSVOL: Initializing
volume heap
4294767519 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FSREG: Mounted RAM
portion of boot registry
4294767519 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: PCIReg(key: Drivers
\BuiltIn\PCI\Instance\KITL, device: 1/3/0)
4294767520 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event SYSTEM/DevMgrApiSetReady
4294767520 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event SYSTEM/PowerManagerReady
4294767520 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event SYSTEM/GweApiSetReady
4294767528 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event ReleaseFSD
4294767528 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event SYSTEM/BatteryAPIsReady
4294767528 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Creating signal
event SYSTEM/NLedAPIsReady
4294767528 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FILESYS: Starting
storage manager.
4294767529 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: >>> Loading module
fsdmgr.dll at address 0x03CD0000-0x03CF3000 (RW data at
0x01FD4000-0x01FD4810)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\FSDMGR.DLL'
4294767543 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Registering file
system StoreMgr, index 3, flags 0x00000001
4294767543 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: InitSharedHeap:
46200000 10000 c
4294767544 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: InitSharedHeap:
return 46200060
4294767544 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FILESYS: Restarting
storage manager.
4294767545 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: >>> Loading module
relfsd.dll at address 0x03E60000-0x03E69000 (RW data at
0x01FEB000-0x01FEBADC)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\RELFSD.DLL'
4294767559 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Registering file
system Release, index 4, flags 0x00000000
4294767559 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: Mounted ReleaseFSD
volume '\Release'
4294767578 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: size of 'dbglist.txt'
= 00000000
4294767579 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Mount complete
(Release, index 4, flags 0x00000000)
4294767579 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FILESYS: Starting
device and waiting for boot file system.
4294767580 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
coredll.dll at address 0x03F50000-0x03FF3000 (RW data at
0x01FFE000-0x01FFF785)
4294767595 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
pm.dll at address 0x03EF0000-0x03F0D000 (RW data at
0x01FF6000-0x01FF6708)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\PM.DLL'
4294767608 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
devmgr.dll at address 0x03F30000-0x03F45000 (RW data at
0x01FFC000-0x01FFC6B4)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\DEVMGR.DLL'
4294767621 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
device.exe at address 0x06010000-0x06013000
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\DEVICE.EXE'
4294767635 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InitSharedHeap:
46200000 0 c
4294767635 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InitSharedHeap:
return 46200060
4294767635 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FS: Waiting for
device to signal BootPhase1 completion
4294767709 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ***
DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0xc3f9457a ***
4294767736 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
+InitDeviceFileSystems
4294767736 PID:43fc9c1a TID:c3f9454a 0x83fc9cf0: FS: Registering file
system $device, index 5, flags 0x00000001
4294767736 PID:43fc9c1a TID:c3f9454a 0x83fc9cf0: FS: Registering file
system $bus, index 6, flags 0x00000001
4294767736 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: -
InitDeviceFileSystems: status is 1
4294767737 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
ceddk.dll at address 0x03C30000-0x03C37000 (RW data at
0x01FC6000-0x01FC60CC)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\CEDDK.DLL'
4294767750 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Ceddk!
CalibrateStallCounter: Enter
4294767750 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Ceddk!
CalibrateStallCounter: Could not find stall counter
4294767750 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Ceddk!
BeginCalibration: min(1194) max(1326)
4294767774 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Ceddk!
BeginCalibration: Elapsed is 1310
4294767774 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Ceddk!
BeginCalibration: Delay is 261
4294767778 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!DevloadInit
4294767778 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!InitDevices:
Root Key is Drivers\BuiltIn.
4294767778 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix)
returned 2
4294767778 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix)
returned 2
4294767779 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
busenum.dll at address 0x03F10000-0x03F17000 (RW data at
0x01FF8000-0x01FF850C)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\BUSENUM.DLL'
4294767820 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Prefix)
returned 2
4294767820 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\BusPrefix)
returned 2
4294767821 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
pcibus.dll at address 0x02670000-0x02689000 (RW data at
0x01E18000-0x01E187B4)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\PCIBUS.DLL'
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/0/0, Host / PCI Bridge
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x3580, Command = 0x0006, Status = 0x2090
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x06
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000008
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x3580
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/0/0.
4294767861 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767862 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767862 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767862 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/0/1, Unknown Device Type
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x3584, Command = 0x0006, Status = 0x0080
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x80, BaseClass = 0x08
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x3584
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767865 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/0/1.
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767866 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/0/3, Unknown Device Type
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x3585, Command = 0x0006, Status = 0x0080
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x80, BaseClass = 0x08
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x3585
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/0/3.
4294767867 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/2/0, VGA Compatible Display Adapter
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x3582, Command = 0x0007, Status = 0x0090
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x03
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767868 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0xD8000008
0xE8180000 0x0000E301 0x00000000 0x00000000 0x00000000
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x3582
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0C, InterruptPin = 0x01, MinGrant = 0x00, MaxLatency = 0x00
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/2/0.
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767869 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767870 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/2/1, Other Display Adapter
4294767880 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x3582, Command = 0x0007, Status = 0x0090
4294767880 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x80, BaseClass = 0x03
4294767880 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767880 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0xE0000008
0xE8100000 0x00000000 0x00000000 0x00000000 0x00000000
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x3582
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/2/1.
4294767881 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/29/0, UHCI USB Bus Controller
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C2, Command = 0x0005, Status = 0x0280
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x03, BaseClass = 0x0C
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x0000E001 0x00000000
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x24C2
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0C, InterruptPin = 0x01, MinGrant = 0x00, MaxLatency = 0x00
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/29/0.
4294767883 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767884 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767884 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767884 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/29/1, UHCI USB Bus Controller
4294767884 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C4, Command = 0x0005, Status = 0x0280
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x03, BaseClass = 0x0C
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x0000E101 0x00000000
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x24C2
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0C, InterruptPin = 0x02, MinGrant = 0x00, MaxLatency = 0x00
4294767885 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767911 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/29/1.
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/29/2, UHCI USB Bus Controller
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C7, Command = 0x0005, Status = 0x0280
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x03, BaseClass = 0x0C
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767912 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x0000E201 0x00000000
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x24C2
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x09, InterruptPin = 0x03, MinGrant = 0x00, MaxLatency = 0x00
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/29/2.
4294767913 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767914 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767914 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767914 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/29/7, Unknown Device Type
4294767927 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24CD, Command = 0x0006, Status = 0x0290
4294767927 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x20, SubClass = 0x03, BaseClass = 0x0C
4294767927 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767927 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767927 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0xE8200000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x24CD
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0B, InterruptPin = 0x04, MinGrant = 0x00, MaxLatency = 0x00
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/29/7.
4294767928 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767929 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/30/0.
4294767929 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
1/4/0, Ethernet Network Controller
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x10EC,
DeviceID = 0x8139, Command = 0x0007, Status = 0x0290
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x10,
ProgIf = 0x00, SubClass = 0x00, BaseClass = 0x02
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x20, HeaderType = 0x00, BIST = 0x00
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x0000D101
0xE8001000 0x00000000 0x00000000 0x00000000 0x00000000
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x10EC, SubSystemID = 0x8139
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0B, InterruptPin = 0x01, MinGrant = 0x20, MaxLatency = 0x40
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 1/4/0.
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 1/5/0.
4294767930 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767932 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767932 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/31/0, PCI / ISA Bridge
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C0, Command = 0x000F, Status = 0x0280
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x01, BaseClass = 0x06
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x80, BIST = 0x00
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x00000000 0x00000000
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x0000, SubSystemID = 0x0000
4294767943 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767944 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x00, InterruptPin = 0x00, MinGrant = 0x00, MaxLatency = 0x00
4294767944 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767944 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/31/0.
4294767944 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767946 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Loaded 'ichide.dll', no matching symbolic information found.
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/31/3, Unknown Device Type
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C3, Command = 0x0001, Status = 0x0280
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x05, BaseClass = 0x0C
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767959 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x00000000
0x00000000 0x00000000 0x00000000 0x00000501 0x00000000
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x8086, SubSystemID = 0x24C2
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0B, InterruptPin = 0x02, MinGrant = 0x00, MaxLatency = 0x00
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/31/3.
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Warning: No Match
template is found for following PCI Device
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: Bus/Device/Function =
0/31/5, Audio Multimedia Device
4294767960 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: VendorID = 0x8086,
DeviceID = 0x24C5, Command = 0x0007, Status = 0x0290
4294767961 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: RevisionID = 0x02,
ProgIf = 0x00, SubClass = 0x01, BaseClass = 0x04
4294767961 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CacheLineSize =
0x00, LatencyTimer = 0x00, HeaderType = 0x00, BIST = 0x00
4294767961 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: BaseAddresses:
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: 0x0000E501
0x0000E601 0xE8201000 0xE8202000 0x00000000 0x00000000
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: CIS = 0x00000000,
SubVendorID = 0x414C, SubSystemID = 0x4770
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: ROMBaseAddress =
0x00000000
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: InterruptLine =
0x0B, InterruptPin = 0x02, MinGrant = 0x00, MaxLatency = 0x00
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0:
-------------------------------------------------------------------------------
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: WARNING: No matching registry key was found for
placed device 0/31/5.
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgCheckBARs: Problems can result if the device is being
used while configuring PCIbus.
4294767962 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgAllocMemSpace: Failed to place Device resource: Bus 0, Device 0,
Function 0
4294767963 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: PCIBUS!
PCICfgAllocIoSpace: Failed to place Device resource: Bus 0, Device 31,
Function 3
4294767963 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: <<< Unloading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Unloaded symbols for 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK
\INTL_ATAPI\BIN\X86\RETAIL\ICHIDE.DLL'
4294767982 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Loaded 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK\INTL_ATAPI\BIN
\X86\RETAIL\ICHIDE.DLL', no matching symbolic information found.
4294767996 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: <<< Unloading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Unloaded symbols for 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK
\INTL_ATAPI\BIN\X86\RETAIL\ICHIDE.DLL'
4294768009 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Loaded 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK\INTL_ATAPI\BIN
\X86\RETAIL\ICHIDE.DLL', no matching symbolic information found.
4294768021 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: <<< Unloading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Unloaded symbols for 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK
\INTL_ATAPI\BIN\X86\RETAIL\ICHIDE.DLL'
4294768308 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\ICHx1\BusPrefix) returned 2
4294768309 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: >>> Loading module
ichide.dll at address 0x024E0000-0x024EC000 (RW data at
0x01DFE000-0x01DFE1A8)
Loaded 'C:\WINCE500\PUBLIC\ADVANTECH\DRIVERS\BLOCK\INTL_ATAPI\BIN
\X86\RETAIL\ICHIDE.DLL', no matching symbolic information found.
4294768322 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\ICHx1\Device0\BusPrefix) returned 2
4294768387 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!LaunchDevice:
Init() failed for device 0x00031f20
4294768387 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
ichide.dll, context 0x602d0dc
4294768387 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\ICHx1\Device1\BusPrefix) returned 2
4294768388 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!LaunchDevice:
Init() failed for device 0x00033f20
4294768388 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
I_ActivateDeviceEx: couldn't activate: prefix DSK, index 1, dll
ichide.dll, context 0x602d0dc
4294768388 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\ICHx1\Device2\BusPrefix) returned 2
4294768570 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\ICHx1\Device3\BusPrefix) returned 2
4294768576 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!LaunchDevice:
Init() failed for device 0x00034d10
4294768576 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
I_ActivateDeviceEx: couldn't activate: prefix DSK, index 2, dll
ichide.dll, context 0x602d0dc
4294768576 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance
\KITL\DllName) returned 2
4294768576 PID:c3f9457a TID:c3f9454a 0x83fc9cf0: DEVICE!
I_ActivateDeviceEx: can't find all required activation values in
'Drivers\BuiltIn\PCI\Instance\KITL'
4294768578 PID:43fc9c1a TID:63f972a2 0x83fcb800: >>> Loading module
mspart.dll at address 0x03CC0000-0x03CC9000 (RW data at
0x01FD2000-0x01FD24B4)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\MSPART.DLL'
4294768590 PID:43fc9c1a TID:43fc9bea 0x83fc9a3c: FILESYS: Starting
device and waiting for boot file system.
4294768616 PID:43fc9c1a TID:63f972a2 0x83fcb800: Loading partition
driver mspart.dll hModule=83F2ACAC
4294768616 PID:43fc9c1a TID:63f972a2 0x83fcb800: Driver mspart.dll
loaded
4294768617 PID:43fc9c1a TID:63f972a2 0x83fcb800: Opened the store
hStore=000A5480
4294768618 PID:43fc9c1a TID:63f972a2 0x83fcb800: NumSec=2001888
BytesPerSec=512 FreeSec=4032 BiggestCreatable=4032
4294768618 PID:43fc9c1a TID:63f972a2 0x83fcb800: Partition Part00
NumSectors=1997793
4294768618 PID:43fc9c1a TID:63f972a2 0x83fcb800: MSPART!
PD_OpenPartition: dwStoreId=000A5480, PartName=Part00
4294768619 PID:43fc9c1a TID:63f972a2 0x83fcb800: >>> Loading module
fatfsd.dll at address 0x03EA0000-0x03EC2000 (RW data at
0x01FF2000-0x01FF263C)
Loaded symbols for 'C:\WINCE500\PBWORKSPACES\HTT2171\RELDIR
\CEPC_X86_DEBUG\FATFSD.DLL