Graphical Shell problems

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - How to add a virtual WAV driver ? Hi all: My paltform,CE5.0,already has a buildin WAV driver(for AC97).And,I want to add a virtual WAV driver,which does only for Bluetooth AG routing.How can i do it ? And I find a parameter uDeviceID in waveOutOpen(), how do I use it? Anything else to be setted in the registry ? Tag: Graphical Shell problems Tag: 71690
  - 2
    - Info needed about CSP Hi, I'm newbie Win CE, I have CSP Driver sources for ARM Processor can I use the same sources for creating new CE 4.2 BSP and CE 5.0 BSP on it, using appropriate PB. Thanx & Regards, John Tag: Graphical Shell problems Tag: 71688
  - 3
    - Missing tools to install SDK (PB5.0) Hello I have installed PB 5.0 and eVC SP4. When i create an SDK from PB and then try and install i get the following dialog box : 'software development tools required to use this SDK for developing apps are not installed on this dev station .....' This dialog links to a webpage where I can download (again) eVC and some other things that I suppose are already installed or on PB5.0 CDROM. Using PB4.2 I never had those problems installink a custom SDK. What is missing ? What do I need to install my own SDK ? Any help will be appreciated. TIA -- Shutruk Tag: Graphical Shell problems Tag: 71686
  - 4
    - Re:How to include CSP HI Steve, Thanx, I have only the ARM CSP sources for the drivers. I don't have the library built for ARM. Do I need to built it for ARM target. Please let me know. Regards, Johns Tag: Graphical Shell problems Tag: 71683
  - 5
    - BSP problem i have a binary BSP for WinCE4.2 how can updata into WinCE5.0 a project Tag: Graphical Shell problems Tag: 71678
  - 6
    - ietheme.dll I built a kernel for an Internet Appliance using CE.50 after downloading all the latest updates (quite a few). It would hang in booting because it tries to download iectl.dll from RELFSD. For some reason ie.bib is renaming iectl.dll as ietheme.dll like this: ; @CESYSGEN IF IE_MODULES_IECTL ietheme.dll $(_FLATRELEASEDIR)\iectl.dll NK SH ; @CESYSGEN ENDIF IE_MODULES_IECTL I also had to add ietheme.dll to the platform before internet explorer can load the msn homepage. Is this a problem? Why is ietheme.dll really iectl.dll? My RELFSD isnt working, but I am debugging that, I think it is something to do with the networking setup on my platform builder workstation. Tag: Graphical Shell problems Tag: 71672
  - 7
    - Cannot license run-time image I am attempting to run the binary image license utility in PB CE 5.0 When I enter my product key from the distribution package, I get an error that says "Cannot license the binary image. The license entered is invalid". So what "license key" is the utility looking for, if it's not the Product Key on the inside of the CD case? Thanks Chuck Tag: Graphical Shell problems Tag: 71671
  - 8
    - What consume memory on startup? Hi, When Windows CE is running the total memory that can be allocated does not match with the total physical memory of the device. In the Memory tab of the System Properties the sum of the two types of memory is smaller than what I expect. I know that the first ~2MB of memory is reserved in config.bib forthe BIOS, bootloader, video buffer... Then the nk.bin file is loaded in RAM and the size it takes may be found with the viewbin.exe tool. What I'm not able to find is what else consume memory? On my device it is 6MB that is not available: 256MB of RAM - 2MB for BIOS - 14MB for nk.bin - Total memory that may be allocated = 6MB. I guess that the OS needs a little bit of memory at start to create heap, stack, ect. but I don't think that it takes as much as 6MB. Does anybody know what takes memory or know a way to find it out? Thank you for your help Tag: Graphical Shell problems Tag: 71668
  - 9
    - NOR flash Hello all, WINCE 4.2, Debug Build, RAM based registry, NO PCMCIA/CF. i am trying to use on-board strata flash as a NOR flash driver. we have two banks of flash in our platform, bank1 (32MB) is used for Eboot loader /XIP... so its untouchable (no driver is used for it, its erased by EBOOT loader in retail mode when OS is downloaded to it, its not erased by Ebootloader in debug mode) bank2 (32 MB) is not used.. we want to be able to use it to save registry/data... our platform is not supported by intel IPSM or datalight FlashX, otherwise we could have just used bank1 for Data/code execution... i am very new to FAT/OS/Flash... so bare with me now, i mapped bank2 to an un-used memeory area in out processor, i see the driver being loaded, flash being formatted, mounted, then unmounted... the same settings will work in debug mode if i use bank1 MemBase Address and MemLen. but i need Bank1 for XIP... (retail build) when i use bank2,the MSFlash partition is available in storage manager, i can format it, but i will not be able to mount it.. storage manager however doesnt show the right parameters for it ( i see different messages when i try manually to format, then mount the parition, but it also fails -from the debug messages below, i c some weired messages such as " NumSec=-1008 BytesPerSec=512 FreeSec=-282727629 BiggestCreatable=-1525897972 4294892157 PID:adf584ce TID:2df430aa 0x8df58000: Partition PART00 NumSectors=-1010 " Q1) why the number such as NumSec are negative? i understand its 64-bit value, doesn negative number means error ? Q2) when use bank1, i see the message "PD_FormatPartition - type is 4" and it works, when ise use bank2, i see the message " PD_FormatPartition - type is 11" , i use the same registry settings for both whats the difference between these two types? please help thanks below are my registry settings platform.reg =================================================================== [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="system.hv" "DefaultUser"="User" ;Added 07.22.2005 "Flags"=dword:1 ; (added ) "Start DevMgr"=dword:1 ; (original) ;end addition IF STRATA_FLASH ; this section is not enclosed in "HIVE BOOT SECTION" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD] "Dll"="stratad.dll" "Order"=dword:2 "Prefix"="DSK" "Ioctl"=dword:4 "Profile"="MSFlash" "IClass"="{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "MemBase"=dword: A8000000 ;this value works for bank1 A0040000 ;A0020000;A0000000;A0009000;A0030000;A000F500;A0000000 "MemLen"=dword: 02000000 ;this value works for bank1 01FC0000 ;01FE0000;02000000;01FF7000;1FD0000;02000000;00800000;01FF0B00;02000000 ;Added 07.21.2005 commented out ; Override names in default profile ;[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash] ; "Name"="MSFLASH for STRATAFLASH" ; "Folder"="NOR Flash" ;[HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\MSFlash] ; "DriverPath"="Drivers\\BuiltIn\\StrataFMD" ; LoadFlags 0x01 == load synchronously ; "LoadFlags"=dword:1 ; "Order"=dword:0 ;end addition ;;Added 07.21.2005 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash] "Name"="MSFLASH for STRATAFLASH" "DefaultFileSystem"="FATFS" "Folder"="NOR Flash" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "AutoFormat"=dword:1 "MountFlags"=dword:2;2(original value) , i tried (11:didntwork), [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MSFlash\FATFS] "Dll"="fatfsd.dll" "Flags"=dword:00100024 ;(original value) "Util"="fatutil.dll" "Paging"=dword:1 "CacheSize"=dword:0;(original value) "FormatTfat"=dword:1 ;Added 07.21.2005 "MountFlags"=dword:2; ; ;end addition ENDIF STRATA_FLASH debug output [upon startup], bank2 used =============================================================== DEVICE!ActivateDeviceEx(Drivers\BuiltIn\StrataFMD) entered 4294773777 PID:adf39802 TID:adf5bdf6 0x8df391b4: >>> Loading module stratad.dll at address 0x026E0000-0x026F2000 (RW data at 0x01F08000-0x01F08AF4) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\STRATAD.DLL' 4294773808 PID:adf39802 TID:adf5bdf6 0x8df391b4: FMD_Init: READ_FROM_REGISTRY 4294773811 PID:adf39802 TID:adf5bdf6 0x8df391b4: FMD InitializeFlash pBaseAddress=a8000000,FlashLength=2000000 4294773813 PID:adf39802 TID:adf5bdf6 0x8df391b4: FMD InitializeFlash g_FMDInfo.BlockSize=40000 4294773819 PID:adf39802 TID:adf5bdf6 0x8df391b4: INFO: FMD_Init: Flash Address=0xa8000000 Length=0x2000000. 4294773820 PID:adf39802 TID:adf5bdf6 0x8df391b4: FMD_GetInfo: pFlashInfo->dwNumBlocks=80,pFlashInfo->dwBytesPerBlock=40000,pFlashInfo->wDataBytesPerSector=200,pFlashInfo->wSectorsPerBlock=1f8 4294773824 PID:adf39802 TID:adf5bdf6 0x8df391b4: FLASHDRV.DLL:BuildupMappingInfo() - Enter. 4294773834 PID:adf39802 TID:adf5bdf6 0x8df391b4: PNP interface class {A4E7EDDA-E575-4252-9D6B-4195D48BB865} (DSK1:) ATTACH 4294774125 PID:adf584ce TID:2df430aa 0x8df58000: >>> Loading module mspart.dll at address 0x03D10000-0x03D1B000 (RW data at 0x01FD7000-0x01FD74A4) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\MSPART.DLL' 4294774157 PID:adf584ce TID:2df430aa 0x8df58000: Loading partition driver mspart.dll hModule=8DE65C48 4294774159 PID:adf584ce TID:2df430aa 0x8df58000: Driver mspart.dll loaded 4294774160 PID:adf584ce TID:2df430aa 0x8df58000: Opened the store hStore=0008EB40 4294774161 PID:adf584ce TID:2df430aa 0x8df58000: NumSec=-1008 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 4294777869 PID:de65692 TID:df397de 0x8de2b400: InitSharedHeap: 44000000 0 c 4294777869 PID:de65692 TID:df397de 0x8de2b400: InitSharedHeap: return 44000060 4294782634 PID:adf39802 TID:2df430aa 0x8df58000: FMD_EraseBlock PD_FormatPartition - type is 11 4294892156 PID:adf584ce TID:2df430aa 0x8df58000: NumSec=-1008 BytesPerSec=512 FreeSec=-282727629 BiggestCreatable=-1525897972 4294892157 PID:adf584ce TID:2df430aa 0x8df58000: Partition PART00 NumSectors=-1010 4294892157 PID:adf584ce TID:2df430aa 0x8df58000: MSPART!PD_OpenPartition: dwStoreId=0008EB40, PartName=PART00 4294892195 PID:adf584ce TID:2df430aa 0x8df58000: >>> Loading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' 4294892237 PID:adf584ce TID:2df430aa 0x8df58000: FSD_MountDisk: mounting volumes for hDsk=0008FC30 4294892242 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: access time updates disabled 4294892242 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: event logging enabled 4294892243 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: automatic scanning disabled 4294892243 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: write verify disabled 4294892244 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: extra FAT on format disabled 4294892245 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: force write through enabled 4294892247 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: Codepage = 1 4294892249 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: Number of path cache entries = 50 4294892250 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!InitVolume: sector 0 byte 0 suspicious (0xb) 4294892251 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!InitVolume: invalid BPB, volume deemed invalid 4294892259 PID:adf584ce TID:2df430aa 0x8df58000: FATFS: Sec/FAT = 0!!! 4294892259 PID:adf584ce TID:2df430aa 0x8df58000: FATFS: CacheSize = 16!!! 4294892283 PID:adf584ce TID:2df430aa 0x8df58000: >>> Loading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 4294892319 PID:adf584ce TID:2df430aa 0x8df58000: FormatDisk!FormatVolume: New BPB successfully written 4294892322 PID:adf584ce TID:2df430aa 0x8df58000: FormatDisk!FormatVolume: New extended boot sector successfully written 84641 PID:adf39802 TID:2df430aa 0x8df58000: FLASHDRV.DLL:WriteToMedia() - request runs off end of media 84642 PID:adf39802 TID:2df430aa 0x8df58000: FLASHDRV.DLL:WriteToMedia() failed. 84642 PID:adf584ce TID:2df430aa 0x8df58000: Unknown: DEBUGCHK failed in file c:\wince420\public\common\oak\drivers\fsd\fatutil\main\diskinterface.cpp at line 44 Unloaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 84645 PID:adf584ce TID:2df430aa 0x8df58000: FormatDisk!FormatVolume: cannot write new FAT sector 32 84648 PID:adf584ce TID:2df430aa 0x8df58000: <<< Unloading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) 84649 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!CloseVolume: retaining volume 0x0008fe90 (following power cycle) 84652 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: access time updates disabled 84653 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: event logging enabled 84654 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: automatic scanning disabled 84654 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: write verify disabled 84655 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: extra FAT on format disabled 84656 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: force write through enabled 84658 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: Codepage = 1 84660 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!OpenVolume: Number of path cache entries = 50 84661 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!InitVolume: sector 0 byte 0 suspicious (0xb) 84662 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!InitVolume: invalid BPB, volume deemed invalid 84670 PID:adf584ce TID:2df430aa 0x8df58000: FATFS: Sec/FAT = 0!!! 84670 PID:adf584ce TID:2df430aa 0x8df58000: FATFS: CacheSize = 16!!! 84676 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!UnmountDisk: unmounting all volumes on disk 0008FC30 84678 PID:adf584ce TID:2df430aa 0x8df58000: FATFS!FATDetach complete (0 sectors written in 0 requests) 84679 PID:adf584ce TID:2df430aa 0x8df58000: <<< Unloading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) Unloaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' Debug output when i try manually to format/mount after it fails in startup (bank2) ============================================================================== 182039 PID:edc8bc4a TID:cdc8bbde 0x8dc75c1c: MSFLASH for STRATAFLASH 183026 PID:adf39802 TID:cdc8bbde 0x8dc75c1c:FMD_EraseBlock MSPART!PD_OpenPartition: dwStoreId=0008EB40, PartName=PART00 338189 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: >>> Loading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' 338538 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FSD_MountDisk: mounting volumes for hDsk=0008F7D0 Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 338539 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!MountDisk: BPB_HiddenSectors(1963221330) != 0 338542 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: access time updates disabled 338542 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: event logging enabled 338543 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: automatic scanning disabled 338543 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: write verify disabled 338543 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: extra FAT on format disabled 338543 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: force write through enabled 338545 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Codepage = 1 338565 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Number of path cache entries = 50 338566 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: sector 0 byte 0 suspicious (0xb) 338566 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: invalid BPB, volume deemed invalid 338574 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: Sec/FAT = 0!!! 338575 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: CacheSize = 16!!! 338599 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: >>> Loading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) 338949 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FormatDisk!FormatVolume: New BPB successfully written 338953 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FormatDisk!FormatVolume: New extended boot sector successfully written 500548 PID:adf39802 TID:cdc8bbde 0x8dc75c1c: FLASHDRV.DLL:WriteToMedia() - request runs off end of media 500549 PID:adf39802 TID:cdc8bbde 0x8dc75c1c: FLASHDRV.DLL:WriteToMedia() failed. 500549 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: Unknown: DEBUGCHK failed in file c:\wince420\public\common\oak\drivers\fsd\fatutil\main\diskinterface.cpp at line 44 Unloaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 500552 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FormatDisk!FormatVolume: cannot write new FAT sector 32 500556 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: <<< Unloading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) 500556 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!CloseVolume: retaining volume 0x0008fcc0 (following power cycle) 500559 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: access time updates disabled 500560 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: event logging enabled Unloaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 500560 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: automatic scanning disabled 500560 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: write verify disabled 500560 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: extra FAT on format disabled 500560 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: force write through enabled 500562 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Codepage = 1 500564 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Number of path cache entries = 50 500586 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: sector 0 byte 0 suspicious (0xb) 500587 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: invalid BPB, volume deemed invalid 500594 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: Sec/FAT = 0!!! 500595 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: CacheSize = 16!!! 500600 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!UnmountDisk: unmounting all volumes on disk 0008F7D0 Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' 500601 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!FATDetach complete (0 sectors written in 0 requests) 500603 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: <<< Unloading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) 500633 PID:de65692 TID:cdc8bbde 0x8dc75c1c: DlgMgr: FindDlgItem id 1 returning NULL. 505644 PID:de65692 TID:cdc8bbde 0x8dc75c1c: DlgMgr: FindDlgItem id 1 returning NULL. 505779 PID:de65692 TID:cdc8bbde 0x8dc75c1c: Grow Gdi handle table from 768 to 832 505801 PID:edc8bc4a TID:cdc8bbde 0x8dc75c1c: >>> Loading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) 507227 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: >>> Loading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) 507546 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FSD_MountDisk: mounting volumes for hDsk=0008F7D0 507547 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!MountDisk: BPB_HiddenSectors(-971454952) != 0 507551 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: access time updates disabled 507552 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: event logging enabled 507552 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: automatic scanning disabled 507552 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: write verify disabled 507552 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: extra FAT on format disabled 507553 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: force write through enabled 507555 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Codepage = 1 507556 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!OpenVolume: Number of path cache entries = 50 507557 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: sector 0 byte 0 suspicious (0xb) 507576 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS!InitVolume: invalid BPB, volume deemed invalid 507584 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: Sec/FAT = 0!!! 507584 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FATFS: CacheSize = 16!!! 507609 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FormatDisk!FormatVolume: New BPB successfully written 507612 PID:adf584ce TID:cdc8bbde 0x8dc75c1c: FormatDisk!FormatVolume: New extended boot sector successfully written 507698 PID:adf39802 TID:de745d2 0x8de740a8: SM_UnmarkSectorsAsDirty: Error, Invalid dirty sector count 507698 PID:adf39802 TID:de745d2 0x8de740a8: FLASHDRV.DLL:CP_CompactBlock() - Unable to unmark physical sector 0x000001f8 as DIRTY 507699 PID:adf39802 TID:de745d2 0x8de740a8: SM_UnmarkSectorsAsDirty: Error, Invalid dirty sector count .......................... FLASHDRV.DLL:CP_CompactBlock() - Unable to map logical sector 0x74042412 to physical sector 0x0000f810 508860 PID:adf39802 TID:de745d2 0x8de740a8: FLASHDRV.DLL:CP_GetNextCompactionBlock() Error: Cannot write to block 0! 508860 PID:adf39802 TID:de745d2 0x8de740a8: Unknown: DEBUGCHK failed in file d:\mckendric\private\winceos\drivers\msflash\src\compactor.c at line 818 508863 PID:adf39802 TID:de745d2 0x8de740a8: FLASHDRV.DLL:CompactorThread() - CompactorThread(0xffffffff) failed; unable to compact!!! debug output when i use bank1 and everything works fine (bank1) =================================================================== 4294778981 PID:4df584ce TID:4df430aa 0x8df58000: >>> Loading module mspart.dll at address 0x03D10000-0x03D1B000 (RW data at 0x01FD7000-0x01FD74A4) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\MSPART.DLL' 4294779030 PID:4df584ce TID:4df430aa 0x8df58000: Loading partition driver mspart.dll hModule=8DE65C90 4294779031 PID:4df584ce TID:4df430aa 0x8df58000: Driver mspart.dll loaded 4294779032 PID:4df584ce TID:4df430aa 0x8df58000: Opened the store hStore=0008E990 4294779034 PID:4df584ce TID:4df430aa 0x8df58000: NumSec=47880 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 4294782487 PID:8df39802 TID:4df430aa 0x8df58000: FMD_EraseBlock ulBlockAddress=a01c0000, g_FMDInfo.BaseAddress =a0040000,blockID=6,g_FMDInfo.BlockSize=40000 4294856839 PID:4df584ce TID:4df430aa 0x8df58000: PD_FormatPartition - type is 4 4294856842 PID:4df584ce TID:4df430aa 0x8df58000: NumSec=47880 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 4294856843 PID:4df584ce TID:4df430aa 0x8df58000: Partition PART00 NumSectors=47878 4294856844 PID:4df584ce TID:4df430aa 0x8df58000: MSPART!PD_OpenPartition: dwStoreId=0008E990, PartName=PART00 4294856882 PID:4df584ce TID:4df430aa 0x8df58000: >>> Loading module fatfsd.dll at address 0x03EE0000-0x03F04000 (RW data at 0x01FF9000-0x01FF9674) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATFSD.DLL' 4294856924 PID:4df584ce TID:4df430aa 0x8df58000: FSD_MountDisk: mounting volumes for hDsk=00090050 4294856928 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: access time updates disabled 4294856929 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: event logging enabled 4294856930 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: automatic scanning disabled 4294856930 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: write verify disabled 4294856931 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: extra FAT on format disabled 4294856931 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: force write through enabled 4294856934 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: Codepage = 1 4294856936 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: Number of path cache entries = 50 4294856937 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!InitVolume: sector 0 byte 0 suspicious (0x0) 4294856938 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!InitVolume: invalid BPB, volume deemed invalid 4294856946 PID:4df584ce TID:4df430aa 0x8df58000: FATFS: Sec/FAT = 0!!! 4294856946 PID:4df584ce TID:4df430aa 0x8df58000: FATFS: CacheSize = 16!!! 4294856970 PID:4df584ce TID:4df430aa 0x8df58000: >>> Loading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) Loaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 4294857012 PID:4df584ce TID:4df430aa 0x8df58000: FormatDisk!FormatVolume: New BPB successfully written 4294857083 PID:4df584ce TID:4df430aa 0x8df58000: FormatDisk!FormatVolume: New FAT #0 successfully written 4294857153 PID:4df584ce TID:4df430aa 0x8df58000: FormatDisk!FormatVolume: New FAT #1 successfully written 4294857202 PID:4df584ce TID:4df430aa 0x8df58000: FormatDisk!FormatVolume: New root directory successfully written 4294857202 PID:4df584ce TID:4df430aa 0x8df58000: FormatDisk!FormatVolume complete. 4294857206 PID:4df584ce TID:4df430aa 0x8df58000: <<< Unloading module fatutil.dll at address 0x03EC0000-0x03ED2000 (RW data at 0x01FF6000-0x01FF70C8) Unloaded symbols for 'C:\WINCE420\PUBLIC\CENET42_SIID\RELDIR\HITACHI_PFM-DS11_SH3DEBUG\FATUTIL.DLL' 4294857206 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!CloseVolume: retaining volume 0x00090540 (following power cycle) 4294857210 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: access time updates disabled 4294857210 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: event logging enabled 4294857211 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: automatic scanning disabled 4294857211 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: write verify disabled 4294857212 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: extra FAT on format disabled 4294857212 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: force write through enabled 4294857215 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: Codepage = 1 4294857217 PID:4df584ce TID:4df430aa 0x8df58000: FATFS!OpenVolume: Number of path cache entries = 50 4294857225 PID:4df584ce TID:4df430aa 0x8df58000: FATFS: Sec/FAT = 47!!! 4294857226 PID:4df584ce TID:4df430aa 0x8df58000: FATFS: CacheSize = 32!!! 4294857241 PID:8df39802 TID:6df0c56e 0x8def175c: TAPI:AddTapiDevice: GetDeviceKeys(\NOR Flash) returned 1200 4294857245 PID:8df39802 TID:6df0c56e 0x8def175c: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 87 Tag: Graphical Shell problems Tag: 71664
  - 10
    - Hive based Registry System bootup hangs Hi, I am using Hive Based Registry for PXA255 Platform winCE 4.2 When i load the system after inlcuding my Hive Registry it hangs waiting for "FILESYS: Starting device and waiting for boot file system." I couldn't find the regsitry entry which affects this, please suggest. Thanks, Peter This is the debg mesg i got: Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\COREDLL.DLL' 4294770480 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: >>> Loading module filesys.exe at address 0x04010000-0x0408C000 Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\FILESYS.EXE' 4294770543 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FileSystem Starting - starting with clean file system 4294770592 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSVOL: Opening existing volume 4294770623 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSVOL: Volume heap already initialized 4294770653 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSREG: Mounted ROM portion of boot registry 4294770683 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSVOL: Creating clean virtual volume 4294770713 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSVOL: Initializing volume heap 4294770779 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSREG: Mounted RAM portion of boot registry 4294770837 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FS: Creating signal event SYSTEM/PowerManagerReady 4294770870 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FS: Creating signal event SYSTEM/GweApiSetReady 4294770902 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FS: Creating signal event ReleaseFSD 4294770944 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FSREG: Unable to read value "Flags" under HKEY_LOCAL_MACHINE\init\BootVars 4294770983 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FILESYS: Starting storage manager and waiting for boot file system. 4294771042 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: >>> Loading module fsdmgr.dll at address 0x03D60000-0x03D7C000 (RW data at 0x01FE5000-0x01FE5754) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\FSDMGR.DLL' 4294771090 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FS: Registering file system StoreMgr, index 2, flags 0x00000001 4294771134 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FILESYS: Starting storage manager and waiting for boot file system. 4294771192 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: >>> Loading module stratad.dll at address 0x035C0000-0x035D4000 (RW data at 0x01F80000-0x01F80AF4) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\STRATAD.DLL' 4294771241 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FMD_Init: SUCCESS 4294771269 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: INFO: FMD_Init: Flash Address=0xb8380000 Length=0x1f80000. 4294771308 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FLASHDRV.DLL:BuildupMappingInfo() - Enter. 4294771373 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: >>> Loading module mspart.dll at address 0x03D50000-0x03D5C000 (RW data at 0x01FE3000-0x01FE34A4) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\MSPART.DLL' 4294771421 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: Loading partition driver mspart.dll hModule=83C69490 4294772949 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: Driver mspart.dll loaded 4294773324 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294773407 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294774483 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: Opened the store hStore=000A34E0 4294775324 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294775407 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FLASHDRV.DLL:ReadFromMedia() - Unable to determine physical sector address for logical sector 0x00000000 4294776519 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: NumSec=62496 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 4294777342 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: >>> Loading module relfsd.dll at address 0x03EA0000-0x03EAB000 (RW data at 0x01FF4000-0x01FF4ABC) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\RELFSD.DLL' 4294777433 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FILESYS: Starting device and waiting for boot file system. 4294777495 PID:83ca3b46 TID:63c7119a 0x83c69ce0: FS: Registering file system Release, index 3, flags 0x00000000 4294777535 PID:83ca3b46 TID:63c7119a 0x83c69ce0: Mounted ReleaseFSD volume '\Release' 4294777617 PID:43c632f6 TID:43c69402 0x83c630b8: >>> Loading module pm.dll at address 0x03F00000-0x03F1E000 (RW data at 0x01FFB000-0x01FFB6C4) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\PM.DLL' 4294778274 PID:43c632f6 TID:43c69402 0x83c630b8: *** Power Manager: DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x43c632f6 *** 4294778319 PID:43c632f6 TID:43c69402 0x83c630b8: >>> Loading module device.exe at address 0x06010000-0x06020000 Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\DEVICE.EXE' 4294778458 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FS: Waiting for device to signal BootPhase1 completion 4294780052 PID:43c632f6 TID:43c69402 0x83c630b8: >>> Loading module ceddk.dll at address 0x03D40000-0x03D46000 (RW data at 0x01FE1000-0x01FE1068) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\CEDDK.DLL' 4294780099 PID:43c632f6 TID:43c69402 0x83c630b8: Ceddk!CalibrateStallCounter: Enter 4294780137 PID:43c632f6 TID:43c69402 0x83c630b8: Ceddk!CalibrateStallCounter: Could not find stall counter 4294780198 PID:43c632f6 TID:43c69402 0x83c630b8: Ceddk!BeginCalibration: min(368) max(460) 4294781576 PID:43c632f6 TID:43c69402 0x83c630b8: Ceddk!BeginCalibration: elapsed is 386 4294782164 PID:43c632f6 TID:43c69402 0x83c630b8: Ceddk!BeginCalibration: delay is 3 4294782215 PID:43c632f6 TID:43c69402 0x83c630b8: +Harita PmInit 4294783583 PID:43c632f6 TID:43c69402 0x83c630b8: +Harita PlatformValidatePMRegistry 4294784166 PID:43c632f6 TID:43c69402 0x83c630b8: -Harita PlatformValidatePMRegistry: returning 0 4294784223 PID:43c632f6 TID:43c69402 0x83c630b8: DeviceListsInit: default GUID found in registry as expected 4294785606 PID:43c632f6 TID:43c69402 0x83c630b8: DeviceListCreate: creating list entry for class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 4294786166 PID:43c632f6 TID:43c69402 0x83c630b8: Harita PlatformDeviceListInit: using stream interface to access class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 4294786253 PID:43c632f6 TID:43c69402 0x83c630b8: DeviceListCreate: creating list entry for class 98c5250d-c29a-4985-ae5f-afe5367e5006 4294787636 PID:43c632f6 TID:43c69402 0x83c630b8: Harita PlatformDeviceListInit: using stream interface to access class 98c5250d-c29a-4985-ae5f-afe5367e5006 4294788165 PID:43c632f6 TID:43c69402 0x83c630b8: DeviceListCreate: creating list entry for class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 4294788242 PID:43c632f6 TID:43c69402 0x83c630b8: Harita PlatformDeviceListInit: using display interface to access class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 4294789673 PID:43c632f6 TID:43c69402 0x83c630b8: InitDisplayDeviceInterface: returning 1 4294790166 PID:43c632f6 TID:43c69402 0x83c630b8: DeviceListCreate: creating list entry for class a32942b7-920c-486b-b0e6-92a702a99b35 4294790243 PID:43c632f6 TID:43c69402 0x83c630b8: Harita PlatformDeviceListInit: using stream interface to access class a32942b7-920c-486b-b0e6-92a702a99b35 4294791709 PID:43c632f6 TID:a3c53176 0x83c69ce0: +PnpThreadProc: thread 0xa3c53176 4294791809 PID:43c632f6 TID:a3c537d6 0x83c53598: +ResumeThreadProc: thread 0xa3c537d6 4294791909 PID:43c632f6 TID:a3c53e36 0x83c53bf8: +ActivityTimersThreadProc: thread 0xa3c53e36 4294792170 PID:43c632f6 TID:a3c53e36 0x83c53bf8: ActivityTimerCreate: ActivityTimerCreate('UserActivity') returning 0x00000000 4294792244 PID:43c632f6 TID:a3c53e36 0x83c53bf8: ActivityTimerCreate: ActivityTimerCreate('SystemActivity') returning 0x00000000 4294793740 PID:43c632f6 TID:43c53e5a 0x83c4c000: +SystemThreadProc: thread 0x43c53e5a 4294794166 PID:43c632f6 TID:43c53e5a 0x83c4c000: +Harita PlatformManageSystemPower 4294794218 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformPMActivelyManagesPower: returning 1 4294795268 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: waiting for initialization to complete 4294796166 PID:43c632f6 TID:23c53f32 0x83c4c67c: +BatteryMonitorThreadProc: thread 0x23c53f32 4294796223 PID:43c632f6 TID:23c53f32 0x83c4c67c: BatteryMonitorThreadProc: battery interface APIs not available, exiting 4294796265 PID:43c632f6 TID:43c69402 0x83c630b8: -Harita PmInit: returning 1 4294798168 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: initialization complete 4294799357 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: read the timeout values 4294800849 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformLoadTimeouts: ACUserIdle 900000, ACSystemIdle 300000, ACSuspend -1, BattUserIdle 900000, BattSystemIdle 180000, BattSuspend 300000 4294802166 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: timeout values read 4294803399 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: waiting for events 4294804891 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: ##### wait returned 4, elapsed time 0, timeout was -1 ##### 4294806166 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformManageSystemPower: UserInactivity 4294807440 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState: activity 'UserInactivity' in state 'UserActive', elapsed time 0 4294808945 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState: we're on AC power 4294810166 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState: a timeout 4294811494 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState:UserActive -> UserInactive 4294812989 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState:changing activity states 4294814166 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState:calculate new timeouts and system power state names 4294815560 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState:UserInactive = on 4294817041 PID:43c632f6 TID:43c53e5a 0x83c4c000: Harita PlatformUpdateSystemPowerState: entering activity state 'UserInactive', state time left 900000 4294818167 PID:43c632f6 TID:43c69402 0x83c630b8: DEVICE!DevloadInit 4294819576 PID:43c632f6 TID:43c69402 0x83c630b8: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 4294821074 PID:43c632f6 TID:23c53f32 0x83c4c67c: -BatteryMonitorThreadProc: exiting 4294822167 PID:43c632f6 TID:43c69402 0x83c630b8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn) entered 4294823637 PID:43c632f6 TID:43c69402 0x83c630b8: >>> Loading module regenum.dll at address 0x03F20000-0x03F27000 (RW data at 0x01FFD000-0x01FFD4A4) Loaded symbols for 'E:\WINCE420\PUBLIC\POWER_TS90BSP_TEST\RELDIR\TS90DEBUG\REGENUM.DLL' 4294825743 PID:43c632f6 TID:43c69402 0x83c630b8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\StrataFMD) entered 4294825784 PID:83ca3b46 TID:83ca3b22 0x83ca38e4: FILESYS: Starting device and waiting for boot file system. Tag: Graphical Shell problems Tag: 71603
  - 11
    - Xscale...Ping Problem Hi I have come across a rather odd problem with our new hardware. Our old hardware is StrongARM (SA1110) based and the new is Xscale (PXA255) based. I can use bot sets of hardware to ping. We have another site where we can use both set of hardware to ping.Bt we have a problem site where the SA1110 based hardware pings without any issue, but the Xscale based hardware will not ping, fails all the time. We are using the same kit at all three sites...using the ciscoaironet350 cards.. Any ideas anyone. Regards Tag: Graphical Shell problems Tag: 71587
  - 12
    - PXA255 USB device controller GetStatus Hi, We have a design using a PXA255 where we need the USB device controller (Serial function). The serial function seems to be working OK. But when we tried to pass certification for Microsoft drivers signing we found, that in some cases the UDC does not answer the Get Status from the host (The answer is 0 bytes instead of 2 Bytes). This happens only 'sporadically'. We fail the test in 5 out of 6 tries. According to the manual and our debugging, the Get Status is handled by the PXA and does not generate an interrupt. I.E. I don't know how I can fix that in my driver. Test setup: HCT test bench from Microsoft using an USB 2.0 EHC controller with a USB 2.0 hub. (As required by the test bench) Win CE using PB 4.2 Any help would be appreciated. P.S. the 0x81 bug (missing OPR) is fixed. Regards, Martin Tag: Graphical Shell problems Tag: 71585
  - 13
    - How to include a CSP Hi, I have to create a new CE 5.0 BSP using PB 5.0 for ARM processor, I have the seperate ARM CSP library(Source) which has the device driver support files in arm directory. How should I include those file to make a BSP. Can u let me know the steps in interfacing these two. Thanx. Regards, John Tag: Graphical Shell problems Tag: 71584
  - 14
    - registry Hi, We are using vortex86 processor, 64 Mb DiskOnChip and 64 Mb RAM. We are developing an application with MFC on Embedded Visual C++. We have three main problems: 1) The application should run on start-up even before the desktop comes onto the screen. How do we change the registry so that the application runs on start-up? 2) Is there an easy way to load NK.bin image file to DiskOnChip? Our embedded system has an IP. We want to load it through the network. 3) We hold the database in DiskOnChip. But it is very slow to read, seek, and write from database. How can we make it fast? Thanks, Alper & Tolga Tag: Graphical Shell problems Tag: 71581
  - 15
    - stupid arm asm question xscale 27x that is. if pc is Axxxxxxx, then it is RAM. if it is 0xxxxxxx, that it is ROM. so, i have two case. if the code is running in ram already, don't init sdram. if it is in rom, then init ram. simple enough? but i couldn't get it work :( mov r1, pc tst r1, #0xA0000000 bne skip_mem_init bl xlli_mem_init skip_mem_init something follow.... Tag: Graphical Shell problems Tag: 71567
  - 16
    - Hive Based Registry Verification Procedure I am working in a WinCE 4.2 PXA255 product. It has 64MB SDRAM, 32MB Flash. I use Intel Strata Flash chips. Here, I am not using any third party file system. So, I added storage manager from the Catalog. I made modifications in the platform.reg file to load the Starata.dll, MSPART.dll. Here, I want to store my system.hv in the same flash chip itself. I downloaded the image and saw the mspart.dll and strata.dll is loaded without any errors. To verify Hive based registry, I created a new Registry Key. Then, I called the RegFlushKey () function to verify my Persistent Storage. After calling this function I restarted my product and looked for the key which I created and it was not there. So, the registry is not persistent. Or my way of verification is wrong? I don;t think my Persistent storage is working. I followed the procedures to include Hive in PB Help. I am sending my reg. file and bib file here. BIB FILE: MODULES mspart.dll $(_FLATRELEASEDIR)\mspart.dll NK SH ; StrataFlash block driver. stratad.dll $(_FLATRELEASEDIR)\stratad.dll NK SH REG FILE: ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles] "AutoMount"=dword:1 "AutoPart"=dword:0 "AutoFormat"=dword:0 "MountFlags"=dword:0 "DefaultFileSystem"="" "PartitionDriver"="mspart.dll" "Folder"=LOC_STORE_DEFAULT_FOLDER ; @CESYSGEN IF PM_PM_DEFAULT_PDD "ActivityEvent"="PowerManager/ActivityTimer/SystemActivity" ; @CESYSGEN ENDIF ; PM_PM_DEFAULT_PDD ; The partition table contain entries where the volume name is the partition type (in %02X format) ; The value is the name of the filesystem. This is used to look up the module to load etc. ; Explicitly call out 07 partition type as NTFS as an expample of another partition type ; Since there is no actual NTFS registry entry, no fileysstem will get loaded [HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable] "01"="FATFS" "04"="FATFS" "06"="FATFS" "07"="NTFS" "0B"="FATFS" "0C"="FATFS" "0E"="FATFS" "0F"="FATFS" "20"="BOOT" "21"="BINFS" "22"="XIP" ; StrataFlash block driver. #include "$(DRIVERS_DIR)\block\msflashfmd\strata\stratad\stratad.reg" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD] "MemBase"=dword:b8380000 "MemLen"=dword:01f80000 ; END HIVE BOOT SECTION ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="Documents and Settings\\system.hv" "PROFILEDIR"="Documents and Settings" "Start DevMgr"=dword:0 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\Drivers\Resources\IRQ] "Identifier"=dword:1 "Minimum"=dword:1 "Space"=dword:20 "Ranges"="1-0x20" ; "Shared"="" [HKEY_LOCAL_MACHINE\Drivers\Resources\IO] "Identifier"=dword:2 "Minimum"=dword:0 "Space"=dword:10000 "Ranges"="0-0xFFFF" ; END HIVE BOOT SECTION Please suggets me what i am missing inthe Hive configruations. Thanks & Regards, Peter Tag: Graphical Shell problems Tag: 71565
  - 17
    - Hive Based registry Verification Procedure ? I am working in a WinCE 4.2 PXA255 product. It has 64MB SDRAM, 32MB Flash. I use Intel Strata Flash chips. Here, I am not using any third party file system. So, I added storage manager from the Catalog. I made modifications in the platform.reg file to load the Starata.dll, MSPART.dll. Here, I want to store my system.hv in the same flash chip itself. I downloaded the image and saw the mspart.dll and strata.dll is loaded without any errors. To verify Hive based registry, I created a new Registry Key. Then, I called the RegFlushKey () function to verify my Persistent Storage. After calling this function I restarted my product and looked for the key which I created and it was not there. So, the registry is not persistent. Or my way of verification is wrong? I am putting my reg. file and bib file here. BIB FILE: MODULES mspart.dll $(_FLATRELEASEDIR)\mspart.dll NK SH ; StrataFlash block driver. stratad.dll $(_FLATRELEASEDIR)\stratad.dll NK SH REG FILE: ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles] "AutoMount"=dword:1 "AutoPart"=dword:0 "AutoFormat"=dword:0 "MountFlags"=dword:0 "DefaultFileSystem"="" "PartitionDriver"="mspart.dll" "Folder"=LOC_STORE_DEFAULT_FOLDER ; @CESYSGEN IF PM_PM_DEFAULT_PDD "ActivityEvent"="PowerManager/ActivityTimer/SystemActivity" ; @CESYSGEN ENDIF ; PM_PM_DEFAULT_PDD ; The partition table contain entries where the volume name is the partition type (in %02X format) ; The value is the name of the filesystem. This is used to look up the module to load etc. ; Explicitly call out 07 partition type as NTFS as an expample of another partition type ; Since there is no actual NTFS registry entry, no fileysstem will get loaded [HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable] "01"="FATFS" "04"="FATFS" "06"="FATFS" "07"="NTFS" "0B"="FATFS" "0C"="FATFS" "0E"="FATFS" "0F"="FATFS" "20"="BOOT" "21"="BINFS" "22"="XIP" ; StrataFlash block driver. #include "$(DRIVERS_DIR)\block\msflashfmd\strata\stratad\stratad.reg" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\StrataFMD] "MemBase"=dword:b8380000 "MemLen"=dword:01f80000 ; END HIVE BOOT SECTION ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="Documents and Settings\\system.hv" "PROFILEDIR"="Documents and Settings" "Start DevMgr"=dword:0 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\Drivers\Resources\IRQ] "Identifier"=dword:1 "Minimum"=dword:1 "Space"=dword:20 "Ranges"="1-0x20" ; "Shared"="" [HKEY_LOCAL_MACHINE\Drivers\Resources\IO] "Identifier"=dword:2 "Minimum"=dword:0 "Space"=dword:10000 "Ranges"="0-0xFFFF" ; END HIVE BOOT SECTION Please suggest me. Thansk & regards, Peter Tag: Graphical Shell problems Tag: 71564
  - 18
    - CE 5.0 Make New Connection problem in release, workaround Hi! I'm using CE 5.0 and a Intel IXC1100 (ARMV4I). I've encountered a problem that all connection types are grayed out when trying to make a new connection in "Network and Dial-up Connections". It started when I mounted the File system as root and shadowed the Windows directory, but only in release build. When I used debug version of Unimodem.dll in release build and enabled debug printouts via a serial port, the problem disappeared. If I set the "Order" value to 3 or greater for the serial drivers it works with the correct version of Unimodem.dll. Has anyone an explanation to this? GÃ¶ran Nordin Tag: Graphical Shell problems Tag: 71562
  - 19
    - Howto connect WinCE5 to a WinXP lan Hi, I wonder if is possible and how to connect WinCE5 to a WinXP lan. Or connect a WinXP PC to a WinCE device sharing a directory folder. Is it possible ? How ? TIA --Shutruk Tag: Graphical Shell problems Tag: 71560
  - 20
    - Question on CEC File ( Need defconfig equalent )?? Hi, I am a newbie in Windows CE world!, I want to make a CEC file such that when I select the platfom all the drivers required for that platfrom must be build with out selecting from catalog? How do I do this. I am using Windows CE 4.2 I went through documentation, I am able to build CEC file and pull components from catalog. However I want to select these drivers by default with platform How do I do this. -- Tag: Graphical Shell problems Tag: 71557
  - 21
    - In my Build All process, It can not generate .dio file! why? I had changed files in platform\Files dir and placed bootloader dir! Tag: Graphical Shell problems Tag: 71555
  - 22
    - problem with my packet IME I build a image with packet IME of Chinese(Simplified),It work right in notebook or other aplication's edit.But when I type Chinese in IE,It will input double .For example,select one word as "ºº"£¬but in the web page¡®s edit £¬it show ¡°ºººº¡±¡£ Can anyone help me? Tag: Graphical Shell problems Tag: 71554
  - 23
    - partial debug and retail image build Hello All, My OS run-image (Nk.nb0) is exceeding the space that is allocated for the image in config.bib during debug builds. I am left with following options to bring down my image size. 1)Make the build configuration smaller by removing unnecessary features. I have already done it and still image size is more. 2)I only want to debug certain components, rest of the components can be in built in retail mode . So i want to make debug versions of only components that need to be debugged. Is there any good way for doing thing? 3) Are there any other methods to bring down the OS image size? Thanks in advance, A. Thirupathi Reddy Tag: Graphical Shell problems Tag: 71546
  - 24
    - Manual startup sever with TCP/IP Hi, I am trying to get eVC to connect to my CE device with manual startup server and TCP/IP as the transport. CESH with KITL works (need PB for this though) . I assume my tcp/ip driver is ok as KITL must be using as underlying transport. I have checked the relevant files and cemgrc are on my device. I type in the command cemgrc.exe /t:tcpipc.dll etc but device does not connect. Also i've tried telneting to my device but can't, so it makes me wonder if there is a problem with the transport, but if this is the case there would be problem with KITL surely. Regards ms Tag: Graphical Shell problems Tag: 71481
  - 25
    - PC/PDA USB transmission question ? Dear all: Lately, I'm programming the USB Tx/Rx program between PC(winXP) and PDA(ce.net). On the PC side, the program, named PCUSB, uses WriteFile() to Tx bytes. On the PDA side, the program, named CEUSB, uses ReadFile() to Rx bytes. But I have belowing problem: Status 1: If PCUSB WriteFile( usbHandle, Buffer, 1000,.. ), CEUSB would Rx 1000 bytes. Status 2: If PCUSB WriteFile( usbHandle, Buffer, 4000,.. ), CEUSB would Rx 2047 bytes. Status 3: If PCUSB WriteFile( usbHandle, Buffer, 8000,.. ), CEUSB would Rx 2047 bytes. Status 4: If PCUSB WriteFile( usbHandle, Buffer, 2000,.. ) Sleep( 1 ); WriteFile( usbHandle, Buffer, 2000,.. ), CEUSB could Rx 4000 bytes. The problem looks like the PCUSB can Tx (SIZE<2048) bytes each. Why? pc usb buffer only 2048 ? or Set Commucation TimeOut Error? Both side, I set the commTimeOut: ReadIntervalTimeOut = MAXDWORD; ReadTimeoutConst,ReadTimeoutMultipler,WriteTimeoutConst,WriteTimeoutMultipler are all zero. Please give me a hand,thx. Tag: Graphical Shell problems Tag: 71474
