SDK Question

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - RNDIS+CETK-Is it possible? Dear All, I have my Board configured as a RNDIS USB Device. In the device manager of the XP host the board apprears under "Netweork adapter". How should I configure my settings to run CETK tests using this network adapter? To make my question simple instead of Activesync/Ethernet i want to use RNDIS to carry put CETK tests Pls suggest/advice, Cheers, Lakshman Tag: SDK Question Tag: 67357
  - 2
    - Two directories to store files making problem(FMD) I meet a problem to implement NAND driver. I am tying to implelent 2 NAND(32MB, 128MB) flash to my target board. Both are 512 bytes / page NANDs and locate different part on board. What I am trying to do is to make 2 directories to store some files in them. And directories are indepent each other. For example, \ResidentFlash and \ResidentFlash2. \ResidentFlash is used only for 32MB and \ResidentFlash2 is for 128MB. The files stored in 128MB is large, so it takes long time to copy them. When OS needs to update, I'd like to change only 32MB(i.e. format and write images including bootloader and OS), so that 128MB is used as before without erase or format. -------- Start of register information -------- [HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable] "21"="BINFS" [HKEY_LOCAL_MACHINE\System\StorageManager\BINFS] "Folder"="BINFS" "FriendlyName"="Bin FileSystem" "DLL"="binfs.dll" "MountFlags"=dword:11 "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\FlashDrv] "DriverPath"="Drivers\\BlockDevice\\FlashDrv" ; LoadFlags 0x01 == load synchronously "LoadFlags"=dword:1 "MountFlags"=dword:11 "BootPhase"=dword:0 ;"Order"=dword:2 [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\FlashDrv2] "DriverPath"="Drivers\\BlockDevice\\FlashDrv2" "LoadFlags"=dword:1 "MountFlags"=dword:11 "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\Drivers\BlockDevice\FlashDrv] "Prefix"="DSK" "Dll"="flashdrv.dll" "Order"=dword:0 "Ioctl"=dword:4 "Profile"="FlashDrv" "FriendlyName"="MSFLASH Driver" "MountFlags"=dword:11 "BootPhase"=dword:0 "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "Flags"=dword:1000 [HKEY_LOCAL_MACHINE\Drivers\BlockDevice\FlashDrv2] "Prefix"="DSK" "Dll"="flashdrv2.dll" "Order"=dword:0 "Ioctl"=dword:4 "Profile"="FlashDrv2" "FriendlyName"="MSFLASH Driver" "MountFlags"=dword:11 "BootPhase"=dword:0 "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "Flags"=dword:1000 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv] "DefaultFileSystem"="BINFS" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "MountFlags"=dword:11 "Folder"="ResidentFlash" "Name"="Microsoft Flash Disk" "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv\FATFS] ; "MountFlags"=dword:0 "MountFlags"=dword:2 ; support hive-based registry "AutoMount"=dword:1 "AutoPart"=dword:1 "Flags"=dword:00280014 "FormatTfat"=dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv2] ; "DefaultFileSystem"="BINFS" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "MountFlags"=dword:11 "Folder"="ResidentFlash2" "Name"="Microsoft Flash Disk2" "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDrv2\FATFS] "MountFlags"=dword:0 "AutoMount"=dword:1 "AutoPart"=dword:1 "Flags"=dword:00280014 "FormatTfat"=dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager\FATFS] "MountFlags"=dword:0 ---------------------------------------------------- My concept to do is in EBOOT, 1) format whole NANDs(32MB and 128MB). 2) write MBR on 32MB 3) write BinFS, FAT FS partition on 32MB 4) write MBR on 128MB 5) write FAT FS partition on 128MB after launch OS, 6) load FlashDrv.dll which points to 32MB 7) load FlashDrv2.dll which points to 128MB Is this way right? If it is or not, any sort of comments are appreciated, thanks, p.s : Before posting this message, I asked Sachin, he said the registry setting look correct. thank for sachin. Tag: SDK Question Tag: 67354
  - 3
    - Closesocket All, I have socket application which needs to use the same socketid within a defined range. The steps are 1) Create socket --> using socket() 2) send, recv..etc..functions 3) Closesocket --> using closesocket() 4) Create socket --> using socket(). The application needs the same socket id as obtained from the 1st socket call. Since I have already closed the socket, the wince is expected to return the same socket id. But it is not. Linux and other OS does it that way, where if socket is closed, the next socket call would return the closed socket id. Any inputs..hints.. help..anything would be very very helpful thanks Arun Tag: SDK Question Tag: 67347
  - 4
    - How to enable intel PSM? Hello,all, I want to integrate intel PSM into wince500. CPU is pxa270,flash is K3.(I have got intel psm3.8 beta version for wince500). MMU addresstable is: DCD 0x9C600000, 0x00000000, 32 ; MAINSTONEII: nCS0: Boot Flash (32MB). and config.bib is RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 9C700000 01400000 RAMIMAGE RAM 80100000 01F00000 RAM I modify plat_api.c as following: UINT8 PLAT_DefineArrayParameters(PSM_OEMInfoPtr oem_info_ptr) { static const PSM_OEMInfo oem_info = { /* PhysicalReadStartAddress */ (VOID_PTR)0x00000000, /* PhysicalWriteStartAddress */ (VOID_PTR)0x00000000, /* PhysicalBurstReadStartAddress */ (VOID_PTR)0x00000000, /* VirtualReadStartAddress */ (VOID_PTR)0xBC600000, /* VirtualWriteStartAddress */ (VOID_PTR)0xBC600000, /* VirtualBurstReadStartAddress */ (VOID_PTR)0xBC600000, /* MaximumArrayLength */ 0x02000000, /* MaximumRegistrySize */ 0x00000000, /* Not used for WCE500 */ /* ManagedAreaStart */ 0x01A00000, /* ManagedAreaLength */ 0x00500000, /* ReadBusWidth */ 32, /* WriteBusWidth */ 32, /* BurstReadBusWidth */ 0 }; and platform.reg: [HKEY_LOCAL_MACHINE\System\StorageManager\AutoLoad\PSM] "Dll"="PSMFSD.dll" "Paging"=dword:1 ; "LoadFlags"=dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager] "Dll"="fsdmgr.dll" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\FlshDrv] "FolderName"="TESTPSM" But when I download os image to flash through eboot,it produces the following messages: Booting kernel with clean memory configuration: Memory Sections: [0] : start: 8014c000, extension: 00002000, length: 01e92000 [1] : start: 82000000, extension: 00002000, length: 01ffe000 Sp=ffffc7cc ARMInit done. Windows CE KernelInit Updated eptr->e32_vsize to = 000ad000 Scheduling the first thread. 0x83fff024: KernelInit2: pCurThread=83fff024 hCurThread=03fff266 hCurProc=03fff002, KernelInit = 9c724d70 0x83fff024: Detecting VFP...0x83fff024: VFP Not Found! 0x83fff024: Updated eptr->e32_vsize to = 00006000 0x83fff024: Updated eptr->e32_vsize to = 00029000 0x83fff024: Updated eptr->e32_vsize to = 00009000 0x83fff024: Updated eptr->e32_vsize to = 00022000 0x83fff024: ERROR: c:\macallan\private\winceos\coreos\nk\kernel\kwin32.c line 777: 0x83fff024: ConnectDebugger failed 0x83fff024: first = 01f20000, last = 02000000, SharedDllBase = 031c0000 0x83fe98fc: CertMod.dll not found, using old OEM Trust Model 0x83fe98fc: FileSystem Starting - starting with clean file system 0x83fe98fc: FS: initializing ROM/RAM file system 0x83fe98fc: SC_CreateAPIHandle: pvData == NULL 0x83fe98fc: FS: Registering file system ROM, index 2, flags 0x00000031 0x83fe98fc: FS: Mount complete (ROM, index 2, flags 0x00000031) 0x83fe98fc: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 0x83fe98fc: Succeeded on CheckFile 0x83fe98fc: RestoreFile(0x23fcaeb2) called fDelete = TRUE 0x83fe98fc: FS: Registering file system StoreMgr, index 3, flags 0x00000001 0x83fe98fc: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x83fe98fc: FSREG: Logging in default user. 0x83fe98fc: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 0x83fe98fc: SetCurrentUser: Logging out (nobody), logging in default 0x83fe98fc: FS: Using default path "\profiles\" 0x83fe98fc: BuildPath: profiles 0x83fe98fc: BuildPath: profiles\default 0x83fe98fc: SetCurrentUser: User hives not supported -- using same registry for all users 0x83fe98fc: FS: Using default path "Windows\" 0x83fe98fc: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 0x83fe98fc: OEMIoControl: Unsupported Code 0x10100f8 - device 0x0101 func 62 0x83fe98fc: FS: Using default path "Windows\" 0x83fe98fc: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars PSMFSD:DLL Process Attach 0x83fe98fc: Initializing Database 0x83fe98fc: DB:Validation: Name already exists DB_notify_events 0x83fe98fc: DB:CeCreateDatabase failed 0x83fe98fc: Filesystem initialized! 0x83fe98fc: FILESYS: Waiting for kernel to be ready to launch apps 0x83fe9400: InitMUI: DISABLED (-1039860968) 0x83fe98fc: FS: Creating signal event SYSTEM/DevMgrApiSetReady 0x83fe98fc: FS: Creating signal event SYSTEM/PowerManagerReady 0x83fe98fc: FS: Creating signal event SYSTEM/GweApiSetReady 0x83fe98fc: FS: Creating signal event system/events/notify/APIReady 0x83fe98fc: FS: Creating signal event SYSTEM/ShellAPIReady 0x83fe98fc: FILESYS: Launching apps 0x83fe98fc: FILESYS: Launching device.exe 0x83f9f1d8: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x63f9f43e *** 0x83f9f1d8: +InitDeviceFileSystems 0x83f9f1d8: FS: Registering file system $device, index 4, flags 0x00000001 0x83f9f1d8: FS: Registering file system $bus, index 5, flags 0x00000001 0x83f9f1d8: -InitDeviceFileSystems: status is 1 0x83f9f1d8: Ceddk!CalibrateStallCounter: Enter 0x83f9f1d8: Ceddk!CalibrateStallCounter: Could not find stall counter 0x83f9f1d8: Ceddk!BeginCalibration: min(3251) max(3612) 0x83f9f1d8: Ceddk!BeginCalibration: Elapsed is 3498 0x83f9f1d8: Ceddk!BeginCalibration: Delay is 27 0x83f9f1d8: DEVICE!DevloadInit 0x83f9f1d8: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 0x83f9f1d8: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 0x83f9f1d8: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 0x83f9f1d8: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\notify\BusPrefix) returned 2 0x83f9f1d8: [NOTIFY] Module loaded Then the system hangs. Could some one give some suggestions? Thanks. Tag: SDK Question Tag: 67341
  - 5
    - where to get platform builder Hi! Sorry for that silly question - but I can't find the platform builder in my MSDN and on the MS site. I'd like to check out CD 5.0 for a future device. Thanx a lot in advance Ralf Tag: SDK Question Tag: 67337
  - 6
    - Problem in Platform.reg Hi, I have some problem in the platform.reg file. I added 2 lines in the platform.reg in the 1st BSP, then created 2nd BSP (Tiny-kernel). I didn't change anything in and after the "New Platform" wizard. Then I checked the platform.reg. The 2 lines exist in the 2nd platform.reg. I deleted all folders under PBWorkspaces, and tried it again. The problem still exist. I don't know if it's a bug of CE 5.0 or I inadvertently changed somewhere in the Platform Builder. Anybody know this problem, please help. (CE 5.0 evaluation version) Thanks in advance. Tag: SDK Question Tag: 67335
  - 7
    - Where to find MFC for WinCE4.10 Hello, I need MFC dll for WinCE 4.10 to run a third party program on a SA1110 based board Unfortunately I have only Platform Builder 4.2 here Could someone please tell me where can I download it ? TIA Tag: SDK Question Tag: 67333
  - 8
    - custom VoIP Media Manager: AEC and Decode Hi all, We are developing a windows ce 5.0 based VoIP device. Target device supports G.723.1 decoding and AEC and VAD through a separate DSP. Windows CE provides VAIL, RTC client architecture for handling this. VAIL contains a media manager which handles sending/receiving audio data through the RTP stack. We have decided to implement a custom media manager object to make the best use of the available hardware for decoding, AEC etc. However this requires us to implement RTP stack in the media manager. Can we not utilize the RTP media stack provided as part of RTC client API implementation, while exploiting the above hw features in the custom Media Manager object implementation? Are there any free RTP stacks available for Windows CE? regards Tag: SDK Question Tag: 67332
  - 9
    - Does WinCE4.2 support SA1110 ? Hi, I am using Platform Builder 4.2 and I can't understand which BSP should I use to create a SA1110 (strongarm) target. The SA1110 system is old, but I still need it. I have installed: ARM Integrator Intel DBPXA250 Samsung SMDK2410 But I can't find any SA1110 Where is it ? TIA Tag: SDK Question Tag: 67330
  - 10
    - Code size problems with Platform Builders ARM C Compiler I have an Initial Program Loader (a very stripped down bootloader) for an ARM 922 based CPU that must fit in 16K so that it can be auto-loaded from the NAND Flash's boot block when the processor is reset. The current code builds under the ARM development suite and fits into the 16K space. I want to move away from using the ARM development suite tools and use only the Platform Builder tools. When I build the same exact code with the Platform Builder tools it generates an image that is 32K and after MAKEIMG runs, it is 64K. What could be causing the PB C compiler to generate code that is 2x larger than the ARM development suite? I have double checked the optimization flags to ensure it is optimizing for size. I'm doing a retail/release build. Mark Moeller Qualnetics Corporation Tag: SDK Question Tag: 67322
  - 11
    - unresolved external symbol NDIS_PORT_TO_PORT Hello, I am modifying an NDIS driver and I keep getting the error message "unresolved external symbol NDIS_PORT_TO_PORT " when calling the function: "NdisReadPortUshort" I can not figure out where this macro is defined. A general text search on the entire OS install does not reveal it. Can someone tell me where this MACRO is located? Platform : PXA255 OS : winCE 4.2 Thanks in advance -Jeff Tag: SDK Question Tag: 67320
  - 12
    - Refreshing NDIS My system uses dynamic power for the 91c111 chip. At any time, the chip can be powered down. I have expanded the typical media sense functionality to also include handling this. The driver calls NdisMIndicateStatus to indicate the chip hardware is down/up When the chip returns, how can I force NDIS to update its information, mainly re-read the MAC address, etc... thanks! Curt Tag: SDK Question Tag: 67314
  - 13
    - Library search order While building the WinCE 5.0 OAL I need to implement a device specific version of a function, that is defined in the x86\COMMON source tree. I added a new file to the platform specific OAL and implemented the function. But the linker does not use my implementation. Instead is uses the version from oal_other_x86.lib. When I defined another dummy function in my implementation source file, my function is linked. So I can state, that the function fulfills the linker requirements. I assume that my function is not linked, because the linker has found the implementation in oal_other_x86, because of the the search order. In the SOURCES file I can find the oal.lib (with my implementation) before the oal_other_x86.lib. I excpected that the order in the TARGETLIBS macro define the order. What's wrong? How dow I overload the default implementation? /Helge Tag: SDK Question Tag: 67310
  - 14
    - SMDK2410 + Eboot.nb0 Can't Program disk image into SmartMedia car Hi all, I use the CE 5.0 Eboot.bin and I can download the nk.bin. But I can't write the image into SmartMedia Card. I got these errors......... ............................................................ INFO: Found bad SmartMedia block [0xABB]. INFO: Found bad SmartMedia block [0xABD]. INFO: Found bad SmartMedia block [0xABE]. INFO: Found bad SmartMedia block [0xABF]. INFO: Found bad SmartMedia block [0xAC0]. INFO: Found bad SmartMedia block [0xAC2]. INFO: Found bad SmartMedia block [0xAC3]. ERROR: Unable to erase SmartMedia block 0xAC6. ERROR: Failed to perform low-level format of SmartMedia card. What else should I do? Thanks Tag: SDK Question Tag: 67307
  - 15
    - Which BSP for Sa1110 Hi, I am using Platform Builder 4.2 and I wonder which BSP should I choice to create a SA1110 (strongarm) target. I have installed: ARM Integrator Intel DBPXA250 Samsung SMDK2410 But I can't find any SA1110 Thanks Tag: SDK Question Tag: 67293
  - 16
    - CE Target Control service and Hive registry I've set up the hive based registry. Everythings seems to work nice except the CE Target Control service. I still have "Enable CE Target control" option checked but service doesn't start any more with hive registry. KITL is working, debugger is working, TCP/IP over VMini is working, all other things are working too. What may cause CE Target Control to not work with a hive registry? Any ideas? Tag: SDK Question Tag: 67285
  - 17
    - Arm build for the new Device Emulator Hi, Does anyone know how to build an emulator image for the new device emulator, the ARM one that ships with Visual Studio 2005 (Beta 2)? The 'old' emulator was x86. TIA, - John Tag: SDK Question Tag: 67282
  - 18
    - PB50 & MIPS CPU: The action of dialog box is slow. Hi, I am using the Platform Builder 5.0, and I am developing a BSP for MIPS based processor. Now, I have met a strange phenomenon, when I enabled the FULL KERNEL MODE, it seems that the action of switching the tabs of dialog box becomes very slow. For example, it can be reproduced on the dialog box of Internet Explorer ([View] > Internet Options, and switch the tab from 'General' to 'Advanced'). I also confirmed same phenomenon on the MALTA board (20kc CPU) and the BSP which are provided by the MIPS Technologies. Would you let me know, if there is information or a hint? Thanks in advance. Regards, Hiro Tag: SDK Question Tag: 67281
  - 19
    - usbd load device driver issue I found in wince42 usbd searchs the registry to find which device driver is correctly for current device,however the device only write the registry information when loading.that seems cause the usbd can't find the correct registry information since there are no relative information then the device driver can't been loaded. the debug message as follow: 4294854552 PID:3c6daca TID:3b654a2 0x83b658d4: CDevice(Function tier 1)::AllocatePipeArray - attempting to allocate 3 pipes 4294854553 PID:3c6daca TID:3b654a2 0x83b658d4: -CDevice(Function tier 1)::AllocatePipeArray, returning BOOL 1 4294854554 PID:3c6daca TID:3b654a2 0x83b658d4: +USBD:HcdDeviceAttached, Interfaces:1 4294854555 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadDeviceDrivers - Device VendorId: 4163, ProductId: 32774, Release: 256 4294854556 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadUSBClient: pInterface: 0x0 4294854557 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\Default\Default 4294854558 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163 4294854559 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774 4294854560 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774_256 4294854561 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163 4294854562 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774 4294854563 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774_256 4294854564 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0 4294854565 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0_0 4294854566 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0_0_0 4294854567 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadDeviceDrivers loading driver for interface 0 4294854568 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadUSBClient: pInterface: 0x5A0F0 4294854569 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadUSBClient, IFClass: 0x8, SubClass: 0x6, Proto: 0x50 4294854570 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163 4294854570 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774 4294854571 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774_256 4294854572 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163 4294854573 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774 4294854574 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\4163_32774_256 4294854575 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0 4294854576 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0_0 4294854577 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\0_0_0 4294854579 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\Default\8 4294854579 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\Default\8_6 4294854580 PID:3c6daca TID:3b654a2 0x83b658d4: USBD:LoadGroupDriver(): no key LoadClients\Default\Default\8_6_80 4294854612 PID:e3b539ba TID:3b654a2 0x83b658d4: DlgMgr: FindDlgItem id 1 returning NULL. 4294854921 PID:43a8c49e TID:c3a84176 0x83a79000: WINDOWCREATED: -2147483391 Debugger disconnected successfully. Tag: SDK Question Tag: 67280
  - 20
    - Does our OS support DirectDraw ? Hi, My platform uses SMDK2410 CPU without other VGA chip, but I add DirectDraw component into our workspace. Howerver, when I run DirectDraw test in CETK, it shows "Skipped". After I check the log, it shows the following message: DirectDrawCreate returned hr=DDERR_NODIRECTDRAWSUPPORT (0x887600DE) [FILE: ddrawuty_singletons.cpp LINE: 88] Why ? Thanks. Yu. Tag: SDK Question Tag: 67279
  - 21
    - how can updata donNET CF to sp3 how can updata donNET CF to sp3. please help me . Tag: SDK Question Tag: 67276
  - 22
    - warn boot problem As from CE4.2 help document <Kernel Power Management>, when get warm boot command, CE system just clear work ram, unlike Power-on reset, reloading the file system and initialize. But I don't know how to do it. I only call Power-on reset like this: ///////////////////////////////////////////// __asm { cli ; Disable Interrupts mov al, 0FEh ; Reset CPU out 064h, al jmp near $ ; Should not get here } ///////////////////////////////////////////// and it takes a long time rebooting. Does anyone know how to get warm boot only clear work ram? KernelIoControl? how to use? Any other configurations?... Tag: SDK Question Tag: 67271
  - 23
    - What is the best way to do this? Hi, I want to be able to change the appearence of all the shell controls during runtime, so if i make a new function like reinitiate_cache() in gcacheviewxp.cpp: void reinitiate_cache(){ HBITMAP hbmScrollThumb; hbmScrollThumb = SHLoadDIBitmap (L"scroll_thumb.bmp"); Gdi::SelectObject_I(g_cacheview.hdcScrollThumb, (HGDIOBJ)hbmScrollThumb); } and then call that function from for example the control panel, what is the best way to make the function global so I can call it from the control panel application? Should I make a dll so I can call the function through a dll function call or is there any simplier way to achieve this? Regards, Dani Tag: SDK Question Tag: 67260
  - 24
    - Question on VirtualAlloc and VirtualCopy Hi, I just need a bit of help understanding something. In OEMAddresstable there is a set of virtual to physical address mappings. When an app or driver running in user mode needs to access a memory mapped device i read in documentation that it must call virtualalloc to reserve some virtual memory and then virtual copy to map it to the physical address. However this mapping is already done in OEMAddresstable, i would expect all memory mapped devices to be setup here, anyway this is what i have seen in MainstoneII BSP for example and others. So why does one need to call Virtualalloc and VirtualCopy. Hope it is easy for someone to explain what i don't understand. Regards ms Tag: SDK Question Tag: 67255
  - 25
    - Get Mfg ID and serial ID of SDcard on PPC using SDIO Now! I am a application software developer on WindowsCE 4.2. I try to use DeviceIoControl with IOCTL_DISK_GET_STORAGEID to get the Manufacturer ID and serial ID of SD card. It works on most HP, Dell, Acer n30 and so on. However, it does not work on some other PPC like Acer n50 and ASUS. I suspect that IOCTL_DISK_GET_STORAGEID only works on those PPC without SDIO Now! support. Does any one know if I am correct? If I want to get the Manufacturer ID and serial ID of SD card on those PPC using SDIO Now!, are there any way to do so? Thank you for any ideas. John Mok john@sky-power.com.hk Tag: SDK Question Tag: 67251
