Help with PartitionTable

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - Help with PartitionTable Hello, I have an x86 WinCE50 system that uses the ATAPI IDE driver for a system CF card. Currently, I have the CF card partitioned into 2 parts: *Partition1 = Fat16 bootable partition with CEPC Nk.bin *Partition2 = TFAT formatted partition for WinCE use. I am currently trying to mount the partition 2 as root, but having no luck at all. I have tried the following approaches. 1) Use MountAsRoot and AutoMount keys for partitions to set which should mount as root, making sure to set part1 MountAsBootable=0. [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile \Part00\FATFS] "AutoMount"=dword:0 "MountAsRoot"=dword:0 "MountAsBootable"=dword:0 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile \Part01\FATFS] "AutoMount"=dword:1 "MountAsRoot"=dword:1 "MountAsBootable"=dword:1 Result: Partition 1 still mounts to root. This seemed to have no effect. Am I messing up the way I use the Profile? (HDProfile \Part00\FATFS)? 2) Use the 'cheating' method to set the PartitionTable key 0x04 to invalid FS. (suggested here: http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/e122bf548aab3c7c/c61f11d3a810184f and by others as well): [HKEY_LOCAL_MACHINE\System\StorageManager\PartitionTable] "04"="SYSBOOT" Result: Both partition 1 and 2 do not mount and the system halts after storage manager. To my understanding the first partition formatted in FAT16 is 0x04. However, shouldn't my TFAT partition be type x0B (MS-DOS 32 bit FAT)? Perhaps I am wrong in my assumptions of how the PartitionTable works. 3) Setting the "PartitionDriverName" to blank in an attempt to load null partition driver [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part00] "PartitionDriverName"="" [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part01] "PartitionDriverName"="MSPART" Result: Both partitions still loaded. Here is where I am at stuck. Can anyone offer advice or help? Thanks in advance -t Below are my current registry settings: [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile] "MountAsRom"=dword:0 "MountAsRoot"=dword:0 "MountAsBootable"=dword:0 "MountPermanent"=dword:0 "Flags"=dword:00080064 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\FATFS] "MountAsRom"=dword:0 "MountAsRoot"=dword:0 "MountAsBootable"=dword:0 "MountPermanent"=dword:0 "Flags"=dword:00080064 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part00] "AutoMount"=dword:0 "AutoFormat"=dword:0 "AutoPart"=dword:0 "DefaultFileSystem"="FATFS" ; "PartitionDriver"="mspart.dll" "PartitionDriver"="" "MountAsRom"=dword:0 "MountAsRoot"=dword:0 "MountAsBootable"=dword:0 "MountPermanent"=dword:0 "Flags"=dword:00080064 [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part01] "AutoMount"=dword:1 "AutoFormat"=dword:0 "AutoPart"=dword:0 "DefaultFileSystem"="FATFS" "PartitionDriver"="mspart.dll" "MountAsRom"=dword:1 "MountAsRoot"=dword:1 "MountAsBootable"=dword:1 "MountPermanent"=dword:0 "Flags"=dword:00080064 Tag: Help with PartitionTable Tag: 112289
  - 2
    - USB Wireless Network Adapters for WinCE? I am currently trying to added wireless support to an existing WinCE OS image. I have added the components to my OS image to support Wi-Fi in Platform builder. I need help trying to find a compatible USB wireless network device that works with WinCE 5.0. My current WinCE OS image is working with the RNDIS USB driver, and I have read the previous posts on the USR5421 Wireless MAXg USB Adapter that is RNDIS complient. The problem is that I don't won't to limit the my customer to using only one type of USB Wireless Network manufacture. Does anyone have a list of USB wireless network devices that is compatible with WinCE 5.0? Tag: Help with PartitionTable Tag: 112286
  - 3
    - running Microsoft Device Emulator from "Device Emulator Manager" I used PB 5.0 to build an emulator using Microsoft Device Emulator, then I built the SDK. Now I am trying to run it from "Device Emulator Manager" in Visual Studio, I can see it - but its more like a category - the devices I can click are sub items in the category "Pocket PC 2003" for example, but I cannot right click on it to connect. Please help, thanks patrick Tag: Help with PartitionTable Tag: 112283
  - 4
    - ndis miniport wakeup filter Hi everybody, is there any way to control the wakeup packet filter ? Currently my miniport receives a OID_PNP_ADD_WAKE_UP_PATTERN with a filter pattern. I don't know where it comes from; I presume from protocol driver. I would like to configure or explicity send my specific wakeup packet filter. Best regards, PaoloC Tag: Help with PartitionTable Tag: 112280
  - 5
    - CreateEvent and SetEvent in WinCE6.0 Hi, I am a newbie to Windows Embedded CE. Try to understand Embedded :) I have a wince 5.0 based Application which creates a unnamed event and sends an IOCTL to driver. Upon completion of requested IO, driver uses setevent on event handle passed by APP. The whole thing works fine on WinCE 5.0 Now I have this driver in wince6.0 for a different platform, when i run the APP (built using wince 5.0), i see exception "Abort data" in driver (setevent, driver built using wince 6.0) using unnamed events is not allowed in WinCE6.0? If so, is there a work around for this instead of using named events? Any information on this would be of great help --Thanks in advance Vikranth Tag: Help with PartitionTable Tag: 112272
  - 6
    - DDKReg_GetWindowInfo() returns ERROR_INVALID_PARAMETER Hi all, I have written a simple device driver that is loaded at boot time. The driver needs to read MemBase and MemLen from the registry when initialised. I use the pointer that I receive in XXX_Init( PVOID Context) to open the device key ( hnd = OpenDeviceKey( (LPCTSTR)Context ); ) and that seems to work. However, when I call DDKReg_GetWindowinfo() with the returned handle it returns ERROR_INVALID_PARAMETER. According to MSDN this "Indicates a problem with the populated DDKWINDOWINFO structure." What does this mean? My registry entry looks like this: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\GDU] "MemBase"=dword:40100000 "MemLen"=dword:40 "Prefix"="GDU" "Dll"="gdudev.dll" "Order"=dword:22 Any ideas are much appreciated. Thanks, Rickard Tag: Help with PartitionTable Tag: 112271
  - 7
    - Wi-Fi Authentication Test... hi! I was checking the wifi authentication test.(I am using WinCE 6.0) Here when i checked the Prerequisites for authentication tests, it requires. Tux.exe kato.dll Authmatrix.dll Enroll.exe Netall.dll Apcontrol.exe I am able to find every thing except Apcontrol.exe Can any one say where i can find this application. Thanks. Tag: Help with PartitionTable Tag: 112270
  - 8
    - Ethernet Throughput Too Slow for Wince 5.0 I am running wince 5.0 with an AMD AU1100 processor running at 396MHz. I am integrating a RTL8305SC ethernet switch within the hardware platform. I am currently getting around 16.5 Mbps throughput uploading a 40Meg file to a server, and 23.5Mbps downloading a file from a server. This seems extremely slow for WinCE 5.0. On the desktop I can get almost 80% of the 100MBps link speed. Is the ndis.dll driver at a low priority such that it is not able to buffer up packets and send them out faster than the current rate I am experiencing? How can I speed up the throughput? Tag: Help with PartitionTable Tag: 112250
  - 9
    - WLAN sample code Hi all, Is any WLAN Driver Sample code is available on net? or any body know from where i take reference for WLAN Driver. I am using Wireless CF card on WINCE 5.0. I required sample code for that. So please if any body know then help us. Thanks in advance Swapnil Tag: Help with PartitionTable Tag: 112244
  - 10
    - How to strip down image of headless device (no display)? Hi, I would like to get rid of many unneeded components for a headless device. However, I cannot uncheck many catalog items because the Platform Builder thinks it is needed. For example: how can I get rid of the Tahoma fonts? Is there any method for this or do I have to apply brute force such as modifying common.bib? Thank you, Peter Tag: Help with PartitionTable Tag: 112241
  - 11
    - ConnMgrRegisterForStatusChangeNotification - #include <connmgr_status.h> problem Hi all, I have subroject where I would like to use "ConnMgrRegisterForStatusChangeNotification" which is declared in connmgr_status.h (according to MSDN). Ther is no such file in WINCE600 folder structure. None of files contains declaration of "ConnMgrRegisterForStatusChangeNotification". I see that it is delay loaded from cellcore.dll (public\cellcore\simtkit\dllload.cpp). I have checked cellcore.dll (ARM emulator build) (using dependancy walker - depend.exe) but it does not export "ConnMgrRegisterForStatusChangeNotification" function. I have installed "Shared source, ARMV4I and X86" OS. Subproject build fails with error: Error 6 fatal error C1083: Cannot open include file: 'connmgr_status.h': No such file or directory. How to use it in WinCE 6? Zdenko Tag: Help with PartitionTable Tag: 112234
  - 12
    - SD card and File System in WinCE 5....? Hi all I am developing SD card driver (SD Host,SD Bus, SD Client), the SD Bus and SD Client Drivers are got from \PUBLIC\COMMON\OAK\DRIVERS\SDCARD\... Now ,I am facing a serial problem, and have no idea to solve it. The condition is: When system suspend and resume , we dont want unload and reload SD Cleint Driver,the reason is if the App is running and read/write data from/to SD card, we hope the App is keeping running, not broken by resume system.(Unload or reload will cause system to broadcast a device changed message, we dont want to get it) In SD host driver,my method is when system resume ,I call the function SDHCDIndicateSlotStateChange(m_pHCContext, 0, SlotResetRequest); And I do a test , that is "I do a file copy/paste by File Explore", but it always failed. I check the data of SD card, it is integrity and identical , nothing lose. And I do other test, that I execute a App(the App is a multimedia tool) to read/write data to SD. When reading/writing from/to SD card, I suspend and resume the system , the App is keeping playing. So I am confused, what happened to it? I really have no idea about it... Could some one help me? ... BRs Jack Tag: Help with PartitionTable Tag: 112231
  - 13
    - Emulator performances I am experiencing a big difference in performances between a Windows CE emulator image generated by me as part of an SDK and the emulator images provided with the Windows Mobile 6.0 SDK. To be more specific, the problem is related to the startup time of a .NET 2.0 application. The application loads many bitmaps at startup and has a startup time of around a minute in release and two or more minutes in debug on my emulator image. That startup time decreases a bit when I include in the image CF 3.5 instead of 2.0 (the application is still CF 2.0 based) bu it's still twice or more of the amount required to start the same application inside the WM6 emulator, provided with the Windows Mobile 6 SDK. The overral performances of the application inside the WM os image seem to be better than those on my own OS image, but the difference in startup times is quite noticeable. Both OS images use the same amount of memory inside the emulator (256MB) and the amount of free memory before the application is started is the same on both emulator instances and the application allocates the same amount of memory etc. Also the screen resolution is the same on both emulator istances (800x480). My OS image include the .NET framework dependencies, the standard shell and not much more. No services or other applications that may "eat" CPU time in background and no KITL or debugging support. I suppose that the WM6 image runs some more drivers in background (for phone emulation, at least) and that the WM shell is, at least, comparable to the standard shell in terms of CPU and memory usage. My OS image is based on CE 6, while the WM6 image is 5.something, but the new kernel should improve performances... and not having the limit of the 32MB slot may allow the .NET application to allocate more memory without requiring a garbage collector compacting operation, so I expect better performances on my OS image than on the WM6 emulator or, at least, the same level of performances... The application executable is installed in \Program Files so it's loaded from RAM on my OS image and does not access external data files etc. It loads some DLLs (most of them are .NET managed code and native code interaction is limited to some API calls). There are some "tweaks" that can be used to enhance device emulator performances? I used the device emulator BSP provide with CE 6 Platform Builder. There are other releases of that BSP available? Most of my customers still use CE 5, so I don't have a direct comparison of the same application running on the same device on the two OS releases. Someone else noticed big performance issues using the .NET framework on CE 6? -- Valter Minute www.fortechembeddedlabs.it Training, support and development for Windows CE (the reply address of this message is invalid) Tag: Help with PartitionTable Tag: 112229
  - 14
    - How to test parallel port in WINCE Dear sir, I use X86 architecture which has a parallel port to develop WINCE platform. Do anyone have idea to test parallel port ? BR, Wiles Tag: Help with PartitionTable Tag: 112215
  - 15
    - RTL 8139 is not working on Wince 5.0 Hello Pls help me if anybody using the rtl 8139 pci card on wince 5.0. Becoz i was tried last 3 weeks, my rtl 8139 card driver is not working. Pls give me the fixed solution . thank you. Tag: Help with PartitionTable Tag: 112206
  - 16
    - register dumping I'm a begginer to device driver. Now I'm trying to set a gpio register and check if it is set correctly. Following is my code. RETAILMSG(1, (TEXT("v_pIOPregs->GPBCON is %ud - %p\r\n", *(v_pIOPregs->GPBCON), v_pIOPregs->GPBCON))); v_pIOPregs->GPBCON = 0x155555; RETAILMSG(1, (TEXT("v_pIOPregs->GPBCON is %ud - %p\r\n", *(v_pIOPregs->GPBCON), v_pIOPregs->GPBCON))); But the result is not same as my expection. 14034 PID:34c9fc6 TID:34ad6ca v_pIOPregs->GPBCON is 2202309720d - 0 14034 PID:34c9fc6 TID:34ad6ca v_pIOPregs->GPBCON is 2202309720d - 60010 Although I set 0x155555 to GPBCON, the retailmsg printed 60010. What's wrong with my code? Please help me. Tag: Help with PartitionTable Tag: 112204
  - 17
    - How to add WZC? Hi all, I am using WINCE 5.0 i am working on wireless Prism2 WLAN driver. Normally when i downloaded image(nk.abf) on board and after that when i inserted Wireless Compact Flash Card it ask for "Enter Driver name" when i given "ISLP2NDS.DLL" name Then on Hyper Terminal it shows some msgs are comming and after some time it will stop in taht msg the driver islp2nds.dll is LOADED and after some seconds it is UNLOADED. I don't know due to why it is unloaded driver. I read some posts in that they written Adding WZC support is done by adding the Wireless LAN (802.11)... item from the catalog. All that will do, of course, is add support for it. The second piece is a wireless LAN adapter that supports WZC. CE 5 includes support for several: Cisco 350-series (PC Card), Intersil Prism2 (chipset, usually PC Card), RNDIS (USB). Is any body know how to add WZC in our BSP or in pbxml? and How it will work?? Thanks in advance Swapnil Tag: Help with PartitionTable Tag: 112199
  - 18
    - Does HyperTerminal support CE6 RDP serial port ? Is there anyone knows that whether HyperTerminal Applet, which is on Windows 2003 RDP server, support RDP serial port redirection application? I connect a RDP session with serial port redirection check box selected, and then open HyperTerminal Applet, set COM2( redirected from terminal device) 9600 bps, data bit:8, Parity:None, stop bits: 1, Flow control: None. Unfortunately, it couldn't work well, it had no response when sending or receiving data. Be surprising, the serial port communication works well with other serial communication tool for test. Could you explain why? Does HyperTerminal Applet not support CE6 RDP serial port ? Tag: Help with PartitionTable Tag: 112198
  - 19
    - CE6 R2: RDP Licenses problem. Excuse me, I found two RDP license problem in my CE6 R2 image: 1) After RDP client connected to RDP Server (Windows server 2003, and Windows Server 2008), I could not see the Licenses in "Terminal Server Client Licenses" list of control panel. I check the source code of licinfo.cpl, found that the function InitializeLicenseInfo() failed because it called LSInitCertutilLib() and failed. 2ï¿½ï¿½In RDP server, I opened "TS Licensing Manager", the issued Licenses list show the terminal device name is "Unkown". My terminal device has specified name, not "Unkown". Could you help me why they happened? How could I fix up? Tag: Help with PartitionTable Tag: 112195
  - 20
    - VS2008 PlugIn Hi, do you know if there will be a PB 6.0 Plugin for Visual Studio 2008? Regards -- Javier Grijalba www.contendosystems.com Embedded Systems J.Grijalba at Contendosystems dot com Tag: Help with PartitionTable Tag: 112194
  - 21
    - CE6 R2: How to restore RDP session password? Excuse me, my CE6 R2 image is Ram-Based, and includes RDP. I set the registry: [HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Terminal Services] "DisablePasswordSaving"=dword:0[HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows NT\Terminal Services] "DisablePasswordSaving"=dword:0 I check the "Save my password" check box when connecting to RDP server. the connection can remember the password and auto-logon next time without reboot. But the RDP session password couldn't be restored after reboot, and I have to retype the password again. By the way, I am sure that I saved the registry before reboot in my own way. The MSDN says that "This build variable, WBT_USEAUTOLOGON, was disabled by default to reduce security risk." So I tried set the WBT_USEAUTOLOGON, and then build and sysgen the image, but still could not restore the password after reboot. Could you give me some advice? Thank you very much. Tag: Help with PartitionTable Tag: 112192
  - 22
    - Dereferencing environment variables in PB5 Hello, In Platform Builder 5.0 you have a dialog "Platform Settings" where you can also define environment variables. I need to dereference an existing variable. That means I want to define something like TEMP_STORAGE that is defined by the value of the TEMP environment variable. If the TEMP variable is defined as "C:\tmp" the variable should be "C:\tmp\my_storage". You can define this in a batch file with "set TEMP_STORAGE=%TEMP%\my_storage". You can dereference the variable in make files and several Platform Build files in this way: "$(TEMP)\my_storage". But no approach works, neither in Platform Builder GUI nor when opening the command line build window. The existing variable value is never used. How can I use the value of an environment variable to define a new one inside Platform Builder? Best regards, Helge -- Time is an ocean but it ends at the shore. Tag: Help with PartitionTable Tag: 112191
  - 23
    - ril suspend / resume Hi, I am using the ril driver from the public root, and using wavecom modem... The RIL hang the system on resume.... Any ideas? Best regards, J -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200805/1 Tag: Help with PartitionTable Tag: 112189
  - 24
    - IoBase conflict in seiral port Hi, I test WinCE5.0 at x86 platform. One strange thing in serial port confused me. Per my past experience , serial driver get IoBase address according to the IoBase value in platform.reg. [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial2] "SysIntr"=dword:14 "IoBase"=dword:02F8 But, when I adjust IO address of COM2 to 3F8h (another value) in BIOS setup, COM2 still can work. Right now, the IoBase in BIOS setup conflicts with IoBase value in platform.reg. I didn't modify platform.reg. Why serial port can work well ? thanks Rick Tag: Help with PartitionTable Tag: 112187
  - 25
    - Query on Windows CE Video Renderer related to MaxBackBuffers! Hi All, We developed a hw assisted decode filter which gets connected with the video renderer. We have enabled DirectDraw support in the display driver. We have accelerated blitting for the RGB offscreen surfaces allocated by the display driver. When video renderer uses DirectDraw RGB offscreen surfaces, it is just creating a single surface. Setting the MaxBackBuffers registry does not seem to have any effect on the number of RGB offscreen surfaces created by it. Does Video Renderer use MaxBackBuffers setting at all when it is working in DDraw mode? If not, is there any way to increase the number of RGB offscreen surfaces created for video render so that decoder thread does not get blocked in m_pAllocator->GetBuffer? Regards Tag: Help with PartitionTable Tag: 112182
