Problem with eboog

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - WDM for PPC Hi, This Is TZ. Is possible WDM for PPC..? And if possible.. How to use this..? Plz answer to me ^^ Tag: Problem with eboog Tag: 52587
  - 2
    - Launch application that it isn't in the image I need to launch and application that it is in the hard drive (compact flash) not in the image. Any idea ? Tag: Problem with eboog Tag: 52578
  - 3
    - SDK exported from PB and used in EVC Hello all, i created (in PB 4.2) a nk.bin OS image to be used on my hardware. I specifically added the SAPI module to let the computer speak in behalf of me! Im lazy :P I also generated the SDK, and installed onto my WinXP machine (im not so lazy). Now Im compiling my speech application using EVC 4.0 and i'm getting the usual error that says that the file "sphelper.h" cannot be found. Indeed in the SDK i just created that file does NOT exist. But i searched more and i found that file IS in the following directory: C:\WINCE420\PUBLIC\SPEECH\SDK\INC Now what i'm missing here? How to incorporate the libs/includes for the speech system into EVC in the ordinary manner? I simply added the right path to EVC to those libs/include directory and i got my app compiled&working, but i would like to do the right thingys instead of my own hacks. Greetings, Luca Tag: Problem with eboog Tag: 52575
  - 4
    - How to reconfigure image without BSPs? Greetings everybody and thanks for taking a look at my topic:0 my device is PXA255-400 based Sitsang board with 640*480 resolution, the os is wince.net 4.2. Intel provided us a nk.bin, but no BSPs is shipped along, How could i do the modifications since there is no BSP? The applications are not so complete and the drivers are running sluggish. So , i 'm wondering if i can duplicate out the files in image BIN, through sync cable while the board is running~ and do some replacement and adds, then rebuilt them into a whole~ I know, this might be a naive newbie idea, just want a verification of my idea and some suggestions to my situation..... If, my method debacle at all, what should i do to continue my project? Create BSPs? would it be easy in limited time , say, one month? I do appreciate you so much to end up with my awkward description, expect your recommonation:)) Tag: Problem with eboog Tag: 52571
  - 5
    - audio driver cause problem This is a multi-part message in MIME format. ------=_NextPart_000_0015_01C44401.E771D6B0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Hi,all: =20 In PB4.1Net,if I removerd the audio driver from the BSP,the OS can = run smoothly,but if I added the audio driver into the BSP,the OS can't = work.why?who konw the reason would be? ------=_NextPart_000_0015_01C44401.E771D6B0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Hi,all:</FONT></DIV> <DIV><FONT size=3D2>   </FONT></DIV> <DIV><FONT size=3D2>   In PB4.1Net,if I removerd the audio = driver from=20 the BSP,the OS can run smoothly,but if I added the audio driver into the = BSP,the=20 OS can't work.why?who konw the reason would = be?</FONT></DIV></BODY></HTML> ------=_NextPart_000_0015_01C44401.E771D6B0-- Tag: Problem with eboog Tag: 52570
  - 6
    - Customize Touch Calibration Hi I would like to write an application with the integrated touch calibration feature instead of customizing "calibrui" or calling "TouchCalibrate()". Is it possible that I can directly call the TouchXXX() APIs exported from touch.dll? I tried it but it didn't work. It seems related to process address space problem because my application will have another set of the global variables for the touch.dll instead of the touch driver's own copy Is there a way to solve it? Tag: Problem with eboog Tag: 52569
  - 7
    - Can Flash Image print message to HyperTerminal when OS running This is a multi-part message in MIME format. ------=_NextPart_000_000A_01C443FF.CB63BFD0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable If can do,how to do? Thank you! ------=_NextPart_000_000A_01C443FF.CB63BFD0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; charset=3Dgb2312"> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>If can do,how to do?</FONT></DIV> <DIV><FONT size=3D2>Thank you!</FONT></DIV></BODY></HTML> ------=_NextPart_000_000A_01C443FF.CB63BFD0-- Tag: Problem with eboog Tag: 52568
  - 8
    - Automatic App Execution after a soft reset Dear TechGurus I want an application to run soon after a soft-reset is given to a PDA Can any registry entries be set so that this happens. In the case of Win2k there is key in Registry under Microsoft called "RunOnce". When a entry is present there, soon after a restart the app path given in the registry starts executing. Similarly is there any registry paths in WInCE where an application would start executing after a soft-reset Thanks a tonne Cheers Lakshma Tag: Problem with eboog Tag: 52565
  - 9
    - Question About the interrupt of Pocket PC 2003 I am migrating PCMCIA & CF card device driver from Pocket PC 2002 to Pocket PC 2003 using Platform Builder 4.2. But the ISR is not called, when hardware interrupt is generated. I'm sure that the hardware has generated the interrupt. And this device driver works well in Pocket PC 2002. CardRequestIRQ return CERR_SUCCESS, however isr was not called. What is changed in the Pocket PC 2003 ? And, What is mean "NoIntrPend=dword:1" ? Is this only solution? Tag: Problem with eboog Tag: 52564
  - 10
    - makeimg: FATAL ERROR: Hi All I am trying to build french an spanish language from command line using platform builder 4.2. If i build english version from command line it builds fine. If i try to build spanish or french language i get the following error makeimg: FATAL ERROR: Must set a supported 4-digit locale code makeimg: FATAL ERROR: Must set a supported 4-digit locale code I had verified that LOCALE variable is still defined correct Need help Tag: Problem with eboog Tag: 52562
  - 11
    - Kitl connection doesn't.. Hello all. I have a headless SH4 platform, and am attempting to get CE4.2 running on it. The hardware is brand new, so it could be a hardware problem of sorts. Basically, I get to a point in the debug where everything just stops. Don't get error messages at all and looking into the device with an ice it appears to still be running (it does not appear to totally step into the weeds). The following is the last portion of my debug dump. What would be a good place for me to look into? I am not positive on how the interrupts are tied from the 91c111 to the processor, but I don't think it is using interrupts at this point yet (they appear to be enabled later in the game) Appreciate any help. Regards, Remco /// debug dump from serial port Host connected Host IP: 165.88.81.123, port 2588 KeyIndex 0 = -1 KeyIndex 1 = -1 KeyIndex 2 = -1 KeyIndex 3 = -1 KeyIndex 4 = -1 KeyIndex 5 = -4194305 KeyIndex 6 = -4194305 KeyIndex 7 = -1 +KITLRegisterDfltClient, service:0 +KITLRegisterDfltClient, service:1 KITLGlobalState == 0x61 KITL Initialized Waiting for service 'DBGMSG' to connect..., fUseSysCalls = 0 ProcessAdminMsg: Receive Config message for service DBGMSG ProcessAdminMsg: Receive Config message for service PPSH ProcessAdminMsg: Receive Config message for service DBGMSG SH3Init done. //// ethernet debug on platform builder My PC's debug shows: <only latter part shown> 0 PID:0 TID:0 IntrPrio[109] = 00000001 0 PID:0 TID:0 IntrPrio[110] = 00000001 0 PID:0 TID:0 IntrPrio[111] = 00000001 0 PID:0 TID:0 DMAUCR = 0x00020000 0 PID:0 TID:0 PHCR (before)= 0x003c 0 PID:0 TID:0 PHCR (after) = 0x0000 0 PID:0 TID:0 Booting Windows CE version 4.20 for (SH-4) 0 PID:0 TID:0 &pTOC = 8c057680, pTOC = 8d483ad4, pTOC->ulRamFree = 8d4bd000, MemForPT = 00000000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 Configuring: Primary pages: 11071, Secondary pages: 0, Filesystem pages = 5535 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: 8d4be000, extension: 00003000, length: 02b3f000 1 PID:0 TID:0 Windows CE KernelInit Tag: Problem with eboog Tag: 52551
  - 12
    - Porting English application to Chinese Hello all. I have a custom XScale board and WinCE 4.1 in a kiosk application. Basically, dialogs are displayed listing options and the user presses buttons to make selections. Right now, my interface is in USA English. I have been asked what it would take to support Chinese. Man, I don't even know where to begin! Can someone point me at any resources I can study - something like "programming a Chinese GUI for dummies"? Are there any books or articles about migrating an application from English to Chinese? Any help would be appreciated, Matt Tag: Problem with eboog Tag: 52547
  - 13
    - BIOS boot loader splash screen, invalid image Can anyone help resolve a problem with a BIOS boot loader? I am trying to display a splash screen from a BIOS boot loader (BLDR) on a Geode based SBC running Windows CE .NET (4.2). I have explored the posts in the newsgroup on microsoft.public.windowsce.platformbuilder. In a post dated 8/21/2003 (see URL below) code to perform this task was graciously provided. I have added the code to main.c and verified the statup.asm (x86 based SBC) initalizes the video. The BLDR builds with no errors or warnings. The BLDR is then transfered to a Compact Flash card using MKDISK and the CE .NET OS is copied to the CF card I converted a BMP file to a raw image file (as suggested by a previous post) with a simple convetor (bmp2raw.exe) found on the internet. When the SBC is powered on the system boots properly, except no image is displayed when the BLDR is executing. The system was powered down and I then modifed main.c by changing SPLASH.IMG to SPLASH.BMP. A new BLDR file was built and flashed to the CF card. The SPLASH.BMP file was also added to the CF card. When the system boots two lines across the top of the screen display multi-colored pixels until the OS starts, indicating to me that an image is attempting to load but is in the wrong format I think I am close to making this work but can't get the image converted correctly. Any help is greatly appreciated URL for previous post containing BLDR code http://groups.google.de/groups?hl=de&lr=&ie=UTF-8&oe=UTF-8&threadm=044b01c3599e%24f1295af0%24a401280a%40phx.gbl&rnum=2&prev=/groups%3Fq%3DErik%2Bboot%2Bsplash%2Bgroup:microsoft.public.windowsce.platbuilder.*%26hl%3Dde%26lr%3D%26ie%3DUTF-8%26oe%3DUTF-8%26group%3Dmicrosoft.public.windowsce.platbuilder.*%26selm%3D044b01c3599e%2524f1295af0%2524a401280a%2540phx.gbl%26rnum%3D2 Tag: Problem with eboog Tag: 52546
  - 14
    - IE 6 context menu Hi All, Does any one know how to make change to the Context menu for the Vertical Scroll bar in IE6. It displays wrong items. It displays the following: Scroll Here --> This is correct Left Edge --> It should read "Top Edge" Right Edge --> It should read "Bottom Edge" Page Left --> It should read "Page Up" Page Right --> It should read "Page Down" Scroll Left --> It should read "Scroll Up" Scroll Right --> It should read "Scroll Down" Thanks Tag: Problem with eboog Tag: 52543
  - 15
    - Hard disk problem I've got a problem with my hard disk. I tried the procedure found in MSDN. I added the driver as explained, but it's not working. Does anybody have a link to a walkthrougth or a website. Thanks Jeff Burroughs Autolog Tag: Problem with eboog Tag: 52535
  - 16
    - Boot fails !!! Hi everybody, my CPU card, based on the Lubbock platform, boot since the data are sent to the display hardware (B&W LCD) and seem to wait something without crash. The debug output is (sorry for the listing) : Kernel debugger is waiting to connect with target. 0 PID:0 TID:0 Booting Windows CE version 4.20 for (ARM) 0 PID:0 TID:0 &pTOC = 800c245c, pTOC = 811d5380, pTOC->ulRamFree = 81222000, MemForPT = 00000000 0 PID:0 TID:0 Old or invalid version stamp in kernel structures - starting clean! 0 PID:0 TID:0 Configuring: Primary pages: 10898, Secondary pages: 0, Filesystem pages = 5449 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: 81223000, extension: 00003000, length: 02a92000 0 PID:0 TID:0 Sp=ffffc7cc 2 PID:0 TID:0 Windows CE KernelInit 4294767296 PID:3cb7002 TID:3cb7262 Updated eptr->e32_vsize to = 000b6000 4294767309 PID:3cb7002 TID:3cb7262 Scheduling the first thread. 4294767321 PID:3cb7002 TID:3cb7262 0x83cb7024: KernelInit2: pCurThread=83cb7024 hCurThread=03cb7262 hCurProc=03cb7002, KernelInit = 800dc3e4 4294767336 PID:3cb7002 TID:3cb7262 0x83cb7024: Detecting VFP... 4294767344 PID:3cb7002 TID:3cb7262 0x83cb7024: VFP Not Found! 4294767351 PID:3cb7002 TID:3cb7262 0x83cb7024: Updated eptr->e32_vsize to = 00016000 4294767363 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module NK.EXE at address 0x800B8000-0x8016E000 (RW data at 0x811E6000-0x8121AD2B) Kernel debugger connected (KDBG stream opened). Kernel Version 1169 loaded at 0x800b8000, data relocated at 0x811e6000 Debugger connection established (Target CPU is ARM). Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\NK.EXE' Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\KD.DLL' Finished re-loading kernel modules. Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CELOG.DLL' Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\COREDLL.DLL' Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\FILESYS.EXE' 4294767383 PID:3cb7002 TID:3cb7262 0x83cb7024: Updated eptr->e32_vsize to = 00005000 4294767393 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module celog.dll at address 0x80188000-0x8018D000 (RW data at 0x812214B0-0x812219F0) 4294767410 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLogInit 4294767418 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog: Large buffer size unspecified, using default size 4294767430 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog: Small buffer size invalid or unspecified, using default size 4294767442 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog: Large buffer size = 131072 4294767451 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog: Small buffer size = 4096 4294767467 PID:3cb7002 TID:3cb7262 0x83cb7024: -CeLogInit 4294767475 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog Zones : CE = 0xFFBFFFFF, User = 0xFFBFFFFF, Proc = 0xFFFFFFFF 4294767487 PID:3cb7002 TID:3cb7262 0x83cb7024: CeLog is now live! 4294767496 PID:3cb7002 TID:3cb7262 0x83cb7024: first = 01eb0000, last = 02000000, SharedDllBase = 030c0000 4294767562 PID:3cb7002 TID:3cb7262 0x83cb7024: >>> Loading module coredll.dll at address 0x03F10000-0x03FF5000 (RW data at 0x01FFF000-0x01FFFFB8) 4294767616 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: >>> Loading module filesys.exe at address 0x04010000-0x0408A000 4294767646 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: FileSystem Starting - starting with clean file system 4294770664 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: >>> Loading module fsdmgr.dll at address 0x03DB0000-0x03DCD000 (RW data at 0x01FEE000-0x01FEE760) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\FSDMGR.DLL' 4294770712 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: InitSharedHeap: 42100000 10000 c 4294770724 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: InitSharedHeap: return 42100060 4294771187 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: FSREG: Logging in default user. 4294771199 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: SetCurrentUser: Logging out (nobody), logging in default 4294771210 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: FS: Using default path "\profiles\" 4294771240 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: SetCurrentUser: User hives not supported -- using same registry for all users 4294771255 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: FS: Using default path "Windows\" 4294775244 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: FS: Using default path "Windows\" 4294775315 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: Initializing Database 4294775349 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: DB:Validation: Name already exists DB_notify_events 4294775360 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: DB:CeCreateDatabase failed 4294775382 PID:43c7dd82 TID:43c7dd5e 0x83c7db20: Filesystem initialized! 4294775393 PID:3cb7002 TID:83c7ff8e 0x83c7d63c: InitializeJit 4294775401 PID:3cb7002 TID:83c7ff8e 0x83c7d63c: InitMUI: DISABLED (-1039664360) 4294775483 PID:23c590fe TID:23c7dafe 0x83c593e8: InitSharedHeap: 42100000 0 c 4294775492 PID:23c590fe TID:23c7dafe 0x83c593e8: InitSharedHeap: return 42100060 4294775525 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module pm.dll at address 0x03EE0000-0x03EFD000 (RW data at 0x01FFB000-0x01FFB6C4) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\PM.DLL' 4294775542 PID:23c590fe TID:23c7dafe 0x83c593e8: *** Power Manager: DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x23c590fe *** 4294775557 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module device.exe at address 0x06010000-0x06020000 Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\DEVICE.EXE' 4294775608 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ceddk.dll at address 0x03DA0000-0x03DA6000 (RW data at 0x01FEC000-0x01FEC068) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CEDDK.DLL' 4294775625 PID:23c590fe TID:23c7dafe 0x83c593e8: Ceddk!CalibrateStallCounter: Enter 4294775647 PID:23c590fe TID:23c7dafe 0x83c593e8: Ceddk!CalibrateStallCounter: Could not find stall counter 4294775658 PID:23c590fe TID:23c7dafe 0x83c593e8: Ceddk!BeginCalibration: min(368) max(460) 4294775670 PID:23c590fe TID:23c7dafe 0x83c593e8: Ceddk!BeginCalibration: elapsed is 408 4294775681 PID:23c590fe TID:23c7dafe 0x83c593e8: Ceddk!BeginCalibration: delay is 9 4294775694 PID:23c590fe TID:23c7dafe 0x83c593e8: +PmInit 4294775701 PID:23c590fe TID:23c7dafe 0x83c593e8: +PlatformValidatePMRegistry 4294775723 PID:23c590fe TID:23c7dafe 0x83c593e8: -PlatformValidatePMRegistry: returning 0 4294775736 PID:23c590fe TID:23c7dafe 0x83c593e8: DeviceListsInit: default GUID found in registry as expected 4294775748 PID:23c590fe TID:23c7dafe 0x83c593e8: DeviceListCreate: creating list entry for class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 4294775769 PID:23c590fe TID:23c7dafe 0x83c593e8: PlatformDeviceListInit: using stream interface to access class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 4294775784 PID:23c590fe TID:23c7dafe 0x83c593e8: DeviceListCreate: creating list entry for class 98c5250d-c29a-4985-ae5f-afe5367e5006 4294775805 PID:23c590fe TID:23c7dafe 0x83c593e8: PlatformDeviceListInit: using stream interface to access class 98c5250d-c29a-4985-ae5f-afe5367e5006 4294775820 PID:23c590fe TID:23c7dafe 0x83c593e8: DeviceListCreate: creating list entry for class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 4294775840 PID:23c590fe TID:23c7dafe 0x83c593e8: PlatformDeviceListInit: using display interface to access class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 4294775857 PID:23c590fe TID:23c7dafe 0x83c593e8: InitDisplayDeviceInterface: returning 1 4294775869 PID:23c590fe TID:23c7dafe 0x83c593e8: DeviceListCreate: creating list entry for class a32942b7-920c-486b-b0e6-92a702a99b35 4294775889 PID:23c590fe TID:23c7dafe 0x83c593e8: PlatformDeviceListInit: using stream interface to access class a32942b7-920c-486b-b0e6-92a702a99b35 4294775908 PID:23c590fe TID:23c47e8e 0x83c7d63c: +PnpThreadProc: thread 0x23c47e8e 4294775931 PID:23c590fe TID:23c47fde 0x83c43400: +ResumeThreadProc: thread 0x23c47fde 4294775946 PID:23c590fe TID:23c47f6a 0x83c43a3c: +ActivityTimersThreadProc: thread 0x23c47f6a 4294775973 PID:23c590fe TID:23c47f6a 0x83c43a3c: ActivityTimerCreate: ActivityTimerCreate('UserActivity') returning 0x00000000 4294775996 PID:23c590fe TID:23c47f6a 0x83c43a3c: ActivityTimerCreate: ActivityTimerCreate('SystemActivity') returning 0x00000000 4294776015 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: +SystemThreadProc: thread 0xa3c43c7a 4294776029 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: +PlatformManageSystemPower 4294776052 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: PlatformPMActivelyManagesPower: returning 1 4294776069 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: PlatformManageSystemPower: waiting for initialization to complete 4294776082 PID:23c590fe TID:83c43d52 0x83c3d4a8: +BatteryMonitorThreadProc: thread 0x83c43d52 4294776095 PID:23c590fe TID:83c43d52 0x83c3d4a8: BatteryMonitorThreadProc: battery interface APIs not available, exiting 4294776108 PID:23c590fe TID:83c43d52 0x83c3d4a8: -BatteryMonitorThreadProc: exiting 4294776119 PID:23c590fe TID:23c7dafe 0x83c593e8: -PmInit: returning 1 4294776145 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: PlatformManageSystemPower: initialization complete 4294776161 PID:23c590fe TID:a3c43c7a 0x83c3fd6c: PlatformLoadTimeouts: ACUserIdle 60000, ACSystemIdle 300000, ACSuspend -1, BattUserIdle 60000, BattSystemIdle 180000, BattSuspend 300000 4294776181 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!DevloadInit 4294776194 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 4294776205 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn) entered 4294776243 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module regenum.dll at address 0x03F00000-0x03F07000 (RW data at 0x01FFD000-0x01FFD4A4) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\REGENUM.DLL' 4294776326 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PCMCIA) entered 4294776375 PID:43c7dd82 TID:e3c60a5a 0x83c7d89c: >>> Loading module psmfsd.dll at address 0x030D0000-0x03104000 (RW data at 0x01F4A000-0x01F5A870) Loaded 'psmfsd.dll', no matching symbolic information found. 4294776393 PID:43c7dd82 TID:e3c60a5a PSMFSD:DLL Process Attach 4294779447 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module pcmcia.dll at address 0x03140000-0x03166000 (RW data at 0x01F5E000-0x01F5EB70) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\PCMCIA.DLL' 4294779464 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA.DLL DLL_PROCESS_ATTACH 4294781639 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIADriverInit: Done!. 4294781662 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 0 (16 bit Attribute window on socket 0) 4294781678 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 1 (16 bit Attribute window on socket 1) 4294781694 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 2 (16 bit Common window on socket 0) 4294781709 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 3 (16 bit Common window on socket 1) 4294781725 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 4 (8 bit I/O window on socket 0) 4294781739 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 5 (8 bit I/O window on socket 1) 4294781754 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 6 (16 bit I/O window on socket 0) 4294781769 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:InitWindowInfo: Window 7 (16 bit I/O window on socket 1) 4294781782 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA: 8 memory windows in the system 4294781791 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA Windows: 4294781799 PID:23c590fe TID:23c7dafe 0x83c593e8: 7 4294781805 PID:23c590fe TID:23c7dafe 0x83c593e8: 6 4294781812 PID:23c590fe TID:23c7dafe 0x83c593e8: 5 4294781818 PID:23c590fe TID:23c7dafe 0x83c593e8: 4 4294781824 PID:23c590fe TID:23c7dafe 0x83c593e8: 3 4294781831 PID:23c590fe TID:23c7dafe 0x83c593e8: 2 4294781837 PID:23c590fe TID:23c7dafe 0x83c593e8: 1 4294781843 PID:23c590fe TID:23c7dafe 0x83c593e8: 0 4294781850 PID:23c590fe TID:23c7dafe 0x83c593e8: 4294781859 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:GetPCMCIAThreadPriority - RegQueryValueEx(Priority256) failed 2 4294781879 PID:23c590fe TID:23c7dafe 0x83c593e8: PCMCIA:StatusChangeThread = 0xa3c1ff6a, IREQThread = 0xa3c1cf7e, CallbackThread = 0xa3c1ff8e 4294781896 PID:23c590fe TID:23c7dafe 0x83c593e8: PNP interface class {6BEAB08A-8914-42fd-B33F-61968B9AAB32} (PCMCIA Card Services) ATTACH 4294781922 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\Serial) entered 4294781973 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module xsc1bd_serial.dll at address 0x03110000-0x03135000 (RW data at 0x01F5C000-0x01F5C608) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\XSC1BD_SERIAL.DLL' 4294782017 PID:23c590fe TID:23c7dafe 0x83c593e8: ??????????????????+HW_XSC1_INIT, 0x30D60 :Reiniting UART for 38400 8N1 mode !!! 4294782040 PID:23c590fe TID:23c7dafe 0x83c593e8: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH 4294782065 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\NDIS) entered 4294782145 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module cxport.dll at address 0x03CE0000-0x03CEB000 (RW data at 0x01FE2000-0x01FE27FC) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CXPORT.DLL' 4294782179 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ndis.dll at address 0x03B30000-0x03B8F000 (RW data at 0x01FC8000-0x01FC8BB4) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\NDIS.DLL' 4294782239 PID:23c590fe TID:23c7dafe 0x83c593e8: NDIS: RebindAdaptersOnResume = 0 4294782300 PID:23c590fe TID:63c0523e 0x83c05708: PNP interface class {6BEAB08A-8914-42fd-B33F-61968B9AAB32} (PCMCIA Card Services) ATTACH 4294782317 PID:23c590fe TID:63c0523e 0x83c05708: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH 4294782332 PID:23c590fe TID:63c0523e 0x83c05708: NDIS: +ProcessPcmciaDeviceNotificationMessages 4294782752 PID:23c590fe TID:23c7dafe 0x83c593e8: PNP interface class {A32942B7-920C-486b-B0E6-92A702A99B35} (NDS0:) ATTACH 4294782802 PID:23c590fe TID:63c0523e 0x83c05708: NDIS: -ProcessPcmciaDeviceNotificationMessages 4294782821 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\TAPI) entered 4294782887 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module tapi.dll at address 0x03A00000-0x03A49000 (RW data at 0x01FB9000-0x01FB9C08) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\TAPI.DLL' 4294782942 PID:23c590fe TID:23c7dafe 0x83c593e8: TAPIStartup: LoadLibrary(unimodem.dll) failed, err=x7e 4294783026 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module afd.dll at address 0x03B90000-0x03BC2000 (RW data at 0x01FCA000-0x01FCAEB8) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\AFD.DLL' 4294783068 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ppp.dll at address 0x03CF0000-0x03D42000 (RW data at 0x01FE4000-0x01FE4D68) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\PPP.DLL' 4294783117 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module tcpstk.dll at address 0x03A50000-0x03B10000 (RW data at 0x01FBB000-0x01FC2E50) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\TCPSTK.DLL' 4294783135 PID:23c590fe TID:23c7dafe 0x83c593e8: TCPIP: dllentry() 4294783170 PID:23c590fe TID:23c7dafe 0x83c593e8: EAP: ERROR - unable to find Dll netlog.dll 4294783223 PID:23c590fe TID:23c7dafe 0x83c593e8: EAP: ERROR - unable to find Dll eap.dll 4294783236 PID:23c590fe TID:23c7dafe 0x83c593e8: InitRcvs s_FreePRcvLock 1FCA69C 4294783245 PID:23c590fe TID:23c7dafe 0x83c593e8: InitNotifyObjects: s_FreeNotifyLock 1FCA674 4294783255 PID:23c590fe TID:3bfef9e 0x83bf9000: PNP interface class {6BEAB08A-8914-42fd-B33F-61968B9AAB32} (PCMCIA Card Services) ATTACH 4294783275 PID:23c590fe TID:3bfef9e 0x83bf9000: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH 4294783294 PID:23c590fe TID:3bfef9e 0x83bf9000: PNP interface class {A32942B7-920C-486b-B0E6-92A702A99B35} (NDS0:) ATTACH 4294783347 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPI:AddTapiDevice: GetDeviceKeys(PCMCIA Card Services) returned 1200 4294783460 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD:AfdInitialize: Can't open Registry key Comm\AFD -- creating 'Stacks' entry 4294783487 PID:23c590fe TID:23c7dafe 0x83c593e8: TCPIP.Register() 4294783494 PID:23c590fe TID:23c7dafe 0x83c593e8: +IPInit() 4294783503 PID:23c590fe TID:23c7dafe 0x83c593e8: +IPGetConfig 4294783542 PID:23c590fe TID:23c7dafe 0x83c593e8: -IPGetConfig: Ret: 0x170070 4294783589 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPI:OldAddTapiDevice - This BSP is loading TSPs by old method!!! Change registry settings to use new way!!! 4294783634 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPIStartup: LoadLibrary(Unimodem.dll) failed, err=x7e 4294783783 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 4294783828 PID:23c590fe TID:23c7dafe 0x83c593e8: IPInit: Unable to Load IPSEC 4294783898 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ws2.dll at address 0x03C90000-0x03CA2000 (RW data at 0x01FDC000-0x01FDCAE8) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\WS2.DLL' 4294783924 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module iphlpapi.dll at address 0x03CC0000-0x03CDC000 (RW data at 0x01FE0000-0x01FE0C50) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\IPHLPAPI.DLL' 4294783964 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module winsock.dll at address 0x03CB0000-0x03CB6000 (RW data at 0x01FDE000-0x01FDE084) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\WINSOCK.DLL' 4294783981 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module autoras.dll at address 0x03B10000-0x03B17000 (RW data at 0x01FC4000-0x01FC450C) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\AUTORAS.DLL' 4294784023 PID:23c590fe TID:23c7dafe 0x83c593e8: IGMPDelInclList: AddrPtr=170ca0 NumDelSources=0 DelSourceList=0 4294784035 PID:23c590fe TID:23c7dafe 0x83c593e8: -IPInit [SUCCESS] 4294784043 PID:23c590fe TID:23c7dafe 0x83c593e8: +TCPGetConfigInfo 4294784079 PID:23c590fe TID:23c7dafe 0x83c593e8: -TCPGetConfigInfo 4294784102 PID:23c590fe TID:23c7dafe 0x83c593e8: *InitTCB: SetIdleTimerReset 4294784135 PID:23c590fe TID:23c7dafe 0x83c593e8: +IPD_Init(0) 4294784146 PID:23c590fe TID:23c7dafe 0x83c593e8: +TCP_Init(0) 4294784153 PID:23c590fe TID:23c7dafe 0x83c593e8: TCPIP.About to register 4294784202 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'tcpip6.dll' 4294784241 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'irdastk.dll' 4294784279 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'btd.dll' 4294784318 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Netbios.dll' 4294784355 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Redir.dll' 4294784393 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Dhcp.dll' 4294784432 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'IPNat.dll' 4294784471 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ws2instl.dll at address 0x03C80000-0x03C86000 (RW data at 0x01FDA000-0x01FDA04C) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\WS2INSTL.DLL' 4294784497 PID:23c590fe TID:23c7dafe 0x83c593e8: Ws2Instl dllentry() -2084692500 4294784543 PID:23c590fe TID:23c7dafe 0x83c593e8: Ws2Instl:IsStackInstalled - LoadLibrary(irdastk) failed 126 4294784588 PID:23c590fe TID:23c7dafe 0x83c593e8: Ws2Instl:IsStackInstalled - LoadLibrary(btd) failed 126 4294784634 PID:23c590fe TID:23c7dafe 0x83c593e8: Ws2Instl:IsStackInstalled - LoadLibrary(tcpip6) failed 126 4294784698 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ssllsp.dll at address 0x03C40000-0x03C54000 (RW data at 0x01FD3000-0x01FD400C) 4294784708 PID:23c590fe TID:83c0befa 0x83bf2448: IPTimer: setting IPTimer of NTE 170160 to 0 4294784721 PID:23c590fe TID:83c0befa 0x83bf2448: *IPTimeout: NOT restarting IPTimeout Timer for NTE 170160 Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\SSLLSP.DLL' 4294784789 PID:23c590fe TID:23c7dafe 0x83c593e8: *TCPIP:ReadyToGo 4294784797 PID:23c590fe TID:23c7dafe 0x83c593e8: +ARPInit() 4294784827 PID:23c590fe TID:23c7dafe 0x83c593e8: -ARPInit [0] 4294784864 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'tcpip6.dll' 4294784902 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'irdastk.dll' 4294784943 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'btd.dll' 4294784980 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Netbios.dll' 4294785018 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Redir.dll' 4294785057 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'Dhcp.dll' 4294785095 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to load library 'IPNat.dll' 4294785105 PID:23c590fe TID:23c7dafe 0x83c593e8: !AFD: Unable to GetProcAddress of ReadyToGo in 'Ws2Instl' 4294785116 PID:23c590fe TID:23c7dafe 0x83c593e8: AFD: Initialization Complete 4294785139 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\sdmmcloader) entered 4294785193 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!StartOneDriver RegisterDevice(SML, 1, sdmmc_loader.dll, 0x602ee68) failed 4294785229 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\autoras) entered 4294785254 PID:23c590fe TID:23c7dafe 0x83c593e8: AUTORAS:: ARS_Init().. 4294785269 PID:23c590fe TID:23c7dafe 0x83c593e8: AUTORAS:: Reg[Dialer] = [rnaapp.exe] 4294785282 PID:23c590fe TID:23c7dafe 0x83c593e8: AUTORAS:: Reg[RasEntryOpt] = [-e] 4294785295 PID:23c590fe TID:23c7dafe 0x83c593e8: AUTORAS:: Reg[NoPromptOpt] = [-p] 4294785337 PID:23c590fe TID:23c7dafe 0x83c593e8: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (ARS1:) ATTACH 4294785405 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\NdisPower) entered 4294785470 PID:23c590fe TID:23c7dafe 0x83c593e8: >>> Loading module ndispwr.dll at address 0x03B20000-0x03B26000 (RW data at 0x01FC6000-0x01FC6514) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\NDISPWR.DLL' 4294785500 PID:23c590fe TID:23c7dafe 0x83c593e8: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (NPW1:) ATTACH 4294785540 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 4294785602 PID:23c590fe TID:3bfef9e 0x83bf9000: TAPI:OldAddTapiDevice RegQueryValueEx(Tsp) returned 2 4294785652 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\FlshDrv) entered 4294785667 PID:23c590fe TID:23c7dafe 0x83c593e8: DEVICE!StartOneDriver RegQueryValueEx(Drivers\BuiltIn\FlshDrv\DllName) returned 2 4294785814 PID:23c7dada TID:23bb8f6e 0x83bb0000: InitSharedHeap: 42100000 0 c 4294785823 PID:23c7dada TID:23bb8f6e 0x83bb0000: InitSharedHeap: return 42100060 4294785834 PID:23c7dada TID:23bb8f6e 0x83bb0000: >>> Loading module gwes.exe at address 0x08010000-0x08180000 Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\GWES.EXE' 4294785871 PID:23c7dada TID:23bb8f6e 0x83bb0000: Grow Gdi handle table from 0 to 64 4294785958 PID:23c7dada TID:23bb8f6e 0x83bb0000: >>> Loading module ddi.dll at address 0x031A0000-0x031D0000 (RW data at 0x01F64000-0x01F684B8) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\DDI.DLL' 4294786055 PID:23c7dada TID:23bb8f6e 0x83bb0000: InitializeDisplayHardware Complete 4294786185 PID:23c7dada TID:23bb8f6e 0x83bb0000: Bits-per-pixel: 16 4294786243 PID:23c7dada TID:23bb8f6e 0x83bb0000: Adding font resource '\Windows\tahoma.ttf'... 4294786290 PID:23c7dada TID:23bb8f6e 0x83bb0000: **** Signature of FONT File is: '0100'... 4294786361 PID:23c7dada TID:23bb8f6e 0x83bb0000: Creating secondary frame buffer for POR and SaveBits 4294786534 PID:23c7dada TID:23bb8f6e 0x83bb0000: >>> Loading module kbdmouse.dll at address 0x03170000-0x03185000 (RW data at 0x01F60000-0x01F60D54) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\KBDMOUSE.DLL' 4294786553 PID:23c7dada TID:23bb8f6e 0x83bb0000: Layout Manager : DLL_PROCESS_ATTACH 4294786566 PID:23c7dada TID:23bb8f6e 0x83bb0000: PS2_SA11X1_Entry: Initialize PS2 ID 0 4294786578 PID:23c7dada TID:23bb8f6e 0x83bb0000: PS2Port::initialize 4294786590 PID:23c7dada TID:23bb8f6e 0x83bb0000: ReadRegDWORD(): HARDWARE\DEVICEMAP\KEYBD -> KbBase is -1083176448 (0xbf700a00) 4294786608 PID:23c7dada TID:23bb8f6e 0x83bb0000: ReadRegDWORD(): HARDWARE\DEVICEMAP\MOUSE -> MouseBase is -1083175936 (0xbf700c00) 4294786627 PID:23c7dada TID:23bb8f6e 0x83bb0000: ReadRegDWORD(): HARDWARE\DEVICEMAP\KEYBD -> PllBase is -1083178496 (0xbf700200) 4294786682 PID:23c590fe TID:23b18f72 0x83b18d34: PNP interface class {6BEAB08A-8914-42fd-B33F-61968B9AAB32} (PCMCIA Card Services) ATTACH 4294786699 PID:23c590fe TID:23b18f72 0x83b18d34: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (COM1:) ATTACH 4294786715 PID:23c590fe TID:23b18f72 0x83b18d34: PNP interface class {A32942B7-920C-486b-B0E6-92A702A99B35} (NDS0:) ATTACH 4294786733 PID:23c590fe TID:23b18f72 0x83b18d34: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (ARS1:) ATTACH 4294786748 PID:23c590fe TID:23b18f72 0x83b18d34: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (NPW1:) ATTACH 4294786804 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeyboardCommandPut Error ff 4294786813 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeyboardCommandPut Error f0 4294786968 PID:23c7dada TID:23bb8f6e 0x83bb0000: MouseCommandPut Error. Received 0xff instead of 0xfa 4294786979 PID:23c7dada TID:23bb8f6e 0x83bb0000: MouseCommandPut Error. Received 0xf2 instead of 0xfa 4294786990 PID:23c7dada TID:23bb8f6e 0x83bb0000: MouseTest fails. Mouse probably not present. 4294787001 PID:23c7dada TID:23bb8f6e 0x83bb0000: Ps2Port::Initialize Complete 4294787171 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeyboardCommandPut Error b4 4294787181 PID:23c7dada TID:23bb8f6e 0x83bb0000: PS2_SA11X1_Entry: Initialization complete 4294787191 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeybdDriverInitializeEx: Initialized PDD 0 - PS/2 SA11X1 (Mask 2) 4294787230 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeybdDriverInitializeEx: Found default input method 00000409 4294787266 PID:23c7dada TID:23bb8f6e 0x83bb0000: KeybdDriverInitializeEx: Layout Manager successfully initialized 4294787277 PID:23c7dada TID:23b15696 0x83b15bb0: ReadRegDWORD: RegQueryValueEx(Priority256) returned 2 4294787396 PID:23c7dada TID:23b15696 0x83b15bb0: ReadRegDWORD(): HARDWARE\DEVICEMAP\KEYBD -> SysIntr is 16 (0x10) 4294787411 PID:23c7dada TID:23b15696 0x83b15bb0: Enabling the keyPad Intr 4294787422 PID:23c7dada TID:23b15696 0x83b15bb0: ReadRegDWORD: RegQueryValueEx(EnableWake) returned 2 4294787627 PID:23c7dada TID:23bb8f6e 0x83bb0000: Could not find touch driver dll. 4294787702 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom Low Pages: 0020 Bytes: 00020000 4294787712 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom Critical Pages: 0014 Bytes: 00014000 4294787723 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom Low Block Pages: 0004 Bytes: 00004000 4294787733 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom Critical Block Pages: 0002 Bytes: 00002000 4294787744 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom App Wait 8000 (dec ms) 4294787762 PID:23c7dada TID:a3b0f24e 0x83b0f670: Grow Gdi handle table from 64 to 128 4294787858 PID:23c7dada TID:23bb8f6e 0x83bb0000: Oom AutoOom 0 4294787873 PID:23c7dada TID:23bb8f6e 0x83bb0000: UpdateIdleTimeoutFromRegistry 4294787929 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::NotifyInit thread 4294787940 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::MakeDatabases 4294787950 PID:43c7dd82 TID:e3b0fcde 0x83b0aa3c: DB:OpenDB fail: DB DB_notify_queue not found 4294787961 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::MakeDatabases::Creating DB for timing notifications 4294787977 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::MakeDatabases::Opened DB for timing notifications 4294787991 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::MakeDatabases::Opened DB for system event associations 4294788003 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::MakeSynchPrimitives 4294788013 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::StartUI 4294788024 PID:23c7dada TID:a3b0af92 0x83b05400: NOTIFICATION::UIThreadProc::UI thread started. Creating UI... 4294788123 PID:a3b058c2 TID:a3c59aa6 0x83b05684: InitSharedHeap: 42100000 0 c 4294788132 PID:a3b058c2 TID:a3c59aa6 0x83b05684: InitSharedHeap: return 42100060 4294788162 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module ole32.dll at address 0x038F0000-0x03949000 (RW data at 0x01FB0000-0x01FB1518) 4294788172 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::StartAlarm 4294788287 PID:23c7dada TID:e3b0fcde 0x83b0aa3c: NOTIFICATION::Constructor::Setting event semaphore Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\OLE32.DLL' 4294788324 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module oleaut32.dll at address 0x038A0000-0x038EE000 (RW data at 0x01FAE000-0x01FAEEE8) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\OLEAUT32.DLL' 4294788383 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module commctrl.dll at address 0x03E10000-0x03ECF000 (RW data at 0x01FF6000-0x01FF6AE8) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\COMMCTRL.DLL' 4294788465 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module aygshell.dll at address 0x03330000-0x03349000 (RW data at 0x01F7E000-0x01F7E798) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\AYGSHELL.DLL' 4294788591 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module shcore.dll at address 0x032C0000-0x032C7000 (RW data at 0x01F7A000-0x01F7A068) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\SHCORE.DLL' 4294788609 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module ceshell.dll at address 0x032D0000-0x03325000 (RW data at 0x01F7C000-0x01F7CC00) Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CESHELL.DLL' 4294788708 PID:a3b058c2 TID:a3c59aa6 0x83b05684: >>> Loading module explorer.exe at address 0x0A010000-0x0A072000 Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\EXPLORER.EXE' 4294788727 PID:23c7dada TID:43b0563e 0x83afc8dc: NOTIFICATION::AlarmThreadProc::Alarm thread started. 4294788738 PID:23c7dada TID:43b0563e 0x83afc8dc: NOTIFICATION::ProcessDatabase::Starting Database Sweep at 06/01/1999 11:26:30 for 01beac219e23d800 4294788754 PID:23c7dada TID:43b0563e 0x83afc8dc: NOTIFICATION::ProcessDatabase::Check wake-up validity/message retiring 4294788766 PID:23c7dada TID:43b0563e 0x83afc8dc: NOTIFICATION::ProcessDatabase::Wait FOREVER 4294788818 PID:43c7dd82 TID:a3c59aa6 0x83b05684: >>> Loading module cplmain.cpl at address 0x7FFB0000-0x7FFF3000 Loaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CPLMAIN.CPL' 4294788833 PID:43c7dd82 TID:a3c59aa6 0x83b05684: <<< Unloading module cplmain.cpl at address 0x7FFB0000-0x7FFF3000 Unloaded symbols for 'C:\WINCE420\PUBLIC\TEST\RELDIR\INTEL_DBPXA250_DEV_PLATFORMARMV4IDEBUG\CPLMAIN.CPL' 4294788881 PID:23c590fe TID:43c7dd5e 0x83c7db20: -DEVICE!DevloadPostInit 4294788913 PID:a3b058c2 TID:a3c59aa6 0x83b05684: Entering InitCapEdit 4294788929 PID:a3b058c2 TID:a3c59aa6 0x83b05684: CAPEDIT registered(49177) 4294788945 PID:a3b058c2 TID:a3c59aa6 0x83b05684: InitTTButton: 4294789160 PID:a3b058c2 TID:a3c59aa6 0x83b05684: Console NOT redirected for process 0x42 4294789631 PID:23c7dada TID:a3c59aa6 0x83b05684: Grow Gdi handle table from 128 to 192 4294790832 PID:43c7dd82 TID:a3c59aa6 0x83b05684: DB:OpenDB fail: DB \RecycleInfo not found I don't understand what append. Can anybody help me ? Olivier SPINELLI Tag: Problem with eboog Tag: 52534
  - 17
    - Bluetooth : how to get started? Hi there, Let me first explain what I want to achieve. I have a custom Xscale device with a bluetooth module. This bluetooth module should function as a cable replacement. In the end, I want to be able to TALK to the device through a desktop computer using hyperterminal. To achieve this, I have included the Bluetooth - Uart only driver in my image. In my debug trace, I can see eveything is going fine. On my IPAQ I can even see the device through the bluetooth manager. This leads me to believe that this is all going according to plan. However, when I try to connect to my custom device, no bluetooth services are exposed. This seems logical as no profiles have been loaded just yet. I'm a bit at loss now. Where do I go from here? Is there an easy way to include the serial port profile on the device? I have gone through the samples that are included in platform builder (especially the sdp ones) but I have no idea what to do next. Do I first try to add an SDP record to advertise the serial port? Is this necessary and if so, how to do it? I can't seem to find a lot of samples or feedback. Any pointers would really help... After that, I would probably need to set up the pairing procedure? After that, I should probably be able to emulate a serial port on the device (using the comtest sample). Does anyone know the procedure to set this up? Kind regards, Jean Tag: Problem with eboog Tag: 52533
  - 18
    - including WPA support for cisco radio I am trying to get WPA included in my image with all the sysgen parameters as found in "Creating a WPA-enabled Wireless Configuration for a CEPC" doc found on the Microsoft site. For some reason WPA is not included in the image when I install. I have even included the QFEs for WPA roaming with no avail. I have all 7 sysgen parameters in the document set and do have the cisco driver included in the image but just cannot set WPA. The only options available for authentication are "Open" and "Shared" I have PB 4.20 and a xscale CE device Any help would be appreciated. Tag: Problem with eboog Tag: 52532
  - 19
    - Runnig built sample Hi, I have built bluetooth samples for ARM by platform builder, but I'm unable to run it on real PPC. It tells "'phoneiu' is not a valid PocketPC application (it has GUI , not console). What should i do for running it? ------ Saman Tag: Problem with eboog Tag: 52531
  - 20
    - Migrating from Windows CE 4.0 to 4.2 Hi ALL, I am migrating Hitachi PFM-DS11 windows CE 4.0 platform builder to windows CE 4.2 according to the guidelines given on following URL http://msdn.microsoft.com/library/default.asp?url=/library/en-us/wcedsn40/html/cghowhowtomigratebsp.asp. On above URL there is mentioned that KErnel page size is to be incresed to 4K from 1K. "Enlarge the page sizes for SH3 and SH4 kernels from 1 KB to 4 KB, and then rebuild any application or device driver binary builds with a 1-KB page size. When you rebuild the binary builds, you enlarge the builds to a 4-KB page size. By performing this procedure, you ensure that the kernels load and run correctly on Windows CE .NET 4.2. Note In previous versions of Windows CE, the default page size for SHx kernels was 1 KB. If you do not enlarge the page size, any binary builds with a 1-KB page size will not run on the current version of Windows CE." I am not able to find any document/help on how to increase the kernel pagesize from 1K to 4K. Can anybody help me on this topic ??? Thanks in advance. regards, Rajesh Tag: Problem with eboog Tag: 52528
  - 21
    - How to modify the resource of File Open Dialog? Dear all I have a problem about the File Open Dialog in WinCE 4.20. It is bigger than my screen, so I want to modify its resource to fit the screen size I have finished the same thing to cplmain.rc. But I can not find the resource of File Open Dialog. Where is it I find a fileopen.res. It has the dialog. But I need its source code Help!!! Thanks!! Best Regards Jacky Tag: Problem with eboog Tag: 52527
  - 22
    - To Microsofts Support Team (Linksys WPC 11 driver question) Dear eMVP's and all other fellows, I know Windows CE4.2 supports the Linksys WPC11 v3.0 card. (Just by setting BSP_NIC_ISLP2NDS = 1) 1) But does this driver also support the Linksys WPC11 v4.0 card? 2) And if not, where can I found such a driver? Linksys tells me they don't support Windows CE and tell me to ask Microsoft itself. So here I am. 3) Will the final release of Windows CE 5.0 also support these 2 cards? Thanks for your support, Peter. Tag: Problem with eboog Tag: 52524
  - 23
    - how convert function address to physical address To guru how to convert address of my function to Physical Address and Virtual Address of smart phone best regard. Mr. Ni Tag: Problem with eboog Tag: 52523
  - 24
    - Handling GetTickCount wrap Seems like GetTickCount will wrap around after 49.7 days. What is the normal way to handle if it wraps around? Suppose I compare timestamps like this: DWORD dwStarted = GetTickCount(); DoLongRunningTask(); // Suppose GetTickCount has wrapped around here DWORD dwStopped = GetTickCount(); DWORD elapsed = dwStopped - dwStarted; Then this would fail if GetTickCount wraps around, since dwStopped<dwStarted, so elapsed would become "negative". I would like my platform to handle running longer than 49.7 days, so I guess I would need to cope with this. I guess the correct thing to do would be something like: DWORD elapsed; if (dwStopped >= dwStarted) { elapsed = dwStopped - dwStarted; } else { elapsed = MAXDWORD - (dwStarted - dwStopped); } Am I thinking right here? Do you people in general handle this, or simply ignore the problem? Tag: Problem with eboog Tag: 52522
  - 25
    - Display functionality during boot Hi, our current platform (based on ARMV4I) doesn´t have any functionality to let the user know that the OS is loading during boot time. Now we want to implement it and this is my task. :-) I took a first (dirty) approach trying to include all the display driver code into our boot routines and creating an instance of the class which implements the driver: static GPE *gpGPE = (GPE *)NULL; . . . gpGPE = new Epson(); The idea was to try to eliminate the code that did not work while booting (reading the registry and so on). Well, my first question is, it is a good approach? I mean, I have spent a lot of time trying to compile the code and I´m still receiving errors without knowing if without compilation errors is going to work. For example, the driver is written in C++, so I´m not sure if I can use the new operator, virtual functions and so on in my bootloader; I have read that I have to enable the MMU (?) or I have to implement my own heap (override the new and delete operator in the class code(?) ). At the end, basically my problem is that I am not sure the limitation (software) that I have while booting. The second question is, if the above approach is wrong, what would be the best way to implement it? Maybe some basic display functionality during booting and after that to let that the OS loads the real display driver? Thanks in advance for your help! Alexander Tag: Problem with eboog Tag: 52521