- Next
  - 1
    - PC connection without file converters? How to install only the the connectivity part of activesync? I need this for debugging programs on the CE device. Full ActiveSync setup installs all the WinCE file types, Outlook and office plugins, and other stuff I don't want on my XP machine. Regards, --PA Tag: Graphical Shell problems Tag: 71463
  - 2
    - force SNMP restart Hi all, is there a way to force from code (eVC++) the SNMP service to restart? (I mean without rebooting the system) I'm working on Windows CE 5.0 Thanks for any suggestions, bye. /Morix Tag: Graphical Shell problems Tag: 71456
  - 3
    - PCL Printing in WinCE5 Hi, I've added the PCL lib to my platform fromt he catalog an downlooaded the image. When i plug in the USB printer (HP PCL3 compatable) i get a windows popup with 'unreconised usb device' title asking for the usb driver for this device. The usb mouse and keyboard still work fine. since the printer is PCL3 compatable (HP6122 inkjet), i assumed that it would be reconised. What am i missing here? Do i need to add somthing into platform.reg ? Please help... joe Tag: Graphical Shell problems Tag: 71449
  - 4
    - No RTTI in SDK? When I export an SDK for EVC4 from my CE 5.0 platform, the RTTI library is not being automatically included (in the same way that it wasn't in the Pocket PC 2003 SDK). Is this a bug in the SDK builder that they didn't fix for CE 5.0 or am I missing some option somewhere? I can always add the ccrtrtti.lib/pdb from WINCE500\PUBLIC\COMMON\OAK\LIB\ARMV4I\RETAIL explicitly into my SDK but it seems odd that I should have to. Tag: Graphical Shell problems Tag: 71448
  - 5
    - Repllog without dialog Hi, we have a problem with ActiveSync when connecting to PC. Connection with PC is made using ActiveSync via local network. Connection is established by "repllog.exe" program with parameter designating this type of connection "repllog.exe /remote", but this program displays a dialog for select connection type and host PC name. Is there any possibility to run it without displaying this dialog box? Or is there any other option, how to make ActiveSync connection via network? Between PDA and PC was already established a partnership (and it is the only partneship used by this PDA and we always want use this one). Tag: Graphical Shell problems Tag: 71442
  - 6
    - USBFN storage device Hi all, I have some problems in getting the USBFN storage working on my target. I want that my device appears as storage device on a PC. When I attach the device the USBFN storage driver tried to access the DSK1: on my Windows CE device. As I do not have that device the CreateFile() fails and is stops the initialisation of the USBFN storage driver. \Wince500\public\common\oak\driver\usbfn\class\storage\emulation\Scsi2\block .cpp What do I need to add to my kernel to get this running? I have included Mass Storage and USBFN driver. I use Windows CE V5.0 for an ARM platform. Thanks for any advice. Mike Engel Tag: Graphical Shell problems Tag: 71438
  - 7
    - Can I write data into specific block of SD card on Wince500 platform? Hi: I have a SD interface hardware, it is not only a SD card, so we can use the standard SD driver provided by MS, but also a sensor. It has two chipsets NAND flash on it .One is on the low 256MB, the other is on high 256MB. I wonder if I can send SD command using API function to the high 256MB flash ? Please guide me how to do that . Tag: Graphical Shell problems Tag: 71432
  - 8
    - Problem about debug eboot on Smdk2410 I want to modify my eboot and debug with pb like debug nk,when my test eboot is same with the eboot on my flash I can download and run it correctly ,however ,when I modify the eboot code and it cannot download correctly,each time it abouted after downloading 26.7kb Could any one help me ? And give me some advice on how to debug eboot. thank you Tag: Graphical Shell problems Tag: 71431
  - 9
    - re: ADOCE You will find the answer here: http://blogs.msdn.com/sloh/archive/category/5374.aspx Cheers, Sue sloh@microsoft.com (remove "online" from reply-to address) Now writing to a different blog! http://blogs.msdn.com/ce_base/ _____________________________________________________________ This posting is provided "AS IS" with no warranties, and confers no rights. _____________________________________________________________ Tag: Graphical Shell problems Tag: 71416
  - 10
    - issue is coming when migrate the OS design from WinCE 4.2 to WinCE hi, i'm using WinCE 5.0 Evaluation version for migrate the OS from WinCE 4.2 to WinCE 5.0 .Now i'm following the MSDN migration steps,currently i'm migrating only the OS design not adding the project code,after i build the design,it is not creating the _setEnv.bat file in the folder ? why so ?(eg:c:\winceroot\pbworkspace\osdesign\osdesign_SetEnv.bat) it should create batch file based on the OS design it is not happening !!!! Also some environment variables used in the WinCE 4.2 is not availble in the WinCE 5.0,for that what i do ? it makes any change in _setEnv.bat ? Please give a suggestion!! thank you bobie Tag: Graphical Shell problems Tag: 71403
  - 11
    - mui_sz loading performance Has anyone else felt like the Date/Time control panel in CE 5.0 takes a while to open ? I went looking at what was happening in my case, and the load of the mui_sz Display and Std keys for each timezone are adding up. Each RegQueryValueEx is taking 10-11ms, of which there are three per timezone for 34ms per time zone. Times 75 timezones is 2.55 seconds which is most of the delay I'm seeing. Am I missing a QFE that improved RegQueryValueEx performance ? Tag: Graphical Shell problems Tag: 71402
  - 12
    - The "Auto list members" feature in eVC is not working with some includes from custom SDK Hello, The "Auto list members" feature in eVC4 is not working for types defined in include files "manually added" to my SDK. By "Manually added" I mean, added using the "Additional files" tab in PB 4.2 SDK Configuration Settings. What can I do to force this feature to work ? By now I have added such includes to eVC project and then "Auto list members" is working fine but should be better solution. Tag: Graphical Shell problems Tag: 71400
  - 13
    - Display BMP on .NET form for WinCE 5.0 Is there an issue with displaying a JPG or Bitmap(8bit and 16bit tested) on a .NET form in WinCE 5.0? If I take an image converted to both a JPG and Bitmap, I find visual errors (distortion) when the images are displayed on .NET forms. To test that the issue is potentially in the .NET forms, I have tested this way: 1. placed the JPG and then the Bitmap as the background image of the winCE desktop. Both versions display properly. 2. placed the JPG and then Bitmap on to a eVC++ app form, and again both images display as expected. 3. opened the JPG and Bitmap in a IE window, and both images display as expected. 4. placed the JPG and the Bitmap onto a C# app for the .NET CF, and the images appear distorted. I am running the eval version of WinCE 5.0 for the ARMV4I chip. I am using VS2003 C# as the development platform. Has anyone encountered this issue, and found a fix? Is this a limitation of the eval version? Am I not including a module in the build? Tag: Graphical Shell problems Tag: 71398
  - 14
    - Newbie embedded Visual C++ question Hi. I suppose this has been asked *lots* of times, but I can't find the information, so here I go... Under Platform Builder 5, I can connect to my CE device using a TCP connection. Using the Platform Builder tools, I see two types of connections : "StandardSDK_500" and "Windows CE Default Platform". I added a connection to the "Windows CE Default Platform" with the following parameters "TCP/IP transport" and "manual server". This works fine. However, if I try to add the same thing to "StandardSDK_500", all I can add is an emulator connection. I can't find the same options and so I can't debug. The point is that under eMbedded Visual C++, apparently the only SDK I can use is the "StandardSDK_500". I can't use the other one. And so, I can't debug anything else than the emulator. I hope this was clear enough. In advance, thanks. Tag: Graphical Shell problems Tag: 71397
  - 15
    - Device Driver programming Dear all, I have been working in Embedded team. Now i try to write the device driver for a printer. But i have no idea about device drivers. i need your help to understand and write the device drivers. Can anybody help me to write a simple device driver? Thanks & Regards, Veerasivakumar.V -- V.Veerasivakumar InLott Technologies Pvt Ltd, Chennai, India. E-Mail: veerasivakumar@inlott.com Tag: Graphical Shell problems Tag: 71392
  - 16
    - formatting to FAT16 using calls to DeviceIoControl I'm stumped on how to format an SD card to FAT16. I can successfully format a card to FAT32 using the following code, but I need it to be formatted as FAT16 instead. How can I change the partition type to FAT16? I'm currently trying to add calls to IOCTL_DISK_SET_PARTITION_INFO but as of now I cannot get it to work. [DllImport("coredll.dll", EntryPoint="CreateFile", SetLastError=true)] internal static extern int CreateFileCE( string lpFileName, uint dwDesiredAccess, uint dwShareMode, int lpSecurityAttributes, uint dwCreationDisposition, uint dwFlagsAndAttributes, int hTemplateFile); [DllImport("coredll.dll", EntryPoint="DeviceIoControl", SetLastError=true)] internal static extern int DeviceIoControlCE( IntPtr hDevice, int dwIoControlCode, byte[] lpInBuffer, int nInBufferSize, byte[] lpOutBuffer, int nOutBufferSize, ref int lpBytesReturned, IntPtr lpOverlapped); internal static int METHOD_BUFFERED = 0; internal static int FILE_ANY_ACCESS = 0; internal static int FILE_READ_ACCESS = 0x0001; internal static int FILE_WRITE_ACCESS = 0x0002; internal static int IOCTL_DISK_BASE = 0x00000007; internal static int IOCTL_DISK_FORMAT_VOLUME = ((IOCTL_DISK_BASE) << 16) | ((FILE_ANY_ACCESS) << 14) | ((0x0088) << 2) | (METHOD_BUFFERED); internal static int IOCTL_DISK_SET_PARTITION_INFO = ((IOCTL_DISK_BASE) << 16) | ((FILE_READ_ACCESS | FILE_WRITE_ACCESS) << 14) | ((0x0002) << 2) | (METHOD_BUFFERED); internal static int IOCTL_DISK_SET_PARTITION_INFO_EX = ((IOCTL_DISK_BASE) << 16) | ((FILE_READ_ACCESS | FILE_WRITE_ACCESS) << 14) | ((0x0013) << 2) | (METHOD_BUFFERED); ----- int var = 0, numMegs = 0, pBar = 0; IntPtr hFile = IntPtr.Zero; System.IntPtr ptr = IntPtr.Zero; object selectedObj; string s_selectedObj = ""; //Get our selected drive, this comes back as a string similiar to //"SD Card - 242MB (formatted" selectedObj = this.Media_Combo_Box.SelectedItem; s_selectedObj = selectedObj.ToString(); //Strip the string from the additional information we gave to the user s_selectedObj = s_selectedObj.Remove(s_selectedObj.IndexOf("-",0,s_selectedObj.Length)-1, s_selectedObj.Length-s_selectedObj.IndexOf("-",0,s_selectedObj.Length)+1); hFile = (IntPtr)CreateFileCE("\\" + s_selectedObj + "\\Vol:", 0x40000000, 0, 0, 3, 0, 0); ok = DeviceIoControlCE(hFile, IOCTL_DISK_FORMAT_VOLUME, null, 0, null, 0, ref var, ptr); Tag: Graphical Shell problems Tag: 71391
  - 17
    - CreateFile() Smartphone 2002 and 2003 Hi, I'm trying to read sectors of the Storage Card on Smartphones 2002 and Smartphones 2003... I've tried to use CreateFile() as I do on PC but it fails and returns me an invalid handle with different error codes depending from the filename I provide... such as "DSK1:", "\Storage Card", \\.\A:, "\DISK0"... Has someone already succeeded in accessing disk informations on these platforms ? Thanks ! -- Thomas Carton Tag: Graphical Shell problems Tag: 71385
  - 18
    - ADOCE Does CE.NET support ADOCE? -- Jerry Masterpiece Technology Tel: 8610-82684081/2/3 ext.306 Fax: 8610-82684081/2/3 ext.105 www.msptc.com Tag: Graphical Shell problems Tag: 71384
  - 19
    - ADOCE Does ce.net support ADOCE ? -- Jerry(ãÉµÇÑ§) Masterpiece Technology(ÃÀË¹±È¿Æ¼¼) Tel: 8610-82684081/2/3 ext.306 Fax: 8610-82684081/2/3 ext.105 www.msptc.com Tag: Graphical Shell problems Tag: 71383
  - 20
    - CE5.0 USB driver, the relationship of PDD and MDD Dear all: Lately, I try to trace CE5.0 usb driver. In Mdd-layer usb driver, it supports the function, UfnMdd_Notify(), to change usb states. But I have no sense how those states are changed. Any document or web link details to describe this. Thx. Tag: Graphical Shell problems Tag: 71374
  - 21
    - Issue when changing IP address from Static to DHCP Hi, I have a board with a PXA270 chip which has a Win CE 5.0 image loaded on it. When booting, the board is given a static IP address of 192.168.0.21 (or something like that). I can open up Platform Builder and use Remote Registry Editor to edit the registry (the device is connected to my dev PC via ActiveSync on a USB cable). I can run a client application written in c# - it basically connects to a server running on my dev PC and plays "TCP packet tennis" by sending an object to the server and the server echoes it, and then the client echoes it and so on... I then needed to set up file sharing on the device. I couldn't do this with the static ip for some reason, so i decided to change the it to a dhcp ip address. This gave it an ip of 10.10.0.xxx, a subnet mask of 255.255.255.0, and gateway 10.10.0.yyy. I was able to access the "Windows CE Remote Management Tool" using IE on my dev PC. I gave permission to share the flash drive and the \Windows folder. I then typed \\10.10.0.xxx on my browser and it worked but it took forever to load. When i browse the shared folders, they too take a long time to load - it's very inconvenient and not very feasible to be put out in the field. I then tried running my app - it ran but it didn't work as nicely as before - it kept receiving packets in segments... I then tried running the Remote Registry editor again and it wouldn't work. Sometimes it would load, but i could browse the main keys. Other times it wouldn't even load. I then decided to change the ip address back to the static version and everything worked fine except for file sharing. What is going on here? Thanks in advance. Tag: Graphical Shell problems Tag: 71371
  - 22
    - ActivateDevice error in USB driver I've created a usb driver by copying source for printer driver given in Public area. I'm using PB 5.0. I am getting NULL returned from ActivateDevice call with following error message in my debug message window "DEVICE!CreateDevice: illegal entry point combination in driver DLL 'PDACOM.DLL'". What are some potential causes for this "illegal entry point combination"? Here is my dumpbin \EXPORT for the dll: Microsoft (R) COFF/PE Dumper Version 7.10.4017 Copyright (C) Microsoft Corporation. All rights reserved. Dump of file PDACOM.dll File Type: DLL Section contains the following exports for PDACOM.dll 00000000 characteristics 42DEDBA9 time date stamp Wed Jul 20 16:18:01 2005 0.00 version 1 ordinal base 10 number of functions 10 number of names ordinal hint RVA name 1 0 000077C8 PDA_Close 2 1 000073DC PDA_Deinit 3 2 00007F38 PDA_IOControl 4 3 00007178 PDA_Init 5 4 000075D4 PDA_Open 6 5 00007C2C PDA_Read 7 6 000078E0 PDA_Write 8 7 00004090 USBDeviceAttach 9 8 00003B3C USBInstallDriver 10 9 00003F64 USBUnInstallDriver Summary 1000 .data 1000 .pdata 1000 .reloc B000 .text Tag: Graphical Shell problems Tag: 71363
  - 23
    - assembly in Platform Builder I am attemping to write some ARM files to send over to my PXA27x DVK. However, I am unfamiliar with the armasm and the procedures to do this through platform builder. Also my debug options to view registers on the 27x are grayed out. Any help is appreciated. Thanks, Fred Thomsen Tag: Graphical Shell problems Tag: 71356
  - 24
    - CEPC 4.1 Persist Default Network Username and Password I need to be able to persist and restore the network id information as it is placed in the system through the user control panel applet. How can I accomplish this? This information is not stored in the registry and is lost when our device powers down. -- Howard Swope [howardsnewsATspitzincDOTcom] Software Engineer Spitz, Inc [http://www.spitzinc.com] Tag: Graphical Shell problems Tag: 71352
  - 25
    - How does power management discover battery state changes? I am trying to develop a PM scheme for our device under WinCE 5.0 and one of the features we need to expose is PM notifications of battery states (critical, charging, etc...) After reading through the help and Boling's book I am still a little unclear as to how the information from the battery driver is communicated to the PM system. The help implies that simply implementing the PDD layer of the batt driver will allow such notifications to function. I am guessing this means that PM polls the battery driver; but this is never explicitly stated and let's just say I'm not exactly batting 1000 on these kind of guesses. Can anyone clairify how the notification part of the system works? Am I missing something painfully obvious in the documentation? TIA -Tim Tag: Graphical Shell problems Tag: 71351

Hi,

Can I use a PPC-like shell in my WinCE 5.0 ? and how to?

Best regards,
Jack Zhao

Re: Graphical Shell problems by Dean

Dean
Tue Jul 26 08:10:30 CDT 2005

Not the same Pocket PC shell that is in the PPC OSes. There is a catalog
component that is geared toward PDA style devices, that is at least better
than the regular shell. It's designed for QVGA portrait devices. I'd say
the best you can do is add this component, and also add the aygshell
component.

--
Dean Ramsier - eMVP

"jackzhao" <jackzhao@yeah.net> wrote in message
news:%23SYe14bkFHA.2724@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> Can I use a PPC-like shell in my WinCE 5.0 ? and how to?
>
> Best regards,
> Jack Zhao
>
>

Top

Re: Graphical Shell problems by Steve

Steve
Tue Jul 26 09:46:58 CDT 2005

Well, as Dean said. Not the exact one from Pocket PCs. You could of course
start with the existing shell and AYGSHELL components and write your own
that is as close to the behavior of the Pocket PC one as possible.

--
Steve Maillet
EmbeddedFusion
www.EmbeddedFusion.com
smaillet at EmbeddedFusion dot com

Top