- Next
  - 1
    - cmd.exe over serial I am working on porting wince to our custom platform. It is a headless device and due to memory constraint we are using tiny kernel configuration. Thus the entire explorer, shell etc are not available. However when the device boots up we need to have "cmd.exe" executed and the prompt available on the serial port. Found that it is possible by the following registry settings [HKEY_LOCAL_MACHINE\Drivers\Console] OutputTo = REG_DWORD:1 // Redirects CMD to COM1 COMSpeed = REG_DWORD:19200 // Speed of serial connection And have cmd.exe executed at startup by a separate application. Since putting cmd.exe in the init registry does execute it but terminates with message "unrecognized option". The application just does a create process and executes cmd.exe. But using platform builder I found that the registry settings set in platform.reg for COMSpeed, does not match with the actual settings on the target. I checked the final reginit.ini which infact had the settings same as platform.reg but the target registry had totally different settings. For ex: A setting of 9600 in platform.reg/reginit.ini would result in target setting of 38400 Any inputs or guidance on this problem Tag: SDK Question Tag: 67242
  - 2
    - XXX_Open not being called !! I need a way to verify that XXX_Open is successfully called, but there is much more to my question... I know that CreateFile will cause the Device Manager to call XXX_Open, and yes, I did verify that XXX_Init is called, and my driver appears in the registry (DLL, and Prefix values only, see below). I use the following C# code to do this: hInDevice = CreateFile(DeviceName.ToString(), GENERIC_WRITE, FILE_SHARE_WRITE, IntPtr.Zero, OPEN_EXISTING, 0, IntPtr.Zero); However, I obtain an exception upon calling CreateFile. The exception description (from C# Exception object) is as follows: "Can't transmit to USB port TRC1:" The entry on WinCE (in the registry) is as folllows: HKEY_LOCAL_MACHINE\Drivers\Active\21 Name = TRC1: Key = Drivers\USB\ClientDrivers\SRT_DEVICE And yes, there is an entry under ClientDrivers. Is my driver actually loaded properly on WinCE? How can I be damn sure that the driver is loaded properly in WinCE? Is just the fact that it shows up in the HKEY_LOCAL_MACHINE\Drivers\Active\xx section good enough to verify this? Tag: SDK Question Tag: 67235
  - 3
    - How to specify the HIVE filesystem? Here is a snippet from the Wince 5.0 documentation: "Hive-based Registry Setup" ... SystemHive is the location and name of the system hive file. Do not include the name of the file system on which the file will be stored; the system will decide which file system to use based on other registry settings. ... My question is: What does it mean "other registry settings"? Could someone pls point me where I can read about? Lets say I have several persistent storages. How do I specify that "system.hv" must be placed to / used from the specified storage? Is it possible to use something like: "SystemHive"="\\MyStorageFolder\\Documents and Settings\\System.hv" Thanks Tag: SDK Question Tag: 67231
  - 4
    - RCP not connecting, continued Hi Matt and everybody else, I cannot seem to post the whole PB debug output. It seems to be too long. Therefore, I'm posting the beginning and the end of the output. Hopefully, it'll have the meaningful info. Let me know how I can send you the full output if this isn't enough. 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 CE Ethernet Bootloader found 32Bit BIOS Entry master_bios32=a00fada0 bios32_call_offset=1b220 for CE/PC 0 PID:0 TID:0 Return from First BIOS EAX=49435000 EBX=f0000,ECX=b6a8 EDX=b250 0 PID:0 TID:0 32 PCI BIOS offset located.addr=1b250 0 PID:0 TID:0 32 PCI BIOS Present EDX=20494350,EAX=11 EBX=f0210,ECX=b600 0 PID:0 TID:0 +GetRoutingOption 0 PID:0 TID:0 search_pci_routing 0 PID:0 TID:0 search_pci_routing found entry =a00fdf60 CE/PC 0 PID:0 TID:0 GetRoutingOption, found ROM version for Routing table. 0 PID:0 TID:0 GetRoutingOption return SUCCESS .AH=1c00 0 PID:0 TID:0 canConfiguredIrq with PCI Exclusive Irq Bit (wExClusive) =1c00 0 PID:0 TID:0 ScanConfigureIrq: BufferSize = 48 @ address 80befc4a 0 PID:0 TID:0 ScanConfigureIrq: for Bus=0 ,Device=12 SlotNumber=1 0 PID:0 TID:0 INTA_LinkValue=2,INTA_IrqBitMap=deb8 0 PID:0 TID:0 INTB_LinkValue=3,INTB_IrqBitMap=deb8 0 PID:0 TID:0 INTC_LinkValue=4,INTC_IrqBitMap=deb8 0 PID:0 TID:0 INTD_LinkValue=1,INTC_IrqBitMap=deb8 0 PID:0 TID:0 ScanConfigureIrq: LinkNumber=2 associated with irq=10 0 PID:0 TID:0 ScanConfigureIrq: for Bus=0 ,Device=13 SlotNumber=2 0 PID:0 TID:0 INTA_LinkValue=3,INTA_IrqBitMap=deb8 0 PID:0 TID:0 INTB_LinkValue=4,INTB_IrqBitMap=deb8 0 PID:0 TID:0 INTC_LinkValue=1,INTC_IrqBitMap=deb8 0 PID:0 TID:0 INTD_LinkValue=2,INTC_IrqBitMap=deb8 0 PID:0 TID:0 ScanConfigureIrq: LinkNumber=3 associated with irq=12 0 PID:0 TID:0 ScanConfigureIrq: for Bus=0 ,Device=19 SlotNumber=0 0 PID:0 TID:0 INTA_LinkValue=1,INTA_IrqBitMap=deb8 0 PID:0 TID:0 INTB_LinkValue=0,INTB_IrqBitMap=deb8 0 PID:0 TID:0 INTC_LinkValue=0,INTC_IrqBitMap=deb8 0 PID:0 TID:0 INTD_LinkValue=0,INTC_IrqBitMap=deb8 0 PID:0 TID:0 ScanConfigureIrq: LinkNumber=1 associated with irq=11 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 = 80226988, pTOC = 80a996f8, pTOC->ulRamFree = 80ce1000, MemForPT = 00042000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 Configuring: Primary pages: 28373, Secondary pages: 0, Filesystem pages = 256 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: 80d24000, extension: 00007000, length: 06ed5000 0 PID:0 TID:0 X86Init done, OEMAddressTable = 8023c6a8. 0 PID:0 TID:0 Windows CE KernelInit 4294767297 PID:7bff002 TID:7bff1da Updated eptr->e32_vsize to = 00092000 4294767297 PID:7bff002 TID:7bff1da Scheduling the first thread. 4294767299 PID:7bff002 TID:7bff1da 0x87bff030: KernelInit2: pCurThread=87bff030 hCurThread=07bff1da hCurProc=07bff002, KernelInit = 8026c70e 4294767300 PID:7bff002 TID:7bff1da 0x87bff030: Updated eptr->e32_vsize to = 00010000 4294767301 PID:7bff002 TID:7bff1da 0x87bff030: >>> Loading module NK.EXE at address 0x80220000-0x802B2000 (RW data at 0x80B7A000-0x80BF7F0B) Kernel debugger connected (KDBG stream opened). Kernel Version 1169 Checked loaded at 0x80220000, data relocated at 0x80b7a000 Debugger connection established (Target CPU is X86). Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\NK.EXE' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\KD.DLL' Finished re-loading kernel modules. Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CELOG.DLL', no matching symbolic information found. Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\COREDLL.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\FILESYS.EXE' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\FSDMGR.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\RELFSD.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\PM.DLL' Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\DEVICE.EXE' 4294767303 PID:7bff002 TID:7bff1da 0x87bff030: Updated eptr->e32_vsize to = 00003000 4294767304 PID:7bff002 TID:7bff1da 0x87bff030: >>> Loading module celog.dll at address 0x802C2000-0x802C5000 (RW data at 0x80C00584-0x80C00AC4) 4294767305 PID:7bff002 TID:7bff1da 0x87bff030: CeLogInit 4294767305 PID:7bff002 TID:7bff1da 0x87bff030: CeLog: Large buffer size unspecified, using default size 4294767305 PID:7bff002 TID:7bff1da 0x87bff030: CeLog: Small buffer size invalid or unspecified, using default size 4294767305 PID:7bff002 TID:7bff1da 0x87bff030: CeLog: Large buffer size = 131072 4294767305 PID:7bff002 TID:7bff1da 0x87bff030: CeLog: Small buffer size = 4096 4294767309 PID:7bff002 TID:7bff1da 0x87bff030: -CeLogInit 4294767310 PID:7bff002 TID:7bff1da 0x87bff030: CeLog Zones : CE = 0xFFBFFFFF, User = 0xFFBFFFFF, Proc = 0xFFFFFFFF 4294767310 PID:7bff002 TID:7bff1da 0x87bff030: CeLog is now live! 4294767311 PID:7bff002 TID:7bff1da 0x87bff030: first = 01f60000, last = 02000000, SharedDllBase = 035d0000 4294767320 PID:7bff002 TID:7bff1da 0x87bff030: >>> Loading module coredll.dll at address 0x03F90000-0x03FF6000 (RW data at 0x01FFF000-0x01FFF950) 4294767321 PID:7bff002 TID:7bff1da 0x87bff030: Did not find emulation code for x86... using floating point hardware. 4294767343 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: >>> Loading module filesys.exe at address 0x04010000-0x04071000 4294767346 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: FileSystem Starting - starting with clean file system 4294767355 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: FSVOL: Opening existing volume 4294767358 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: FSVOL: Volume heap already initialized 4294767360 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: FSVOL: Initializing volume heap 4294767381 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: PCIReg(key: Drivers\BuiltIn\PCI\Instance\KITL, device: 0/12/0) 4294767398 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: >>> Loading module fsdmgr.dll at address 0x03ED0000-0x03EE7000 (RW data at 0x01FEF000-0x01FEF760) 4294767410 PID:47bb5be2 TID:47bb5bb2 0x87bb5a08: >>> Loading module relfsd.dll at address 0x03F20000-0x03F29000 (RW data at 0x01FF5000-0x01FF5ABC) 4294767439 PID:67b86c5a TID:67b86c2a 0x87b86a80: >>> Loading module pm.dll at address 0x03F70000-0x03F77000 (RW data at 0x01FFB000-0x01FFB55C) 4294767441 PID:67b86c5a TID:67b86c2a 0x87b86a80: *** Power Manager: DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x67b86c5a *** 4294767442 PID:67b86c5a TID:67b86c2a 0x87b86a80: >>> Loading module device.exe at address 0x06010000-0x0601D000 4294767445 PID:47bb5be2 TID:47b8cf5a 0x87b86800: Mounted ReleaseFSD volume '\Release' 4294768598 PID:67b86c5a TID:67b86c2a 0x87b86a80: >>> Loading module ceddk.dll at address 0x03EB0000-0x03EB5000 (RW data at 0x01FEB000-0x01FEB06C) Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEDDK.DLL' 4294768600 PID:67b86c5a TID:67b86c2a 0x87b86a80: Ceddk!CalibrateStallCounter: Enter 4294768601 PID:67b86c5a TID:67b86c2a 0x87b86a80: Ceddk!CalibrateStallCounter: Could not find stall counter Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\REGENUM.DLL' 4294768602 PID:67b86c5a TID:67b86c2a 0x87b86a80: Ceddk!BeginCalibration: min(119) max(149) 4294768605 PID:67b86c5a TID:67b86c2a 0x87b86a80: Ceddk!BeginCalibration: elapsed is 149 4294768605 PID:67b86c5a TID:67b86c2a 0x87b86a80: Ceddk!BeginCalibration: delay is 20 4294768606 PID:67b86c5a TID:67b86c2a 0x87b86a80: +PmInit 4294768607 PID:67b86c5a TID:67b86c2a 0x87b86a80: -PmInit: returning 1 4294768608 PID:67b86c5a TID:67b86c2a 0x87b86a80: DEVICE!DevloadInit 4294768608 PID:67b86c5a TID:67b86c2a 0x87b86a80: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 4294768609 PID:67b86c5a TID:67b86c2a 0x87b86a80: DEVICE!ActivateDeviceEx(Drivers\BuiltIn) entered 4294768617 PID:67b86c5a TID:67b86c2a 0x87b86a80: >>> Loading module regenum.dll at address 0x03F80000-0x03F85000 (RW data at 0x01FFD000-0x01FFD4A4) 4294768661 PID:67b86c5a TID:67b86c2a 0x87b86a80: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCI) entered 4294769839 PID:67b86c5a TID:67b86c2a 0x87b86a80: >>> Loading module pcibus.dll at address 0x03620000-0x03633000 (RW data at 0x01F66000-0x01F6671C) Loaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\PCIBUS.DLL' <<< SOME LINES STRIPPED >>> 11595 PID:479e9822 TID:47a54f7a 0x879e99d0: >>> Loading module CEMGRC.EXE at address 0x10010000-0x1001E000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE', no matching symbolic information found. 11659 PID:479e9822 TID:47a54f7a 0x879e99d0: >>> Loading module cetlkitl.dll at address 0x01F50000-0x01F55000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CETLKITL.DLL', no matching symbolic information found. 11670 PID:479e9822 TID:47a54f7a Opening KITL stream "platmanXport"... 11673 PID:479e9822 TID:47a54f7a KITL stream platmanXport: buffer start=0x42600000 end=0x42606400 12769 PID:479e9822 TID:47a54f7a CKITLConnection established for stream platmanXport 12770 PID:479e9822 TID:47a54f7a CKITLConnection::Close stream platmanXport 12772 PID:479e9822 TID:47a54f7a Opening KITL stream "strm-13"... 12774 PID:479e9822 TID:47a54f7a KITL stream strm-13: buffer start=0x42600000 end=0x42606400 12973 PID:479e9822 TID:47a54f7a CKITLConnection established for stream strm-13 13222 PID:479e9822 TID:47a54f7a Opening KITL stream "platmanXport"... 13225 PID:479e9822 TID:47a54f7a KITL stream platmanXport: buffer start=0x42700000 end=0x42706400 13431 PID:479e9822 TID:47a54f7a CKITLConnection established for stream platmanXport 13433 PID:479e9822 TID:47a54f7a CKITLConnection::Close stream platmanXport 13435 PID:479e9822 TID:47a54f7a Opening KITL stream "strm-14"... 13437 PID:479e9822 TID:47a54f7a KITL stream strm-14: buffer start=0x42700000 end=0x42706400 13635 PID:479e9822 TID:47a54f7a CKITLConnection established for stream strm-14 13639 PID:479e9822 TID:47a54f7a Checking if extended keep alive timeouts feature is set...No 17544 PID:e79a70da TID:e79b2bca 0x879a7198: >>> Loading module CEMGRC.EXE at address 0x12010000-0x1201E000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE', no matching symbolic information found. 17619 PID:e79a70da TID:e79b2bca 0x879a7198: e79a70da.e79b2bca> 17620 PID:e79a70da TID:e79b2bca 0x879a7198: Cairole: 17621 PID:e79a70da TID:e79b2bca 0x879a7198: DLL doesn't have fully qualified path in registry \Windows\PSPubSubCE.dll 17630 PID:e79a70da TID:e79b2bca 0x879a7198: >>> Loading module pspubsubce.dll at address 0x01F40000-0x01F46000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\PSPUBSUBCE.DLL', no matching symbolic information found. 27409 PID:e79a70da TID:e79b2bca 0x879a7198: Process CEMGRC.EXE loaded Module pspubsubce.dll without freeing it before process exit 27412 PID:e79a70da TID:e79b2bca 0x879a7198: <<< Unloading module CEMGRC.EXE at address 0x12010000-0x1201E000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE' 27416 PID:e79a70da TID:e79b2bca 0x879a7198: <<< Unloading module pspubsubce.dll at address 0x01F40000-0x01F46000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\PSPUBSUBCE.DLL' 27479 PID:279a713a TID:279a70da 0x879a7e58: >>> Loading module CEMGRC.EXE at address 0x12010000-0x1201E000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE', no matching symbolic information found. 27556 PID:279a713a TID:279a70da 0x879a7e58: 279a713a.279a70da> 27557 PID:279a713a TID:279a70da 0x879a7e58: Cairole: 27558 PID:279a713a TID:279a70da 0x879a7e58: DLL doesn't have fully qualified path in registry \Windows\rtsce.dll 27568 PID:279a713a TID:279a70da 0x879a7e58: >>> Loading module rtsce.dll at address 0x01F40000-0x01F4E000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\RTSCE.DLL', no matching symbolic information found. 53067 PID:279a713a TID:279a70da 0x879a7e58: Process CEMGRC.EXE loaded Module rtsce.dll without freeing it before process exit 53070 PID:279a713a TID:279a70da 0x879a7e58: <<< Unloading module CEMGRC.EXE at address 0x12010000-0x1201E000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE' 53074 PID:279a713a TID:279a70da 0x879a7e58: <<< Unloading module rtsce.dll at address 0x01F40000-0x01F4E000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\RTSCE.DLL' 53136 PID:479b2b5a TID:479a70da 0x87978560: >>> Loading module msitlogr.dll at address 0x01F30000-0x01F43000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\MSITLOGR.DLL', no matching symbolic information found. 53168 PID:479b2b5a TID:479a70da 0x87978560: CSharedMemory::CommonOpen 'DLP_Administration' 11392 bytes - new memory 53191 PID:479b2b5a TID:479a70da 0x87978560: >>> Loading module rtsce.dll at address 0x01F20000-0x01F2E000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\RTSCE.DLL', no matching symbolic information found. 53207 PID:479b2b5a TID:479a70da 0x87978560: >>> Loading module ConPMon.exe at address 0x12010000-0x12017000 Loaded 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CONPMON.EXE', no matching symbolic information found. 53220 PID:479b2b5a TID:479a70da 0x87978560: CSharedMemory::CommonOpen 'CECAP-PERTHREAD' 1048576 bytes - new memory 64541 PID:479b2b5a TID:479a70da 0x87978560: <<< Unloading module msitlogr.dll at address 0x01F30000-0x01F43000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\MSITLOGR.DLL' 64545 PID:479b2b5a TID:479a70da 0x87978560: Process ConPMon.exe loaded Module rtsce.dll without freeing it before process exit 64548 PID:479b2b5a TID:479a70da 0x87978560: <<< Unloading module ConPMon.exe at address 0x12010000-0x12017000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CONPMON.EXE' 64552 PID:479b2b5a TID:479a70da 0x87978560: <<< Unloading module rtsce.dll at address 0x01F20000-0x01F2E000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\RTSCE.DLL' 107232 PID:479e9822 TID:679e9852 CKITLConnection::Close stream strm-14 107234 PID:479e9822 TID:679e9852 CKITLConnection::Close stream strm-13 107238 PID:479e9822 TID:47a54f7a CKITLConnection::ReadBytes - CallKitlRecv failed 107240 PID:479e9822 TID:47a54f7a 0x879e99d0: <<< Unloading module cetlkitl.dll at address 0x01F50000-0x01F55000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CETLKITL.DLL' 107497 PID:479e9822 TID:47a54f7a 0x879e99d0: <<< Unloading module CEMGRC.EXE at address 0x10010000-0x1001E000 Unloaded symbols for 'D:\WINCE420\PUBLIC\NCA_HL\RELDIR\IEI_WAFER-5823RDEBUG\CEMGRC.EXE' Thanks for your support Regards Oskar Tag: SDK Question Tag: 67226
  - 5
    - Modifying dial-up settings from the registry Hi all, I have an application which saves the dial-up registry settings in a file and sets the registry values according to these saved settings when the device boots (I use ram-based registry so after a cold reboot all dial up connection info is lost). I save and modify the settings of the following registry keys: [HKCU\ControlPanel\Comm] AutoCnct Cnct [HKCU\ControlPanel\Dial] HighLocID CurrentLoc [HKCU\ControlPanel\Dial\Locations] "0" "1" [HKCU\Comm\Rasbook\'Desktop @ 19200'] Entry [HKCU\Comm\Rasbook\MyConnection] Entry DevCfg Domain User [HKLM\Comm\Autoras] Dialer RasEntry NoPromptOpt RasEntryOpt When I modify the registry data using these entries I can see "MyConnection" dial-up connection and all its properties in the connmc.exe window. However, if I double-click on the MyConnection icon to open the Dial-up Connection dialog box I get an exception because of the dialing pattern. Normally the "Phone" edit box on the dialog shows the phone number of the connection with the dialing pattern prefixes. Phone: 9,011,90 555 1234567 But after I modify the registry this edit box shows nothing but commas, causing an exception to occur: Phone: , , If I click on the Dial Properties button and close the window by pressing Enter or the OK button on the top right, the phone number is displayed correctly. (I don't change anything in the dialing properties dialog box since the modifications I make are displayed correctly). Here is a part of the debug output: //////////////////////////////////////////////////// 85008 PID:c3486fd2 TID:c35dbd2a 0x834fc000: >>> Loading module rnaapp at address 0x12010000-0x1201F000 Loaded symbols for 'D:\WINCE420\PUBLIC\PWIT\RELDIR\ESIT_VORTEX86DEBUG\RNAAPP.EXE' 85101 PID:c36a8f92 TID:e3458032 0x83458e28: -AfdRasGetEntryProperties Return Code 603 85298 PID:c36a8f92 TID:e3458032 0x83458e28: -PmGetDevicePower: returning dwStatus 2 85442 PID:c36a8f92 TID:835c6c7a 0x835c23d8: AUTORAS:: Dialer notifies: [Dialer Start] 85844 PID:c36a8f92 TID:23551f9a 0x834aa800: ParseTranslateStrings - RegEnumValue returned 2. 85844 PID:c36a8f92 TID:23551f9a 0x834aa800: Exception 00e Thread=834aa800 Proc=c36a8f92 'device.exe' 85844 PID:c36a8f92 TID:23551f9a 0x834aa800: AKY=ffffffff PC=03fc8531 ESP=0826f7dc EA=00000000 85848 PID:c36a8f92 TID:23551f9a 0x834aa800: KPSLExceptionHandler: flags=0 ControlPc=00000000 85860 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 85864 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 85870 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 85873 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 93292 PID:235c292a TID:c35dbd2a 0x834fc000: DlgMgr: FindDlgItem id 1 returning NULL. 94070 PID:235c292a TID:c35dbd2a 0x834fc000: DlgMgr: FindDlgItem id 2 returning NULL. 94072 PID:c36a8f92 TID:c35dbd2a 0x834fc000: Got IDCANCEL 94335 PID:c36a8f92 TID:23441332 0x833ef9b8: ParseTranslateStrings - RegEnumValue returned 2. 94336 PID:c36a8f92 TID:23441332 0x833ef9b8: Exception 00e Thread=833ef9b8 Proc=c36a8f92 'device.exe' 94336 PID:c36a8f92 TID:23441332 0x833ef9b8: AKY=ffffffff PC=03fc8531 ESP=0826f7dc EA=00000000 94339 PID:c36a8f92 TID:23441332 0x833ef9b8: KPSLExceptionHandler: flags=0 ControlPc=00000000 94353 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 94356 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 94363 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 94366 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 97682 PID:235c292a TID:c35dbd2a 0x834fc000: DlgMgr: FindDlgItem id 1 returning NULL. 101327 PID:235c292a TID:c35dbd2a 0x834fc000: DlgMgr: FindDlgItem id 1 returning NULL. 101329 PID:c36a8f92 TID:c35dbd2a 0x834fc000: Got IDOK 101630 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 101632 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 101639 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\0 returned 2 101642 PID:c36a8f92 TID:c35dbd2a 0x834fc000: TAPI:OpenTollList - RegOpenKeyEx Locations\TollLists\1 returned 2 108839 PID:c36a8f92 TID:2357035a 0x835c6aa0: i_lineOpen: ptLine x38810, ptLineApp x389F0 108846 PID:c36a8f92 TID:346a832 0x833ef9b8: ASYNCMAC: Dialing 'T9,08222115600' 108847 PID:c36a8f92 TID:346a832 0x833ef9b8: UNIMODEM:TSPI_lineMakeCall - Check CallParams 108857 PID:c36a8f92 TID:34fcc42 0x833eb0a8: UNIMODEM:DevlineOpen - device already open 110407 PID:c36a8f92 TID:34fcc42 0x833eb0a8: UNIMODEM:ModemInit Error x2 reading Init string 2 112508 PID:c36a8f92 TID:34fcc42 0x833eb0a8: UNIMODEM:ModemInit Error x2 reading Init string 2 141865 PID:c36a8f92 TID:634fc852 0x834aa800: PPP: -pppMac_GetLinkInfo 143852 PID:c36a8f92 TID:4366fbba 0x83627218: +OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp Handle 0x81BF7A4) 143854 PID:c36a8f92 TID:4366fbba 0x83627218: Opened registry info for Comm\Hayes Compatible on COM1:\Parms\TcpIp 143855 PID:c36a8f92 TID:4366fbba 0x83627218: -OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp *Handle 0x81BF7A4, BOOL Ret: 1) 143855 PID:c36a8f92 TID:4366fbba 0x83627218: +GetGeneralIFConfig(ConfigInfo 0x81BF73C Handle 0x87600) 143857 PID:c36a8f92 TID:4366fbba 0x83627218: Converted 10.10.20.6 to address A0A1406 143859 PID:c36a8f92 TID:4366fbba 0x83627218: Converted 213.243.1.40 to address D5F30128 143860 PID:c36a8f92 TID:4366fbba 0x83627218: Converted 213.243.1.42 to address D5F3012A 143862 PID:c36a8f92 TID:4366fbba 0x83627218: GetGeneralIFConfig:Unable to read WINS value! 143864 PID:c36a8f92 TID:4366fbba 0x83627218: -GetGeneralIFConfig(ConfigInfo 0x81BF73C Handle 0x87600 Ret: TRUE) 143866 PID:c36a8f92 TID:4366fbba 0x83627218: +GetIFAddrList(NumAddr* 0x81BF6D8 Handle 0x87600) 143868 PID:c36a8f92 TID:4366fbba 0x83627218: Converted 62.29.72.184 to address 3E1D48B8 143868 PID:c36a8f92 TID:4366fbba 0x83627218: Converted 255.0.0.0 to address FF000000 143869 PID:c36a8f92 TID:4366fbba 0x83627218: -GetIFAddrList(NumAddr* 0x81BF6D8/1 Ret: 0xC8760) 143870 PID:c36a8f92 TID:4366fbba 0x83627218: *IPAddNTE: calling PPPDynRegister 143872 PID:c36a8f92 TID:4366fbba 0x83627218: InitNTE: setting fIPRouteOn to 1 143872 PID:c36a8f92 TID:4366fbba 0x83627218: *InitNTE: Restarting IPRouteTimeout timer 143875 PID:c36a8f92 TID:4366fbba 0x83627218: LanaUp: (NB) pLana 53BC0 (4) up Addr B8481D3E Mask FF Bcast FFFFFF3E 143877 PID:c36a8f92 TID:4366fbba 0x83627218: *CloseIFConfig(Handle 0x87600) 143880 PID:c36a8f92 TID:4366fbba 0x83627218: +OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp Handle 0x81BF5F8) 143882 PID:c36a8f92 TID:4366fbba 0x83627218: Opened registry info for Comm\Hayes Compatible on COM1:\Parms\TcpIp 143883 PID:c36a8f92 TID:4366fbba 0x83627218: -OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp *Handle 0x81BF5F8, BOOL Ret: 1) 143884 PID:c36a8f92 TID:4366fbba 0x83627218: *CloseIFConfig(Handle 0x87600) 143886 PID:c36a8f92 TID:4366fbba 0x83627218: IGMPDelInclList: AddrPtr=c6f20 NumDelSources=0 DelSourceList=0 143887 PID:c36a8f92 TID:4366fbba 0x83627218: +AfdAddInterface(Adapter Hayes Compatible on COM1: Nte 0xC6430 Context 2, Flags 0 IPAddr B8481D3E cDns 2 cWins 0) 143889 PID:c36a8f92 TID:4366fbba 0x83627218: -AfdAddInterface: fRet: 1 143891 PID:c36a8f92 TID:4366fbba 0x83627218: +IPNotifyClientsIPEvent 143891 PID:c36a8f92 TID:4366fbba 0x83627218: IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 446f0 143892 PID:c36a8f92 TID:4366fbba 0x83627218: IPNotifyClientsIPEvent: PendingIrp 446f0 143892 PID:c36a8f92 TID:4366fbba 0x83627218: IPNotifyClientsIPEvent: SetEvent 143894 PID:c36a8f92 TID:4366fbba 0x83627218: -IPAddInterface [SUCCESS] 143902 PID:c36a8f92 TID:e3430aea 0x834aa800: +RDR:NetBIOSNotifyFunc: Lana 4, flags: 0x1 143903 PID:c36a8f92 TID:e3430aea 0x834aa800: +RDR:NetupIndication, lana 4 143905 PID:c36a8f92 TID:e3430aea 0x834aa800: +RDR:BindToNet: lananum: 4 143908 PID:c36a8f92 TID:e3430aea 0x834aa800: +RDR:BindToNetbiosTransport 143909 PID:c36a8f92 TID:e3430aea 0x834aa800: -RDR:BindToNet successful for lana 4 143910 PID:c36a8f92 TID:e3430aea 0x834aa800: -RDR:NetBIOSNotifyFunc: Lana 4 143914 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: ************DHCP MEDIA STATUS************ 143915 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: SeqNo: 7 143917 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: MediaStatus: 11026 143918 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: Context: 2 - 3 143919 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: AdapterName: Hayes Compatible on COM1: 143919 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: Media Status is: IP_BIND_ADAPTER 143920 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: IPDispatchDeviceControl returned Status 103 143943 PID:c3486fd2 TID:c35dbd2a 0x834fc000: Posting WM_NETCONNECT(TRUE) message 143961 PID:c36a8f92 TID:834fcdd2 0x833ef000: +RDR:RdrUIThread starting 143962 PID:c36a8f92 TID:834fcdd2 0x833ef000: RdrUIThread: SH_WMGR is ready 144049 PID:c36a8f92 TID:e3458032 0x83458e28: -AfdRasGetEntryProperties Return Code 603 144263 PID:c36a8f92 TID:e3458032 0x83458e28: -PmGetDevicePower: returning dwStatus 2 144876 PID:c36a8f92 TID:4366fbba 0x83627218: IPTimer: setting IPTimer of NTE C6430 to 0 147826 PID:c36a8f92 TID:c35dbd2a 0x834fc000: +AfdAddInterface(Adapter Hayes Compatible on COM1: Nte 0xC6430 Context 2, Flags 1 IPAddr B8481D3E cDns 0 cWins 0) 147827 PID:c36a8f92 TID:c35dbd2a 0x834fc000: -AfdAddInterface: fRet: 1 147830 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147832 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147832 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147834 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147835 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147836 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147838 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147840 PID:c36a8f92 TID:c35dbd2a Search Route #2: Route not found 147842 PID:c36a8f92 TID:c35dbd2a Delete Route #3: Route not found 147842 PID:c36a8f92 TID:c35dbd2a Delete Route #3: Route not found 147844 PID:c36a8f92 TID:c35dbd2a Delete Route #3: Route not found 147845 PID:c36a8f92 TID:c35dbd2a 0x834fc000: +OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp Handle 0x1202F358) 147848 PID:c36a8f92 TID:c35dbd2a 0x834fc000: Opened registry info for Comm\Hayes Compatible on COM1:\Parms\TcpIp 147849 PID:c36a8f92 TID:c35dbd2a 0x834fc000: -OpenIFConfig(Comm\Hayes Compatible on COM1:\Parms\TcpIp *Handle 0x1202F358, BOOL Ret: 1) 147850 PID:c36a8f92 TID:c35dbd2a 0x834fc000: *CloseIFConfig(Handle 0x87600) 147852 PID:c36a8f92 TID:c35dbd2a 0x834fc000: +IPNotifyClientsIPEvent 147852 PID:c36a8f92 TID:c35dbd2a 0x834fc000: IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 446f0 147854 PID:c36a8f92 TID:c35dbd2a 0x834fc000: IPNotifyClientsIPEvent: PendingIrp 446f0 147855 PID:c36a8f92 TID:c35dbd2a 0x834fc000: IPNotifyClientsIPEvent: SetEvent 147857 PID:c36a8f92 TID:c35dbd2a 0x834fc000: IPNotifyClientsIPEvent: remove old 147858 PID:c36a8f92 TID:c35dbd2a Search Route #3: Route not found 147865 PID:c36a8f92 TID:434fcb3a 0x834aa800: +RDR:NetBIOSNotifyFunc: Lana 4, flags: 0x0 147867 PID:c36a8f92 TID:434fcb3a 0x834aa800: +RDR:NetDownIndication, lana: 4 147870 PID:c36a8f92 TID:4366fbba 0x83627218: +RDR:NetCleanupFunc: Lana:4 147871 PID:c36a8f92 TID:4366fbba 0x83627218: +RDR:UnbindFromNet, lana: 4 147873 PID:c36a8f92 TID:4366fbba 0x83627218: -RDR:StopBrowserOnNet: Browser not started on lana 4 147873 PID:c36a8f92 TID:4366fbba 0x83627218: -RDR:Stopped redir on lana 4 147875 PID:c36a8f92 TID:434fcb3a 0x834aa800: -RDR:NetBIOSNotifyFunc: Lana 4 147879 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: ************DHCP MEDIA STATUS************ 147880 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: SeqNo: 8 147881 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: MediaStatus: 11027 147882 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: Context: 65535 - 65535 147882 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: AdapterName: Hayes Compatible on COM1: 147884 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: Media Status is: IP_UNBIND_ADAPTER 147885 PID:c36a8f92 TID:a35e1fd2 0x835e1e28: IPDispatchDeviceControl returned Status 103 147886 PID:c36a8f92 TID:834fcdd2 0x833ef000: -RDR:RdrUIThread exiting 147890 PID:c36a8f92 TID:4366fbba 0x83627218: +RDR:UnbindFromNetbiosTransport 147891 PID:c36a8f92 TID:4366fbba 83627218: -RDR:UnbindFromNetbiosTransport 147892 PID:c36a8f92 TID:4366fbba 0x83627218: -RDR:UnbindFromNet 147892 PID:c36a8f92 TID:4366fbba 0x83627218: -RDR:NetCleanupFunc: Lana:4 148875 PID:c36a8f92 TID:4366fbba 0x83627218: IPRouteTimeout: setting fIPRouteOn to 0 148876 PID:c36a8f92 TID:4366fbba 0x83627218: *IPRouteTimeout: NOT restarting IPRouteTimeout 153869 PID:c36a8f92 TID:43430bda 0x83430800: ASYNCMAC: lineDrop result=6 153873 PID:c36a8f92 TID:235ccdba 0x835dfdd8: Mac:WaitCommEvent failed 87 153885 PID:c36a8f92 TID:34fcc42 0x833eb0a8: COM_Close: (1 handles) total RX 508, total TX 625, dropped (mdd, pdd) 0,0 153887 PID:c36a8f92 TID:34fcc42 0x833eb0a8: COM_Close: (0 handles) total RX 508, total TX 625, dropped (mdd, pdd) 0,0 153895 PID:c36a8f92 TID:23622c22 0x833ef000: AM: OID_TAPI_CLOSE_CALL: SetCommMask failed, error=6 153902 PID:c36a8f92 TID:435849fa 0x8343ed80: AM: TxThread exiting 153973 PID:c3486fd2 TID:c35dbd2a 0x834fc000: DESTROY 154057 PID:c36a8f92 TID:e35005a2 0x83458090: TAPI:TAPIlineGetMessage hLineApp now invalid 154158 PID:c3486fd2 TID:c35dbd2a 0x834fc000: Posting WM_NETCONNECT(FALSE) message, ErrorCode = 631(0x277) 154177 PID:c3486fd2 TID:c35dbd2a 0x834fc000: <<< Unloading module rnaapp at address 0x12010000-0x1201F000 //////////////////////////////////////////////////////////// Can someone give me an idea how to solve this problem? I would appreciate any help. Thanks in advance, -- Selin Metin selinm_AT_esit_._com_._tr Tag: SDK Question Tag: 67218
  - 6
    - Firing up the LCD Ver2 on the SMDK2410 using CE5 I'm using the SMDK2410x (Board version: 1.33) with the SMDK2410-LCD (version 2.0 LTS350Q1-PE2) I can build an image and successfully download it to the board and it will run, but the LCD doesn't do more than display a white bar at the side of a black screen. The image includes - s3c2410x_lcd.dll (the code for this hasn't been changed from the default) Display Support and all the other stuff that comes with using the Mobile Handheld design template. It doesn't include - A BSP_NODISPLAY environment variable Or any other error or warning referring to the display (that I can make out!) Anyone got any ideas on how to get this thing running? Is there anything I've stupidly forgotten to do? Tag: SDK Question Tag: 67214
  - 7
    - CS8900A product Ethernet in 5.0? Hi, In PB 5.0 the CS8900 product Ethernet driver seems to be missing. We need support for this. What's the best way to achieve this? Thanks, Jojje Tag: SDK Question Tag: 67213
  - 8
    - [Q]: Exception while streaming video This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C54686.364B6580 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Folks, -- WinCE 4.2 .net -- I have come across an exception while playing streaming video by = ceplayer.exe application, when the audio driver[audio.dll] is NOT loaded. [reasons for not loading may be due to absence of audio codec hardware = or likewise]. The exception is as follows: First-chance exception in DXMASF.DLL (0xc0000005: Access violation) in file : WINCEROOT\private\directx\wmt40\filters\nssplut.cpp Exception 002 Thread=3D87e79668 Proc=3D47db1e92 AKY=3D00000041 PC=3D01e12718 RA=3D01e12704 BVA=3D00000000 Process 'ceplayer.exe' This exception is observed when the = 'WinCEPB42-040331-2004Q1-MIPSII_FP.EXE' QFE packet is installed and the platform is 'rebuild all'. Prior to 2004Q1 QFE installation this exception is NOT observed. If I restore the old dxmasf.lib & dxmasf.pdb files in = WINCEROOT\PUBLIC\DIRECTX\OAK\LIB\MIPSII_FP and 'rebuild all' the platform, everything works fine again. Now, I would like to know, what is the difference between the updated = dxmasf.lib=20 compared to that of old one ? The document 'WinCE .NET 4.2_Update_Readme_2004Q1.htm' does not detail = the new expected behavior for the same. Can anyone get me the link where I can find technical information = [changed behavior of the binaries] for QFE update. regards Sajid ------=_NextPart_000_000D_01C54686.364B6580 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 6.00.2800.1498" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Hi Folks,</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>-- WinCE 4.2 .net --</FONT></DIV><FONT size=3D2> <DIV>I have come across an exception while playing streaming video by=20 ceplayer.exe application,<BR>when the audio driver[audio.dll] is NOT=20 loaded.<BR>[reasons for not loading may be due to absence of audio codec = hardware or likewise].</DIV> <DIV> </DIV> <DIV>The exception is as follows:</DIV> <DIV> </DIV> <DIV>First-chance exception in DXMASF.DLL<BR>(0xc0000005: Access=20 violation)</DIV> <DIV> </DIV> <DIV>in file : WINCEROOT\private\directx\wmt40\filters\nssplut.cpp</DIV> <DIV> </DIV> <DIV>Exception=20 002 Thread=3D87e79668 Proc=3D47db1e92<BR>AKY=3D00000041 PC= =3D01e12718 RA=3D01e12704 BVA=3D00000000<BR>Process=20 'ceplayer.exe'</DIV> <DIV> </DIV> <DIV>This exception is observed when the = 'WinCEPB42-040331-2004Q1-MIPSII_FP.EXE'=20 QFE packet<BR>is installed and the platform is 'rebuild all'.</DIV> <DIV> </DIV> <DIV>Prior to 2004Q1 QFE installation this exception is NOT = observed.</DIV> <DIV> </DIV> <DIV>If I restore the old dxmasf.lib & dxmasf.pdb files in=20 WINCEROOT\PUBLIC\DIRECTX\OAK\LIB\MIPSII_FP<BR>and 'rebuild all' the = platform,=20 everything works fine again.</DIV> <DIV> </DIV> <DIV>Now, I would like to know, what is the difference between the = updated=20 dxmasf.lib <BR>compared to that of old one ?</DIV> <DIV> </DIV> <DIV>The document 'WinCE .NET 4.2_Update_Readme_2004Q1.htm' does not = detail the=20 new expected behavior for the same.</DIV> <DIV> </DIV> <DIV>Can anyone get me the link where I can find technical information = [changed=20 behavior of the binaries] for QFE update.</DIV> <DIV> </DIV> <DIV>regards</DIV> <DIV>Sajid</FONT></DIV></BODY></HTML> ------=_NextPart_000_000D_01C54686.364B6580-- Tag: SDK Question Tag: 67209
  - 9
    - Dialog animation Hello, When I show a dialog on my CE device the showing process is animated. It starts with a rectangle in the middle of the screen and the rectangle is growing and moving to its final position and size for the dialog. The closing process is also animated. Does anyone know if there is a registry setting that can turn this animation effect off? Thanks / Lars Tag: SDK Question Tag: 67206
  - 10
    - FATFS don't handle error Hello, we have a problem with FAT filesystem. We use FAT on a strata flash with long file names.(WinCe4.2 SH4) That will work but sometimes FATFS reports BogusDirectory. (see below) The highlevel calls CreateFile WriteFile GetLast Error does not report it up to the caller thread. And so the overlayed data management will be confused. Also the thread that call ScanDisk on such a Volume hangs. So what went wrong on my system? What' to do to prevent such a error? Is such an error detectable? Thanks in advance. Johannes 4294927076 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +CreateFile:\FLASH2\000\Test.dat 4294927104 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 4294927105 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FAT_GetFileAttributesW(\000\Test.dat) returned 0xffffffff (13) 4294927106 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 4294927111 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 4294927125 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: -CreateFile: OK 4294927140 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +WriteFile:\FLASH2\000\Test.dat 4294927199 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 4294927250 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: WriteFile: ok 260 Bytes Written 663273 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +CreateFile:\FLASH2\000\Test.dat 663318 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 663319 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FAT_GetFileAttributesW(\000\Test.dat) returned 0xffffffff (13) 663320 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 663325 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 663369 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: -CreateFile: OK 663414 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +WriteFile:\FLASH2\000\Test.dat 663465 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 663515 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: WriteFile: ok 260 Bytes Written 669033 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +CreateFile:\FLASH2\000\Test123456789.dat 669078 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 669079 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FAT_GetFileAttributesW(\000\Test123456789.dat) returned 0xffffffff (13) 669080 PID:8dfe351a TID:ade7cc3e 0x8de7ca0c: FATFS!FindNext: bogus directory! 669085 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 669129 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: -CreateFile: OK 669173 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: +WriteFile:\FLASH2\000\Test123456789.dat 669225 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: 0=GetLastError() 669274 PID:ade7cc62 TID:ade7cc3e 0x8de7ca0c: WriteFile: ok 260 Bytes Written Tag: SDK Question Tag: 67204
  - 11
    - Driver for Capture Interface (camera) for PXA27x Hi, According to Intel's web site, the BSP for the PXA27x released with platform builder 5.0 should include driver for the quick capture interface. I could not find any driver or documentation for it, except for a header file with some definitions and prototypes. Is there any driver for the capture interface? Thanks, Lrz Tag: SDK Question Tag: 67203
  - 12
    - Ram size recognizing; Hi , I have a small problem in my image, Win Ce5.0: on board, Geode gx300, we installed a RAM of 128 Mbyte but system continuing to recognize only 64Mbyte. There is a mode to fix it . Thank you. Tiziano Fabbri Tag: SDK Question Tag: 67202
  - 13
    - booting from compact flash, x86_geode Hi Luca, Hi Jimbo thank you for yours replys. Today is an experiment's event: double language !! //**// I try to focalize about my boot from compact flash problem using BLDR, project "Loader" %WINCEROOT\public\common\oak\csp\x86\ biosloader\loader: I make modification regarding the definition READ_BUFFER_LENGTH_MAX in fat.h, and building the project by right cliccking on root name "Loader" and selecting menu's row "Build Current Project", all OK. Problem now is exchange new bldr in the floppy disk because in generally I use the utility named setupdisk.144 that, by intuition, looks like a compacted file that by Websetup utility it de-compacted in the floppy disk all necessary (inside there is a bldr version dated April 22th 2004) Over my intuition I did 2 test: starting from a floppy disk made by utility setupdisk.144, compile loader, one with the modification and one in the original format, and one after other one, these are copied to the floppy disk manually: 2 different time 2 different tests. Last operation is preparing the compact flash, that I do on my Geode board, and only at least I copy by hands 3 files, NK.bin, splash.bmx, boot.ini (I make a substitution of eboot.bix with nk.bin in the "BinFile" key in boot.ini), and launching mkdisk c: that prepare disk c:, CF, to boot by bldr. Now I answer at your question Luca, what I see by serial debug: nothing. Bldr continuing sending the comment of this elaborated instruction: {main.c} // Display loader startup banner. RTLMSG(TRUE, ("%s %s.%s (Built %s)\r\n", BLDR_SPLASH_MESSAGE, BLDR_VERSION_MAJOR, BLDR_VERSION_MINOR, __DATE__)); and after system reboot. This is a redundant effect: message and reboot. On video I can see only the ram test and after the reboot. Remember I repeated test one time with the original and one time with modified file but same method of compiling and copy to floppy disk. My conclusion is that although the modification I never tested it !!! One more specify: if I use a floppy disk made with setupdisk.144 in original format, so the contents has been created by utility less than I did any manual operations on it, starting and the debug messages keep sense (look my first newsgroup thread regarding this problem, I don't repeat thread message because I did a long test on 3 differents devices). Please let me know which operations I must to do to use new BLDR. Thank you very much, Tiziano Fabbri //**// Vedo di focalizzare il problema del boot da compact flash utilizzando BLDR, progetto Loader %WINCEROOT\public\common\oak\csp\x86\ biosloader\loader: ho fatto la modifica riguardo la definizione READ_BUFFER_LENGTH_MAX in fat.h, eseguo il building di progetto via tasto destro del mouse clicckando sulla radice loader e selezionando la voce di menu' Build Current Project, tutto ok. Il problema ora Ã¨ sostituire il nuovo bldr nel dischetto visto che generalmente io utilizzo l'utility setupdisk.144 la quale, vado a intuito, sembra essere un file compattato il quale per mezzo dell'utility Websetup si scompatta nel dischetto. Oltre all'intuito ho fatto 2 prove: parto da un dischetto preparato con setupdisk.144, compilo loader uno con la modifica e uno originale e prima uno poi l'altro li copio manualmente sul dischetto che utilizzerÃ². L'operazione finale della preparazione della compact flash, che io faccio a bordo della scheda Geode, e solo in ultimo copio 3 file manualmente per mezzo di card writer/reader: NK.bin, splash.bmx, boot.ini (faccio poi la sostituzione di eboot.bix con nk.bin nella chiave "BinFile" nel file boot.ini), Ã¨ di lanciare mkdisk c:, l'utility prepara c: al boot anche attraverso bldr. Vengo alla domanda che mi hai fatto Luca, cosa vedo via seriale: quasi niente. Bldr mi spedisce il commento elaborato da questa istruzione: {main.c} // Display loader startup banner. RTLMSG(TRUE, ("%s %s.%s (Built %s)\r\n", BLDR_SPLASH_MESSAGE, BLDR_VERSION_MAJOR, BLDR_VERSION_MINOR, __DATE__)); e poi il sistema fa il reboot. Questo effetto Ã¨ ridondante: scritta e reboot. A livello video si vede solo il test della ram e poi c'Ã¨ il reboot. Ricordate ho ripetuto la prova una volta con il bldr originale e l'altra con il progetto modificato, ma utilizzando la stessa tecnica di compilazione e copia manuale sul dischetto. La conclusione Ã¨ che nonostante la modifica ESSA io non l'ho mai testata. Altra precisazione: se utilizzo il dischetto setupdisk.144 in formato originale, il cui contenuto Ã¨ stato creato dall'utility senza che io abbia fatto interventi manuali sopra, l'avviamento e i messaggi in uscita hanno senso (vedi mio primo thread nel newsgroup a riguardo, non sto a ripetere perchÃ¨ avevo fatto un test molto lungo su tre tipi di dispositivi). per favore mi spiegate le operazioni che devo fare per utilizzare il nuovo BLDR. Grazie a tutti. Tiziano Fabbri Tag: SDK Question Tag: 67200
  - 14
    - smdk2410 registry key question? Hi, I am transferring my platform from x86 to smdk2410. If I flash my nk.bin to smdk2410 nand flash, which registry key architecture should I use? Hive ? or Implement the ReadRegistryFromOEM? Is it necessary use the MS Flash driver? Thanks. Tag: SDK Question Tag: 67198
  - 15
    - Run-Time Image for the Emulator tutorial doesn't work I'm trying to make the Win CE first tutorial work, but I can't in spite of the fact that I've followed all the instructions one by one. I tried to make it work yesterday and again today with a new project but I've obtained the same error message. Tutorial: Building a Run-Time Image for the Emulator - Step 1: Creating a Custom OS Design for the Emulator Done, everything OK. - Step 2: Building the Custom Run-Time Image for the Emulator Done, everything OK, 0 errors and 4 warnings (the tutorial says not to worry about the warnings) - Step 3: Setting Up a Connection to the Emulator and Downloading the Run-Time Image Doesn't work. I can read on the debugger: Failed to connect debug message service! Please check the transport settings. Transport service failed to connect Warning: One or more services failed to connect. Make sure that the service is properly configured. ***************************************** Since I'm trying to work with the Emulator there are no settings available on Target - Connectivity options - Transport. I would really appreciate if someone could help me. Yours Asier Tag: SDK Question Tag: 67197
  - 16
    - usb host isp1160 issue I use isp116x driver from Philips,and modified the mem address,interrupt,msc.. however,it can't works,when I plug in the usb device,it run to deviceattach:DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS and at WaitForSingleObject( m_hHubStatusChangeEvent, INFINITE ) waiting forever. Tag: SDK Question Tag: 67193
  - 17
    - UserKInfo array or API Hook question. Hi I am working with the CE API hook method and able to hook few coredll functions. I am using the API sets from the UserKInfo[KINX_APISETS] array. Some of the coredll functions are in SH_WIN32 API set. The API set for HT_SOCKET is empty (number of methods = 0). I am trying hook the following function AFDConnect in wsock.h(this header is in kernel code that come with platform builder) #define AFDConnect WINSOCK_CALL (DWORD, 4, \ (SOCKHAND Socket, \ LPSOCKADDR Address, \ DWORD AddressLength, \ CRITICAL_SECTION *pDllCS)) My guess is the HT_SOCKET API set in UserKInfo[] array probably gets filled after a SOCKET HANDLE is created thru AFDSocket() call. Since AFDSocket() is under API set SH_COMM and I am able to hook it. I tried to dump the UserKInfo[KINX_APISETS] inside the AFDSocket() hook after the call to original AFDSocket() has returned. Even then HT_SOCKET set in UserKInfo says the number of methods is 0 (Not filled yet). So I am unable to hook HT_SOCKET calls. Can some please let me know when this HT_SOCKET API set gets filled or is it possible to hook HT_SOCKET calls? Thanks very much for any help. Have a good day Ganesan Tag: SDK Question Tag: 67191
  - 18
    - Windows CE virtual Modem Driver - Not Dynamically being added to TAPI modem list. I have written a virtual modem driver for CE5.0. I register the device in the _Init function. I initially had a DeviceType of 1 for an external modem. I tried to change it to 7 for a dynamic modem. When I load it after a cold boot, the device is in the registry but doesn't show up on a modem list (ex when creating a new dial-up connection) until after a warm boot. It is as if TAPI locks out reenumeration of the modem list after a warm boot. Is there something I'm doing wrong? I have looked in the TSPI_lineOpen call in tspi.c and I think I'm doing the same thing. The only thing I may not be doing like TSPI_lineOpen is the use of he instance context blob (parameter 4 in RegisterDevice). I can't seem to find good documentation on this parameter. Thanks. Gene Chang Tag: SDK Question Tag: 67174
  - 19
    - USB Transport option in PB5 What exactly is the USB transport option in the PB kernel transport configuration dialog box? When selected, "(USBDevice)" is listed underneath the dropdown box. How is this different from SERIAL when using a USB serial function driver on the device side? Help doesn't provide much info at all - just states that when using USB-KITL as the transport - you can disable logging of all KITL packets via a "usbserkitl" key in the registry. What host side driver does PB use when configured for this USB transport? Thanks, -Chris Tag: SDK Question Tag: 67173
  - 20
    - CEPC BSP for P4 Does anyone know of a third party BSP for a motherbaord with a P4 processor. The CEPC x86 BSP shipped with PB 5.0 supports only P5,PII,PIII,Celeron,K6x and Athlon processors as per MSDN documentation. Tag: SDK Question Tag: 67171
  - 21
    - Bluetooth Manager - Scanning devices Hi! I'm facing a problem and I can't figure out what is causing it. To my image I've added bluetooth support (SYSGEN_BTH and SYSGEN_BTH_USB). When I launch the Bluetooth Manager and scan for devices I find other devices but not the profiles they support, i.e the devices only appear in the "UNTRUSTED" list with a '?' icon. This is when running CE 5.0. But when doing the exact same thing with 4.2 on the same platform it works, i.e. the different profiles are enumerated in the list. I'm starting to believe that I'm experiencing problems with the communication to the USB dongle because sometimes no devices are found and sometimes only a few (5.0), besides the fact that at no time have I found a profile using 5.0. Any suggestions? Sincerely, Nicklas Tag: SDK Question Tag: 67168
  - 22
    - Why the performance of media player in WinCE 4.2 is worse than that in PPC2003? Hi, In same H/W platform, I have PPC 2003 and WinCE 4.2 OS images. I use the same audio and display drivers to build the two OS images. I found using media player to play WMV is smooth in PPC, but it is bad in WinCE 4.2. Why ? How to improve the performance of media player in WinCE 4.2 ? Thanks. Yu. Tag: SDK Question Tag: 67161
  - 23
    - How to eliminate the "BUILD: [01:0000001496:INFO ]" In Windows CE 5.0, is there any setting whilc can filter the "BUILD: [01:0000001496:INFO ]" in build.log? Thanks Charles Wang Tag: SDK Question Tag: 67159
  - 24
    - Adding a new codec I've been looking into how to add a new codec to Windows CE, to support the decoding of an audio format. The obvious way to do this seems to be to add an ACM (Audio Compression Manager) driver dll. Is this the best way to do it or should I be considering any other options? I have been looking at the faad2 AAC decoder, with a view to establishing how much effort would be involved in porting this to CE 5. Thanks Matt Tag: SDK Question Tag: 67138
  - 25
    - Several Storage Manager profiles using one block driver Hello CE world. Is it possible to create several Storage Manager profiles using the same block driver? I would like to have several profiles (eg. one hidden with AutoPart, AutoMaunt and AutoFormat disabled and another one vsisible with AutoPart, AutoMaunt and AutoFormat enabled) using the same block driver. I tried the following settings in registry: HKEY_LOCAL_MACHINE\Drivers\Strorage\MyBlockDriver1 "Dll"="MyBlockDriver.dll" "Prefix"="DSK" "Profile"="MyProfile1" .... HKEY_LOCAL_MACHINE\Drivers\Strorage\MyBlockDriver2 "Dll"="MyBlockDriver.dll" "Prefix"="DSK" "Profile"="MyProfile2" .... [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MyProfile1] "Name"="Private Storage" "Folder"="Private Storage" .... [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\MyProfile2] "Name"="Public Storage" "Folder"="Public Storage" .... Everything seems to work as expected except one thing: after loading folder names are assigned as MyProfile1 -> Private Storage MyProfile2 -> Private Storage2 (instead of "Public Storage") Any ideas? Tag: SDK Question Tag: 67134

When I initially received CE 5.0 in Sept 2004, I created an SDK. Since
then, I have installed the QFE's for 2004
(WinCEPB50-041231-Product-Update-Rollup-X86.msi). Is it necessary to create
a new SDK because of changes made by the QFE's?

Top