Re: Error 4309 returned when writing files

On May 20, 10:12 am, Ken Hill <kenneth_h...@xxxxxxx> wrote:
On May 19, 7:41 pm, "Michel Verhagen (eMVP)" <mic...@xxxxxxxxxx>
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...@xxxxxxxxxx>
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 ...

read more »

I fixed this "lockup" problem described in my previous post (after
much searching in the NG and blogs). I turned off the "Enable access
to desktop files" feature on the core services settings on the
connectivity settings dialog and now the debug environment works.

I'm getting a whole bunch of 4309 errors in the debug output when I
run my app. I'll spare you the entire debug output, but here is the
last few lines below:

444788 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!CommitStream
returned 4309 for '<ROOT>'
444788 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 4040
444788 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!FindNext:
unexpected error (4309)
444789 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 3929
444789 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 3929
444789 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!CommitStream
returned 4309 for '<ROOT>'
444800 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 3929
444800 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!CommitStream
returned 4309 for '<ROOT>'
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 4040
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!FindNext:
unexpected error (4309)
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 3929
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!CommitStream
returned 4309 for '<ROOT>'
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 4040
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!FindNext:
unexpected error (4309)
444816 PID:43fc9c1a TID:835c3fca 0x8359f890: Read/Write Sector failed
(4309) on Sector 4040
444817 PID:43fc9c1a TID:835c3fca 0x8359f890: FATFS!
FAT_CreateFileW(\rawdata\log00001.dat) returned 0x0 (4309)

I now suspect I have a bad card. I'm swapping out the disk with
another card. I'll keep ya'll posted on what I find...:-)

Cheers,
Ken
.

Relevant Pages

  • NOR flash
    ... WINCE 4.2, Debug Build, RAM based registry, NO PCMCIA/CF. ... invalid BPB, volume deemed invalid ... New extended boot sector successfully written ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Debug and RELFSD
    ... There have been some notes in the past about problems with the kernel ... but if I build a debug version and load it via debug ... Kernel debugger connected. ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Error 4309 returned when writing files
    ... You need to show us the debug output. ... I enabled KITL and the kernel debugger in my retail build and set ...
    (microsoft.public.windowsce.platbuilder)
  • Re: Error 4309 returned when writing files
    ... You need to show us the debug output. ... I enabled KITL and the kernel debugger in my retail build and set ...
    (microsoft.public.windowsce.platbuilder)
  • Re: NAND Flash Query
    ... Kernel debugger is waiting to connect with target. ... 0x87fcf028:>>> Loading module coredll.dll at address 0x03F80000-0x03FF3000 ... doesn't exist for logical sector 0x0!!! ...
    (microsoft.public.windowsce.platbuilder)