- Next
  - 1
    - internal serial ports on CE4.2 vs CE5.0 I have a PC-104 RF transceiver plug-in module that requires a normal serial port configuration in order to communicate. I had been using the following serial port setup in my platform.reg for CE4.2: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5] "SysIntr"=dword:1e "IoBase"=dword:0300 "IoLen"=dword:8 "DeviceArrayIndex"=dword:4 "Prefix"="COM" "Dll"="Com16550.Dll" "Order"=dword:0 "Index"=dword:5 [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5\Unimodem] "Tsp"="Unimodem.dll" "DeviceType"=dword:0 "FriendlyName"="RF_PORT 5" ;19,200 baud "DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 00,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00 This worked fine in CE4.2, but I can't get the same trick to work in CE 5.0. It appears that, by enabling interrupts to the CE5.0 port, I can transmit, but I cannot receive any information back. Below is the code for the CE5.0 serial ports, COM3 and COM4. COM 3 is a serial port provided on the VersaLogic Python board, I can communicate with a hyperterminal connection fine. COM 4 then is my attempt to construct a serial port for my RF plug-in device: ; COM3 [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial3] "Index"=dword:3 "SysIntr"=dword:13 "IoBase"=dword:03E8 "IoLen"=dword:8 "DeviceArrayIndex"=dword:2 "Prefix"="COM" "IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}" "Dll"="Com16550.Dll" "Order"=dword:0 ; Turn on follows for Installable ISR (isr16550 supporting SOFTWARE FIFO) "Irq"=dword:3 "IsrDll"="isr16550.dll" "IsrHandler"="ISRHandler" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial3\Unimodem] "Tsp"="Unimodem.dll" "DeviceType"=dword:0 "FriendlyName"="COM3:" ; byte 9 = 0 for NONE, 10 for HDW handshake. Bytes 13-16 control baudrate (reverse order, i.e. 00004b00 = 19.2kb) "DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 00,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00 ; COM4 [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial4] "Index"=dword:4 "SysIntr"=dword:1a "IoBase"=dword:0300 "IoLen"=dword:8 "DeviceArrayIndex"=dword:3 "Prefix"="COM" "IClass"="{CC5195AC-BA49-48a0-BE17-DF6D1B0173DD}" "Dll"="Com16550.Dll" "Order"=dword:0 "Priority"=dword:0 ; Turn on follows for Installable ISR (isr16550 supporting SOFTWARE FIFO) "Irq"=dword:a "IsrDll"="isr16550.dll" "IsrHandler"="ISRHandler" [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial4\Unimodem] "Tsp"="Unimodem.dll" "DeviceType"=dword:0 "FriendlyName"="RF_PORT_4:" "DevConfig"=hex: 10,00, 00,00, 05,00,00,00, 00,01,00,00, 00,4B,00,00, 00,00, 08, 00, 00, 00,00,00,00 I tried with and without interrupts, with and without the "IClass" statement (what is this?), but nothing has worked. Any ideas or assistance would be greatly appreciated. Thanks, Pat Harris Tag: Help with PartitionTable Tag: 112179
  - 2
    - Mouse pointer in Windows Ce 5.0 Hello, is there a option in Windows Ce 5.0 to change the mouse pointer for the whole system? There has to be a bitmap somewhere, that can be changed before building my run-time-image!?! Any suggestions? Thanks for help. Tag: Help with PartitionTable Tag: 112177
  - 3
    - new vs. LocaAlloc when determining heap memory size Hi, Using the ToolHelp functions and the Remote Performance Monitor I've been trying to determine the Heap memory size in my application. This does not seem to work when using 'new' to allocate memory from the heap, however when using 'LocalAlloc' I can monitor the changes. What is the difference in using new or LocalAlloc when it comes to the functions described above? In which way can I monitor the heap memory if I use the 'new' operator? Many thanks! // Nicklas Tag: Help with PartitionTable Tag: 112175
  - 4
    - problem booting a hive based registry Hi all I'm trying to startup a hive based registry on a customer board. I have set everything (i suppose) in common.reg and platform.reg as below ******************************* common.reg: ******************************* ; HIVE BOOT SECTION [HKEY_LOCAL_MACHINE\init\BootVars] "SystemHive"="system.hv" ; "ProfileDir"="Documents and Settings" "Flags"=dword:1 "Start DevMgr"=dword:1 ; END HIVE BOOT SECTION *********************************** platform.reg *********************************** IF BSP_NAND_FMD ; HIVE BOOT SECTION ; ; Use Device Manager to load the NAND FMD driver as a built-in block driver. ; This can be used for both WinCE and Windows Mobile builds. ; ; Note: We support Windows Mobile Image Update build for SmartPhone, ; and the registry settings below get conflicts with the ones needed by Image Update. ; So we will overwrite them and setup Storage Manager Autoload keys in SmartPhone section ; to load NAND FMD driver as persistent storage during the early boot phases. ; [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\NANDFMD] "Dll"="nandfmd.dll" "Prefix"="DSK" "Profile"="FlashDisk" "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "FriendlyName"="Freescale NAND Flash Driver" "Order"=dword:1 IF IMGTPC "MemBase"=dword:80000000 "MemLen"=dword:8000000 ; 128 MB of NAND flash on MX31 ADS. "ReservedBlocks"=dword:1 ; Reserve 1 512 kB block for compaction. "CompactionPrio256"=dword:ff "CompactionCritPrio256"=dword:ffffffff ENDIF ; IMGTPC ; Override names in default profile. These settings are also required to ; support the automatic mounting and creation of the "NAND Flash" folder. ; [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk] "DriverPath"="Drivers\\BuiltIn\\NANDFMD" "Name"="NAND FLASH" "Folder"="NAND Flash" "DefaultFileSystem"="FATFS" #if (defined BSP_SMARTPHONE || defined BSP_POCKETPC) "PartitionDriver"="" ; Explicitly specify the use of the TFAT filesystem for NAND flash. ; [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\FlashDisk\FATFS] "Flags"=dword:00000014 "FormatTfat"=dword:1 ; Format partitions to be TFAT "MountAsRom"=dword:0 "MountAsHidden"=dword:0 "MountAsBootable"=dword:1 #endif ; BSP_SMARTPHONE || BSP_POCKETPC ; END HIVE BOOT SECTION ENDIF ; BSP_NAND_FMD Then booting the board I get the following messages ************************************* Debug boot loog ************************************* Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\NK.EXE' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\KD.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\OSAXST1.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\OSAXST0.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\HD.DLL' 4294767306 PID:ffdf002 TID:ffdf266 0x8ffdf024: first = 01ce0000, last = 02000000, SharedDllBase = 02100000 4294767327 PID:ffdf002 TID:ffdf266 0x8ffdf024: >>> Loading module coredll.dll at address 0x03F00000-0x03FF2000 (RW data at 0x01FFE000-0x01FFF7A5) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\COREDLL.DLL' 4294767344 PID:ffc4596 TID:ffc4572 0x8ffc4330: >>> Loading module coredll.dll at address 0x03F00000-0x03FF2000 (RW data at 0x01FFE000-0x01FFF7A5) 4294767346 PID:ffc4596 TID:ffc4572 0x8ffc4330: >>> Loading module filesys.exe at address 0x04010000-0x040A5000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\FILESYS.EXE' 4294767349 PID:ffc4596 TID:ffc4572 0x8ffc4330: CertMod.dll not found, using old OEM Trust Model 4294767357 PID:ffc4596 TID:ffc4572 0x8ffc4330: FileSystem Starting - starting with clean file system 4294767360 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: initializing ROM/RAM file system 4294767360 PID:ffc4596 TID:ffc4572 0x8ffc4330: SC_CreateAPIHandle: pvData == NULL 4294767360 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Registering file system ROM, index 2, flags 0x00000031 4294767360 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Mount complete (ROM, index 2, flags 0x00000031) 4294767363 PID:ffc4596 TID:ffc4572 0x8ffc4330: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 4294767365 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSVOL: Opening existing volume 4294767367 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSVOL: Volume heap already initialized 4294767367 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSREG: Mounted ROM portion of boot registry 4294767367 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSVOL: Creating clean virtual volume 4294767367 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSVOL: Initializing volume heap 4294767376 PID:ffc4596 TID:ffc4572 0x8ffc4330: FSREG: Mounted RAM portion of boot registry 4294767379 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Creating signal event SYSTEM/DevMgrApiSetReady 4294767380 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Creating signal event SYSTEM/PowerManagerReady 4294767380 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Creating signal event SYSTEM/GweApiSetReady 4294767380 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Creating signal event ReleaseFSD 4294767380 PID:ffc4596 TID:ffc4572 0x8ffc4330: FILESYS: Starting storage manager. 4294767387 PID:ffc4596 TID:ffc4572 0x8ffc4330: >>> Loading module fsdmgr.dll at address 0x03C10000-0x03C3E000 (RW data at 0x01FD3000-0x01FD3808) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\FSDMGR.DLL' 4294767389 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Registering file system StoreMgr, index 3, flags 0x00000001 4294767390 PID:ffc4596 TID:ffc4572 0x8ffc4330: InitSharedHeap: 48200000 10000 c 4294767390 PID:ffc4596 TID:ffc4572 0x8ffc4330: InitSharedHeap: return 48200060 4294767391 PID:ffc4596 TID:ffc4572 0x8ffc4330: FILESYS: Restarting storage manager. 4294767396 PID:ffc4596 TID:ffc4572 0x8ffc4330: >>> Loading module relfsd.dll at address 0x03DF0000-0x03DFB000 (RW data at 0x01FEB000-0x01FEBADC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\RELFSD.DLL' 4294767401 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Registering file system Release, index 4, flags 0x00000000 4294767401 PID:ffc4596 TID:ffc4572 0x8ffc4330: Mounted ReleaseFSD volume '\Release' 4294767410 PID:ffc4596 TID:ffc4572 0x8ffc4330: size of 'dbglist.txt' = 00000000 4294767411 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Mount complete (Release, index 4, flags 0x00000000) 4294767411 PID:ffc4596 TID:ffc4572 0x8ffc4330: FILESYS: Starting device and waiting for boot file system. 4294767417 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module coredll.dll at address 0x03F00000-0x03FF2000 (RW data at 0x01FFE000-0x01FFF7A5) 4294767428 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module pm.dll at address 0x03E90000-0x03EB3000 (RW data at 0x01FF6000-0x01FF6708) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\PM.DLL' 4294767430 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module devmgr.dll at address 0x03EE0000-0x03EF9000 (RW data at 0x01FFC000-0x01FFC6B4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\DEVMGR.DLL' 4294767432 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module device.exe at address 0x06010000-0x06014000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\DEVICE.EXE' 4294767436 PID:2ff85dca TID:2ff85da6 0x8ff85b64: InitSharedHeap: 48200000 0 c 4294767436 PID:2ff85dca TID:2ff85da6 0x8ff85b64: InitSharedHeap: return 48200060 4294767437 PID:ffc4596 TID:ffc4572 0x8ffc4330: FS: Waiting for device to signal BootPhase1 completion 4294767441 PID:2ff85dca TID:2ff85da6 0x8ff85b64: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x2ff85dca *** 4294767441 PID:2ff85dca TID:2ff85da6 0x8ff85b64: +InitDeviceFileSystems 4294767441 PID:ffc4596 TID:2ff85da6 0x8ff85b64: FS: Registering file system $device, index 5, flags 0x00000001 4294767441 PID:ffc4596 TID:2ff85da6 0x8ff85b64: FS: Registering file system $bus, index 6, flags 0x00000001 4294767441 PID:2ff85dca TID:2ff85da6 0x8ff85b64: -InitDeviceFileSystems: status is 1 4294767441 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module ceddk.dll at address 0x03B50000-0x03B59000 (RW data at 0x01FC7000-0x01FC70C4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\CEDDK.DLL' 4294767443 PID:2ff85dca TID:2ff85da6 0x8ff85b64: Ceddk!CalibrateStallCounter: Enter 4294767444 PID:2ff85dca TID:2ff85da6 0x8ff85b64: Ceddk!CalibrateStallCounter: Could not find stall counter 4294767444 PID:2ff85dca TID:2ff85da6 0x8ff85b64: Ceddk!BeginCalibration: min(16626) max(18473) 4294767463 PID:2ff85dca TID:2ff85da6 0x8ff85b64: Ceddk!BeginCalibration: Elapsed is 18433 4294767463 PID:2ff85dca TID:2ff85da6 0x8ff85b64: Ceddk!BeginCalibration: Delay is 27 4294767476 PID:2ff85dca TID:2ff85da6 0x8ff85b64: DEVICE!DevloadInit 4294767476 PID:2ff85dca TID:2ff85da6 0x8ff85b64: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 4294767476 PID:2ff85dca TID:2ff85da6 0x8ff85b64: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 4294767477 PID:2ff85dca TID:2ff85da6 0x8ff85b64: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 4294767483 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module busenum.dll at address 0x03EC0000-0x03ECA000 (RW data at 0x01FF8000-0x01FF851C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\BUSENUM.DLL' 4294767489 PID:2ff85dca TID:2ff85da6 0x8ff85b64: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NANDFMD\BusPrefix) returned 2 4294767489 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module cspddk.dll at address 0x02150000-0x0215D000 (RW data at 0x01E80000-0x01E800B0) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\CSPDDK.DLL' 4294767490 PID:2ff85dca TID:2ff85da6 0x8ff85b64: >>> Loading module nandfmd.dll at address 0x01DA0000-0x01DB4000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\NANDFMD.DLL' 4294767495 PID:2ff85dca TID:2ff85da6 0x8ff85b64: FLASHDRV.DLL:BuildupMappingInfo() - Enter. 4294767496 PID:2ff85dca TID:2ff85da6 0x8ff85b64: FLASHDRV.DLL:L2P_GetPhysicalSectorAddr() - Secondary table doesn't exist for logical sector 0x0!!! 4294767665 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: >>> Loading module mspart.dll at address 0x03C00000-0x03C0E000 (RW data at 0x01FD1000-0x01FD14AC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\MSPART.DLL' 4294767667 PID:ffc4596 TID:ffc4572 0x8ffc4330: FILESYS: Starting device and waiting for boot file system. 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: Loading partition driver mspart.dll hModule=8FF178C8 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: Driver mspart.dll loaded 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: Opened the store hStore=000C4DB0 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: NumSec=32704 BytesPerSec=512 FreeSec=0 BiggestCreatable=0 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: Partition Part00 NumSectors=32702 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: MSPART!PD_OpenPartition: dwStoreId=000C4DB0, PartName=Part00 4294767683 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: >>> Loading module fatfsd.dll at address 0x03E30000-0x03E63000 (RW data at 0x01FF2000-0x01FF265C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\FATFSD.DLL' 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FSD_MountDisk: mounting volumes for hDsk=000C6490 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: access time updates disabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: event logging enabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: automatic scanning disabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: write verify disabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: extra FAT on format disabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: force write through enabled 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: Codepage = 1 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!OpenVolume: Number of path cache entries = 50 4294767689 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: >>> Loading module diskcache.dll at address 0x03E20000-0x03E29000 (RW data at 0x01FF0000-0x01FF04F4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\DITRONECASHER\RELDIR\DITRON_TROUBLE_DEBUG\DISKCACHE.DLL' 4294767717 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: CreateCache: Successful. Cache Size: 16 KB, Start: 1, End: 32. 4294767717 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: CreateCache: Successful. Cache Size: 32 KB, Start: 33, End: 32701. 4294767728 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!InitVolume: FAT version: 16 4294767728 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!InitVolume: Cluster Size (Sectors): 4 4294767729 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FATFS!InitVolume: TFAT enabled: FALSE 4294767730 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FS: Registering file system NAND Flash, index 7, flags 0x00000000 4294767730 PID:ffc4596 TID:4ff8afce 0x8ffc76ac: FS: Mount complete (NAND Flash, index 7, flags 0x00000000) The persistent storage media is a NAND that works fine. The mount process seems to be closed but then the FileSys hangs up and never goes on. Please help me to understand better. Any help will be appreciated fabio antonini kasko networks Tag: Help with PartitionTable Tag: 112173
  - 5
    - Problem in WinCE 6.0 USB Composite Driver I am Porting USB Composite Driver in WinCE 6.0, I am using Two Composite Client Device(Composite Driver Child Device) 1. USB_Serial Client and 2. Mass_Storage_Device Client I can able to get the Mass_Storage_Device, but I am facing problem while using Activesync, when i Connect the USB Client Cable of the WinCE Device to My PC, initially it is detecting the ActiveSync after 10 seconds it is automattically getting disconnected with Error Message AUTORAS:: Dialer notifies: [2] [Dialer Terminate] Endpoint Zero FAILED SETUP udccsr=0x90. Sent STALL But i can able to get both working when i do like this: 1.Disabled ActiveSync in PC. 2.Connected the USB Client Cable of Win CE Device to PC. 3.After the Mass storage Device mounted ,i have enabled the ActiveSync in PC. In this case i am able to get both working, but Why it is(Activesync) getting Terminated, when both(mass storage & Acitvesync) are working simultaneously? Please help me in solving the issue. Thanks in advance. Tag: Help with PartitionTable Tag: 112170
  - 6
    - Unable to dismount Hi, I am running an x86 CEPC (5.0) with PCI IDE drives configured as follows: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\GenericIDE\Device0] "Prefix"="DSK" "Dll"="ATAPI.dll" "Settings"=dword:f "DefaultDMAMode"=dword:0 "DeviceId"=dword:0 "Ioctl"=dword:4 "DoubleBufferSize"=dword:10000 "Protection" = dword:0 "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" ; Uncomment the following lines if you want to enable slave device. [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\GenericIDE\Device1] ... [HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile] "Name"="IDE Hard Disk Drive" "Folder"="Hard Disk" Using standard FATFS file system. I am able to see the drives in storage manager and on my system in CE, but I cannot dismount the volume/partition. The error message I see via CTLPNL storage manager is "Unable to dismount store", and the body of the error dialog is empty. Running a debug build doesn't appear to give me any useful info either. Any ideas or help is appreciated -t Tag: Help with PartitionTable Tag: 112168
  - 7
    - WinCE 6.0 link failure Hi all, After doing a fresh install of VS 2005 w/ PB 6.0 and after carefully doing all updates in the order listed on the March 2008 update page, I get this error when building a new OSDesign... ------------------------------------------- TARGETNAME: fsdmgr makefile.def: Including C:\WINCE600\public\common\oak\misc\sources.ReleaseType_OAK BUILD_MARKER:LINK_DLL_START Linking C:\WINCE600\OSDesigns\Test9261OSDesign\Test9261OSDesign\Wince600\9261TestBSP_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fsdmgr.lib link -lib -out:C:\WINCE600\OSDesigns\Test9261OSDesign\Test9261OSDesign\Wince600\9261TestBSP_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fsdmgr.lib -def:C:\WINCE600\OSDesigns\Test9261OSDesign\Test9261OSDesign\Wince600\9261TestBSP_ARMV4I\cesysgen\oak\lib\ARMV4I\retail\fsdmgr.def -machine:thumb @C:\DOCUME~1\mmoreno\LOCALS~1\Temp\nm1090.tmp The system cannot execute the specified program. NMAKE : fatal error U1077: 'link' : return code '0x1' Stop. NMAKE : fatal error U1077: 'C:\WINCE600\sdk\bin\i386\nmake.exe' : return code '0x2' Stop. NMAKE : fatal error U1077: 'C:\WINCE600\sdk\bin\i386\nmake.exe' : return code '0x2' Stop. ------------------------------------------- Can anyone tell me what may be causing this? Thanks, Marco Tag: Help with PartitionTable Tag: 112158
  - 8
    - Build error after QFE's Jan/Feb/march 2008 C:\WINCE600\PUBLIC\COMMON\CESYSGEN>NMAKE /nologo C:\WINCE600\PUBLIC\COMMON\OAK\LIB\ARMV4I\RETAIL\0409\wldap32.res 1>nul Copying fulllibc.* NMAKE : fatal error U1077: 'xcopy' : return code '0xc0000005' Stop. Looks familiar ? anyone ? Greetings, Rob. Tag: Help with PartitionTable Tag: 112154
  - 9
    - KDBG hangs Hi everybody I'm still working on my ARM platform trying to bring up the debugger. I'm using a serial port connection for KITL with an interrupt based mecanism. If I disable the debugger, I am able to connect the platform and run remote tools and programs. When I enable the debugger in the build option, the system begin to boot and hangs during debugger initialization. I noticed that in the kdstub source code, the interrupts are disabled during KdSend and KdRecv calls. To avoid this first problem, I force the interrupts to be enabled each time I write a frame in the KITL driver. But even after doing this, the debugger hangs after having displayed this in the VS window : PB Debugger The Kernel Debugger connection has been established (Target CPU is ARM). PB Debugger Target name: Board PB Debugger Probe name: KdStub PB Debugger Binary Image should be loaded at 0x80000000 / Data relocated at 0x803a6000 In the debug serial port I can read : >>KITLSend KDBG Seq:44(0x0000002C), Flags:0x00000001 (DEV ), DataLen: 43 <<KITLRecv KDBG Seq:44(0x0000002C), Flags:0x00000004 (ACK ), DataLen: 0 --KdSend: 1 --KdpSendPacket <<KITLRecv ADMIN RETRANSMIT , DataLen: 0 <<KITLRecv ADMIN RETRANSMIT , DataLen: 0 .... The last message is then displayed indefinetly. Someone has an idea about this issue's source ? Tag: Help with PartitionTable Tag: 112151
  - 10
    - Create partition at Run Time Hello to all, I am working in winCE 5.0. The BSP is SMDK2440. I want to create partition at run time By the API CreatePartition() function.Can any body tell me that what will be the entry point to call the CreatePartation() function, if there is no already partition exists. Thanx -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200805/1 Tag: Help with PartitionTable Tag: 112148
  - 11
    - Create partition at Run Time Hi to all, I am working in winCE 5.0. The BSP that i am using is "SMDK2440". i have created a partition of 23MB in the NAND -Flash. This is created before the image is burned/downloaded. and after partition creation the image is downloaded to the Nand flash. Now i want to create partition at run time. is there any way to do this? can any body tell me the steps to through which i can accomplish my work. Any help will be appreciated..............Thanks -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200805/1 Tag: Help with PartitionTable Tag: 112142
  - 12
    - setFPEmul() missing Hi, I have migrated our project from CE5.0 to CE6.0 on a ICOP PC104 platform. In 5.0 there was a problem in the init part of the private kernel code that cuased the kernel to essentially crash if power was cycled too quickly on the device. We had a fix for it in the private code. I migrated that change to 6.0 and rebulilt the kernel in %WINCEROOT%\PRIVATE\WINCEOS\COREOS\NK\KERNEL. It built fine but now system build failed due to missing setFPEmul function. I noticed that this was a fairly recent addition in a QFE. Is the private source code out of sync with the provided binaries or? /Daniel Tag: Help with PartitionTable Tag: 112137
  - 13
    - Help WIn CE 4.20 Building error I using WinCE 4.20 for CEPC. Os building is ok. But when I try to build USB driver, Then I meet a link error: Linking... Creating library CEPC__X86Dbg/USBTest.lib and object CEPC__X86Dbg/USBTest.exp USBTest.obj : error LNK2019: unresolved external symbol _RegisterClientSettings referenced in function _USBInstallDriver USBTest.obj : error LNK2019: unresolved external symbol _GetSetKeyValues referenced in function _USBInstallDriver AesIo.obj : error LNK2001: unresolved external symbol _GetSetKeyValues USBTest.obj : error LNK2019: unresolved external symbol _RegisterClientDriverID referenced in function _USBInstallDriver AesIo.obj : error LNK2019: unresolved external symbol _IssueBulkTransfer referenced in function "unsigned long __cdecl ReadUsb(struct _USBFPS_CONTEXT *,unsigned char *,unsigned long,unsigned long)" (?ReadUsb@@YAKPAU_USBFPS_CONTEXT@@PAEKK@Z) AesIo.obj : error LNK2019: unresolved external symbol _DefaultTransferComplete referenced in function "unsigned long __cdecl ReadUsb(struct _USBFPS_CONTEXT *,unsigned char *,unsigned long,unsigned long)" (?ReadUsb@@YAKPAU_USBFPS_CONTEXT@@PAEKK@Z) CEPC__X86Dbg/USBTest.dll : fatal error LNK1120: 5 unresolved externals Error PB2505: Error executing link.exe. USBTest.dll - 8 error(s), 0 warning(s) These APIs seem in usbd.lib. I tried set usbd.lib in lib directory, but no help. Thanks for any suggestion! Tony Tag: Help with PartitionTable Tag: 112134
  - 14
    - about ICS registry setting.. Hi? I'm constructing a NAT (Network address translation) equipment using ce 5.0. From help document, port mapping is possible by adding corresponding informaion to HKEY_LOCAL_MACHINE/COMM/ConnectionSharing/Servers/Services entry. The entry has 5 types like following, InternalName : IP address of lan side InternalPort : port number from wan side IsEnabled Port : port number of lan side Protocol : Tcp or udp. Using the above registry keys I can register "one" port mapping entry. But how should I do if I need to add multiple entries like following. wan side port number 80 --> lan side 192.168.1.100 's 8080 port wan side port number 21 --> lan side 192.168.1.101's 21 port ... Tag: Help with PartitionTable Tag: 112119
  - 15
    - catlog items in CE6.0 Hi all, I am using VS 2005 with CE 6.0 i don't know how to add previously catalog item into our BSP? IS anybody know? Thanks in advance NIL Tag: Help with PartitionTable Tag: 112108
  - 16
    - Error:Image is too large for current RAM and RAMIMAGE settings Hi; i'm here again with this problem. Windows Embedded CE 6.0 and Visual Studio 2005 using.. Warning: Unable to do imports from ppp.dll to RSAENH.dll - will late bind Warning: Unable to do imports from ppp.dll to ntlmssp.dll - will late bind Warning: Unable to do imports from schannel.dll to RSAENH.dll - will late bind Warning: Unable to do imports from k.schannel.dll to RSAENH.dll - will late bind Warning: Unable to do imports from ipsec.dll to RSAENH.dll - will late bind Warning: Unable to do imports from ipsecsvc.dll to RSAENH.dll - will late bind Warning: Unable to do imports from eapol.dll to RSAENH.dll - will late bind Warning: Unable to do imports from eapchap.dll to RSAENH.dll - will late bind Warning: Unable to do imports from crypt32.dll to RSAENH.dll - will late bind Warning: Unable to do imports from k.crypt32.dll to RSAENH.dll - will late bind Warning: Unable to do imports from cryptdll.dll to RSAENH.dll - will late bind Warning: Unable to do imports from k.cryptdll.dll to RSAENH.dll - will late bind Warning: Unable to do imports from credssp.dll to RSAENH.dll - will late bind Warning: Unable to do imports from k.credssp.dll to RSAENH.dll - will late bind Warning: Unable to do imports from k.oleaut32.dll to k.ole32 - will late bind Warning: Unable to do imports from mstscax.dll to CREDUI.dll - will late bind Warning: Unable to do imports from cetsc.exe to CREDUI.dll - will late bind Pass 2... RAM AutoSize: RAM Start=83811000 RAM Size=fe3ef000 Error: Image is too large for current RAM and RAMIMAGE settings The default end address of RAM was exceeded. You may try setting the environment variable IMGRAM64=1 (or equivalent) if supported for this platform. Fatal error hit, exiting... makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). makeimg: FATAL ERROR: Command returned non-zero exit code 1 (dec). BLDDEMO: VegaCE build complete. VegaCE - 4 error(s), 21 warning(s) ========== Build: 0 succeeded or up-to-date, 1 failed, 0 skipped ========== C:\WINCE600\PLATFORM\VIAMARK\CESYSGEN\files\config.bib how to repair config.bib ?? No speak English...Sorry :( Please Help me!! Tag: Help with PartitionTable Tag: 112105
  - 17
    - Missing ufnmdd.lib from WINCE 6.0 Hi all, I am using Visual studio 2005 in WINCE 6.0 i can't found ufnmdd.lib file.This file is created in CE 5.0 but not created in CE 6.0. Is any body know what is the problem?? Thanks in advance Nil Tag: Help with PartitionTable Tag: 112103
  - 18
    - Platform Builder conflict error Hi Visual Studio 2005 / CE 6.0 R2 I get the following error when I try to build an image for x86 with no emulation. Error 1 Catalog Id "StringTable:MS:Deviceemulator:1041" duplicated in files "C:\WINCE600\platform\ARMSDK\catalog \1041\deviceemulatorstrings.pbcxml" and "C:\WINCE600\platform \DEVICEEMULATOR\catalog\1041\deviceemulatorstrings.pbcxml" with equivalent version numbers. Ignoring second record (file "C: \WINCE600\platform\DEVICEEMULATOR\catalog \1041\deviceemulatorstrings.pbcxml"). C:\WINCE600\platform \DEVICEEMULATOR\catalog\1041\deviceemulatorstrings.pbcxml 0 Can anybody explain what the heel this means. Thanks in advance Stewart Tag: Help with PartitionTable Tag: 112102
  - 19
    - Bluetooth crashes Hi, I am integrating WT11 Bluetooth module to our CE 4.2 device. Currently we support only 2 profiles OBEX Inbox and FTP. As a base for our FTP server we use OBEXFILE & OBEXINBX examples from the PB. I have random stack crashes with a single connection. But what I noticed that when I transfer file from PC to PDA (our CE 4.2 device), and at the same time try to send a file to PDA from my Bluetooth capable cell phone, stack immediately crashes. Well, I am not terribly experienced with Bluetooth world, but I assume I can have more than one concurrent connection at the same time with the MS CE stack. If not, how I can limit it to one connection, so the others are rejected to preserve current file transfer. Any thoughts will be appreciated. Thanks in advance, -PK Tag: Help with PartitionTable Tag: 112099
  - 20
    - CE5 to CE6 port, Kitl Question I am porting an existing BSP to CE6 and have followed the migration guide regarding the new Kernel/OAL/Kitl architecture. I have oal.exe and kitl.dll built as well as the rest of the ROM image. I also have the bootloader ported and functional. After the image is downloaded to RAM via Ethernet the image is launched successfully, but in OEMInit() the call to KITLIoctl (IOCTL_KITL_STARTUP,...) is not invoking OEMKitlStartup() in kitl.dll and the system is hanging. Thoughts as to why I am not seeing the entry into OEMKitlStartup()?? I have debug tracing everywhere and am sure this is where the hang is occurring. I have verified that the interrupts are being setup correctly, and as I stated, this is a working BSP with CE 5.0, just want to upgrade to CE 6.0 for the newer memory architecture. Thanks. Tag: Help with PartitionTable Tag: 112094
  - 21
    - Need Help: CE5.0 flash is not shown as USB mass storage device in Hi All, I am trying to expose my flash folders as a USB mass storage device. Added SYSGEN_USBFN_STORAGE catalog item and added following regisry. settings to my platform.reg: [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"=- ; erase previous default [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers] "DefaultClientDriver"="Mass_Storage_Class" [HKEY_LOCAL_MACHINE\Drivers\USB\FunctionDrivers\Mass_Storage_Class] "Dll"="usbmsfn.dll" "InterfaceSubClass"=dword:06 "InterfaceProtocol"=dword:50 "DeviceName"="DSK1:" "FriendlyName"="Mass Storage" "idVendor"=dword:045E "Manufacturer"="Generic Manufacturer (PROTOTYPE--Remember to change idVendor)" "idProduct"=dword:FFFF "Product"="Generic Mass Storage (PROTOTYPE--Remember to change idVendor)" "bcdDevice"=dword:0 But still if i connect my ce5.0 device(active sync disabled), it is getting recognized as "Windows CE devices" and not as a mass storage device. If i enable active sync, it works with USB. When i check with Remote Process viewer, i could not see the usbmsfn.dll. I checked the device names using storage manager application and in the registry too. The name is DSK1,DSK2 for platform&application and DSK3 is for SD cards. I am not sure, whether i need to make any code changes in USBFN driver to show my flash folders as a SUSB mass storage device. Could anyone please tell me what are changes we need to make to show as terminal's flash as USB storage device? Please give me your valuable inputs. I appreciate your help in advance. Thanks Saravana Tag: Help with PartitionTable Tag: 112093
  - 22
    - WMA recorder Hi, I am looking at a requirement to possibly record voice on my device in wma format.... but dont seem to be getting anywhere, probably due to lack of experience in Audio! I went thru the waverec sample, which basically records in .wav format. Is there a way to convert the .wav file to wma? Better-off, I would like to directly sample and create the wma file. Does anyone have some experience on this? Thanks - TaN Tag: Help with PartitionTable Tag: 112086
  - 23
    - Prefetch Abort Dear all: I built a WinCE5.0 Debug mode Image,after download and the system start up. Everything think OK,but after load EXPLORER.EXE, I got Prefetch Abort,then the system die. Here is my Oemaddress table: g_oalAddressTable ;------------------------------------------------------------- ; Virtual(cached) Phys Addr MB ;------------------------------------------------------------- DCD 0x80000000, 0xA0000000, 32 ; SDRAM CS0 DCD 0x82000000, 0xA4000000, 32 ; SDRAM CS1 DCD 0x86000000, 0xE0000000, 1 ; Zero-Bank (in RSVD slot)- No Phy Mem needed to back up DCD 0x86100000, 0x48000000, 1 ; Memory Controller DCD 0x86200000, 0x40000000, 32 ; Mem-Mapped Registers (perifs) DCD 0x88200000, 0x20000000, 32 ; PCMCIA S0 I/O Space DCD 0x8A200000, 0x28000000, 32 ; PCMCIA S0 ATTRIBUTE MEM Space DCD 0x8C200000, 0x2C000000, 64 ; PCMCIA S0 COMMON MEM Space DCD 0x90200000, 0x30000000, 32 ; PCMCIA S1 I/O Space DCD 0x92200000, 0x38000000, 32 ; PCMCIA S1 ATTRIBUTE MEM Space DCD 0x94200000, 0x3C000000, 64 ; PCMCIA S1 COMMON MEM Space DCD 0x98200000, 0x44000000, 1 ; LCDC DCD 0x98300000, 0x00000000, 32 ; CS0 DCD 0x9F800000, 0x14000000, 1 ; CS5 DCD 0x00000000, 0x00000000, 0 ; End of Table (MB MUST BE ZERO!) : 0 PID:0 TID:0 -OALKitlStart(rc = 1) 0 PID:0 TID:0 Start running 0 PID:0 TID:0 Error Reporting Memory Reserved, dump size = 00020000 0 PID:0 TID:0 Booting Windows CE version 5.00 for (ARM) 0 PID:0 TID:0 &pTOC = 8010aafc, pTOC = 8024e170, pTOC->ulRamFree = 80cd2000, MemForPT = 00000000 0 PID:0 TID:0 Configuring: Primary pages: 4875, Secondary pages: 7350, Filesystem pages = 6112 0 PID:0 TID:0 Booting kernel with clean memory configuration: 0 PID:0 TID:0 Memory Sections: 0 PID:0 TID:0 [0] : start: 80cd3000, extension: 00002000, length: 0130b000 0 PID:0 TID:0 [1] : start: 82000000, extension: 00002000, length: 01cb6000 0 PID:0 TID:0 Sp=ffffc7cc 1 PID:0 TID:0 Windows CE KernelInit 4294767296 PID:3cb7002 TID:3cb7266 Updated eptr->e32_vsize to = 000ee000 4294767297 PID:3cb7002 TID:3cb7266 Scheduling the first thread. 4294767298 PID:3cb7002 TID:3cb7266 0x83cb7024: KernelInit2: pCurThread=83cb7024 hCurThread=03cb7266 hCurProc=03cb7002, KernelInit = 801505b0 4294767299 PID:3cb7002 TID:3cb7266 0x83cb7024: Detecting VFP... 4294767300 PID:3cb7002 TID:3cb7266 0x83cb7024: VFP Not Found! 4294767300 PID:3cb7002 TID:3cb7266 0x83cb7024: Updated eptr->e32_vsize to = 00006000 4294767302 PID:3cb7002 TID:3cb7266 0x83cb7024: Updated eptr->e32_vsize to = 00029000 4294767303 PID:3cb7002 TID:3cb7266 0x83cb7024: Updated eptr->e32_vsize to = 00009000 4294767305 PID:3cb7002 TID:3cb7266 0x83cb7024: Updated eptr->e32_vsize to = 00022000 4294767306 PID:3cb7002 TID:3cb7266 0x83cb7024: Starting kernel debugger software probe (KdStub) - KD API version 18 4294767308 PID:3cb7002 TID:3cb7266 0x83cb7024: >>> Loading module NK.EXE at address 0x80100000-0x801EE000 (RW data at 0x80C46000-0x80CB8187) 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 0x80100000 / Data relocated at 0x80c46000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\NK.EXE' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\KD.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\OSAXST1.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\OSAXST0.DLL' Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\HD.DLL' 4294767326 PID:3cb7002 TID:3cb7266 0x83cb7024: first = 01f70000, last = 02000000, SharedDllBase = 035f0000 4294767364 PID:3cb7002 TID:3cb7266 0x83cb7024: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\COREDLL.DLL' 4294767455 PID:3cb7002 TID:3cb7266 0x83cb7024: OALIoCtlHalPostInit 4294767483 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) 4294767487 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: >>> Loading module filesys.exe at address 0x04010000-0x0409C000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\FILESYS.EXE' 4294767491 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: CertMod.dll not found, using old OEM Trust Model 4294767505 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FileSystem Starting - starting with clean file system 4294767507 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: +OALIoCtlHalInitRTC(...) 4294767509 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: Set Real time 4294767512 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: initializing ROM/RAM file system 4294767514 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: SC_CreateAPIHandle: pvData == NULL 4294767515 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Registering file system ROM, index 2, flags 0x00000031 4294767517 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Mount complete (ROM, index 2, flags 0x00000031) 4294767521 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: OEMIoControl: Unsupported Code 0x101008c - device 0x0101 func 35 4294767711 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: Succeeded on CheckFile 4294767712 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: RestoreFile(0xc3c80f7e) called fDelete = TRUE 4294768666 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: OALKitlInitRegistry 4294768667 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: +OALArgsQuery(2) 4294768669 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: OAL_ARGS_QUERY_KITL 4294768670 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: -OALArgsQuery(pData = 0xa00ff018) 4294768695 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: >>> Loading module fsdmgr.dll at address 0x03D50000-0x03D7E000 (RW data at 0x01FE8000-0x01FE8808) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\FSDMGR.DLL' 4294768699 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Registering file system StoreMgr, index 3, flags 0x00000001 4294768713 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: >>> Loading module relfsd.dll at address 0x03EA0000-0x03EAB000 (RW data at 0x01FF2000-0x01FF2ADC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\RELFSD.DLL' 4294768724 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Registering file system Release, index 4, flags 0x00000000 4294768726 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: Mounted ReleaseFSD volume '\Release' 4294768739 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: size of 'dbglist.txt' = 00000000 4294768743 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Mount complete (Release, index 4, flags 0x00000000) 4294768745 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FSREG: Unable to read value "NoDefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294768746 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FSREG: Logging in default user. 4294768748 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FSREG: Unable to read value "DefaultUser" under HKEY_LOCAL_MACHINE\init\BootVars 4294768749 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: SetCurrentUser: Logging out (nobody), logging in default 4294768751 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Using default path "\profiles\" 4294768752 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: BuildPath: profiles 4294768755 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: BuildPath: profiles\default 4294768757 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: SetCurrentUser: User hives not supported -- using same registry for all users 4294768759 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Using default path "Windows\" 4294768762 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: OEMIoControl: Unsupported Code 0x10100d0 - device 0x0101 func 52 4294768763 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: +OALArgsQuery(2) 4294768765 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: OAL_ARGS_QUERY_KITL 4294768766 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: -OALArgsQuery(pData = 0xa00ff018) 4294768825 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Using default path "Windows\" 4294768833 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FSREG: Unable to read value "DBFlags" under HKEY_LOCAL_MACHINE\init\BootVars 4294768900 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: Initializing Database 4294768918 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: DB:Validation: Name already exists DB_notify_events 4294768919 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: DB:CeCreateDatabase failed 4294768922 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: Filesystem initialized! 4294768924 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Waiting for kernel to be ready to launch apps 4294768925 PID:3cb7002 TID:23c9e642 0x83c9ea64: InitMUI: DISABLED (-1039729896) 4294768928 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event SYSTEM/DevMgrApiSetReady 4294768929 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event SYSTEM/PowerManagerReady 4294768931 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event SYSTEM/GweApiSetReady 4294768932 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event ReleaseFSD 4294768933 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event system/events/notify/APIReady 4294768934 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FS: Creating signal event SYSTEM/ShellAPIReady 4294768936 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Launching apps 4294768937 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Launching shell.exe 4294768950 PID:83c73dfa TID:83c73f92 0x83c6a000: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) 4294768955 PID:83c73dfa TID:83c73f92 0x83c6a000: >>> Loading module toolhelp.dll at address 0x03E80000-0x03E86000 (RW data at 0x01FEE000-0x01FEE058) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\TOOLHELP.DLL' 4294768963 PID:83c73dfa TID:83c73f92 0x83c6a000: >>> Loading module shell.exe at address 0x06010000-0x0602B000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\SHELL.EXE' 4294769056 PID:83c73dfa TID:83c73f92 0x83c6a000: Shell: No extension DLLs found 4294769062 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: SignalStarted loop = 1 4294769063 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Launching device.exe 4294769073 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) 4294769096 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module pm.dll at address 0x03ED0000-0x03EF3000 (RW data at 0x01FF6000-0x01FF6708) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\PM.DLL' 4294769099 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module devmgr.dll at address 0x03F20000-0x03F39000 (RW data at 0x01FFC000-0x01FFC6B4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\DEVMGR.DLL' 4294769102 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module device.exe at address 0x08010000-0x08014000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\DEVICE.EXE' 4294769241 PID:3c6a836 TID:3c73e1e 0x83c9e400: *** DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x3c6a836 *** 4294769305 PID:3c6a836 TID:3c73e1e 0x83c9e400: +InitDeviceFileSystems 4294769306 PID:a3c9c3da TID:3c73e1e 0x83c9e400: FS: Registering file system $device, index 5, flags 0x00000001 4294769308 PID:a3c9c3da TID:3c73e1e 0x83c9e400: FS: Registering file system $bus, index 6, flags 0x00000001 4294769310 PID:3c6a836 TID:3c73e1e 0x83c9e400: -InitDeviceFileSystems: status is 1 4294769314 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module ceddk.dll at address 0x03D40000-0x03D49000 (RW data at 0x01FE6000-0x01FE60C4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\CEDDK.DLL' 4294769316 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ceddk!CalibrateStallCounter: Enter 4294769320 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ceddk!CalibrateStallCounter: Could not find stall counter 4294769322 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ceddk!BeginCalibration: min(3687) max(4096) 4294769331 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ceddk!BeginCalibration: Elapsed is 4016 4294769332 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ceddk!BeginCalibration: Delay is 9 4294769371 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!DevloadInit 4294769373 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 4294769375 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Prefix) returned 2 4294769376 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\BusPrefix) returned 2 4294769393 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module busenum.dll at address 0x03F00000-0x03F0A000 (RW data at 0x01FF8000-0x01FF851C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\BUSENUM.DLL' 4294769473 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\notify\BusPrefix) returned 2 4294769489 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module notify.dll at address 0x03EB0000-0x03ECA000 (RW data at 0x01FF4000-0x01FF4960) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\NOTIFY.DLL' 4294769557 PID:3c6a836 TID:3c73e1e 0x83c9e400: [NOTIFY] Module loaded 4294769560 PID:3c6a836 TID:63bfd3de 0x83bfd800: [NOTIFY] Initializing. 4294769562 PID:a3c9c3da TID:63bfd3de 0x83bfd800: DB:OpenDB fail: DB DB_notify_queue not found 4294769566 PID:3c6a836 TID:63bfd3de 0x83bfd800: [NOTIFY] Initialization completed successfully 4294769569 PID:3c6a836 TID:83bf7c92 0x83bf7a50: [NOTIFY] ProcessDatabase::started at local time 01/03/2003 04:37:13 4294769573 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\NDIS\BusPrefix) returned 2 4294769603 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module cxport.dll at address 0x03CC0000-0x03CD3000 (RW data at 0x01FDB000-0x01FDCA74) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\CXPORT.DLL' 4294769606 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module ndis.dll at address 0x03B40000-0x03BA2000 (RW data at 0x01FC4000-0x01FC51F4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\NDIS.DLL' 4294769738 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD NFY0: 4294769757 PID:3c6a836 TID:3c73e1e 0x83c9e400: NDIS: RebindAdaptersOnResume = 0 4294769759 PID:3c6a836 TID:3c73e1e 0x83c9e400: NDIS: PcmciaNeedsMapToScrap = 0 4294769770 PID:3c6a836 TID:3c73e1e 0x83c9e400: NDIS:: CE_DeleteBusFriendlyNames() failed deleting [HKLM\Comm\BusFriendlyNames] 4294769777 PID:3c6a836 TID:3c73e1e 0x83c9e400: DeviceFolder::LoadDevice!Enumerate Found deprecated load instructions at (Drivers\BuiltIn\AFD). Driver cannot be unloaded. 4294769791 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module afd.dll at address 0x03BB0000-0x03BEB000 (RW data at 0x01FC7000-0x01FC7F08) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\AFD.DLL' 4294769858 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD NDS0: 4294769877 PID:3c6a836 TID:3c73e1e 0x83c9e400: Can't load library ppp.dll 4294769878 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD:AfdInitialize: Can't open Registry key Comm\AFD -- creating 'Stacks' entry 4294769900 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module tcpstk.dll at address 0x03A50000-0x03B1E000 (RW data at 0x01FB9000-0x01FC0DA4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\TCPSTK.DLL' 4294769962 PID:3c6a836 TID:3c73e1e 0x83c9e400: TCPIP: dllentry() 4294769964 PID:3c6a836 TID:3c73e1e 0x83c9e400: TCPIP.Register() 4294769970 PID:3c6a836 TID:3c73e1e 0x83c9e400: *** New TcpStack *** 4294769972 PID:3c6a836 TID:3c73e1e 0x83c9e400: +IPInit() 4294769974 PID:3c6a836 TID:3c73e1e 0x83c9e400: +IPGetConfig 4294769979 PID:3c6a836 TID:3c73e1e 0x83c9e400: -IPGetConfig: Ret: 0xF0950 4294769992 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module dhcp.dll at address 0x03B20000-0x03B35000 (RW data at 0x01FC2000-0x01FC2614) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\DHCP.DLL' 4294770054 PID:3c6a836 TID:3c73e1e 0x83c9e400: Dhcp: dllentry() -2084740208 4294770055 PID:3c6a836 TID:3c73e1e 0x83c9e400: +DhcpRegister: 4294770057 PID:3c6a836 TID:3c73e1e 0x83c9e400: -DhcpRegister: Ret = 33940 4294770058 PID:3c6a836 TID:3c73e1e 0x83c9e400: IPInit: registered w/ DHCP 4294770069 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module netbios.dll at address 0x039C0000-0x039DA000 (RW data at 0x01FB4000-0x01FB4AEC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\NETBIOS.DLL' 4294770166 PID:3c6a836 TID:3c73e1e 0x83c9e400: IPInit: Unable to Load IPSEC 4294770187 PID:3c6a836 TID:3c73e1e 0x83c9e400: IGMPDelInclList: AddrPtr=f1380 NumDelSources=0 DelSourceList=0 4294770188 PID:3c6a836 TID:3c73e1e 0x83c9e400: -IPInit [SUCCESS] 4294770190 PID:3c6a836 TID:3c73e1e 0x83c9e400: +TCPGetConfigInfo 4294770195 PID:3c6a836 TID:3c73e1e 0x83c9e400: -TCPGetConfigInfo 4294770200 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(TCPIP\IPDevice\BusPrefix) returned 2 4294770222 PID:3c6a836 TID:3c73e1e 0x83c9e400: +IPD_Init(802dec0) 4294770226 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(TCPIP\TCPDevice\BusPrefix) returned 2 4294770231 PID:3c6a836 TID:3c73e1e 0x83c9e400: +TCP_Init(802dec0) 4294770234 PID:3c6a836 TID:3c73e1e 0x83c9e400: TCPIP.About to register 4294770253 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'tcpip6.dll' 4294770267 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD IPD0: 4294770269 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD TCP0: 4294770275 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'irdastk.dll' 4294770294 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'btd.dll' 4294770333 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module redir.dll at address 0x039E0000-0x03A4A000 (RW data at 0x01FB6000-0x01FB7550) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\REDIR.DLL' 4294770397 PID:3c6a836 TID:3c73e1e 0x83c9e400: RdrMain: DLL_PROCESS_ATTACH, hInst:0x83BD6880 4294770398 PID:3c6a836 TID:3c73e1e 0x83c9e400: +RDR:Redir helper func: Ctxt:0x0, OpCode:1 4294770399 PID:3c6a836 TID:3c73e1e 0x83c9e400: +RDR:InitRedir 4294770421 PID:3c6a836 TID:3c73e1e 0x83c9e400: InitRedirConfig: 4294770423 PID:3c6a836 TID:3c73e1e 0x83c9e400: ClearTxtPwd: FALSE 4294770424 PID:3c6a836 TID:3c73e1e 0x83c9e400: ServerTimeoutMs: 10000 4294770425 PID:3c6a836 TID:3c73e1e 0x83c9e400: FindCacheMaxSize: 8192 4294770426 PID:3c6a836 TID:3c73e1e 0x83c9e400: ResourceExpiryInt: 600 4294770428 PID:3c6a836 TID:3c73e1e 0x83c9e400: RecvBufSize: 9000 4294770429 PID:3c6a836 TID:3c73e1e 0x83c9e400: RecvThreadPrio256: 251 4294770430 PID:3c6a836 TID:3c73e1e 0x83c9e400: RegisterFSRoot: TRUE 4294770438 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module secur32.dll at address 0x03C30000-0x03C39000 (RW data at 0x01FCD000-0x01FCD52C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\SECUR32.DLL' 4294770442 PID:3c6a836 TID:3c73e1e 0x83c9e400: SECUR32: Loading package DLL: 'schannel.dll'. 4294770461 PID:3c6a836 TID:3c73e1e 0x83c9e400: SECUR32: Loading package DLL: 'ntlmssp.dll'. 4294770479 PID:3c6a836 TID:3c73e1e 0x83c9e400: SECUR32: Loading package DLL: 'kerberos.dll'. 4294770498 PID:3c6a836 TID:3c73e1e 0x83c9e400: SECUR32: Loading package DLL: 'spnego.dll'. 4294770518 PID:3c6a836 TID:3c73e1e 0x83c9e400: SECUR32: Locating package 'Negotiate' ... 4294770519 PID:3c6a836 TID:3c73e1e 0x83c9e400: Package NOT found. 4294770520 PID:3c6a836 TID:3c73e1e 0x83c9e400: RDR: Did not find Kerberos (err 0x80090305) 4294770523 PID:3c6a836 TID:3c73e1e 0x83c9e400: <<< Unloading module secur32.dll at address 0x03C30000-0x03C39000 (RW data at 0x01FCD000-0x01FCD52C) Unloaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\SECUR32.DLL' 4294770525 PID:3c6a836 TID:3c73e1e 0x83c9e400: +RDR:InitNetBIOS 4294770527 PID:3c6a836 TID:3c73e1e 0x83c9e400: NETBIOS: NB_NET_NOTIFY for callback at address 0x3a36f18 4294770528 PID:3c6a836 TID:3c73e1e 0x83c9e400: Browser initialized 4294770530 PID:3c6a836 TID:3c73e1e 0x83c9e400: +RDR:FSAPIInit 4294770532 PID:a3c9c3da TID:3c73e1e 0x83c9e400: FS: Registering file system Network, index 1, flags 0x00000000 4294770534 PID:3c6a836 TID:3c73e1e 0x83c9e400: -RDR:FSAPIInit 4294770543 PID:3c6a836 TID:3c73e1e 0x83c9e400: +RDR_Init 4294770545 PID:3c6a836 TID:3c73e1e 0x83c9e400: -RDR:InitRedir, initialization successful 4294770582 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'IPNat.dll' 4294770600 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module ws2.dll at address 0x03C70000-0x03C84000 (RW data at 0x01FD5000-0x01FD5B24) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\WS2.DLL' 4294770604 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module ws2instl.dll at address 0x03C60000-0x03C6A000 (RW data at 0x01FD3000-0x01FD3131) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\WS2INSTL.DLL' 4294770676 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ws2Instl dllentry() -2084842808 4294770679 PID:3c6a836 TID:83bb97e2 0x83bb9cac: IPDispatchDeviceControl returned Status 103 4294770698 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ws2Instl:IsStackInstalled - LoadLibrary(irdastk) failed 126 4294770719 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ws2Instl:IsStackInstalled - LoadLibrary(btd) failed 126 4294770738 PID:3c6a836 TID:3c73e1e 0x83c9e400: Ws2Instl:IsStackInstalled - LoadLibrary(tcpip6) failed 126 4294770759 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'DhcpV6L.dll' 4294770781 PID:3c6a836 TID:3c73e1e 0x83c9e400: *TCPIP:ReadyToGo 4294770783 PID:3c6a836 TID:3c73e1e 0x83c9e400: +ARPInit() 4294770787 PID:3c6a836 TID:3c73e1e 0x83c9e400: -ARPInit [0] 4294770807 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'tcpip6.dll' 4294770825 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'irdastk.dll' 4294770844 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'btd.dll' 4294770845 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to GetProcAddress of ReadyToGo in 'Netbios' 4294770846 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to GetProcAddress of ReadyToGo in 'Redir' 4294770848 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to GetProcAddress of ReadyToGo in 'Dhcp' 4294770868 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'IPNat.dll' 4294770869 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to GetProcAddress of ReadyToGo in 'Ws2Instl' 4294770888 PID:3c6a836 TID:3c73e1e 0x83c9e400: !AFD: Unable to load library 'DhcpV6L.dll' 4294770889 PID:3c6a836 TID:3c73e1e 0x83c9e400: AFD: Initialization Complete 4294770892 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\credsvc\BusPrefix) returned 2 4294770910 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module credsvc.dll at address 0x03C00000-0x03C22000 (RW data at 0x01FCB000-0x01FCB67C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\CREDSVC.DLL' 4294770981 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module credprov.dll at address 0x03BF0000-0x03BF5000 (RW data at 0x01FC9000-0x01FC949C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\CREDPROV.DLL' 4294771050 PID:3c6a836 TID:3c73e1e 0x83c9e400: CREDSVC: LoadVProviders: There are no virtual type providers present 4294771055 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\TIMESVC\BusPrefix) returned 2 4294771072 PID:3c6a836 TID:3c73e1e 0x83c9e400: >>> Loading module timesvc.dll at address 0x037B0000-0x037B9000 (RW data at 0x01FA2000-0x01FA255C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\TIMESVC.DLL' 4294771079 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCC_MAINSTONEII0\DllName) returned 2 4294771081 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\PCC_MAINSTONEII0' 4294771083 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\Touch\DllName) returned 2 4294771085 PID:3c6a836 TID:3c73e1e 0x83c9e400: DEVICE!I_ActivateDeviceEx: can't find all required activation values in 'Drivers\BuiltIn\Touch' 4294771087 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD CRD0: 4294771089 PID:3c6a836 TID:43c5c266 0x83c9ea64: [NOTIFY] HandleSystemEvent 7 /ADD NTP0: 4294771091 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [TIMESVC DST] System Started... 4294771093 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] CeRunAppAtEvent - clearing system event registration for \\.\Notifications\NamedEvents\DSTTzChange 4294771095 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] CeRunAppAtEvent - clearing system event registration for \\.\Notifications\NamedEvents\DSTTimeChange 4294771097 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] RemoveAppRunAtTime::Starting Database Sweep... 4294771109 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification (or replacing 00000000) 4294771110 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification::Registring system watch: event 12 app \\.\Notifications\NamedEvents\DSTTzChange args AppRunAfterTzChange 4294771116 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification (or replacing 00000000) 4294771117 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification::Registring system watch: event 1 app \\.\Notifications\NamedEvents\DSTTimeChange args AppRunAfterTimeChange 4294771131 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] RemoveAppRunAtTime::Starting Database Sweep... 4294771133 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification (or replacing 00000000) 4294771139 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] SetUserNotification::Setting event semaphore 4294771141 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: [NOTIFY] ProcessDatabase::started at local time 01/03/2003 04:37:15 4294771143 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: +OEMSetAlarmTime(2003/3/9 2:0:0.000) 4294771144 PID:3c6a836 TID:e3bb0fa6 0x83bb56e4: -OEMSetAlarmTime(rc = 1) 4294771146 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: SignalStarted loop = 2 4294771147 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Launching gwes.exe 4294771217 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) 4294771222 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module gwes.exe at address 0x0A010000-0x0A186000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\GWES.EXE' 4294771245 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module ceddk.dll at address 0x03D40000-0x03D49000 (RW data at 0x01FE6000-0x01FE60C4) 4294771248 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Ceddk!CalibrateStallCounter: Enter 4294771252 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Ceddk!CalibrateStallCounter: Stall counter loaded from registry(9) 4294771320 PID:63bae9b2 TID:63c6a682 0x83bbdda4: System Default HKL value set to 00000409 4294771341 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Grow Gdi handle table from 0 to 64 4294771344 PID:63bae9b2 TID:63c6a682 0x83bbdda4: LogFontFromRegistry(SYSTEM\GDI\SysFnt), lfHeight = -12 4294771419 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module ddi.dll at address 0x03640000-0x036A4000 (RW data at 0x01F85000-0x01F954C4) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\DDI.DLL' 4294771525 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Display Driver Initialization Complete 4294771537 PID:63bae9b2 TID:63c6a682 0x83bbdda4: found:B505 4294771558 PID:63bae9b2 TID:63c6a682 0x83bbdda4: OEMIoControl: Unsupported Code 0x10100fc - device 0x0101 func 63 4294771563 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Bits-per-pixel: 16 4294771571 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Adding font resource '\Windows\tahoma.ttf'... 4294771576 PID:63bae9b2 TID:63c6a682 0x83bbdda4: **** Signature of FONT File is: '0100'... 4294771589 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Creating secondary frame buffer for POR and SaveBits 4294771624 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module kbdmouse.dll at address 0x03610000-0x03624000 (RW data at 0x01F81000-0x01F81E8C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\KBDMOUSE.DLL' 4294771688 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Layout Manager : DLL_PROCESS_ATTACH 4294771693 PID:63bae9b2 TID:63c6a682 0x83bbdda4: PS2_8042_Entry: Initialize Matrix ID 0 4294771694 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Ps2Keybd::Initialize 4294771695 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ++Ps2Keybd::KeybdPowerOn 4294771697 PID:63bae9b2 TID:63c6a682 0x83bbdda4: --Ps2Keybd::KeybdPowerOn 4294771699 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Ps2Keybd::Initialize Done 4294771700 PID:63bae9b2 TID:63c6a682 0x83bbdda4: IsrThreadStart: 4294771701 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ++KeybdDriverInitializeAddresses 4294771703 PID:63bae9b2 TID:63c6a682 0x83bbdda4: --KeybdDriverInitializeAddresses 4294771704 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ++Ps2Keybd::KeybdPowerOn 4294771705 PID:63bae9b2 TID:63c6a682 0x83bbdda4: --Ps2Keybd::KeybdPowerOn 4294771707 PID:63bae9b2 TID:63c6a682 0x83bbdda4: PS2_8042_Entry: Initialization complete 4294771708 PID:63bae9b2 TID:63c6a682 0x83bbdda4: KeybdDriverInitializeEx: Initialized PDD 0 - Matrix (Mask 8) 4294771710 PID:63bae9b2 TID:63c6a682 0x83bbdda4: KeybdDriverInitializeEx: Found default input method 00000409 4294771716 PID:63bae9b2 TID:63c6a682 0x83bbdda4: KeybdDriverInitializeEx: Layout Manager successfully initialized 4294771717 PID:63bae9b2 TID:63c6a682 0x83bbdda4: KeybdDriverInitializeEx: Layout Manager successfully initialized to 1 4294771722 PID:63bae9b2 TID:63c6a682 0x83bbdda4: AddToProcessInputLocaleTable: Added process to ProcessInputLocale table, hProcess = 0x63BAE9B2 4294771725 PID:63bae9b2 TID:63c6a682 0x83bbdda4: LogFontFromRegistry(SYSTEM\GWE\Menu\BarFnt), lfHeight = -12 4294771728 PID:63bae9b2 TID:63c6a682 0x83bbdda4: LogFontFromRegistry(SYSTEM\GWE\Menu\PopFnt), lfHeight = -12 4294771747 PID:63bae9b2 TID:63c6a682 0x83bbdda4: >>> Loading module touch.dll at address 0x03630000-0x0363B000 (RW data at 0x01F83000-0x01F836AC) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\TOUCH.DLL' 4294771812 PID:63bae9b2 TID:63c6a682 0x83bbdda4: calibrating 0 point set 4294771814 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ***********ACLink Alloc successful 4294771816 PID:63bae9b2 TID:63c6a682 0x83bbdda4: AC97GpioConfiguring 4294771817 PID:63bae9b2 TID:63c6a682 0x83bbdda4: UCB1400 Power up 4294771935 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ***********UCB1400 is ready 4294771936 PID:63bae9b2 TID:63c6a682 0x83bbdda4: AC97GpioConfigured 4294772048 PID:63bae9b2 TID:63c6a682 0x83bbdda4: touch power on 4294772050 PID:63bae9b2 TID:63c6a682 0x83bbdda4: TouchPanelEnable:2a0 4294772052 PID:63bae9b2 TID:63c6a682 0x83bbdda4: TOUCH:ThrdPrio = 96, ThrdHighPrio = 80 4294772055 PID:63bae9b2 TID:63c6a682 0x83bbdda4: calibrating 5 point set 4294772060 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Maximum Allowed Error 9: 4294772061 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Calibration Results: 4294772063 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Screen => Mapped 4294772064 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ( 120, 160) => ( 119, 161) 4294772065 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ( 48, 64) => ( 48, 63) 4294772067 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ( 48, 256) => ( 49, 256) 4294772068 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ( 192, 256) => ( 192, 255) 4294772072 PID:63bae9b2 TID:63c6a682 0x83bbdda4: ( 192, 64) => ( 193, 64) 4294772073 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Maximum error (square of Euclidean distance in screen units) = 2 4294772080 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom Low Pages: 0020 Bytes: 00020000 4294772081 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom Critical Pages: 0014 Bytes: 00014000 4294772082 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom Low Block Pages: 0004 Bytes: 00004000 4294772084 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom Critical Block Pages: 0002 Bytes: 00002000 4294772085 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom App Wait 8000 (dec ms) 4294772086 PID:63bae9b2 TID:63c6a682 0x83bbdda4: Oom AutoOom 0 4294772089 PID:63bae9b2 TID:43b1bf96 0x83b17400: ++KeybdDriverInitializeAddresses 4294772090 PID:63bae9b2 TID:43b17642 0x83b17a98: Ps2KeybdIsrThread: 4294772092 PID:63bae9b2 TID:43b17642 0x83b17a98: ReadRegDWORD: RegQueryValueEx(Priority256) returned 2 4294772094 PID:63bae9b2 TID:43b17642 0x83b17a98: ReadRegDWORD(): HARDWARE\DEVICEMAP\KEYBD -> Priority256 is 0x0 4294772095 PID:63bae9b2 TID:43b17642 0x83b17a98: IsrThreadProc: 4294772107 PID:63bae9b2 TID:43b1b826 0x83b1bc9c: +OALIoCtlHalEnableWake(sysIntr = 18) 4294772109 PID:63bae9b2 TID:43b1b826 0x83b1bc9c: +OALIoCtlHalEnableWake(rc = 1) 4294772110 PID:63bae9b2 TID:43b1b826 0x83b1bc9c: PwrButtonIntrThread start 4294772113 PID:63bae9b2 TID:43b1068a 0x83b10aac: Grow Gdi handle table from 64 to 128 4294772116 PID:63bae9b2 TID:63c6a682 0x83bbdda4: UpdateIdleTimeoutFromRegistry 4294772139 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: SignalStarted loop = 3 4294772140 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Launching explorer.exe 4294772143 PID:63bae9b2 TID:83bfdeea 0x83bf7400: AddToProcessInputLocaleTable: Added process to ProcessInputLocale table, hProcess = 0x03C6A836 4294772160 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module coredll.dll at address 0x03F40000-0x03FFF000 (RW data at 0x01FFE000-0x01FFF2E5) 4294772171 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module ole32.dll at address 0x03930000-0x0398B000 (RW data at 0x01FAD000-0x01FAE520) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\OLE32.DLL' 4294772181 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module oleaut32.dll at address 0x038D0000-0x03921000 (RW data at 0x01FAB000-0x01FABF04) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\OLEAUT32.DLL' 4294772192 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module commctrl.dll at address 0x03DA0000-0x03E7B000 (RW data at 0x01FEC000-0x01FECC0C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\COMMCTRL.DLL' 4294772205 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module shcore.dll at address 0x03720000-0x03727000 (RW data at 0x01F9D000-0x01F9D078) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\SHCORE.DLL' 4294772208 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module ceshell.dll at address 0x03730000-0x037A5000 (RW data at 0x01F9F000-0x01FA038C) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\CESHELL.DLL' 4294772218 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module ieceext.dll at address 0x03850000-0x03861000 (RW data at 0x01FA7000-0x01FA7274) Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\IECEEXT.DLL' 4294772222 PID:23b0ddba TID:23c6a7d2 0x83b0db78: >>> Loading module explorer.exe at address 0x0C010000-0x0C06E000 Loaded symbols for 'C:\WINCE500\PBWORKSPACES\MS400B\RELDIR\MS400B_ARMV4I_DEBUG\EXPLORER.EXE' 4294772250 PID:63bae9b2 TID:23c6a7d2 0x83b0db78: AddToProcessInputLocaleTable: Added process to ProcessInputLocale table, hProcess = 0x23B0DDBA 4294772359 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: FILESYS: Done launching apps 4294772361 PID:3c6a836 TID:a3c9c3b6 0x83c9c174: -DEVICE!DevloadPostInit 4294772364 PID:a3c9c3da TID:a3c9c3b6 0x83c9c174: This device has booted 1 times !!! 4294772480 PID:23b0ddba TID:23c6a7d2 0x83b0db78: Console redirected to DEBUG for process 0x23B0DDBA 4294772543 PID:63bae9b2 TID:23c6a7d2 0x83b0db78: Grow Gdi handle table from 128 to 192 4294772703 PID:a3c9c3da TID:23c6a7d2 0x83b0db78: DB:OpenDB fail: DB RecycleData not found 4294772751 PID:a3c9c3da TID:23c6a7d2 0x83b0db78: Prefetch Abort: Thread=83b0db78 Proc=80c96fd0 'filesys.exe' 4294772753 PID:a3c9c3da TID:23c6a7d2 0x83b0db78: AKY=00000023 PC=00000751(???+0x00000751) RA=00000751(???+0x00000751) BVA=00000751 FSR=000004f0 The Kernel Debugger has been disconnected successfully. Tag: Help with PartitionTable Tag: 112083
  - 24
    - PXA 270 USB client not function after suspend/resume Hi, I am using mainstoneii bsp and found that the USB client does not work after suspend and resume... Any idea? Best regards, James -- Message posted via PocketPCJunkies.com http://www.pocketpcjunkies.com/Uwe/Forums.aspx/wince-pb/200804/1 Tag: Help with PartitionTable Tag: 112081
  - 25
    - Can't link nk.lib and coredll.lib in kern.exe Hi all, I am using WinCE 5, for creating an settopbox. In the OAL I want to adjust the OALArgsQuery(OAL_ARGS_QUERY_DEVID) so that the mac address of the device is returned to the calling function. In this case OALIoCtlHalGetDeviceId( ), this is needed for DRM to work. In OALArgsQuery(OAL_ARGS_QUERY_DEVID), I use the DeviceIOControl(OID_802_3_CURRENT_ADDRESS) to get the current mac address of the device. The function DeviceIOControl uses Coredll.lib, so I link this library in the source of kern.exe, but NK.lib is already linked here, and there are dubble methodcalls in the library's so I use /FORCE:MULTIPLE. This generates several warnings, but the image builds. But when I run the image, it does nothing. It won't boot. So I have a couple of questions about that. Q1) Is it possible to link the two library's in the same source? If so how? Q2) Is there another way to retrieve the current mac address? I have already tried GetAdaptersInfo, but that doesn't work either. Michel van Geffen Student at the Avans University of Professional Education Tag: Help with PartitionTable Tag: 112065

Hello, I have an x86 WinCE50 system that uses the ATAPI IDE driver for
a system CF card.

Currently, I have the CF card partitioned into 2 parts:
*Partition1 = Fat16 bootable partition with CEPC Nk.bin
*Partition2 = TFAT formatted partition for WinCE use.

I am currently trying to mount the partition 2 as root, but having no
luck at all. I have tried the following approaches.

1) Use MountAsRoot and AutoMount keys for partitions to set which
should mount as root, making sure to set Part1 MountAsBootable=0 so it
does not think system/hive files are on the drive.

Result: Partition 1 still mounts to root. This seemed to have no
effect. Maybe I am messing up the way I use the Profile? (HDProfile
\Part00\ see my reg below)?

2) Use the 'cheating' method to set the PartitionTable key 0x04 to
invalid FS. (suggested here:
http://groups.google.com/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/e122bf548aab3c7c/c61f11d3a810184f)

[HKLM\System\StorageManager\PartitionTable]
"04"="SYSBOOT"

Result: Both partition 1 and 2 do not mount and the system halts after
storage manager. To my understanding, the first partition formatted
in FAT16 is 0x04. However, shouldn't my TFAT partition be type x0B
(MS-DOS 32 bit FAT)? Perhaps I am wrong in my assumptions of how the
PartitionTable works.

3) Setting the "PartitionDriverName" to blank in an attempt to load
null partition driver
[HKLM\System\StorageManager\Profiles\HDProfile\Part00]
"PartitionDriverName"=""
[HKLM\System\StorageManager\Profiles\HDProfile\Part01]
"PartitionDriverName"="MSPART"

Result: Both partitions still loaded.

Here is where I am at stuck. Can anyone offer advice or help? Thanks
in advance
-t

Below are my current registry settings - some may have been enabled/
disabled per the 3 steps above (which I tried one at a time).
[HKLM\System\StorageManager\Profiles\HDProfile]
"MountAsRom"=dword:0
"MountAsRoot"=dword:0
"MountAsBootable"=dword:0
"MountPermanent"=dword:0
"Flags"=dword:00080064

[HKLM\System\StorageManager\Profiles\HDProfile\FATFS]
"MountAsRom"=dword:0
"MountAsRoot"=dword:0
"MountAsBootable"=dword:0
"MountPermanent"=dword:0
"Flags"=dword:00080064

[HKLM\System\StorageManager\Profiles\HDProfile\Part00]
"AutoMount"=dword:0
"AutoFormat"=dword:0
"AutoPart"=dword:0
"DefaultFileSystem"="FATFS"
; "PartitionDriver"="mspart.dll"
"PartitionDriver"=""
"MountAsRom"=dword:0
"MountAsRoot"=dword:0
"MountAsBootable"=dword:0
"MountPermanent"=dword:0
"Flags"=dword:00080064

[HKLM\System\StorageManager\Profiles\HDProfile\Part01]
"AutoMount"=dword:1
"AutoFormat"=dword:0
"AutoPart"=dword:0
"DefaultFileSystem"="FATFS"
"PartitionDriver"="mspart.dll"
"MountAsRom"=dword:1
"MountAsRoot"=dword:1
"MountAsBootable"=dword:1
"MountPermanent"=dword:0
"Flags"=dword:00080064

Top

Re: Help with PartitionTable by trucker

trucker
Fri May 09 16:41:58 PDT 2008

Just a quick note - the registry setting in my Part01 "MountAsRom" is
a typo. It actually is set to 0.

Top

Re: Help with PartitionTable by Michel

Michel
Fri May 09 21:18:55 PDT 2008

Try this (note the omission of FATFS at the end!):

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part00]
"Folder"="NK"
"AutoFormat"=dword:1
"MountPermanent"=dword:1

[HKEY_LOCAL_MACHINE\System\StorageManager\Profiles\HDProfile\Part01]
"Folder"="Root"
;Indicate this partition can store the hive registry, mount as root and
make it TFAT
"MountAsBootable"=dword:1
"MountAsRoot"=dword:1
"MountPermanent"=dword:1
"AutoFormat"=dword:1
"FormatTfat"=dword:1
"Flags"=dword:410034

Make sure you use the code (or similar technique) from one of my
previous posts
(http://groups.google.co.nz/group/microsoft.public.windowsce.platbuilder/browse_thread/thread/3607ffc6f69b59e3/851812ab08988a6a?hl=en&lnk=st&q=#851812ab08988a6a)
to create the partitions on the disk.

These are working settings on one of my customers device.

Good luck,

Michel Verhagen, eMVP
Check out my blog: http://GuruCE.com/blog

GuruCE Ltd.
Microsoft Embedded Partner
http://GuruCE.com
Consultancy, training and development services.

trucker wrote:
> Just a quick note - the registry setting in my Part01 "MountAsRom" is
> a typo. It actually is set to 0.

Top

Re: Help with PartitionTable by trucker

trucker
Sun May 11 15:56:22 PDT 2008

Thanks for the help, between your links and ideas and a few random
settings, I am able to get this system working!

Top