I created a tiny kernel OS image for the CE 4.20 emulator. This all works
fine in release and debug builds. Then I added TCP/IP 4 from the catalog.
When I create a release build everything works fine. But when I create a
debug build, and try to "Download/Intialize" from Platform builder,
I get a "First chance exception in NK.EXE. (0xC000001C:
Invalid System Service)" dialog. I made sure "Enable Full Kernel Mode",
"Enable Images Larger than 32MB" and "Enable Kernel Debugger" are all
selected. "Enable CE Target Control Support", "Enable EBoot Space in
Memory" and "Enable KITL" are also selected. What am I doing wrong?
Kernel debugger is waiting to connect with target.
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 X86Init done, OEMAddressTable = 8026a648.
Welcome to the Windows CE Shell. Type ? for help.
Kernel debugger failed to connect with target (KDBG open stream failed).
Debugger could not initialize connection.
Kernel debugger is waiting to connect with target.
0 PID:0 TID:0 CEPC Firmware Init
0 PID:0 TID:0 RTC - Status Reg B - 0x02
0 PID:0 TID:0 PCIBIOS:: BIOS Address static map to addr=a00e0000
0 PID:0 TID:0 GetPicRoutingIrqTable: Start
0 PID:0 TID:0 search_pci_bios start
0 PID:0 TID:0 search_pci_bios end fails
0 PID:0 TID:0 GetPicRoutingIrqTable: FAILS!!!
0 PID:0 TID:0 Firmware Init Done.
0 PID:0 TID:0 Looking for rom chain
0 PID:0 TID:0 Rom chain NOT found
0 PID:0 TID:0 Booting Windows CE version 4.20 for (x86)
0 PID:0 TID:0 &pTOC = 80245a78, pTOC = 804a071c, pTOC->ulRamFree =
80511000, 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: 15078, Secondary pages: 0,
Filesystem pages = 7539
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: 80516000, extension: 00004000, length:
03ae6000
0 PID:0 TID:0 X86Init done, OEMAddressTable = 802ab7b8.
0 PID:0 TID:0 Windows CE KernelInit
4294767306 PID:3fff002 TID:3fff1da Updated eptr->e32_vsize to = 00080000
4294767316 PID:3fff002 TID:3fff1da Scheduling the first thread.
4294767316 PID:3fff002 TID:3fff1da 0x83fff030: KernelInit2:
pCurThread=83fff030 hCurThread=03fff1da hCurProc=03fff002, KernelInit =
8028be3e
4294767336 PID:3fff002 TID:3fff1da 0x83fff030: Updated eptr->e32_vsize to =
00010000
4294767356 PID:3fff002 TID:3fff1da 0x83fff030: >>> Loading module NK.EXE at
address 0x80240000-0x802C0000 (RW data at 0x804D3000-0x8050648B)
Kernel debugger connected (KDBG stream opened).
Kernel Version 1169 Checked loaded at 0x80240000, data relocated at
0x804d3000
Debugger connection established (Target CPU is X86).
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\NK.EXE'
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\KD.DLL'
Finished re-loading kernel modules.
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\COREDLL.DLL'
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\FILESYS.EXE'
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\FSDMGR.DLL'
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\RELFSD.DLL'
4294767406 PID:3fff002 TID:3fff1da 0x83fff030: first = 01fb0000, last =
02000000, SharedDllBase = 03d10000
4294767436 PID:3fff002 TID:3fff1da 0x83fff030: >>> Loading module
coredll.dll at address 0x03FB0000-0x03FF5000 (RW data at
0x01FFF000-0x01FFF7B0)
4294767466 PID:3fff002 TID:3fff1da 0x83fff030: Did not find emulation code
for x86... using floating point hardware.
4294767556 PID:a3feff4a TID:a3feff1a 0x83fefd70: >>> Loading module
filesys.exe at address 0x04010000-0x0404E000
4294767606 PID:a3feff4a TID:a3feff1a 0x83fefd70: FileSystem Starting -
starting with clean file system
4294767706 PID:a3feff4a TID:a3feff1a 0x83fefd70: >>> Loading module
fsdmgr.dll at address 0x03F60000-0x03F77000 (RW data at
0x01FF7000-0x01FF7760)
4294767756 PID:a3feff4a TID:a3feff1a 0x83fefd70: >>> Loading module
relfsd.dll at address 0x03F90000-0x03F99000 (RW data at
0x01FFB000-0x01FFBABC)
4294767806 PID:a3feff4a TID:a3feff1a 0x83fefd70: FSREG: Logging in default
user.
4294767806 PID:a3feff4a TID:a3feff1a 0x83fefd70: SetCurrentUser: Logging out
(nobody), logging in default
4294767806 PID:a3feff4a TID:a3feff1a 0x83fefd70: FS: Using default path
"\profiles\"
4294767816 PID:a3feff4a TID:a3feff1a 0x83fefd70: SetCurrentUser: User hives
not supported -- using same registry for all users
4294767816 PID:a3feff4a TID:a3feff1a 0x83fefd70: FS: Using default path
"Windows\"
4294767866 PID:a3feff4a TID:a3feff1a 0x83fefd70: FS: Using default path
"Windows\"
4294767946 PID:a3feff4a TID:43fd1fd2 0x83ff2db8: Mounted ReleaseFSD volume
'\Release'
4294767996 PID:a3feff4a TID:a3feff1a 0x83fefd70: Filesystem initialized!
4294767996 PID:3fff002 TID:e3ff2f92 0x83fef800: InitializeJit
4294767996 PID:3fff002 TID:e3ff2f92 0x83fef800: InitMUI: DISABLED
(-2145012568)
4294768246 PID:e3fefbb2 TID:e3fcbc32 0x83ff2db8: >>> Loading module
toolhelp.dll at address 0x03F80000-0x03F84000 (RW data at
0x01FF9000-0x01FF9054)
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\TOOLHELP.DLL'
4294768256 PID:e3fefbb2 TID:e3fcbc32 0x83ff2db8: >>> Loading module
shell.exe at address 0x06010000-0x06023000
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\SHELL.EXE'
4294768366 PID:83fd1fd2 TID:83fcb93a 0x83fcba88: >>> Loading module
device.exe at address 0x08010000-0x0801C000
Loaded symbols for
'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\DEVICE.EXE'
4294768556 PID:83fcba5a TID:83fefd32 0x83fef800: >>> Loading module
ceemulsrv.exe at address 0x0A010000-0x0A014000
Loaded 'C:\WINCE420\PUBLIC\GCUSTOM\RELDIR\EMULATOR_X86DEBUG\CEEMULSRV.EXE',
no matching symbolic information found.
4294768576 PID:a3feff4a TID:83fefd32 0x83fef800: ObjectCall: Failed(1): 16
4294768576 PID:a3feff4a TID:83fefd32 0x83fef800: Exception ffffffff
Thread=83fef800 Proc=a3feff4a 'filesys.exe'
4294768576 PID:a3feff4a TID:83fefd32 0x83fef800: AKY=00000013 PC=8029c33a
ESP=0a11d5c0 EA=00000000
Debugger disconnected successfully.