- Next
  - 1
    - Using SetPassword to change the system password Is it possible to use SetPassword in an application built with embedded Visual C++? Or does it have to be used in a function as part of the operating system (Win CE 4.2) I have tried adding the fspass component and create a SDK for embedded Visual C++, but I still don't have access to the SetPassword API Thx. Tag: Problem with eboog Tag: 52517
  - 2
    - Firewall IÂ´m trying to make a Firewall rule that blocks all OutBound traffic, but it isnÂ´t workin IÂ´m using Platform Builder 4.2 and IÂ´m adding this key to Platform.re [HKEY_LOCAL_MACHINE\COMM\Firewall\Rules\BlockOutbound "Mask"=dword:1 ; FWM_POR "Flags"=dword:11 ; FWF_BLOCK | FWF_OUTBOUN "PrivateHost"=hex:02,00 ; I didnÂ´t get how the firewall rules do work, what happens if I put two rules that conflicts (one for blocking and other one for allowing) Tag: Problem with eboog Tag: 52509
  - 3
    - required smartcard driver registry entries? I'm developing a smartcard reader driver under 4.20. So far I have not been able to successfully register my smartcard reader with the resource manager (as far as I can tell) The driver loads as a stream interface just fine. Interrupts are working etc. But when I try to access the registered reader list using SCardListReaders, it returns SCARD_E_NO_READERS_AVAILABLE The driver on startup calls SmartcardInitialize, which is successful, and prints this debug output SCI!SmartcardInitialize: Enter. Version 150, Mr1 032:24 2:2 SCI!SmartcardInitialize: Exi Shortly there after this debug output is printed PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (SMC1:) ATTAC (SMC1 being the device name) So, it seems like it successfully registered. But no such luck I read in the documentation that the following registry entry needs to exist [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\SmartCardDriver "Start"=dword: "Type"=dword: "Group"="Smart Card Reader "ErrorControl"=dword: The "SmartCardDriver" bit was italicized, so I assume it means to replace that with the name of the smartcard driver as exists under HKEY_LOCAL_MACHINE\Drivers\BuiltIn. (I've tried both ways) So here is my complete registry setup for this driver [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\smc "Prefix"="SMC "Dll"="smc.dll "Order"=dword: "Index"=dword: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\smc "Start"=dword: "Type"=dword: "Group"="Smart Card Reader "ErrorControl"=dword: Is that all I need in the registry to get the driver to register correctly with the resource manager? Or am I missing some initialization steps? I've been searching for quite a while on this, and haven't come up with anything. Any insight on where I should focus my debugging efforts would be greatly appriciated. Thanks Tag: Problem with eboog Tag: 52507
  - 4
    - Installing and binding NDIS IM Driver in Windows CE h I have written an NDIS intermediate driver that is to be placed below the protocol driver and above the miniport driver. Please tell me how can I install my IM Driver in the Windows CE environment. I do not know the registry entries that have to be created and the files in which these entries and the linkages are to be written. How do I tell the location where my IM Driver is to be placed regards Varun Varshne IIT Guwahati, India Tag: Problem with eboog Tag: 52503
  - 5
    - Remote Ip configuration I have a Geode Motherboard with an ethernet port. I need an TFTP to downloa files in a specific directory. My idea is modify the inital registry in the platform builder and change DHCP to static IP (ex: ip: 10.0.0.1 , mask: 0.0.0.0 gateway: 10.0.0.1 I am thinking in telnet service to modify the default static address by the "ip address that the client need for their local network. Somebody can explain me how to enabl the telnet service and how can i change the static ip remotely Thanks in advance Oscar Tag: Problem with eboog Tag: 52502
  - 6
    - ISR freeze Hi, I am trying to create a test application with eVC4 that manage a ISR Following the few examples found in internet I created these functions I call SetupMyInterrupt and after that I expect to see ThreadIST called by ISR. I can see the first START INTERRUPT called and only one INTERRUPT called after that the system freeze. What I am missing ? TIA DWORD SetupMyInterrupt( void ) { BOOL fRetVal; DWORD dwIrq = 5 ; DWORD dwThreadID; // Create an event // g_hevInterrupt = CreateEvent(NULL, FALSE, FALSE, NULL); if(!g_hevInterrupt) return 10; // Have the OAL Translate the IRQ to a system irq // fRetVal = KernelIoControl( IOCTL_HAL_TRANSLATE_IRQ, &dwIrq, sizeof( dwIrq ), &g_dwSysInt, sizeof( g_dwSysInt ), NULL ); if( !fRetVal ) return 11; // Create a thread that waits for signaling // g_htIST = CreateThread( NULL, // CE Has No Security 0, // No Stack Size ThreadIST, // Interrupt Thread NULL, // No Parameters CREATE_SUSPENDED, // Create Suspended until we are done &dwThreadID // Thread Id ); if( !g_htIST ) return 12; // Set the thread priority to real time // if( !CeSetThreadPriority( g_htIST, DEMO_IST_PRIORITY )) return 13; // Initialize the interrupt // if ( !InterruptInitialize(g_dwSysInt, g_hevInterrupt,NULL,0) ) return 14; return 0; } DWORD WINAPI ThreadIST( LPVOID lpvParam ) { DWORD dwStatus, g_dwInterruptCount = 0 ; TRACE1("START INTERRUPT %x", 5); while( g_fRun ) { dwStatus = WaitForSingleObject(g_hevInterrupt, INFINITE); if( dwStatus == WAIT_OBJECT_0 ) { TRACE1("INTERRUPT %x", 5); g_dwInterruptCount ++; InterruptDone( g_dwSysInt ); } } return 0; } Tag: Problem with eboog Tag: 52494
  - 7
    - cepb.exe - Application Error Hi, I kept getting this problem "cepb.exe - Application error" The memory could not be "read". when I try to debug my platform thru Ethernet connection. I already tried rebuilding the Ethernet bootloader, the whole platform and even tried reinstalling platform builder. It works fine if I disable the Kernel Debugger. Here are the build options that I enabled: KITL Kernel Debugger Full Kernel Mode Eboot Space in Memory CE Target Control Support Any help will be greatly appreciated. Thanks! Tag: Problem with eboog Tag: 52489
  - 8
    - RDP key in code will change when connect to server Dear all I use the RDP function of WinCE.Net 4.2 connect to Windows XP professional Server The language of client (WinCE) is Japanese. The language of Windows XP is Traditional chinese When I connect to Server, I find that I key in character via Visual keyboard and show confused code Do anybody meet this problem? Could you tell me how can I do to slove the problm Thanks a lot Jeffrey Tag: Problem with eboog Tag: 52487
  - 9
    - What is the equivalent of linker script in ARM assembler ? Hi, Sorry, this question may not be apt for this mailing list, but then i'm encountering this problem while implementing the the WinCE for ARM. What is the equivalent of linker script (used in GNU assembler) in ARM assembler ? Do we have to implement the relocated - Absolute, Text address in the .S file itself ? How do we implement these ? just by assigning the address values to these variables, like using DCD ? but then I wont know the proper address of these variables if they are in the text area, before I get the map file ? Is there any other mailing list where i can get info regarding the ARM assembler ? Regards Esha Tag: Problem with eboog Tag: 52480
  - 10
    - Bluetooth BCSP power management on CE.NET 4.2 Hi all, I have an issue with bluetooth power management on CE.NET 4.2. I am using BCSP over a serial port to talk to a CSR bluetooth module on PXA255 CPU. The bluetooth works fine on intial power up. When I suspend the unit then resume it the bluetooth no longer functions. Our hardware removes power from the module while in suspend. Power does get reapplied to the module and the serial driver is back in a state where it can communicate again. Any ideas on a workaround for this issue? Regards, Dean Wood Intrinsyc Europe Ltd Tag: Problem with eboog Tag: 52478
  - 11
    - How can I remove software-based input panel (SIP)'s Tittle Hi, everyone How can I remove software-based input panel (SIP)'s Tittle? I want to use my customized SIP. But when my SIP pop up,it always has the system's tittle. How can I remove it? thanks. hutyn. Tag: Problem with eboog Tag: 52476
  - 12
    - Keyboard layout Hi I would like to add Polish keyboard Layout. Does anyone have document how to do it ? Regards /Martin Tag: Problem with eboog Tag: 52475
  - 13
    - Monitor Flickering problem with via PLE133 chipset Hi, I am using WINCE .Net 4.2 wbt thin client platform builder. The display driver chipset is ddrawkple501 v1.671.net42. We found that there is some monitor flickering problem occur when we switch off and switch on the monitor. But once we restart the client it does'nt happend. The same hardware is working with same monitor with other os. Does any one had idea about this. regards R.Muthukumar Tag: Problem with eboog Tag: 52472
  - 14
    - USB client Hi I have a target device of DBPXA255 and use wince.net 4.2 OS. I use the default source code and set "BSP_NOUSBSER=". But when I plus the usb client line to PC, the PC can't recognise the new device. I don't konw the reason. I have set up activesyn3.71 , so my PC has setup the usbclient driver for wince What should I do Any idea will be welcome Thanks Fred Tag: Problem with eboog Tag: 52469
  - 15
    - How to make my platform support KITL and kernel debug? Hi, everyon I have a platform like Sandgate with PXA255 processor and wince.net 4.2 OS. It has only one ethernet port of CF LAN CARD. I want to use this CF lan card to download the NK.BIN and to support KITL. Now I can use it to download image file to target device, but I can't make it support KITL. I don't modify the default source code except taking out macro EBOOT. what should I do Any idea will be welcome Thanks Fred Tag: Problem with eboog Tag: 52468
  - 16
    - why be unloading? I add a new stream interface driver to BSP ,and functions dont do anything. but loading period occurs the following result: 0x8bea5cb0: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\SCI) entered 0x8bea5cb0: >>> Loading module sci.dll at address 0x01E60000-0x01E65000 Loaded symbols for 'E:\WINCE420\PUBLIC\ARM926EJS_01\RELDIR\ARM_REALVIEW_VERSATILE_PB926EJ-S_ARM V4IDEBUG\SCI.DLL' 0x8bea5cb0: SCI port process attach 0x8bea5cb0: SCI process detach called 0x8bea5cb0: <<< Unloading module sci.dll at address 0x01E60000-0x01E65000 Unloaded symbols for 'E:\WINCE420\PUBLIC\ARM926EJS_01\RELDIR\ARM_REALVIEW_VERSATILE_PB926EJ-S_ARM V4IDEBUG\SCI.DLL' 0x8bea5cb0: DEVICE!StartOneDriver RegisterDevice(sci, 1, sci.dll, 0x802ee60) failed I want to ask why the new driver is unloaded after loading? thanks! Tag: Problem with eboog Tag: 52467
  - 17
    - why be unloading? I add a new stream interface driver to BSP ,and functions dont do anything. but loading period occurs the following result: 0x8bea5cb0: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\SCI) entered 0x8bea5cb0: >>> Loading module sci.dll at address 0x01E60000-0x01E65000 Loaded symbols for 'E:\WINCE420\PUBLIC\ARM926EJS_01\RELDIR\ARM_REALVIEW_VERSATILE_PB926EJ-S_ARM V4IDEBUG\SCI.DLL' 0x8bea5cb0: SCI port process attach 0x8bea5cb0: SCI process detach called 0x8bea5cb0: <<< Unloading module sci.dll at address 0x01E60000-0x01E65000 Unloaded symbols for 'E:\WINCE420\PUBLIC\ARM926EJS_01\RELDIR\ARM_REALVIEW_VERSATILE_PB926EJ-S_ARM V4IDEBUG\SCI.DLL' 0x8bea5cb0: DEVICE!StartOneDriver RegisterDevice(sci, 1, sci.dll, 0x802ee60) failed I want to ask why the new driver is unloaded after loading? thanks! Tag: Problem with eboog Tag: 52466
  - 18
    - smart card reader driver? I want to develop smart cart reader driver built-in platform.I know that sci driver is stream interface driver, but there are only usb/serial smart card reader driver sample in windows CE4.2. someone can give me a smart card driver built-in platform other than usb/pcmcia based smart card driver, or some advices, thanks! Tag: Problem with eboog Tag: 52464
  - 19
    - power manager problem,in call OEMPowerOff, for pxa255 my platform is pxa255, when i suspend my system, it call OEMPowerOff, but it can't wakeup i find the OEMPowerOff code in my bsp,, but i can't find the wrong, what can i do?? or how can i debug it! thank!! Tag: Problem with eboog Tag: 52461
  - 20
    - How to add the ceplayer module into my platform? Hi everyone, An error was reported to me when my platform included the ceplayer module. The error is: fatal error U1073: don't know how to make 'E:\WINCE420\public\directx\oak\lib\ARMV4I\retail\ceplayer.lib' NMAKE : fatal error U1077: 'E:\WINCE420\sdk\bin\i386\nmake.exe' : return code '0x2' So, I removed this module by not set SYSGEN_CEPLAYER to avoid this build error. Then, my Application have no Media Player, this is not a good idea. Could you tell me how to add ceplayer to my platform successfully? Thanks a lot. Tag: Problem with eboog Tag: 52451
  - 21
    - PRB:how to create a Mobile Handheld I want to use platform builder to create a Mobile Handheld ( My pda:Compaq iPAQ H3800 series , CPU: StrongARM v1110 Do I must set up a CEPC to create a Mobile Handheld ? Can't I just download the custom OS image to the Emulator ? Tag: Problem with eboog Tag: 52449
  - 22
    - WinCE QFE releases for the week of May 17 - May 21, 2004 The following updates for Windows CE have been recently released and are available for download. More information for each update is provided in the Readme document available after the individual update(s) has been installed. Windows CE .NET 4.2 Update name: Windows CE .NET 4.2 Platform Builder QFE 040505_KB84110 Download link: http://www.microsoft.com/downloads/details.aspx?FamilyId=542A7C5B-5CBB-400A-AEE9-1F52CA6257D8&displaylang=en Component: DHCP Description: The DHCP server may fail to hand out an IP address if the DHCP server has moved to a different subnet. Update name: Windows CE .NET 4.2 Platform Builder QFE 040506_KB838785 Download link: http://www.microsoft.com/downloads/details.aspx?FamilyId=F3BB812F-F91A-4929-92E4-723FA7CF8B89&displaylang=en Component: Wininet Description: When repeatedly browsing to new pages and prior to pages fully loading, the browser may hang for a while and then display a message "The page is not found". Update name: Windows CE .NET 4.2 Platform Builder QFE 040507_KB832263 Download link: http://www.microsoft.com/downloads/details.aspx?FamilyId=12C5EA2C-6EF1-4747-862B-63696DED5CB0&displaylang=en Component: IPv6 Description: Windows CE .NET 4.2 may not be compliant with some tests for the "IPv6 Ready!" logo. Update name: Windows CE .NET 4.2 Platform Builder QFE 040519_KB836632 Download link: http://www.microsoft.com/downloads/details.aspx?FamilyId=032117CA-AC53-4EEA-9F3C-F2200CDDAC65&displaylang=en Component: NetBIOS Description: Attempts to access a local file share via a UNC path may cause Windows Explorer to hang. Windows CE .NET 4.1 Update name: Windows CE .NET 4.1 Platform Builder QFE 040510_KB841547 Download link: http://www.microsoft.com/downloads/details.aspx?FamilyId=4B971978-2969-4910-A46F-493A5D0DF0CF&displaylang=en Component: Common Controls Description: When browsing to a folder with no subfolders, the hour-glass cursor may no change to the mouse pointer. Download Link - directs you to the Microsoft Download Center page associated with each update. Each update is contained in a self-extracting compressed file. Component - displays the module(s) updated in each QFE Description - provides more information on the issue(s) fixed **DO NOT REPLY - THIS E-MAIL IS BEING SENT TO YOU FROM AN UNMONITORED ACCOUNT. Due to Microsoft's security requirements, the hyperlink(s) contained in this e-mail may not automatically open your browser. If you experience any difficulty, please copy the link and paste into your browser. ** Tag: Problem with eboog Tag: 52446
  - 23
    - PCI Bus enumeration I have been studying the code in the public/drivers/common/oak/PCIBUS folder because I have a PCI device that I want to get running on an ARM based platform. Since the PCI device is not configured from a BIOS, I need to do it manually. In PCIBUS, the code loops for all devices/slots/features, calls into PCIRsrc.c for new resources and adds PCI devices to a linked list. Is this the "I/O Resource Manager" described in the PB help? The code queries the PCI device for it's type (memory or IO) and size. It then asks for resources and updates the linked list. I guess, at some point, it also updates the registry. This all makes sense. But where does the driver determine the starting memory and IO addresses it can use for mapping PCI devices? Is this passed in at some point? If so, how does the caller determine what this base address is? Is this platform specific? Thanks, Nick. Tag: Problem with eboog Tag: 52445
  - 24
    - Editor Question I keep getting editor dialog boxes indicating that the file I am currently editing has been modified outside of the source editor and asking if I want to reload it. Sometimes if I answer "Yes" I lose the work I just added. Is there something going on in the background processing of Platform Builder that keeps changing the source files I working on ? How can I change this ? Tag: Problem with eboog Tag: 52443
  - 25
    - Re: Any USB 802.11b device supported by WinCE ? Hi, Anyone know of a USB 802.11b wireless device with support for Windows CE .NET? Best Regards, Samuel Phung ICOP Technology Inc. Tag: Problem with eboog Tag: 52438

I have found my date on my computer is 2003,and I have changed it to 2004.
but the same problem still appears.
No Server Process Associated With File Name bg
Error in TFtpReceiver
****** Data record 52 corrupted, ABORT!!! ******

how can i resolve it ??

Top