Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Leaking D3DM Object: Vertex Buffer Hi there, i am currently working on porting my D3DM driver from Windows CE 5.0 to Windows CE 6.0. In the process, i have of course already added in necessary changes like kernel-to-user memory mapping for surfaces/buffers and changing of the shared memory resource pool allocation API's (as per the sample null driver). When running the MS Widows CE CETK tests for D3DM, the interface tests passed as expected, but in the verification tests, i found that the middleware seems to not destroy the 1 vertex buffer it creates for each test. in my driver, my contexts are not destroyed prematurely until the last surface gets destroyed, this is causing the contexts to leak as well. The tests start, run and finish, posting the results, but it destroys all surfaces except the vertex buffer it created and then invokes my driver to destroy the context. This is happenning when on CETK D3DM Verification tests (tests 200 and above). I find the d3dm middleware displaying the following debug message just before destroying the context: "Leaked D3DM Object: Vertext Buffer, [hex address of vtx buf]" anyone has any ideas why this is happenning? Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97518
  - 2
    - WinCE 5 - clone catalog item again - unable to do via PB ? Hello, it was enough said not to modify the code under PUBLIC tree. Even if some of us occasionally do, some day tried to clone just a subtree as an example of good doing (as opposed to worng doing, which is directly alter the needed source code under whatever tree it is). So the Help in PB 5 [ms-help://MS.WindowsCE.500/wceosdev5/html/wce50tskCloningCatalogItem.htm ] says that ...... Create or open a workspace containing an OS design you want to modify. In the Catalog, select the Catalog item you want to clone into your OS design and then, from the context menu, choose Add to OS Design. The item is added to your OS design as an user-specified Catalog item. 1.. In the Workspace window, on the OSDesignView tab, select the Catalog item you added and then perform one of the following: 2.. From the context menu, select Clone Catalog Item. 3.. From the Platform menu, select Clone Catalog Item. The Clone Libraries dialog box appears. Why is the menu item in both cases 2 and 3 is grayed out ? Yes, for some items in OSDesignView it is not grayed out, but for several ones - it is grayed. For example {Windows XP-like Sample Skin} or {Standard Shell}. Does it mean these items aren't supported to be cloned [via PB] ? Perhaps anyone have seen this before, right ? Thank you for your consideration Sergei R Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97514
  - 3
    - Bug in rtc.c in SMDK2440A BSP Hi all, I have just found a problem in rtc.c in SRC\ARM\SAMSUNG\S3C2440A\Rtc. All references of pRTCReg->BCDDATE and pRTCReg->BCDDAY are swapped: BCDDATE should be used to store the day (1-31). (pTime->wDay) BCDDAY should be used to store the weekday (1-7). (pTime->wDayOfWeek) However, in the original rtc.c file they are used the other way around. Hope this helps someone. BTW, in case there is an updated version of the SMDK2440A, where can I get it? Thanks, H Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97503
  - 4
    - Enabling DMA into SMSC LAN9118 driver rel.1.08 Hello, I've integrated rel.1.08 of the SMSC driver into a Windows CE 5.0 kernel for the PXA270. It works in PIO mode (slow!). After enabling RX and TX DMA, I am able to see all PIO packets on the network sniffer. The first TX packet using DMA is not transmitted by the LAN chip, although it seems to be transmitted ok by the driver functions. The next packet transmission fails due to a "TX FIFO full" condition (free space = 0 bytes). TX FIFO free space should be at least 4608(empty)-736(previous)=3872 bytes(free). So, are you using DMA with LAN9115/6/7/8? Is it required to add glue code for DMA, other than the one present into the driver itself? Peace & Happiness Panino Colsalame Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97489
  - 5
    - ActiveSync on COM4 !!! I have a GENE5312 from AAEON with WinCE 5.0 and 4 COM : COM1,COM2,COM3 and COM4. When I run Repllog, Repllog send caracters CLIENT on COM4 and I want to use COM1. Anybody knows which register or anything else to modify the serial line -- Thanks Damien Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97480
  - 6
    - Loading problem, WinCE 6.0 dm9000 Ndis driver Hi, Im trying to move our old DM9000 miniport ndis driver from our old WinCE 4.2 platform to WinCE 6.0. It all works well when running in debug mode but when I do a release build the dm9000.dll won't load. I have verified that the dm9000.dll resides in the image and that ndis is running. I have also built a release image with kitl support and added some RETAILMSG to the DriverEntry function, but it does not output anything. This is the registry entries: [HKEY_LOCAL_MACHINE\Comm\DM9CE] "DisplayName"="DM9000 Fast Ethernet Adapter" "Group"="NDIS" "ImagePath"="dm9000.dll" [HKEY_LOCAL_MACHINE\Comm\DM9CE\Linkage] "Route"=multi_sz:"DM9CE1" [HKEY_LOCAL_MACHINE\Comm\DM9CE1] "DisplayName"="DM9000 Fast Ethernet Adapter" "Group"="NDIS" "ImagePath"="dm9000.dll" [HKEY_LOCAL_MACHINE\Comm\DM9CE1\Parms] "BusNumber"=dword:0 "BusType"=dword:1 "SysIntr"=dword:1F "XmitBuffer"=dword:64 "RecvBuffer"=dword:20 [HKEY_LOCAL_MACHINE\Comm\DM9CE1\Parms\TcpIp] "DefaultGateway"="" "UseZeroBroadcast"=dword:0 "IpAddress"="192.168.1.1" "Subnetmask"="255.255.255.0" "DNS"="" "WINS"="" "EnableDHCP"=dword:0 [HKEY_LOCAL_MACHINE\Comm\Tcpip\Linkage] "Bind"="DM9CE1" Anyone have any suggestions why this is happening? Why does it work in debug mode and not in release mode? Thanks in advance! Best regards, Bjorn Hall Beijer Electronics Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97478
  - 7
    - CE4.2 InternetReadFile oddities + PPP debug. I have been experiencing very strange behavior in the wininet InternetReadFile API. I am using InternetReadFile to download a 1Mb file via FTP (Passive). The server side is IIS's FTP server. The environment is quite involved and by no means orthodox. I am testing on a custom Windows CE 4.2 platform (handheld device). The handheld is using the Microsoft Bluetooth Stack with a customized stream driver that can multiplex several virtual serial devices over the wireless bluetooth connection (SPP) to a 'black box' which finally demuxes to physical RS232 ports. I am testing with a DUN RAS connection via a GPRS modem (Siemens MC35 terminal) physically plugged into that 'black box'. InternetReadFile() is called in a worker thread to manage the timeouts as per KB176420/KB224318 (fixed 60 min timeouts?!) I have tried pulling 512 and 2048 chunks on each successive call. The actual InternetReadFile() quirks are listed below, I am only able to reproduce these quirks with a GPRS/CDMA wireless modem (~1.5KiB/s throughput). Obviously there are wireless network and mux/demux (bluetooth) latency and delays. High speed direct serial (PC to PC) connections are fine. I suspect latency, is a big player. Quirk 1. InternetReadFile() is blocking indefinitely on 9 out 10 file transfer sessions, usually at similar points (often at ~90%). I have visibility of ppp stack's polled reads through debugging traces of COM_Read's in the mux driver. I can see that 2k chunks of data are still being polled, though sometimes not. So there can be activity under the hood while it is blocking. Quirk 2. Occasionally, InternetReadFile() returns with success and zero bytes (EOF) even though it has only transferred part of the file. This just shouldn't happen. Quirk 3. Rarely, InternetReadFile() will return with 12031 (connection reset). What is most interesting is that if I don't call InternetReadFile() in a worker thread it tends to work fine. Also, the PPP connection is still alive and well after the FTP transfer fails. I am also pretty confident the mux/demux driver and hardware are working correctly. I'm sure you can appreciate how difficult this is to debug. Compounding this is that the original engineer has left the project, I am merely mopping up. :( My questions: - 1. Has anyone seen these problems with InternetReadFile() before? 2. Are there any metrics/statistics that I can check in the TCP/IP or PPP stack to ensure there are no framing errors or bad packets? 3. Can I get access to the wininet source to work out what is going on? 4. Is it possible to get detailed logs from the PPP stack under Windows CE? I don't easily have access to the platform build (managed by another division of my employer). Thanks in advance. :) David. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97477
  - 8
    - Usage of SetSystemPowerState Hi All, I have been working on an MFC application which will be deployed on a Samsung SMDK2410 board. I need to turn off the system (or put it in suspended state) on a button click. The code that I have used to turn off the power is as follows: void CMyAppDlg::OnButtonClick() { SetSystemPowerState(NULL,POWER_STATE_SUSPEND,0); } I am currently testing this on the PB emulator and following are the issues I am facing: 1. As soon as I click the button, the system is going into suspend mode but after a few seconds it resumes operation(without any mouse click or keyboard hit from my side). A call to GetSystemPowerState( ) returned POWER_STATE_ON as the current state. What am I supposed to do if I need to keep the system in the suspended state till a mouse click happens or the touch screen is touched? 2. The PB documentation mentioned about registering power events in a POWER_BROADCAST structure. Do I need to do this before calling SetSystemPowerState? Thanks in advance Treadstone Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97475
  - 9
    - Is zero-length USB packet supported in Windows CE 5.0 ? We are developing a USB Device Driver in Windows CE 5.0. We are using the BSP for Intel PXA27X ARM Processor. Our USB device has 1 Bulk-In endpoint, 1 Bulk-Out endpoint and 1 Interrupt-In endpoint. For the Bulk-Out transfers, we will send out a zero-length packet for data transfer of multiple of 64 bytes. However from the CATC USB anaylzer, we don't see the zero-length packet being transmitted out by the USB Bus. Since the device did not receive the zero-length packet, the device could not determine the end of transfer and would always appear to "hang" whenever a multiple of 64 bytes of data is sent. We tested the same driver in Windows CE 4.2 and we don't have such problem. Thank you. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97471
  - 10
    - Is it a celog bug to get the dwCodeBase? I wrote an application and change the default base address (using /base option) to 0x20000. To my understanding, if the process is loaded to address 0x1c000000, the execute code will begin from 0x1c020000. However, in the my celog, the dwCodeBase field of the structure CEL_EXTRA_PROCESS_INFO still returns 0x10000. Is it a bug of celog? If not, is there any way that I can get the correct value? Platform: Windows Mobile 5.0 for Pocket PC + XScale target + visual studio 2005 Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97468
  - 11
    - Flash File system FMD Erase Block HI I am using PXA270 and Mainstone ii BSP with wince 5.0. For Flash file system i am using the driver provided by win ce i.e fmd.cpp . i am using intel strata paired flash of 128Mb (with 64MB each). Using shawdowing whole windows directory is mapped to flash. But it is calling FMD Erase block some times with lot of inconsistency. but data in the flash remains unaffected. I suspect that bcoz of this operation our application is crashed after 2 hrs or some times even 20 minutes. could any one pls help on this issue?? thanks in advance Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97466
  - 12
    - USB is not recognized+wince Hi, I am working in Wince for s3c2440 target board. I want to download my Nk.nb0 thro' USB from Eboot. I added USB client driver for USB support in Bootcode for downloading my Nk.nb0. Any thing i have to do in Host side(PC) for recognizing my USB device. It always shows my USB is not recognized.... How i have to configure so that i can proceed downloading. Thanks Kirthika Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97465
  - 13
    - CE6 CEPC debug NICs Why does CE6 have worse CEPC NIC support than CE5? CE5 doesn't support many CEPC target NICs but at least I found one 100BT NIC, Netgear FA311, that it does support. CE6 will download to a target that has this but then the target hangs when it jumps into the image. The exact same hardware works fine in CE5. When the fast NIC is replaced by a clunky old 10BT (Kingston) CE6 works OK but communicates many times slower than CE5 on this same NIC. Why are we going backwards? Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97459
  - 14
    - WinCE 6.0 / PB6 very slow builds? Has anyone noticed very slow builds, using PB6? I've been using PB4.20, then PB6beta without any problems with the build times. My platform was built within a few minutes, with a CPU usage around 70%, while the disk was working loudly. With PB6 (RTM + VS2005 SP1) the builds takes 10-20 minutes, CPU usage 100%, but almost no disk activity at all ?!? The CPU is hogged so hard that the computer can hardly be used for anything else during the build... :-( Similar problems seems to appear when I Attach to my device (and starts debugging) - the machine gets very slow... Are there any solutions or suggestions out there? Thanks in advance -- Johan Ekstrom Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97447
  - 15
    - Need Help to set breakpoint to debug the code Hi All, I have problem in bringing up the kernel, I have enabled KITL and I do get the debug messages on platform builder as kernel debugger connected and some debug message. But if I set a breakpoint the colour changes but the code doesn't stop there. I tried adding debugbreak() function in oal layer it works but how do I set breakpoint in kernel code using debugbreak() function. Please reply. Thanks & Regards, Chitra Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97444
  - 16
    - Ohci2 suspend/resume memory leak Hi, Some months ago I struggled with a memory leak I had in my image when doing suspend/resume. After a break, now I started debugging this again. My system is a Samsung S3C2410 with CE 5.0. First, when not having usb host controller in the image, there is no leak. Now, I think I might be on to something about the leak related to when ohci2 unloads/loads the usb client drivers after resume. It seems ohci2 can't close some of the pipes, and free related memory (see >>>>>>> in the debug output below). The platform have a USB hub (tusb2046b). When resuming I get the following debug output related to the usb unload/load (I have a USB mouse connected): 1895168 PID:5fa369a TID:e5df876a 0x85deb400: +CHub(Root tier 0)::HandleDetach 1895170 PID:5fa369a TID:e5df876a 0x85deb400: CHub(Root tier 0)::HandleDetach - status change thread closed in 2 ms 1895170 PID:5fa369a TID:e5df876a 0x85deb400: +CHub(External tier 1)::HandleDetach 1895174 PID:5fa369a TID:85e09666 0x85d9b690: ndisMResetCompleteStage2: Internal reset 1895177 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDMemory: +SlotEventCallBack - 1 1895177 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDMemory: - SlotEventCallBack 1895180 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDMemory: +SMC_Deinit 1895183 PID:5fa369a TID:e5df876a 0x85deb400: CHub(External tier 1)::HandleDetach - status change thread closed in 12 ms 1895183 PID:5fa369a TID:e5df876a 0x85deb400: +CQueuedPipe(Control)::ClosePipe >>>>>>> 1895198 PID:5fa369a TID:e5df876a 0x85deb400: !CQueuedPipe(Control)::ClosePipe 00289e20 doesn't exist! 1895198 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 83488 bytes; TotalSize = 94208 bytes 1895199 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE6C20, VA = 0x00289C20, Size = 512, Desc = IssueTransfer TDs 1895199 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 84000 bytes; TotalSize = 94208 bytes 1895199 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 84000 bytes; TotalSize = 94208 bytes 1895200 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE6420, VA = 0x00289420, Size = 2048, Desc = IssueTransfer TDs 1895200 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86048 bytes; TotalSize = 94208 bytes 1895201 PID:5fa369a TID:e5df876a 0x85deb400: - CQueuedPipe(Control)::ClosePipe 1895201 PID:5fa369a TID:e5df876a 0x85deb400: +CQueuedPipe(Interrupt)::ClosePipe 1895205 PID:5fa369a TID:c5b3dc56 0x85b11c60: +IPNotifyClientsIPEvent 1895206 PID:5fa369a TID:c5b3dc56 0x85b11c60: IPNotifyClientsIPEvent: replumb stack 1895211 PID:5fa369a TID:e5e99bb6 0x85e68aac: +OpenIFConfig(Comm \VMINI1\Parms\TCPIP Handle 0x621FD90) 1895213 PID:5fa369a TID:e5e99bb6 0x85e68aac: Opened registry info for Comm\VMINI1\Parms\TCPIP 1895213 PID:5fa369a TID:e5e99bb6 0x85e68aac: -OpenIFConfig(Comm \VMINI1\Parms\TCPIP *Handle 0x621FD90, BOOL Ret: 1) 1895214 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86048 bytes; TotalSize = 94208 bytes 1895215 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE7680, VA = 0x0028A680, Size = 32, Desc = OpenPipe ED 1895215 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86080 bytes; TotalSize = 94208 bytes 1895215 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86080 bytes; TotalSize = 94208 bytes 1895216 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE7640, VA = 0x0028A640, Size = 64, Desc = IssueTransfer TDs 1895216 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86144 bytes; TotalSize = 94208 bytes 1895217 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 86144 bytes; TotalSize = 94208 bytes 1895217 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE6E40, VA = 0x00289E40, Size = 2048, Desc = IssueTransfer TDs 1895217 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 88192 bytes; TotalSize = 94208 bytes 1895218 PID:5fa369a TID:e5df876a 0x85deb400: - CQueuedPipe(Interrupt)::ClosePipe 1895218 PID:5fa369a TID:e5df876a 0x85deb400: +CFunction(tier 2)::HandleDetach 1895218 PID:5fa369a TID:e5df876a 0x85deb400: +CQueuedPipe(Control)::ClosePipe 1895223 PID:5fa369a TID:e5e99bb6 0x85e68aac: +GetGeneralIFConfig(ConfigInfo 0x621FD24 Handle 0xC92A0) 1895225 PID:5fa369a TID:e5e99bb6 0x85e68aac: GetGeneralIFConfig:Unable to read DefaultGateway value! 1895226 PID:5fa369a TID:e5e99bb6 0x85e68aac: GetGeneralIFConfig:Unable to read DNS value! 1895227 PID:5fa369a TID:e5e99bb6 0x85e68aac: GetGeneralIFConfig:Unable to read WINS value! 1895228 PID:5fa369a TID:e5e99bb6 0x85e68aac: GetGeneralIFConfig:Unable to read UseZeroBroadcast value! All-nets broadcasts will be addressed to 255.255.255.255 1895230 PID:5fa369a TID:e5e99bb6 0x85e68aac: - GetGeneralIFConfig(ConfigInfo 0x621FD24 Handle 0xC92A0 Ret: TRUE) 1895230 PID:5fa369a TID:e5e99bb6 0x85e68aac: +GetIFAddrList(NumAddr* 0x621FD98 Handle 0xC92A0) 1895231 PID:5fa369a TID:e5e99bb6 0x85e68aac: *CloseIFConfig(Handle 0xC92A0) >>>>>>> 1895232 PID:5fa369a TID:e5df876a 0x85deb400: !CQueuedPipe(Control)::ClosePipe 0028b0a0 doesn't exist! 1895233 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 88192 bytes; TotalSize = 94208 bytes 1895233 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE7EA0, VA = 0x0028AEA0, Size = 512, Desc = IssueTransfer TDs 1895233 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 88704 bytes; TotalSize = 94208 bytes 1895234 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 88704 bytes; TotalSize = 94208 bytes 1895234 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE76A0, VA = 0x0028A6A0, Size = 2048, Desc = IssueTransfer TDs 1895234 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 90752 bytes; TotalSize = 94208 bytes 1895235 PID:5fa369a TID:e5df876a 0x85deb400: - CQueuedPipe(Control)::ClosePipe 1895235 PID:5fa369a TID:e5df876a 0x85deb400: +CQueuedPipe(Interrupt)::ClosePipe 1895238 PID:5fa369a TID:c5b3dc56 0x85b11c60: IPNotifyClientsIPEvent: PendingIPGetIPEventRequest 2caae0 1895238 PID:5fa369a TID:c5b3dc56 0x85b11c60: IPNotifyClientsIPEvent: SetEvent 1895238 PID:5fa369a TID:c5b3dc56 0x85b11c60: IPNotifyClientsIPEvent: remove old 1895240 PID:5fa369a TID:c5b3dc56 0x85b11c60: IPNotifyClientsIPEvent: remove old 1895245 PID:5fa369a TID:c5b3dc56 0x85b11c60: +OpenIFConfig(Comm \VMINI1\Parms\TCPIP Handle 0xC0FDEF0) 1895247 PID:5fa369a TID:c5b3dc56 0x85b11c60: Opened registry info for Comm\VMINI1\Parms\TCPIP 1895247 PID:5fa369a TID:c5b3dc56 0x85b11c60: -OpenIFConfig(Comm \VMINI1\Parms\TCPIP *Handle 0xC0FDEF0, BOOL Ret: 1) 1895249 PID:5fa369a TID:c5b3dc56 0x85b11c60: *CloseIFConfig(Handle 0xC92A0) 1895259 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 90752 bytes; TotalSize = 94208 bytes 1895259 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE89C0, VA = 0x0028B9C0, Size = 32, Desc = OpenPipe ED 1895260 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 90784 bytes; TotalSize = 94208 bytes 1895260 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 90784 bytes; TotalSize = 94208 bytes 1895261 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE88C0, VA = 0x0028B8C0, Size = 256, Desc = IssueTransfer TDs 1895261 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 91040 bytes; TotalSize = 94208 bytes 1895261 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 91040 bytes; TotalSize = 94208 bytes 1895262 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem FreeMemory : PA = 0x31CE80C0, VA = 0x0028B0C0, Size = 2048, Desc = IssueTransfer TDs 1895262 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 93088 bytes; TotalSize = 94208 bytes 1895262 PID:5fa369a TID:e5df876a 0x85deb400: - CQueuedPipe(Interrupt)::ClosePipe 1895263 PID:5fa369a TID:e5df876a 0x85deb400: +USBD:ClosePipe, hPipe: 0x2BB840 1895263 PID:5fa369a TID:e5df876a 0x85deb400: -USBD:ClosePipe 1895263 PID:5fa369a TID:e5df876a 0x85deb400: +USBD:ClosePipe, hPipe: 0x2B82B0 1895264 PID:5fa369a TID:e5df876a 0x85deb400: -USBD:ClosePipe 1895284 PID:5fa369a TID:e5df876a 0x85deb400: <<< Unloading module mouhid.dll at address 0x033F0000-0x033F7000 (RW data at 0x01F5A000-0x01F5A4A8) Unloaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\MOUHID.DLL' 1895311 PID:5fa369a TID:45eed6aa 0x85e00af0: StartInterruptTransfer: IssueInterruptTransfer failed 1895318 PID:5fa369a TID:e5df876a 0x85deb400: <<< Unloading module usbhid.dll at address 0x034D0000-0x034E6000 (RW data at 0x01F6E000-0x01F6E540) Unloaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\USBHID.DLL' 1895319 PID:5fa369a TID:e5df876a 0x85deb400: <<< Unloading module hidparse.dll at address 0x03420000-0x03435000 (RW data at 0x01F60000-0x01F60474) Unloaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\HIDPARSE.DLL' 1895322 PID:5fa369a TID:e5df876a 0x85deb400: -CFunction(tier 2)::HandleDetach 1895323 PID:5fa369a TID:e5df876a 0x85deb400: -CHub(External tier 1)::HandleDetach 1895323 PID:5fa369a TID:e5df876a 0x85deb400: -CHub(Root tier 0)::HandleDetach 1895324 PID:5fa369a TID:e5df876a 0x85deb400: +CDevice::DeInitialize 1895325 PID:5fa369a TID:e5df876a 0x85deb400: <<< Unloading module usbd.dll at address 0x034F0000-0x03501000 (RW data at 0x01F70000-0x01F705D0) Unloaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\USBD.DLL' 1895327 PID:5fa369a TID:e5df876a 0x85deb400: -CDevice::DeInitialize 1895329 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 94208 bytes; TotalSize = 94208 bytes 1895329 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 32768 bytes; TotalSize = 32768 bytes 1895330 PID:5fa369a TID:e5df876a 0x85deb400: +COhcd::Initialize. Entry 1895330 PID:5fa369a TID:e5df876a 0x85deb400: +CDeviceGlobal::Initialize 1895348 PID:5fa369a TID:e5df876a 0x85deb400: >>> Loading module usbd.dll at address 0x034F0000-0x03501000 (RW data at 0x01F70000-0x01F705D0) Loaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\USBD.DLL' 1895414 PID:5fa369a TID:e5df876a 0x85deb400: USBD: DLL attach 1895415 PID:5fa369a TID:e5df876a 0x85deb400: +USBD:HcdAttach, hcd: 0x5DC80 1895415 PID:5fa369a TID:e5df876a 0x85deb400: -CDevice::Initialize, success! 1895415 PID:5fa369a TID:e5df876a 0x85deb400: +CHW::Initialize base=0x270000, intr=0x11 1895416 PID:5fa369a TID:e5df876a 0x85deb400: -CHW::Initialize, success! 1895416 PID:5fa369a TID:e5df876a 0x85deb400: +CPipe::Initialize 1895417 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 94208 bytes; TotalSize = 94208 bytes 1895417 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem AllocateMemory : PA = 0x31CE6000, VA = 0x00289000, Size = 1056, Desc = Permanent EDs 1895417 PID:5fa369a TID:e5df876a 0x85deb400: CPhysMem ValidateHeaps : FreeSize = 93152 bytes; TotalSize = 94208 bytes 1895419 PID:5fa369a TID:e5df876a 0x85deb400: -CPipe::Initialize. Success! 1895420 PID:5fa369a TID:e5df876a 0x85deb400: +CHW::EnterOperationalState 1895420 PID:5fa369a TID:e5df876a 0x85deb400: - CHW::EnterOperationalState 1895420 PID:5fa369a TID:e5df876a 0x85deb400: -COhcd::Initialize. Success!! 1895444 PID:25d4c06e TID:c5b3dc56 0x85b11c60: Back from PowerOffSystem. 1895479 PID:e5c10402 TID:e5d9355e 0x85dadd30: [NOTIFY] HandleSystemEvent 9 none 1895484 PID:e5c10402 TID:25f94db6 0x85f94570: [NOTIFY] HandleSystemEvent 7 /REMOVE DSK2: 1895488 PID:e5c10402 TID:25f94db6 0x85f94570: [NOTIFY] HandleSystemEvent 7 /REMOVE HID1: 1895500 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDMemory: -SMC_Deinit 1895501 PID:5fa369a TID:a5d9bf5e 0x85d68940: <<< Unloading module sdmemory.dll at address 0x03510000-0x03524000 (RW data at 0x01F72000-0x01F72594) Unloaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\SDMEMORY.DLL' 1895505 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDGetClientFunctions: +Init 1895505 PID:5fa369a TID:a5d9bf5e 0x85d68940: SDGetClientFunctions: - Init 1895508 PID:5fa369a TID:a5dabfae 0x85da8000: ************DHCP MEDIA STATUS************ 1895508 PID:5fa369a TID:a5dabfae 0x85da8000: SeqNo: 3 1895508 PID:5fa369a TID:a5dabfae 0x85da8000: MediaStatus: 11024 1895509 PID:5fa369a TID:a5dabfae 0x85da8000: Context: 2 - 3 1895509 PID:5fa369a TID:a5dabfae 0x85da8000: AdapterName: VMINI1 1895510 PID:5fa369a TID:a5dabfae 0x85da8000: Media Status is: IP_MEDIA_CONNECT 1895514 PID:5fa369a TID:a5dabfae 0x85da8000: IPDispatchDeviceControl returned Status 103 1895524 PID:e5c10402 TID:45befde2 0x85befba0: [NOTIFY] HandleSystemEvent 11 none 1895530 PID:5fa369a TID:e5e99bb6 0x85e68aac: VMini:: Detected DHCP [REQUEST] 1895531 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0101 1895537 PID:5fa369a TID:e5e99bb6 0x85e68aac: SetDhcpConfig: set IPAddr 280D15AC 1895542 PID:5fa369a TID:e5e99bb6 0x85e68aac: SetDhcpConfig: set LeaseObtained 1bd179c 5256d000 1895545 PID:5fa369a TID:e5e99bb6 0x85e68aac: SetDhcpConfig: T1 34bc0 T2 5c490 Lease 69780 1895550 PID:5fa369a TID:e5e99bb6 0x85e68aac: DHCP:EventMediaConnect: Successful renewal 1895632 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::HubStatusChangeThread - device attached on port 1 1895632 PID:5fa369a TID:45e37242 0x85ac26e8: +CHub(Root tier 0)::AttachDevice - port = 1, fIsLowSpeed = 0 1895632 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0 1895633 PID:5fa369a TID:45e37242 0x85ac26e8: +CControlPipe::OpenPipe 1895633 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 93152 bytes; TotalSize = 94208 bytes 1895634 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE6420, VA = 0x00289420, Size = 2048, Desc = IssueTransfer TDs 1895634 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 91104 bytes; TotalSize = 94208 bytes 1895635 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 91104 bytes; TotalSize = 94208 bytes 1895635 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE6C20, VA = 0x00289C20, Size = 512, Desc = IssueTransfer TDs 1895635 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 90592 bytes; TotalSize = 94208 bytes 1895636 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 90592 bytes; TotalSize = 94208 bytes 1895636 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE6E20, VA = 0x00289E20, Size = 32, Desc = OpenPipe ED 1895637 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 90560 bytes; TotalSize = 94208 bytes 1895637 PID:5fa369a TID:45e37242 0x85ac26e8: -CControlPipe::OpenPipe 1895637 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0 1895638 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0 1895705 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 0 1895707 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0 1895709 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0 1895720 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures = 0 1895722 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0 1895724 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0 1895725 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures = 0 1895727 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0 1895729 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0 1895730 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - Select Configuration 0 on DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE step 1895730 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0 1895732 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_HUB_DESCRIPTOR, failures = 0 1895734 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_CREATE_NEW_HUB, failures = 0 1895735 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY, failures = 0 1895735 PID:5fa369a TID:45e37242 0x85ac26e8: CHub(Root tier 0)::AttachDevice - status = DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures = 0 1895736 PID:5fa369a TID:45e37242 0x85ac26e8: +CInterruptPipe::OpenPipe 1895736 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 90560 bytes; TotalSize = 94208 bytes 1895737 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE6E40, VA = 0x00289E40, Size = 2048, Desc = IssueTransfer TDs 1895737 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 88512 bytes; TotalSize = 94208 bytes 1895737 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 88512 bytes; TotalSize = 94208 bytes 1895738 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE7640, VA = 0x0028A640, Size = 64, Desc = IssueTransfer TDs 1895738 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 88448 bytes; TotalSize = 94208 bytes 1895739 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 88448 bytes; TotalSize = 94208 bytes 1895739 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem AllocateMemory : PA = 0x31CE7680, VA = 0x0028A680, Size = 32, Desc = OpenPipe ED 1895740 PID:5fa369a TID:45e37242 0x85ac26e8: CPhysMem ValidateHeaps : FreeSize = 88416 bytes; TotalSize = 94208 bytes 1895740 PID:5fa369a TID:45e37242 0x85ac26e8: CInterruptPipe::OpenPipe - setting the poll interval to 32 ms instead of 255 ms 1895740 PID:5fa369a TID:45e37242 0x85ac26e8: - CInterruptPipe::OpenPipe, returning HCD_REQUEST_STATUS 0 1895741 PID:5fa369a TID:45e37242 0x85ac26e8: -CHub(Root tier 0)::AttachDevice - port = 1, fIsLowSpeed = 0, address = 1 1895745 PID:5fa369a TID:25df8fa2 0x85df8b8c: CExternalHub::SetOrClearFeature - port = 1, set/clear = 0x3, feature = 0x16, FAILED 1895748 PID:5fa369a TID:25df8fa2 0x85df8b8c: CExternalHub::SetOrClearFeature - port = 2, set/clear = 0x3, feature = 0x16, FAILED 1895751 PID:5fa369a TID:25df8fa2 0x85df8b8c: CExternalHub::SetOrClearFeature - port = 3, set/clear = 0x3, feature = 0x16, FAILED 1895754 PID:5fa369a TID:25df8fa2 0x85df8b8c: CExternalHub::SetOrClearFeature - port = 4, set/clear = 0x3, feature = 0x16, FAILED 1895960 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0301 1896062 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - device attached on port 1 1896062 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CHub(External tier 1)::AttachDevice - port = 1, fIsLowSpeed = 1 1896062 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0 1896063 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CControlPipe::OpenPipe 1896063 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 88416 bytes; TotalSize = 94208 bytes 1896064 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE76A0, VA = 0x0028A6A0, Size = 2048, Desc = IssueTransfer TDs 1896064 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 1896065 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 1896065 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE7EA0, VA = 0x0028AEA0, Size = 512, Desc = IssueTransfer TDs 1896065 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85856 bytes; TotalSize = 94208 bytes 1896066 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85856 bytes; TotalSize = 94208 bytes 1896066 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE80A0, VA = 0x0028B0A0, Size = 32, Desc = OpenPipe ED 1896067 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85824 bytes; TotalSize = 94208 bytes 1896067 PID:5fa369a TID:25df8fa2 0x85df8b8c: -CControlPipe::OpenPipe 1896067 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_USING_ADDRESS0, failures = 0 1896068 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_RESET_AND_ENABLE_PORT, failures = 0 1896139 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR_TEST, failures = 0 1896141 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_SET_ADDRESS, failures = 0 1896143 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_LEAVE_ADDRESS0, failures = 0 1896154 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_DEVICE_DESCRIPTOR, failures = 0 1896156 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_DEVICE_DESCRIPTOR, failures = 0 1896158 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SETUP_CONFIGURATION_DESCRIPTOR_ARRAY, failures = 0 1896158 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_INITIAL_CONFIG_DESCRIPTOR, failures = 0 1896161 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_GET_CONFIG_DESCRIPTOR, failures = 0 1896164 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE, failures = 0 1896164 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - Select Configuration 0 on DEVICE_CONFIG_STATUS_DETERMINE_CONFIG_TO_CHOOSE step 1896165 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SCHEDULING_SET_CONFIG, failures = 0 1896167 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_CREATE_NEW_FUNCTION, failures = 0 1896167 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_INSERT_NEW_DEVICE_INTO_UPSTREAM_HUB_PORT_ARRAY, failures = 0 1896168 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_SIGNAL_NEW_DEVICE_ENTER_OPERATIONAL_STATE, failures = 0 1896236 PID:5fa369a TID:25df8fa2 0x85df8b8c: >>> Loading module hidparse.dll at address 0x03420000-0x03435000 (RW data at 0x01F60000-0x01F60474) Loaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\HIDPARSE.DLL' 1896237 PID:5fa369a TID:25df8fa2 0x85df8b8c: >>> Loading module usbhid.dll at address 0x034D0000-0x034E6000 (RW data at 0x01F6E000-0x01F6E540) Loaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\USBHID.DLL' 1896423 PID:5fa369a TID:25df8fa2 0x85df8b8c: DEVICE! RegReadActivationValues RegQueryValueEx(Drivers\USB\ClientDrivers\Hid \Instance\Prefix) returned 2 1896424 PID:5fa369a TID:25df8fa2 0x85df8b8c: DEVICE! RegReadActivationValues RegQueryValueEx(Drivers\USB\ClientDrivers\Hid \Instance\BusPrefix) returned 2 1896428 PID:5fa369a TID:25df8fa2 0x85df8b8c: DEVICE! RegReadActivationValues RegQueryValueEx(Drivers\USB\ClientDrivers\Hid \Hid_Class\BusPrefix) returned 2 1896439 PID:5fa369a TID:25df8fa2 0x85df8b8c: +USBD:OpenPipe, EP: 0x81, MaxPkt: 4, Type: Interrupt 1896440 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CInterruptPipe::OpenPipe 1896440 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85824 bytes; TotalSize = 94208 bytes 1896440 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE80C0, VA = 0x0028B0C0, Size = 2048, Desc = IssueTransfer TDs 1896441 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83776 bytes; TotalSize = 94208 bytes 1896441 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83776 bytes; TotalSize = 94208 bytes 1896442 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE88C0, VA = 0x0028B8C0, Size = 256, Desc = IssueTransfer TDs 1896442 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 1896443 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 1896443 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE89C0, VA = 0x0028B9C0, Size = 32, Desc = OpenPipe ED 1896443 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83488 bytes; TotalSize = 94208 bytes 1896445 PID:5fa369a TID:25df8fa2 0x85df8b8c: CInterruptPipe::OpenPipe - setting the poll interval to 8 ms instead of 10 ms 1896445 PID:5fa369a TID:25df8fa2 0x85df8b8c: - CInterruptPipe::OpenPipe, returning HCD_REQUEST_STATUS 0 1896445 PID:5fa369a TID:25df8fa2 0x85df8b8c: -USBD:OpenPipe success, hPipe = 2BB4A0 1896453 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Preparing to Allocate memory 1896454 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Top Level Collection 1 found 1896455 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Enter Link Collection 1896455 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Exit Link Collection 1896456 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Collection 1 exit 1896457 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Starting Parsing Pass 1896457 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Parse Collection 1 1896458 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Main Offset:8 1896458 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Main Offset:b 1896459 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'Main Offset: 10 1896460 PID:5fa369a TID:25df8fa2 0x85df8b8c: HidParse: 'X Parse Collection 1 1896479 PID:5fa369a TID:25df8fa2 0x85df8b8c: >>> Loading module mouhid.dll at address 0x033F0000-0x033F7000 (RW data at 0x01F5A000-0x01F5A4A8) Loaded symbols for 'C:\WINCE500\PLATFORM\CDS\CALE_CDS\RELDIR \CDS_ARMV4I_DEBUG\MOUHID.DLL' 1896483 PID:e5c10402 TID:25f94db6 0x85f94570: [NOTIFY] HandleSystemEvent 7 /ADD HID1: 1897079 PID:5fa369a TID:25df8fa2 0x85df8b8c: -CHub(External tier 1)::AttachDevice - port = 1, fIsLowSpeed = 1, address = 2 When connecting/disconnecting the USB mouse I get the following debug output related to opening/closing pipes (ohci2 manages to close all previously opened pipes): ******* connecting mouse ******* 2547047 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0301 2547150 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - device attached on port 1 2547151 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CHub(External tier 1)::AttachDevice - port = 1, fIsLowSpeed = 1 2547151 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::AttachDevice - status = DEVICE_CONFIG_STATUS_OPENING_ENDPOINT0_PIPE, failures = 0 2547152 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CControlPipe::OpenPipe 2547152 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 88416 bytes; TotalSize = 94208 bytes 2547152 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE76A0, VA = 0x0028A6A0, Size = 2048, Desc = IssueTransfer TDs 2547153 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 2547153 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 2547154 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE7EA0, VA = 0x0028AEA0, Size = 512, Desc = IssueTransfer TDs 2547154 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85856 bytes; TotalSize = 94208 bytes 2547155 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85856 bytes; TotalSize = 94208 bytes 2547155 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE80A0, VA = 0x0028B0A0, Size = 32, Desc = OpenPipe ED 2547155 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85824 bytes; TotalSize = 94208 bytes 2547156 PID:5fa369a TID:25df8fa2 0x85df8b8c: -CControlPipe::OpenPipe 2547475 PID:5fa369a TID:25df8fa2 0x85df8b8c: +USBD:OpenPipe, EP: 0x81, MaxPkt: 4, Type: Interrupt 2547476 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CInterruptPipe::OpenPipe 2547476 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 85824 bytes; TotalSize = 94208 bytes 2547477 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE80C0, VA = 0x0028B0C0, Size = 2048, Desc = IssueTransfer TDs 2547477 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83776 bytes; TotalSize = 94208 bytes 2547477 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83776 bytes; TotalSize = 94208 bytes 2547478 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE88C0, VA = 0x0028B8C0, Size = 256, Desc = IssueTransfer TDs 2547478 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 2547479 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 2547479 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem AllocateMemory : PA = 0x31CE89C0, VA = 0x0028B9C0, Size = 32, Desc = OpenPipe ED 2547480 PID:5fa369a TID:25df8fa2 0x85df8b8c: CPhysMem ValidateHeaps : FreeSize = 83488 bytes; TotalSize = 94208 bytes ******* disconnecting mouse ******* 2692335 PID:5fa369a TID:5e07fde 0x85deb400: +USBD:ResetPipe 2692337 PID:5fa369a TID:5e07fde 0x85deb400: CFunction::SetOrClearFeature - recipient = 2, wIndex = 129, set/clear = 0x1, feature = 0x0, FAILED 2692353 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - port 1, change = 0x0001, status = 0x0100 2692353 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::HubStatusChangeThread - device detached on port 1 2692354 PID:5fa369a TID:25df8fa2 0x85df8b8c: +CHub(External tier 1)::DetachDevice - port = 1 2692354 PID:5fa369a TID:25df8fa2 0x85df8b8c: CHub(External tier 1)::DetachDevice - created worker thread to handle device detach 2692356 PID:5fa369a TID:e5dfafda 0x85d9b690: +CHub::DetachDownstreamDeviceThread 2692356 PID:5fa369a TID:e5dfafda 0x85d9b690: +CFunction(tier 2)::HandleDetach 2692356 PID:5fa369a TID:e5dfafda 0x85d9b690: +CQueuedPipe(Control)::ClosePipe 2692359 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 83488 bytes; TotalSize = 94208 bytes 2692359 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE80A0, VA = 0x0028B0A0, Size = 32, Desc = OpenPipe ED 2692360 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 2692360 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 83520 bytes; TotalSize = 94208 bytes 2692361 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE7EA0, VA = 0x0028AEA0, Size = 512, Desc = IssueTransfer TDs 2692361 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 84032 bytes; TotalSize = 94208 bytes 2692361 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 84032 bytes; TotalSize = 94208 bytes 2692362 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE76A0, VA = 0x0028A6A0, Size = 2048, Desc = IssueTransfer TDs 2692362 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86080 bytes; TotalSize = 94208 bytes 2692362 PID:5fa369a TID:e5dfafda 0x85d9b690: - CQueuedPipe(Control)::ClosePipe 2692363 PID:5fa369a TID:e5dfafda 0x85d9b690: +CQueuedPipe(Interrupt)::ClosePipe 2692365 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86080 bytes; TotalSize = 94208 bytes 2692365 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE89C0, VA = 0x0028B9C0, Size = 32, Desc = OpenPipe ED 2692366 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86112 bytes; TotalSize = 94208 bytes 2692366 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86112 bytes; TotalSize = 94208 bytes 2692366 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE88C0, VA = 0x0028B8C0, Size = 256, Desc = IssueTransfer TDs 2692367 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 2692367 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 86368 bytes; TotalSize = 94208 bytes 2692368 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem FreeMemory : PA = 0x31CE80C0, VA = 0x0028B0C0, Size = 2048, Desc = IssueTransfer TDs 2692368 PID:5fa369a TID:e5dfafda 0x85d9b690: CPhysMem ValidateHeaps : FreeSize = 88416 bytes; TotalSize = 94208 bytes 2692368 PID:5fa369a TID:e5dfafda 0x85d9b690: - CQueuedPipe(Interrupt)::ClosePipe 2692369 PID:5fa369a TID:e5dfafda 0x85d9b690: +USBD:ClosePipe, hPipe: 0x2BA380 2692369 PID:5fa369a TID:e5dfafda 0x85d9b690: -USBD:ClosePipe 2692369 PID:5fa369a TID:e5dfafda 0x85d9b690: +USBD:ClosePipe, hPipe: 0x2BB030 2692370 PID:5fa369a TID:e5dfafda 0x85d9b690: -USBD:ClosePipe Any idea what's going on? Why do I get "! CQueuedPipe(Control)::ClosePipe 00289e20 doesn't exist!", does this cause a memory leak? Thanks, Jojje Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97442
  - 17
    - Cannot download NK.bin with PB My PB can download nk.bin before. But now it cannot download. the following is the message printed in hyperterminal: ProcessDHCP()::DHCP IP Address Resolved as 10.193.101.88, netmask: 255.255.255.0 Lease time: 43200 seconds Got Response from DHCP server, IP address: 10.193.101.88 No ARP response in 2 seconds, assuming ownership of 10.193.101.88 +EbootSendBootmeAndWaitForTftp Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Sent BOOTME to 255.255.255.255 Got EDBG_CMD_JUMPIMG Got EDBG_CMD_CONFIG, flags:0x00000000 -EbootSendBootmeAndWaitForTftp Download successful! Jumping to image at 0h... Clearing RAM How can I fix the issue? Thanks a lot. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97441
  - 18
    - Suspend Problem.. Hi, I'm working on a x86 processor. I ported winCE on that, and its booting. The only problem is, when i click on suspend option, system halts, but desktop didnt go away. When i press any key in keyboard, USB mouse gets power up, but not working. I'm using AGX display driver. After 1 min, due to system idle time which i have set, monitor power gets down. The following s the some part of debug output. 0x83cc58a8: >>> Loading module netui.dll at address 0x03BE0000-0x03C2B000 (RW data at 0x01FC0000-0x01FC6808) 0x83cc58a8: >>> Loading module commctrl.dll at address 0x03D60000-0x03E04000 (RW data at 0x01FE1000-0x01FE1C0C) 0x83cc5a84: >>> Loading module ssllsp.dll at address 0x03AD0000-0x03AE1000 (RW data at 0x01FA8000-0x01FA9055) 0x83cc5a84: >>> Loading module wspm.dll at address 0x03B00000-0x03B05000 (RW data at 0x01FAD000-0x01FAD154) 0x83f81a54: Geode PM: IOCTL_POWER_SET called 0x83f81a54: Geode PM: IOCTL_POWER_SET called 0x83d2de48: Bailing on save bits because someone has an open DC! 0x83d2de48: Geode PM: IOCTL_POWER_SET called 0x83d2de48: FS: Got Power notif 0x00000002 0x83d2de48: FSREG: Flushing registry 0x83d2de48: FSRAM: Flushing cached file data 0x83d2de48: Powering Off system: 0x83d2de48: Calling GWES power proc. 0x83d2de48: Calling device manager power proc. 0x83d2de48: Calling OEMPowerOff... RTC - Status Reg B - 0x22 0x83d2de48: Back from OEMPowerOff 0x83d2de48: Calling device manager power proc. Help me friends... Regards, Mekas.. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97437
  - 19
    - CHKDSK reports file system error on Compact Flash Hi, We are using CE 6.0 with Hive based registry.( amd LX platform) The CE 6.0 image successfully bootsup with "Documents and settings" folder in Compact Flash. But when we takeout Compact flash and do CHKDSK,it reports file system error in "Documents and settings" folder. Is it a bug with Hive Based registry in CE 6.0? Thanks & Regards, Krishna Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97435
  - 20
    - Problems with serial port during booting We have a problem with COM3 on a CE5 device (PXA255). On this COM port we have connected a GPS receiver. On startup (startup is always an cold boot on our device) the GPS receiver sends immediatly data to the COM-Port. Now it seems, that the serial port driver could not handle this. The system hangs in device.exe. in the launch section we have defined the call to shell.exe later, but it will be never called. If we start the system with disconnected GPS receiver , everythings works fine. If we reconnect later (system is running now), we get the GPS data fine . Thanks for your help Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97431
  - 21
    - Unsupported Device Type Dear All: I have Windows CE 5.0 based Handheld Device, and I tried to install a cab file which support WinCE 5.0 platform, but anytime I try to run the CAB file in my device, I got error message "Unsupported Device Type". I tried the same CAB file withe another WinCE 5.0 based platform, workds fine. My question is, where in the file or in OS, I define this Handheld is WinCE 5.0 device. Please help. Thanks Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97428
  - 22
    - Issues with HIve based Registry Hi all, i have read a lot of messages on this but nothing seems to help.Please provide me with any information you have as i am new to WinCE. I am trying to implement hive based registry. I selected it in catalog items and did a clean sysgen. My platform.reg enteries read as ;===================================== ; Settings for NOR fLash ;===================================== ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\NORFLASH] "DriverPath"="Drivers\\BuiltIn\\NORFLASH" "LoadFlags"=dword:1 "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NORFLASH] "Prefix" = "DSK" "Dll" = "nor_flash.dll" "Index" = dword:1 "IClass"="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" "Size" = dword:200000 "Address"= dword:02100000 "Profile"="NORFLASH" "Flags"=dword:1000 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\NORFLASH\FATFS] "MountAsBootable"= dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\NORFLASH] "Name"="AMD NOR Flash" "Folder"="NOR_Flash" "FileSystem"="fatfsd.dll" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "AutoFormat"=dword:1 "MountFlags"=dword:0 "MountAsBootable"= dword:1 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSYSRAM ;===================================== ; Settings for hive based registry ;===================================== ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="Registry\\system.hv" "PROFILEDIR"="Registry" "Flags"=dword:3 "Start DevMgr"=dword:1 "DefaultUser"="aalok" ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF Also in command line i gave set PRJ_ENABLE_FSREGHIVE=1 set BSP_ENABLE_FSREGHIVE=1 My debug info reads as... PB Debugger Kernel debugger connected. 4294767296 PID:0 TID:0 [0] : start: 8186a000, extension: 0000b000, length: 05567000 4294767296 PID:0 TID:0 NKStartup done, starting up kernel. 4294767297 PID:0 TID:0 Windows CE KernelInit 4294767317 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first = c0010000, last = c1110000 4294767318 PID:400002 TID:2 g_pprcNK == 0x81861aa0 4294767319 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0000e000 4294767319 PID:400002 TID:410002 Initializing Memory Mapped File Support 4294767329 PID:400002 TID:410002 Scheduling the first thread. 4294767329 PID:400002 TID:410002 Detecting VFP... 4294767330 PID:400002 TID:410002 VFP Not Found! 4294767330 PID:400002 TID:410002 LoaderInit: Initialing loader 4294767331 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0000e000 4294767332 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000 4294767335 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00018000 4294767433 PID:400002 TID:410002 Heap Statistics at 0xC01B7AA0 4294767457 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool 4294767458 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool 4294767472 PID:400002 TID:410002 OSAXST0: Platform Name = PLATFORM_TYPE 4294767490 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll' (0x86DB987C) at address 0xC0010000-0xC0045000 in Process 'NK.EXE' (0x81861AA0) 4294767494 PID:400002 TID:410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 22 4294767551 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x81861AA0) at address 0x80000000-0x8000E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM). PB Debugger Target name: CE Device PB Debugger Probe name: KdStub PB Debugger Binary Image should be loaded at 0x80000000 / Data relocated at 0x81806000 PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\NK.EXE' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\NK.EXE' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\COREDLL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KITL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KERNEL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OALIOCTL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\HD.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OSAXST0.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OSAXST1.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.COREDLL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KD.DLL' 4294769800 PID:400002 TID:410002 HD: Immediate debugger module load notifications ACTIVE (slower boot - non real-time). 4294769827 PID:400002 TID:410002 Message Queue support initialized, g_hMsgQHeap = d0040750 4294769851 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'filesys.dll' (0x86D93DD4) at address 0xC01F0000-0xC0289000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\FILESYS.DLL' 4294769857 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x86D90300) at address 0xC01D0000-0xC01E8000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.FPCRT.DLL' 4294769873 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x86D90438) at address 0xC05C0000-0xC0605000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\FSDMGR.DLL' 4294769876 PID:400002 TID:600002 FSDMGR!DllMain: DLL_PROCESS_ATTACH 4294769878 PID:400002 TID:650002 CertMod.dll not found, using old OEM Trust Model 4294769907 PID:400002 TID:650002 FileSystem Starting - starting with clean file system 4294769912 PID:400002 TID:650002 FSDMGR!STOREMGR_Initialize 4294769914 PID:400002 TID:650002 FSDMGR!InitializeStoreAPI 4294769922 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2 4294769923 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1) 4294769924 PID:400002 TID:650002 FSDMGR!InitializeROMFileSystem: File System=ROM 4294769930 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x86D636F0) at address 0xC0290000-0xC0297000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\ROMFSD.DLL' 4294769937 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "ROM" at index 3 4294769938 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3 (Name="ROM", MountFlags=0x71) 4294769951 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'eventlog.dll' (0x86D63B4C) at address 0xC0DA0000-0xC0DC4000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\EVENTLOG.DLL' 4294769953 PID:400002 TID:650002 EventLog:: EventLogInit() called 4294769959 PID:400002 TID:650002 FSVOL: Opening existing volume 4294769967 PID:400002 TID:650002 FSVOL: Volume heap already initialized 4294769968 PID:400002 TID:650002 FSREG: Mounted ROM portion of boot registry 4294769969 PID:400002 TID:650002 FSVOL: Creating clean virtual volume 4294769973 PID:400002 TID:650002 FSVOL: Initializing volume heap 4294770012 PID:400002 TID:650002 FSREG: Mounted RAM portion of boot registry 4294770026 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ DevMgrApiSetReady 4294770027 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ PowerManagerReady 4294770029 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ GweApiSetReady 4294770029 PID:400002 TID:650002 FS: Creating signal event ReleaseFSD 4294770032 PID:400002 TID:650002 FILESYS: Starting boot phase 0. 4294770032 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1) 4294770040 PID:400002 TID:650002 FSDMGR: File security disabled. 4294770046 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1 4294770049 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore 4294770053 PID:400002 TID:650002 FILESYS: RAM File System FSD_MountDisk registering folder "Object Store" 4294770057 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4 4294770058 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x46) 4294770060 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=NORFLASH 4294770061 PID:400002 TID:650002 FSDMGR!AutoLoadBlockDevice: Auto- loading block driver from "Drivers\BuiltIn\NORFLASH" 4294770063 PID:400002 TID:650002 FSDMGR!MountStore: Failed opening new store "NORFLASH"; error=4319 4294770064 PID:400002 TID:650002 FSDMGR!StoreDisk_t::~StoreDisk_t: deleting store (D0045DD0) 4294770065 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: Unable to auto-load HKLM\System\StorageManager\AutoLoad\NORFLASH; error=4319 4294770071 PID:400002 TID:650002 FILESYS: Starting boot phase 1. 4294770071 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0) 4294770072 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1 4294770074 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=1, RootKey=System\StorageManager\AutoLoad, FileSystem_t=Relfsd 4294770081 PID:400002 TID:9f0002 FSDMGR!PNPThread: Using PNPUnloadDelay of 4096 4294770090 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'relfsd.dll' (0x86D47C90) at address 0xC0590000-0xC059F000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\RELFSD.DLL' 4294770099 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "Release" at index 5 4294770099 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5 (Name="Release", MountFlags=0x0) 4294770101 PID:400002 TID:650002 Mounted ReleaseFSD volume '\Release' 4294770105 PID:400002 TID:650002 size of 'dbglist.txt' = 00000000 4294770184 PID:400002 TID:9f0002 FSDMGR!PNPThread: PNPThread starting! 4294773121 PID:400002 TID:650002 FILESYS: Starting device and waiting for boot file system. 4294773128 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'device.dll' (0x86D3D5C8) at address 0xC0480000-0xC0485000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVICE.DLL' 4294773170 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'devmgr.dll' (0x86D3D700) at address 0xC0490000-0xC04B7000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVMGR.DLL' 4294773174 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x86D3D838) at address 0xC0680000-0xC068E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.CEDDK.DLL' 4294773191 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'pm.dll' (0x86D3D980) at address 0xC04E0000-0xC0508000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\PM.DLL' 4294773193 PID:400002 TID:650002 Console NOT redirected for process 0x400002 4294773195 PID:400002 TID:650002 Exception 'Data Abort' (4): Thread- Id=00650002(pth=86d907d4), Proc-Id=00400002(pprc=81861aa0) 'NK.EXE', VM-active=00400002(pprc=81861aa0) 'NK.EXE' 4294773269 PID:400002 TID:650002 PC=c00f6184(k.coredll.dll +0x00036184) RA=00000030(???+0x00000030) SP=d00ce3c4, BVA=00000030 4294773277 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'pm.dll' (0x86D3D980) at address 0xC04E0000-0xC0508000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\PM.DLL' 4294773280 PID:400002 TID:650002 DoImport Failed! Unable to import from Library 'PM.dll' 4294773280 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'k.ceddk.dll' (0x86D3D838) at address 0xC0680000-0xC068E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.CEDDK.DLL' 4294773428 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'devmgr.dll' (0x86D3D700) at address 0xC0490000-0xC04B7000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVMGR.DLL' 4294773431 PID:400002 TID:650002 DoImport Failed! Unable to import from Library 'DEVMGR.dll' 4294773436 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'device.dll' (0x86D3D5C8) at address 0xC0480000-0xC0485000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVICE.DLL' 4294773516 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos \COREOS \filesys\main\.\fsmain.c line 2399: 4294773517 PID:400002 TID:650002 Filesys: Failed to load device.dll 4294773596 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos \COREOS \filesys\reg\reghive\.\registry.c line 922: 4294773596 PID:400002 TID:650002 FSREG: Unable to start device! 4294773688 PID:400002 TID:650002 FSREG: Unable to load system registry! Registry will be unavailable. 4294773688 PID:400002 TID:650002 FileSys: DEBUGCHK failed in file C: \ymzki\private\winceos\COREOS\filesys\reg\reghive\.\registry.c at line 1147 4294773700 PID:400002 TID:650002 FSREG: Unable to read value "ProfileDir" under HKEY_LOCAL_MACHINE\init\BootVars 4294773700 PID:400002 TID:650002 FSREG: No profile directory provided. Using default: Documents and Settings 4294773780 PID:400002 TID:650002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294774142 PID:400002 TID:650002 FSREG: Unable to read value "RequireCertMod" under HKEY_LOCAL_MACHINE\init\BootVars 4294774143 PID:400002 TID:650002 Error creating Comm\Security\Crypto key 4294774221 PID:400002 TID:650002 FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294774221 PID:400002 TID:650002 FSREG: Logging in default user. 4294774222 PID:400002 TID:650002 FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294774222 PID:400002 TID:650002 SetCurrentUser: Logging out (nobody), logging in default 4294774223 PID:400002 TID:650002 BuildPath: Documents and Settings 4294774455 PID:400002 TID:650002 BuildPath: Documents and Settings \default 4294774533 PID:400002 TID:650002 FSREG: Mounting ROM portion of user hive 4294774615 PID:400002 TID:650002 FSVOL: Opening existing volume 4294774690 PID:400002 TID:650002 FSVOL: Volume heap already initialized 4294774750 PID:400002 TID:650002 Mounting user hive from Documents and Settings\default\user.hv 4294774752 PID:400002 TID:650002 FSREG: Mounting clean user hive 4294774753 PID:400002 TID:650002 FSVOL: Creating new volume (size=28672 bytes) 4294774761 PID:400002 TID:650002 FSVOL: Initializing volume heap 4294774925 PID:400002 TID:650002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294774937 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=2 (PrevBootPhase=1) 4294774937 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=1 4294774944 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'sqlcese30.sys.dll' (0x86D3D664) at address 0xC0F80000-0xC0FED000 in Process 'NK.EXE' (0x81861AA0) 4294774985 PID:400002 TID:9f0002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=2 PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\SQLCESE30.SYS.DLL' 4294775047 PID:400002 TID:650002 Initializing Database 4294775060 PID:400002 TID:650002 DB:Validation: Name already exists DB_notify_events 4294775061 PID:400002 TID:650002 DB:CeCreateDatabase failed 4294775066 PID:400002 TID:650002 Filesystem initialized! 4294775069 PID:400002 TID:650002 FILESYS: Waiting for kernel to be ready to launch apps 4294775139 PID:400002 TID:600002 InitMUI: DISABLED (0) 4294775140 PID:400002 TID:650002 FS: HKLM\System\Events not available, no signal events created. 4294775140 PID:400002 TID:650002 FILESYS: Launching apps 4294775141 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos \COREOS \filesys\main\.\fsmain.c line 2563: 4294775141 PID:400002 TID:650002 Unable to locate init key for starting apps! 4294775142 PID:400002 TID:650002 FILESYS: Done launching apps 4294775219 PID:400002 TID:650002 This device has booted 0 times !!! And it gets stuck at this point. Please help me. I have tried a lot of things but nothing seems to work. Do i give "flags"=dword:1 at other places also...? And what is wrong with the settings i have kept?? Thanks in advance. Regards Aalok Sood Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97427
  - 23
    - ActiveSync connection problem after reboot Hi, For an S3C2440 WinCE 5.0 platform we must implement POWER_STATE_OFF and POWER_STATE_SUSPEND power states. If the device is connected to the PC via USB (ActiveSync working fine) and I suspend/resume, it is possible to reconnect ActiveSync, although I have to unplug and plug back the USB cable. Annoying, but I don't care at this point. However, if I completely power off the system (this is done with a locally modified version of public\common\oak\drivers\pm\pdd\default\platform.cpp in the function PlatformSetSystemPowerState), at the next time the system boots I keep getting RAS error 608 (ERROR_DEVICE_DOES_NOT_EXIST as defined in raserror.h). I "traced" (by doing string searches) this error message to ras.c file from the private source tree (private\winceos\comm\ppp2\ppp\ras\ras.c, line 895 - inside the function pppRasCntlGetDispPhone, a call to FindAdapter is failing). The only way I found to restore ActiveSync functionality in this case is by deleting the system.hv registry file (with command RegReplaceKey(HKEY_LOCAL_MACHINE, NULL, NULL, NULL) and another reboot). Am I doing something wrong? It looks like the registry is being left in a funny state that affects ActiveSync. I am using hive-based registry. Any suggestion is welcome. Thanks! H Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97425
  - 24
    - embedded web server over ActiveSync? My device does not have ethernet or any other TCP/IP connections. I do have USB client with ActiveSync working (RNDIS and serial clients installed). And ActiveSync launches automatically when USB cable plugged in. I would like to run an embedded web server that I can browse from the desktop via AtiveSync. Is this possible? I have the web httpd installed standard registry settings .. IsEnabled etc. I think AS uses 192.168.55.101 but when I type: http://192.168.55.101 from the desktop browser I get nothing. Can this be done? Do I need to "Bind" it some how? Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97424
  - 25
    - problem with typically HelloWorld application Hey i made an CustomDevice OS (with no extra options) and this works fine but now i want to add the typically HelloWorld application to my OS. But when i'm building it i get errors because of unreferenced symbols.Now i have two questions. 1) How can i get away these errors (maybe by adding a lib to my source file or something like that) 2) On my OS there's nothing implemented like a display driver or gwes or gdi and i see it's a graphical application, but if i add minimal gwes or minimal gdi via the catalog items, my OS crashes after the debug note Launching apps so wich elements do i have to add for the graphical part and what's the best way to include them. Below you see my errors unresolved external symbol DispatchMessageW referenced in function WinMain BUILD: [01:0000000035:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol TranslateMessage referenced in function WinMain BUILD: [01:0000000036:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol TranslateAcceleratorW referenced in function WinMain BUILD: [01:0000000037:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol GetMessageW referenced in function WinMain BUILD: [01:0000000038:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol LoadAcceleratorsW referenced in function WinMain BUILD: [01:0000000039:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol RegisterClassW referenced in function "unsigned short __cdecl MyRegisterClass(struct HINSTANCE__ *)" (? MyRegisterClass@@YAGPAUHINSTANCE__@@@Z) BUILD: [01:0000000040:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol GetStockObject referenced in function "unsigned short __cdecl MyRegisterClass(struct HINSTANCE__ *)" (? MyRegisterClass@@YAGPAUHINSTANCE__@@@Z) BUILD: [01:0000000041:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol UpdateWindow referenced in function "int __cdecl InitInstance(struct HINSTANCE__ *,int)" (? InitInstance@@YAHPAUHINSTANCE__@@H@Z) BUILD: [01:0000000042:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol ShowWindow referenced in function "int __cdecl InitInstance(struct HINSTANCE__ *,int)" (? InitInstance@@YAHPAUHINSTANCE__@@H@Z) BUILD: [01:0000000043:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol CreateWindowExW referenced in function "int __cdecl InitInstance(struct HINSTANCE__ *,int)" (? InitInstance@@YAHPAUHINSTANCE__@@H@Z) BUILD: [01:0000000044:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol DefWindowProcW referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (? WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000045:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol PostQuitMessage referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (?WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000046:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol EndPaint referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (? WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000047:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol DrawTextW referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (? WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000048:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol GetClientRect referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (? WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000049:ERRORE] HelloWorld.obj : error LNK2019: unresolved external symbol BeginPaint referenced in function "long __cdecl WndProc(struct HWND__ *,unsigned int,unsigned int,long)" (? WndProc@@YAJPAUHWND__@@IIJ@Z) BUILD: [01:0000000050:ERRORE] obj\MIPSII\debug\HelloWorld.exe : fatal error LNK1120: 16 unresolved externals Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97414
- Next
  - 1
    - link problem with DeviceIOControl in driver the linker can't find DeviceIOControl(). I checked coredll.dll with dumpbin and it is there. I can link with ReadFile()/WriteFile() fine. Am I missing anything else? void olSetBits(unsigned int BitsToSet) { DWORD BytesWritten; //WriteFile(hMLT, &BitsToSet, 2, &BytesWritten, NULL); DeviceIOControl(hMLT, IOCTL_MLT_SETBITS, &BitsToSet, 2, NULL, 0, &BytesWritten, NULL); //only write these bits } sources file: TARGETNAME=xrtc RELEASETYPE=PLATFORM TARGETTYPE=DYNLINK TARGETLIBS= \ $(_COMMONSDKROOT)\lib\$(_CPUINDPATH)\coredll.lib \ $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\ceddk.lib \ SOURCELIBS= \ DEFFILE=xrtc.def PREPROCESSDEFFILE=1 DLLENTRY=XRC_DllEntry SOURCES=xrtc.c \ rtcx.c Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97406
  - 2
    - Serial port driver bug Hello! IÂ´m using RS485 2-wire communication and found the following behaviour of the serial port driver: The condition for RS485 communication in both directions is to set dcb.fRtsControl = RTS_CONTROL_TOGGLE. Now sending some bytes over the serial port depends on the speed of the processor. Using a Geode GX2 and 115200 baud the bytes are all sent. Using a GeodeLX and 115200 baud the last byte is not sent correctly. Using the GeodeGX2 with slower baudrate eg. 110 baud the last byte is also not correctly sent. This behaviour is caused by the Com_Write Function in mdd.c which clears the RTS without waiting for the Transmitter Empty Flag of the Line Status Register. So i made the following changes: if ( pSerialHead->DCB.fRtsControl == RTS_CONTROL_TOGGLE ) { // Patch if(pFuncTbl->HWGetLSR != NULL) while(!(pFuncTbl->HWGetLSR(pHWHead) & 0x40)); // wait for Transmitter Empty (TEMT) Flag // End Patch pFuncTbl->HWClearRTS(pHWHead); } HWGetLSR is a extension of the HW_VTABLE Struct, which is linked with the included SerGetLSR Function in cserpdd.c. The SerGetLSR Function uses the GetLineStatus Function in pdd16550.cpp. The functions are implemented like the HWClearRTS and SerClearRTS functions. Now the serial RS422 2-wire communications works well. Regards, Andy Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97402
  - 3
    - USB Disk On Key Hi, When I try to connect a DOK with a large number of files to my device , the OS freezes while displaying the file list through Windows Explorer. When that happens, I disconnect and reconnect the DOK and then go back to explorer. After doing so, all the files are displayed . I'm running CE 5.0 with all the QFEs. It looks like there is a buffer that gets filled up and requires a refresh. Any ideas how to fix this? The problem occures with all types of DOKS. thanks Ohad Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97401
  - 4
    - PlatforMBuilder+SDK I'm trying to build a SDK in PlatformBuilder for Win CE 5.0 I find this kind of error Committing database changes Rolling sysgen'ed headers and libs Emulator: x86_Release CreateFile failed to open "C:\WINCE500\PBWorkspaces\ms\SDK\ms\Include\Emulator\shellsdk.h" , Err = 32 ==> The process cannot access the file because it is being used by another process. Sorry I'm new,but I don't understand what's happened ....somebody helps me! thanks Mauro Savoiardo msavoiardo@tin.it Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97400
  - 5
    - limitation of VirtualAlloc calls? hi i get an error when i try to load a dll with the LoadLibrary() call whithin my application. my app is quite big and contains many dll's. with the GetLastError() i got the 14 (ERROR_OUTOFMEMORY) error. so i did some logging with several tools to check the virutal memory situation. the result was the following (Slot1 and Slot 0): free virtual memory: Total commit: 34476032 Total reserved: 14319616 Total free: 18313216 Total waste: 487424 Total avail: 17825792 Largest contiguous free memory block: size 7208960 at 0x00650000 The largest contiguous free memorblock resides in slot 0. The dll i try to load is about 1,8MB so it shout fit into that gap well. i heard about a maximum number of VirtualAlloc calls. could this be a problem? Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97394
  - 6
    - linker settings Hello, I had problems to load DLLs with Platform Builder 5.0 in debug build. The DLLs are built with VS2005 and therefore had a different set of linker settings. The linker setting that affected most is /INCREMENTAL:NO, that is used in PB build but not in VS2005. This caused the linker to generate an .idata section. PB failed to laod this DLLs. Other differences are the use of /LARGEADDRESSAWARE and "/MERGE:.rdata=.text". AFAIK "edit, compile and continue" does not work with Windows CE at all. So I dont understand, why this is enabled by default for samrt devices. But about with the other options, are there requirements? What effect has the merge option? /Helge -- Time is an ocean but it ends at the shore. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97392
  - 7
    - How to dynamically change control color? Hi friends, I need to dynamically(at runtime) change the colors of static text's, slidebar's and editbox background color. I can individually change them handling WM_CTLCOLORSTATIC, WM_CTLCOLORBTN and WM_CTLCOLOREDIT messages but i can't change them at runtime. Do these messages come only once? If so how can i send these messages. I tried to use SendMessage but i also doesn't work. Any sugeestions please...Thanks.. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97386
  - 8
    - How to resume ce 5 from pxa27x deep-sleep mode Dear all, some people showed me an handheld device from hp with a nice behaviour: 1) launch some applications 2) remove battery pack 3) insert battery pack 4) the device restart quickly with the applications in the previous state I am very surprised because the pxa27x comes out of deep-sleep only with one register preserved (pspr) How can I achieve the same goal? Thank you very much Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97384
  - 9
    - Issues with Hive based Registry on NOR flash Hi all, i have read a lot of messages on this but nothing seems to help.Please provide me with any information you have as i am new to WinCE. I am trying to implement hive based registry. I selected it in catalog items and did a clean sysgen. My platform.reg enteries read as ;===================================== ; Settings for NOR fLash ;===================================== ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\System\StorageManager\Autoload\NORFLASH] "DriverPath"="Drivers\\BuiltIn\\NORFLASH" "LoadFlags"=dword:1 "BootPhase"=dword:0 [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NORFLASH] "Prefix" = "DSK" "Dll" = "nor_flash.dll" "Index" = dword:1 "IClass"="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}" "Size" = dword:200000 "Address"= dword:02100000 "Profile"="NORFLASH" "Flags"=dword:1000 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\NORFLASH\FATFS] "MountAsBootable"= dword:1 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\NORFLASH] "Name"="AMD NOR Flash" "Folder"="NOR_Flash" "FileSystem"="fatfsd.dll" "PartitionDriver"="mspart.dll" "AutoMount"=dword:1 "AutoPart"=dword:1 "AutoFormat"=dword:1 "MountFlags"=dword:0 "MountAsBootable"= dword:1 ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF FILESYS_FSYSRAM ;===================================== ; Settings for hive based registry ;===================================== ; @CESYSGEN IF FILESYS_FSREGHIVE ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SYSTEMHIVE"="Registry\\system.hv" "PROFILEDIR"="Registry" "Flags"=dword:3 "Start DevMgr"=dword:1 "DefaultUser"="aalok" ; END HIVE BOOT SECTION ; @CESYSGEN ENDIF Also in command line i gave set PRJ_ENABLE_FSREGHIVE=1 set BSP_ENABLE_FSREGHIVE=1 My debug info reads as... PB Debugger Kernel debugger connected. 4294767296 PID:0 TID:0 [0] : start: 8186a000, extension: 0000b000, length: 05567000 4294767296 PID:0 TID:0 NKStartup done, starting up kernel. 4294767297 PID:0 TID:0 Windows CE KernelInit 4294767317 PID:400002 TID:2 Reserve VM for kernel XIP DLls, first = c0010000, last = c1110000 4294767318 PID:400002 TID:2 g_pprcNK == 0x81861aa0 4294767319 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0000e000 4294767319 PID:400002 TID:410002 Initializing Memory Mapped File Support 4294767329 PID:400002 TID:410002 Scheduling the first thread. 4294767329 PID:400002 TID:410002 Detecting VFP... 4294767330 PID:400002 TID:410002 VFP Not Found! 4294767330 PID:400002 TID:410002 LoaderInit: Initialing loader 4294767331 PID:400002 TID:410002 Updated eptr->e32_vsize to = 0000e000 4294767332 PID:400002 TID:410002 Updated eptr->e32_vsize to = 000a2000 4294767335 PID:400002 TID:410002 Updated eptr->e32_vsize to = 00018000 4294767433 PID:400002 TID:410002 Heap Statistics at 0xC01B7AA0 4294767457 PID:400002 TID:410002 PGPOOL: Reserved 768 pages for Loader pool 4294767458 PID:400002 TID:410002 PGPOOL: Reserved 256 pages for File pool 4294767472 PID:400002 TID:410002 OSAXST0: Platform Name = PLATFORM_TYPE 4294767490 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'kd.dll' (0x86DB987C) at address 0xC0010000-0xC0045000 in Process 'NK.EXE' (0x81861AA0) 4294767494 PID:400002 TID:410002 KD: Starting kernel debugger software probe (KdStub) - KD API version 22 4294767551 PID:400002 TID:410002 OSAXST1: >>> Loading Module 'NK.EXE' (0x81861AA0) at address 0x80000000-0x8000E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM). PB Debugger Target name: CE Device PB Debugger Probe name: KdStub PB Debugger Binary Image should be loaded at 0x80000000 / Data relocated at 0x81806000 PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\NK.EXE' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\NK.EXE' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\COREDLL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KITL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KERNEL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OALIOCTL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\HD.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OSAXST0.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\OSAXST1.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.COREDLL.DLL' PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\KD.DLL' 4294769800 PID:400002 TID:410002 HD: Immediate debugger module load notifications ACTIVE (slower boot - non real-time). 4294769827 PID:400002 TID:410002 Message Queue support initialized, g_hMsgQHeap = d0040750 4294769851 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'filesys.dll' (0x86D93DD4) at address 0xC01F0000-0xC0289000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\FILESYS.DLL' 4294769857 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'k.fpcrt.dll' (0x86D90300) at address 0xC01D0000-0xC01E8000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.FPCRT.DLL' 4294769873 PID:400002 TID:600002 OSAXST1: >>> Loading Module 'fsdmgr.dll' (0x86D90438) at address 0xC05C0000-0xC0605000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\FSDMGR.DLL' 4294769876 PID:400002 TID:600002 FSDMGR!DllMain: DLL_PROCESS_ATTACH 4294769878 PID:400002 TID:650002 CertMod.dll not found, using old OEM Trust Model 4294769907 PID:400002 TID:650002 FileSystem Starting - starting with clean file system 4294769912 PID:400002 TID:650002 FSDMGR!STOREMGR_Initialize 4294769914 PID:400002 TID:650002 FSDMGR!InitializeStoreAPI 4294769922 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "StoreMgr" at index 2 4294769923 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 2 (Name="StoreMgr", MountFlags=0x1) 4294769924 PID:400002 TID:650002 FSDMGR!InitializeROMFileSystem: File System=ROM 4294769930 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'romfsd.dll' (0x86D636F0) at address 0xC0290000-0xC0297000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\ROMFSD.DLL' 4294769937 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "ROM" at index 3 4294769938 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 3 (Name="ROM", MountFlags=0x71) 4294769951 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'eventlog.dll' (0x86D63B4C) at address 0xC0DA0000-0xC0DC4000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\EVENTLOG.DLL' 4294769953 PID:400002 TID:650002 EventLog:: EventLogInit() called 4294769959 PID:400002 TID:650002 FSVOL: Opening existing volume 4294769967 PID:400002 TID:650002 FSVOL: Volume heap already initialized 4294769968 PID:400002 TID:650002 FSREG: Mounted ROM portion of boot registry 4294769969 PID:400002 TID:650002 FSVOL: Creating clean virtual volume 4294769973 PID:400002 TID:650002 FSVOL: Initializing volume heap 4294770012 PID:400002 TID:650002 FSREG: Mounted RAM portion of boot registry 4294770026 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ DevMgrApiSetReady 4294770027 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ PowerManagerReady 4294770029 PID:400002 TID:650002 FS: Creating signal event SYSTEM/ GweApiSetReady 4294770029 PID:400002 TID:650002 FS: Creating signal event ReleaseFSD 4294770032 PID:400002 TID:650002 FILESYS: Starting boot phase 0. 4294770032 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=0 (PrevBootPhase=-1) 4294770040 PID:400002 TID:650002 FSDMGR: File security disabled. 4294770046 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=0, LoadFlags=1 4294770049 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=ObjectStore 4294770053 PID:400002 TID:650002 FILESYS: RAM File System FSD_MountDisk registering folder "Object Store" 4294770057 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "Object Store" at index 4 4294770058 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 4 (Name="", MountFlags=0x46) 4294770060 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=0, RootKey=System\StorageManager\AutoLoad, FileSystem_t=NORFLASH 4294770061 PID:400002 TID:650002 FSDMGR!AutoLoadBlockDevice: Auto- loading block driver from "Drivers\BuiltIn\NORFLASH" 4294770063 PID:400002 TID:650002 FSDMGR!MountStore: Failed opening new store "NORFLASH"; error=4319 4294770064 PID:400002 TID:650002 FSDMGR!StoreDisk_t::~StoreDisk_t: deleting store (D0045DD0) 4294770065 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: Unable to auto-load HKLM\System\StorageManager\AutoLoad\NORFLASH; error=4319 4294770071 PID:400002 TID:650002 FILESYS: Starting boot phase 1. 4294770071 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=1 (PrevBootPhase=0) 4294770072 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=1, LoadFlags=1 4294770074 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystem: CurrentBootPhase=1, RootKey=System\StorageManager\AutoLoad, FileSystem_t=Relfsd 4294770081 PID:400002 TID:9f0002 FSDMGR!PNPThread: Using PNPUnloadDelay of 4096 4294770090 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'relfsd.dll' (0x86D47C90) at address 0xC0590000-0xC059F000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\RELFSD.DLL' 4294770099 PID:400002 TID:650002 FSDMGR! MountTable_t::RegisterVolumeName: Registered "Release" at index 5 4294770099 PID:400002 TID:650002 FSDMGR!MountTable_t::RegisterVolume: Registered volume at index 5 (Name="Release", MountFlags=0x0) 4294770101 PID:400002 TID:650002 Mounted ReleaseFSD volume '\Release' 4294770105 PID:400002 TID:650002 size of 'dbglist.txt' = 00000000 4294770184 PID:400002 TID:9f0002 FSDMGR!PNPThread: PNPThread starting! 4294773121 PID:400002 TID:650002 FILESYS: Starting device and waiting for boot file system. 4294773128 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'device.dll' (0x86D3D5C8) at address 0xC0480000-0xC0485000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVICE.DLL' 4294773170 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'devmgr.dll' (0x86D3D700) at address 0xC0490000-0xC04B7000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVMGR.DLL' 4294773174 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'k.ceddk.dll' (0x86D3D838) at address 0xC0680000-0xC068E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.CEDDK.DLL' 4294773191 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'pm.dll' (0x86D3D980) at address 0xC04E0000-0xC0508000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\PM.DLL' 4294773193 PID:400002 TID:650002 Console NOT redirected for process 0x400002 4294773195 PID:400002 TID:650002 Exception 'Data Abort' (4): Thread- Id=00650002(pth=86d907d4), Proc-Id=00400002(pprc=81861aa0) 'NK.EXE', VM-active=00400002(pprc=81861aa0) 'NK.EXE' 4294773269 PID:400002 TID:650002 PC=c00f6184(k.coredll.dll+0x00036184) RA=00000030(???+0x00000030) SP=d00ce3c4, BVA=00000030 4294773277 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'pm.dll' (0x86D3D980) at address 0xC04E0000-0xC0508000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\PM.DLL' 4294773280 PID:400002 TID:650002 DoImport Failed! Unable to import from Library 'PM.dll' 4294773280 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'k.ceddk.dll' (0x86D3D838) at address 0xC0680000-0xC068E000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\K.CEDDK.DLL' 4294773428 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'devmgr.dll' (0x86D3D700) at address 0xC0490000-0xC04B7000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVMGR.DLL' 4294773431 PID:400002 TID:650002 DoImport Failed! Unable to import from Library 'DEVMGR.dll' 4294773436 PID:400002 TID:650002 OSAXST1: <<< Unloading Module 'device.dll' (0x86D3D5C8) at address 0xC0480000-0xC0485000 in Process 'NK.EXE' (0x81861AA0) PB Debugger Unloaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\DEVICE.DLL' 4294773516 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos\COREOS \filesys\main\.\fsmain.c line 2399: 4294773517 PID:400002 TID:650002 Filesys: Failed to load device.dll 4294773596 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos\COREOS \filesys\reg\reghive\.\registry.c line 922: 4294773596 PID:400002 TID:650002 FSREG: Unable to start device! 4294773688 PID:400002 TID:650002 FSREG: Unable to load system registry! Registry will be unavailable. 4294773688 PID:400002 TID:650002 FileSys: DEBUGCHK failed in file C: \ymzki\private\winceos\COREOS\filesys\reg\reghive\.\registry.c at line 1147 4294773700 PID:400002 TID:650002 FSREG: Unable to read value "ProfileDir" under HKEY_LOCAL_MACHINE\init\BootVars 4294773700 PID:400002 TID:650002 FSREG: No profile directory provided. Using default: Documents and Settings 4294773780 PID:400002 TID:650002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294774142 PID:400002 TID:650002 FSREG: Unable to read value "RequireCertMod" under HKEY_LOCAL_MACHINE\init\BootVars 4294774143 PID:400002 TID:650002 Error creating Comm\Security\Crypto key 4294774221 PID:400002 TID:650002 FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294774221 PID:400002 TID:650002 FSREG: Logging in default user. 4294774222 PID:400002 TID:650002 FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294774222 PID:400002 TID:650002 SetCurrentUser: Logging out (nobody), logging in default 4294774223 PID:400002 TID:650002 BuildPath: Documents and Settings 4294774455 PID:400002 TID:650002 BuildPath: Documents and Settings \default 4294774533 PID:400002 TID:650002 FSREG: Mounting ROM portion of user hive 4294774615 PID:400002 TID:650002 FSVOL: Opening existing volume 4294774690 PID:400002 TID:650002 FSVOL: Volume heap already initialized 4294774750 PID:400002 TID:650002 Mounting user hive from Documents and Settings\default\user.hv 4294774752 PID:400002 TID:650002 FSREG: Mounting clean user hive 4294774753 PID:400002 TID:650002 FSVOL: Creating new volume (size=28672 bytes) 4294774761 PID:400002 TID:650002 FSVOL: Initializing volume heap 4294774925 PID:400002 TID:650002 FSREG: Unable to read value "RegistryFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294774937 PID:400002 TID:650002 FSDMGR!STOREMGR_StartBootPhase BootPhase=2 (PrevBootPhase=1) 4294774937 PID:400002 TID:650002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=1 4294774944 PID:400002 TID:650002 OSAXST1: >>> Loading Module 'sqlcese30.sys.dll' (0x86D3D664) at address 0xC0F80000-0xC0FED000 in Process 'NK.EXE' (0x81861AA0) 4294774985 PID:400002 TID:9f0002 FSDMGR!AutoLoadFileSystems: CurrentBootPhase=2, LoadFlags=2 PB Debugger Loaded symbols for 'C:\WINCE600\OSDESIGNS\BLOCK_FLASH \RELDIR\SFUMATO_ARMV4I_DEBUG\SQLCESE30.SYS.DLL' 4294775047 PID:400002 TID:650002 Initializing Database 4294775060 PID:400002 TID:650002 DB:Validation: Name already exists DB_notify_events 4294775061 PID:400002 TID:650002 DB:CeCreateDatabase failed 4294775066 PID:400002 TID:650002 Filesystem initialized! 4294775069 PID:400002 TID:650002 FILESYS: Waiting for kernel to be ready to launch apps 4294775139 PID:400002 TID:600002 InitMUI: DISABLED (0) 4294775140 PID:400002 TID:650002 FS: HKLM\System\Events not available, no signal events created. 4294775140 PID:400002 TID:650002 FILESYS: Launching apps 4294775141 PID:400002 TID:650002 ERROR: C:\ymzki\private\winceos\COREOS \filesys\main\.\fsmain.c line 2563: 4294775141 PID:400002 TID:650002 Unable to locate init key for starting apps! 4294775142 PID:400002 TID:650002 FILESYS: Done launching apps 4294775219 PID:400002 TID:650002 This device has booted 0 times !!! And it gets stuck at this point. Please help me. I have tried a lot of things but nothing seems to work. Do i give "flags"=dword:1 at other places also...? And what is wrong with the settings i have kept?? Thanks in advance. Regards Aalok Sood Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97379
  - 10
    - ceqfecheck utility can anyone plz tell me from where can i get ceqfecheck utility Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97374
  - 11
    - reloading the driver after resume This is a multi-part message in MIME format. ------=_NextPart_000_0071_01C76013.45F18610 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Dear All, I suspend my device using = "SetSystemPowerState(NULL,POWER_STATE_SUSPEND,POWER_FORCE)) " After I Resume from the suspend mode the wireless does not work. What am I missing during startup do I need to reload the wireless = driver? How do I do this reloading? Thanks in Advance ------=_NextPart_000_0071_01C76013.45F18610 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.6000.16414" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY> <DIV><FONT face=3DArial size=3D2>Dear All,</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial><FONT size=3D2>I suspend my device using "<SPAN=20 style=3D"FONT-WEIGHT: bold; COLOR: rgb(51,102,255)"><FONT=20 color=3D#000000>SetSystemPowerState(NULL,POWER_STATE_SUSPEND,POWER_FORCE)= )=20 "</FONT></SPAN></FONT></FONT></DIV> <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20 style=3D"FONT-WEIGHT: bold; COLOR: = rgb(51,102,255)"></SPAN></FONT></FONT> </DIV> <DIV><FONT face=3DArial><FONT size=3D2><SPAN=20 style=3D"FONT-WEIGHT: bold; COLOR: rgb(51,102,255)"></SPAN>After I = Resume from the=20 suspend mode the wireless does not work.</FONT></FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>What am I missing during startup do I = need to=20 reload the wireless driver? How do I do this reloading?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thanks in Advance</FONT><FONT = face=3DArial=20 size=3D2></FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML> ------=_NextPart_000_0071_01C76013.45F18610-- Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97368
  - 12
    - Which JATG probe ? Hi all, I am going to start BSP development (Eboot+AOL) for an ARM926EJS SoC. So I would like to know which are the suggested JTAG probes for CE 5.0 and possibly CE 6.0. Any help will be highly appreciated, PaoloC Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97367
  - 13
    - Bluetooth stack wince 5 with virtual com port feature Hi, i want to use a bluetooth dongle (connected on USB) on a wince 5.0 platform with the Virtual ComPort feature. I use the Microsoft Stack included in PB5 but i have a speed limitation of the "classic" com port (128.000 baud). I need a stack that allows me to go beyond this limit. I have seen that broadcomm have one, but if possible i need something freeware. Can someone give me some information? Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97365
  - 14
    - code hangs after loading hd.dll Hi, Can anyone Please tell me which are all the dlls to be loaded in order to make sure that the kernel is up. Which dll must be loaded in order to get the shell. Please if possible could anybody give a sample debug log which would be of great help to find out which are all the dlls to be loaded. I am developing BSP for MC9328MXL board in WINCE5.0 and this is my debug log which I get on my platform builder after enaling KITL. Kernel debugger connected. The Kernel Debugger connection has been established (Target CPU is ARM). Target name: CE Device Probe name: KdStub Binary Image should be loaded at 0x80200000 / Data relocated at 0x820e6000 Loaded symbols for 'E:\WINCE500\PBWORKSPACES\UPANDRUN_25_02\RELDIR \MC9328MXL_ARM_ARMV4I_DEBUG\NK.EXE' Loaded symbols for 'E:\WINCE500\PBWORKSPACES\UPANDRUN_25_02\RELDIR \MC9328MXL_ARM_ARMV4I_DEBUG\KD.DLL' Loaded symbols for 'E:\WINCE500\PBWORKSPACES\UPANDRUN_25_02\RELDIR \MC9328MXL_ARM_ARMV4I_DEBUG\OSAXST1.DLL' Loaded symbols for 'E:\WINCE500\PBWORKSPACES\UPANDRUN_25_02\RELDIR \MC9328MXL_ARM_ARMV4I_DEBUG\OSAXST0.DLL' Loaded symbols for 'E:\WINCE500\PBWORKSPACES\UPANDRUN_25_02\RELDIR \MC9328MXL_ARM_ARMV4I_DEBUG\HD.DLL' and there is no further progress. I had a look at ce.bib and found the coredll.dll entry is there but I don't why it doesn't get loaded. I have no clue what might be reason. Has anybody faced such a problem. Please let me know. Please reply to chitra.r@globaledgesoft.com Thanks & Regards, Chitra Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97362
  - 15
    - Garbage Collection in the FAL of NAND Flash Driver Hi, I am interested to know that whether the Garbage collection is handled by the FAL in WinCE 5.0? About the Wear Leveling there are some sources which states that FAL handles the same. But for Garbage Collection there is no relevant information. Please guide if somebody is aware of whether FAL handles garbage collection or not? ST Microelectronics suggests one block driver named stnftl which is a replacement of FAL. This stnftl handles garbage collection through some Tranlation Module. But still it is not clear that FAL handles the same or not? Link for the same is given below. http://www.st.com/stonline/products/literature/an/12673.pdf Regards, Himangshu Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97361
  - 16
    - DDSCAPS_PALETTE supported? Does any one here know if DDSCAPS_PALETTE is supported under WinCE 6.0? The documentation for _DDSCAPS says that DDSCAPS_PALETTE is not supported, and yet some of the sample WinCE display drivers include that flag. Thanks Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97353
  - 17
    - Event signaled only once by kernel? Riddle me this, Batman. I have a kernel LIB that's simple. It takes in an event handle via an IOControl, then in another method it sets that event when a condition is met. Something like this: HANDLE hEvent; BOOL IOControl(...) { hEvent = *(HANDLE*)pDataIn; } void MyMethod() { while(true) { // check some stuff if(condition) { // I have a pointer to this method, so yes it is valid to call EventModify(hEvent, EVENT_SET); } } } Then in my app I create the event and wait on it, something like this: HANDLE hLib = LoadKernelLibrary(...); HANDLE hEvent = CreateEvent(...); KernelLibIoControl(hLib, hEvent ...); while(true) { if(WaitForSingleObject(hEvent, 5000) == WAIT_TIMEOUT) { // WTF? continue; } // do stuff } Now for the _first_ iteration, the event is set as normal and the app thread unblocks and does its job processing. After that first unblock however the WaitForSingleObject always times out. I've got DEBUGMSGs that show the kernel lib _is_ setting the event again, and the handle value is unchanged and matches that in the app. If I change the event to a manual reset event then the app spins as expected becasue the event is always set. If I manually reset it by calling ResetEvent in the app loop right after the wait I get the same bad behavior of unblocking once and then timing our forever after. I've even gone so far as to change to using a named event and passing the name to the kernel to ensure that it's not a "handle sharing" issue and the same behavior persists. Any thoughts on what might be happening? What could be prventing this event from going to a signaled state after that first Wait or Reset is called? -- Chris Tacke - Embedded MVP OpenNETCF Consulting Managed Code in the Embedded World www.opennetcf.com -- Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97349
  - 18
    - Adding a codepage Hi, I have to add eastern european language support to an existing WinCE 4.2 project which is based on a VIA chipset BSP, I specifically need to add Czech, so I need to add LCID 0405 and codepage 1250. I found these two MSDN references that discuss adding a codepage. http://msdn2.microsoft.com/en-us/library/ms930801.aspx and a locale http://msdn2.microsoft.com/en-us/library/ms923603.aspx Following those instructions, I added the 0405 to the file WINCE420\Public\Common\Oak\Files\Nlscfg.inf and I created a Nlscpg.txt file in the directory WINCE420\PUBLIC\MyProject\WINCE420\VIACEPC\oak\files. The Nlscpg.txt file has a single line with the codepage number, 1250 and CR & LF. When I build the platform, the build output doesn't have the additional LCID or codepage when the locale configuration is parsed. I tried it out anyway on my system and the .NET CF call to set the locale to 0405 throws a PlatformNotSupportedException, which indicates to me that the locale isn't there. Should I see the additional codepage and LCID in the build output? Did I put the Nlscpg.txt file in the right place? the MSDN page says: -quote- 1. Create the Nlscpg.txt file in the %_WINCEROOT%\Public\Project\WINCE420\Platform\Oak\Files directory. -end quote- I assume Platform really means in my case VIACEPC, or do I need to create a Platform\Oak\Files sub-directory and put it there? If I have it in the right place, do I have to add the codepage number somewhere else in addition? Am I missing anything else? Is adding the LCID in Nlscfg.inf and the codepage number in Nlscpg.txt all that is needed? Do I need to add a 0405 directory for the locale in WINCE420\PUBLIC\MyProject\WINCE420\VIACEPC\oak\files\INTLTRNS? I don't need to localize WinCE, the end user only sees my application. Thanks, Bruce Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97348
  - 19
    - Problem with AMD Rumba Design Reference Hi gurus, I am with geode plataform (AMD RUMBA Geode design reference) and I am with problem in image startup. I read all post in the group about memory crash, OEMAdressTable, Startup, pc.h, and others , because I am with this problem about 3 weeks My problem is: When I turn on the device, it startup normally, after that I turn off the device and wait 2 minutos when I turn on the device again it is not starting up. The debug information are: ================================================================= (when it startup) Connec EzBox WinCE Bootloader Versao 2.3 (Compilacao Feb 13 2007) ID do drive....: 0x80 Tamanho setor..: 0x200 Cabecas........: 0x10 Set. x Trilha..: 0x3F Tam. Cluster...: 0x1000 Numero de FATs.: 0x2 Setores por FAT: 0xBB Set. escondidos: 0x03F Set. reservados: 0x1 Largura........: 800 Altura.........: 600 Cores..........: 16 Largura Fisica.: 0 Altura Fisica..: 0 Porta Serial...: COM1 Baudrate.......: 3 IRQ Rede.......: 0x0 End Rede.......: 0x0 IP.............: 0.0.0.0 Imagem.........: nk.bin Imagem Backup..: rescue.bin Device Root....: CONNEC Zona de Debug..: 0x1 Flags do Loader: 0x1 Carregando nk.bin Jump para image em 0x2245E8) Debug Serial Init SysInit: GDTBase=823370e8 IDTBase=82358860 KData=82361800 Windows CE Kernel for i486 Built on Aug 8 2006 at 16:22:46 g_pPageDir = 82362000 X86Init done, OEMAddressTable = 80224608. ELOTOUCH DllMain attach Elo After read reg gbEnableCursor = 1: status 0 Ok Elo Unable to open serial port Elo Version 1.09, Build# 211 ELOTOUCH ELO_Init WAS successful ... ... ================================================================= (when it doesnot startup) Connec EzBox WinCE Bootloader Versao 2.3 (Compilacao Feb 13 2007) ID do drive....: 0x80 Tamanho setor..: 0x200 Cabecas........: 0x10 Set. x Trilha..: 0x3F Tam. Cluster...: 0x1000 Numero de FATs.: 0x2 Setores por FAT: 0xBB Set. escondidos: 0x03F Set. reservados: 0x1 Largura........: 800 Altura.........: 600 Cores..........: 16 Largura Fisica.: 0 Altura Fisica..: 0 Porta Serial...: COM1 Baudrate.......: 3 IRQ Rede.......: 0x0 End Rede.......: 0x0 IP.............: 0.0.0.0 Imagem.........: nk.bin Imagem Backup..: rescue.bin Device Root....: CONNEC Zona de Debug..: 0x1 Flags do Loader: 0x1 Carregando nk.bin Jump para image em 0x2245E8) Debug Serial Init SysInit: GDTBase=823370e8 IDTBase=82358860 KData=82361800 Windows CE Kernel for i486 Built on Aug 8 2006 at 16:22:46 g_pPageDir = 82362000 X86Init done, OEMAddressTable = 80224608. ================================================================= I configured the follows files: startup.asm (D:\WINCE500\PLATFORM\COMMON\src\x86\COMMON\STARTUP) OEMAddressTable ; RAM 0x80000000 -> 0x00000000, size 512M dd 80000000h, 0, 20000000h dd 0, 0, 0 config.bib ; 128 MB of RAM (note: AUTOSIZE will adjust boundary) NK 80220000 00C00000 RAMIMAGE RAM 80E20000 03000000 RAM pc.h (D:\WINCE500\PUBLIC\COMMON\OAK\CSP\X86\INC) #define CEPC_EXTRA_RAM_START 0x81C00000 // 28 MB is default top of RAM for auto-detect #define CEPC_EXTRA_RAM_SIZE 0x02400000 // Potentially add another 36 MB Anybody give me any advice ? Mauricio de Sousa Coelho Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97345
  - 20
    - problem with pci bus No i'm migrtaing the SG2_VR4131 to my vr4121 controller no i've adapted the OAL and the os (custom device with no options is runnng) the big differnce between my bsp and the vr4131 bsp is tahat i don't have a pcibus. now witch changes do i have to do like the is setting BSP_NOPCIBUS=1 an option but like in the platform .reg i see this code but if i delete it my platform doesn't ork anymore so i really want to know what changes that i have to make or maybe another solution to remove completely the pci settings ; HIVE BOOT SECTION #include "$(DRIVERS_DIR)\pcibus\pcibus.reg" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI] "NoConfig"=dword:0 "MemBase"=dword:10000000 "MemLen"=dword:06000000 "IoBase"=dword:00001000 "IoLen"=dword:01FFF000 "Latency"=dword:40 ; Set latency timer for all devices to 64 "SecondaryLatency"=dword:40 ; Dtto for secondary latence on bridges ; END HIVE BOOT SECTION Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97325
  - 21
    - Multi-ICE problem. Hi all, Currently i am working on ARM 922T core. My Multi ICE(version 1.2) is detecting ARM920T core. But it is unable to detect ARM922 core. Please let me know how to make it to work..? Whether i need to connect any separate power supply or is there any configuration file i need to configure. Thanks in advance Arun Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97324
  - 22
    - Webcam :-( Hi, I tried : http://www.gotdotnet.com/workspaces/messageboard/home.aspx?id=0eb87e35-13e4-4fa3-9fde-71e9136f47de It does not work for the cams I have. I cannot get the "old" quickcam 5000 pro, that does not seem to have a problem. What is a working combination of Webcam + driver for CE ? Greetings, Rob. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97319
  - 23
    - Platform builder packets data Hello, I have been developing a KITL for my device. Booting of my WinCE will stop after sending the first debug message into Platform Builder (PB). My device waits for debug packet (service: DBGMSG, flags: KITL_FL_ACK, cmd: KITL_CMD_SVC_DATA). But PB will not send it. Instead of it it sends config data for KDBG and retransmit command all over again. Does anybody know, where can I find, what PB needs and what it sends back? I mean the content of data transmited between a device PB. Thanks, George H. Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97318
  - 24
    - Device ActiveSync DIALOG Box - How to disable?? We developed a Windows CE 5.0 device that uses Activesync to connect to a host PC via USB. My problem is that we have a very specialized UI and DONT want the Activesync dialog (and the associated connection sound) to momentarily appear on the device UI at connection time. Is there a way to disable this (and the correspond sound)? Thanks Tag: Calling crypto APIs from OAL (OEMCertifyModule) in CE 5.0 Tag: 97315
  - 25
    - CE5.0 device as Router (wireless accespoint) Hi, What would be required to make a CE5.0 device with Wired & wireless network act as an accespoint