Re: Problem with Monte-carlo profiling - all modules reported as unknown

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - IOCTL_HAL_GET_HWENTROPY - should this be unique to each hardware? Hi, I need to supply IOCTL_HAL_GET_HWENTROPY. should this be unique to the device, or can it be a function of some device property such as "Available free memory" ? etc Thanks in advance!!!! Rags Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76226
  - 2
    - Secure Digital - atomic sector writes? Hi -- I have a question regarding SecureDigital memory. I've noticed that the TFAT file system implementation requires atomic sectory writes. The embedded platform I have (PXA270) uses SD memory exclusively as the storage medium. Does anyone with expert knowledge on SecureDigital know whether SD provides atomic sector write support? If not, what storage mediums do provide for atomic writes? Has anyone used TFAT with SD memory and had good results with the filesystem? Thanks Dave Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76221
  - 3
    - slot 1 XIP dll problem Hi, I want modify the export function entry point of tcpstk.dll, this dll loaded by device.exe. So I writed a general stream driver. it loaded by device.exe too. The steam driver can use LoadLibrary to load tcpstk.dll and get the base address, but I can't read or write the memory address of tcpstk.dll. I think the reason is tcpstk.dll is a XIP dll and running in slot 1, how can I access it? Any idea? - Strickland Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76212
  - 4
    - fscanf, sscanf performance hit under CE5 Hi folks, After doing some profiling and benchmarking, we've found something odd in the performance of the stdioa [fs]scanf routines in Windows CE 5.0 vs. 4.2. With a huge test file (50,000 lines, 3 tokens per line), under 4.2 and 5.0 both it takes about 2 seconds to just chunk my way through it with CreateFile / ReadFile (all these tests are just throwing away the data, there's no processing time involved). It takes a little over half a second to fgets() it one line at a time. But if I either work directly through it with fscanf() or read it a line at a time with fgets() and use sscanf() on that line, on 4.2 it takes about 4.5 to 5 seconds, while on 5.0 it takes _16_ seconds! And, of course, our standard (and large, and complex <g>) application is heavy on fscanf usage... :) Has anybody seen similar behavior from these or other stdioa crt functions? Can anyone explain what's going on that's causing such a performance hit? FWIW, here are a couple of sample runs (they are representative, I've got many similar runs): WinCE 4.2: Readfile took 2386 ms fread took 622 ms fgets took 711 ms fscanf(s) took 5075 ms (fgets took 854 ms and sscanf took 4520 ms) WinCE 5.0: Readfile took 2197 ms fread took 570 ms fgets took 646 ms fscanf(s) took 15991 ms (fgets took 777 ms and sscanf (%d) took 15398 ms) (fgets took 1530 ms and sscanf (%s) took 17289 ms) Thanks, -- Brian Bender Vocollect, Inc. Pittsburgh, PA, USA [Apologies for the following "disclaimer" -- it's corporate policy.] -CONFIDENTIAL, PRIVILEGED COMMUNICATION- This e-mail transmission is private and intended for the addressee(s) only. It may contain information that is privileged and/or confidential. If you have received this transmission in error, you are not authorized to read, copy, disclose or disseminate it in any manner. If you have received it in error, please delete it and all copies (including backup copies) that have been made, and transmit a reply message informing the sender that it was misdirected. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76207
  - 5
    - launch Calibration Screen at start up Dear Sir Driver development is over ..now i am stuck ..i compiled BSP and D/L , but no touch calibration screen appears on the scree. What is the procedure to invoke Touch Screen at the start up Regards Manish Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76200
  - 6
    - display driver hangs Hi My display driver hangs. The following is the debug message. Any help is appreciated. thanks Anand OEMInitDebugSerial using UART1 Windows CE Kernel for ARM (Thumb Enabled) Built on May 3 2005 at 14:03:39 ProcessorType=02d0 Revision=6 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 800b9d8c OEMInit ++ OEMInit -- Booting Windows CE version 4.20 for (ARM) &pTOC = 800bb6b0, pTOC = 8093c01c, pTOC->ulRamFree = 809ea000, MemForPT = 00000000 Old or invalid version stamp in kernel structures - starting clean! Configuring: Primary pages: 13001, Secondary pages: 0, Filesystem pages = 6500 Booting kernel with clean memory configuration: Memory Sections: [0] : start: 809eb000, extension: 00004000, length: 032c9000 Sp=ffffc7cc ARMInit done. Windows CE KernelInit Updated eptr->e32_vsize to = 00093000 Scheduling the first thread. 0x83cb7024: KernelInit2: pCurThread=83cb7024 hCurThread=03cb7262 hCurProc=03cb7002, KernelInit = 80109820 0x83cb7024: Detecting VFP...0x83cb7024: VFP Not Found! 0x83cb7024: first = 01f90000, last = 02000000, SharedDllBase = 037e0000 0x83ca5644: FileSystem Starting - starting with clean file system 0x83ca5644: FSREG: Logging in default user. 0x83ca5644: SetCurrentUser: Logging out (nobody), logging in default 0x83ca5644: FS: Using default path "\profiles\" 0x83ca5644: SetCurrentUser: User hives not supported -- using same registry for all users 0x83ca5644: FS: Using default path "Windows\" 0x83ca5644: FS: Using default path "Windows\" 0x83ca5644: Initializing Database 0x83ca5644: DB:Validation: Name already exists DB_notify_events 0x83ca5644: DB:CeCreateDatabase failed 0x83ca5644: Filesystem initialized! 0x83ca5000: InitializeJit 0x83ca5000: InitMUI: DISABLED (-1039926520) 0x83c7f0a8: *** Power Manager: DLL_PROCESS_ATTACH - Current Process: 0x42, ID: 0x23ca5612 *** 0x83c7f0a8: Ceddk!CalibrateStallCounter: Enter 0x83c7f0a8: Ceddk!CalibrateStallCounter: Could not find stall counter 0x83c7f0a8: Ceddk!BeginCalibration: min(368) max(460) 0x83c7f0a8: Ceddk!BeginCalibration: elapsed is 450 0x83c7f0a8: Ceddk!BeginCalibration: delay is 22 0x83c7f0a8: +PmInit 0x83c7f0a8: +PlatformValidatePMRegistry 0x83c7f0a8: -PlatformValidatePMRegistry: returning 0 0x83c7f0a8: DeviceListsInit: default GUID found in registry as expected 0x83c7f0a8: DeviceListCreate: creating list entry for class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 0x83c7f0a8: PlatformDeviceListInit: using stream interface to access class 8dd679ce-8ab4-43c8-a14a-ea4963faa715 0x83c7f0a8: DeviceListCreate: creating list entry for class 98c5250d-c29a-4985-ae5f-afe5367e5006 0x83c7f0a8: PlatformDeviceListInit: using stream interface to access class 98c5250d-c29a-4985-ae5f-afe5367e5006 0x83c7f0a8: DeviceListCreate: creating list entry for class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 0x83c7f0a8: PlatformDeviceListInit: using display interface to access class eb91c7c9-8bf6-4a2d-9ab8-69724eed97d1 0x83c7f0a8: InitDisplayDeviceInterface: returning 1 0x83c7f0a8: DeviceListCreate: creating list entry for class a32942b7-920c-486b-b0e6-92a702a99b35 0x83c7f0a8: PlatformDeviceListInit: using stream interface to access class a32942b7-920c-486b-b0e6-92a702a99b35 0x83ca5000: +PnpThreadProc: thread 0x03c7085e 0x83c70c90: +ResumeThreadProc: thread 0x03c70ece 0x83c6c400: +ActivityTimersThreadProc: thread 0x03c70fde 0x83c6c400: ActivityTimerCreate: ActivityTimerCreate('UserActivity') returning 0x00000000 0x83c6c400: ActivityTimerCreate: ActivityTimerCreate('SystemActivity') returning 0x00000000 0x83c6a6d0: +SystemThreadProc: thread 0x83c70faa 0x83c6a6d0: +PlatformManageSystemPower 0x83c6a6d0: PlatformPMActivelyManagesPower: returning 1 0x83c6a6d0: PlatformManageSystemPower: waiting for initialization to complete 0x83c6adb4: +BatteryMonitorThreadProc: thread 0x43c6c6f2 0x83c6adb4: BatteryMonitorThreadProc: battery interface APIs not available, exiting 0x83c6adb4: -BatteryMonitorThreadProc: exiting 0x83c7f0a8: -PmInit: returning 1 0x83c6a6d0: PlatformManageSystemPower: initialization complete 0x83c6a6d0: PlatformLoadTimeouts: ACUserIdle 60000, ACSystemIdle 300000, ACSuspend -1, BattUserIdle 60000, BattSystemIdle 180000, BattSuspend 300000 0x83c7f0a8: DEVICE!DevloadInit 0x83c7f0a8: DEVICE!InitDevices: Root Key is Drivers\BuiltIn. 0x83c7f0a8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn) entered 0x83c7f0a8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\sdmmcloader) entered 0x83c7f0a8: SDMMCLoader : DLL_PROCESS_ATTACH 0x83c7f0a8: Entering SML_Init. 0x83c7f0a8: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (SML1:) ATTACH 0x83c7f0a8: DEVICE!ActivateDeviceEx(Drivers\BuiltIn\PWRBUTTON) entered 0x83c7f0a8: PwrButton : DLL_PROCESS_ATTACH 0x83c7f0a8: PwrButton PWR Init ++ 0x83c7f0a8: PNP interface class {f8a6ba98-087a-43ac-a9d8-b7f13c5bae31} (PWR1:) ATTACH 0x83c672ec: Grow Gdi handle table from 0 to 64 0x83c672ec: GPE:::DLLMAIN Entered 0x83c672ec: GPE:::DLLMAIN : DLL_PROCESS_ATTACH 0x83c672ec: GPE:::DLLMAIN Exit 0x83c672ec: SA2Video::GetGPE ++ 0x83c672ec: GPE::GPE() 0x83c672ec: SA2Video::SA2Video ++ 0x83c672ec: DispDrvrInitialize ++ 0x83c672ec: Failed to get display frame buffer value, Error 0x2 0x83c672ec: Done getting Registry values: bpp: 0x10 CxScreen: 0xf0 CyScreen: 0x140 Display Type: HITACHI 0x83c672ec: DispDrvrInitialize ReadRegistryData ++ 0x83c672ec: MapVirtualAddress ++ 0x83c672ec: MapVirtualAddress -- 0x83c672ec: InitCursor ++ 0x83c672ec: InitCursor -- 0x83c672ec: DispDrvrInitialize InitCursor ++ 0x83c672ec: LcdSetupGPIOs ++ 0x83c672ec: LcdSetupGPIOs -- 0x83c672ec: DispDrvrInitialize LcdSetupGPIOs ++ 0x83c672ec: ClearFrameBuffer ++ 0x83c672ec: ClearFrameBuffer -- 0x83c672ec: DispDrvrInitialize ClearFrameBuffer ++ 0x83c672ec: InitLCDController ++ 0x83c672ec: Setting display type HITACHI0x83c672ec: InitLCDController -- 0x83c672ec: DispDrvrInitialize InitLCDController ++ 0x83c672ec: LCDClearStatusReg 0x83c672ec: LCDClearStatusReg -- 0x83c672ec: DispDrvrInitialize LCDClearStatusReg ++ 0x83c672ec: EnableLCDController ++ 0x83c672ec: EnableLCDController -- 0x83c672ec: DispDrvrInitialize EnableLCDController ++ 0x83c672ec: DispDrvrInitialize -- 0x83c672ec: SA2Video::SA2Video -- 0x83c672ec: SA2Video::NumModes 0x83c672ec: SA2Video::GetGPE ++ 0x83c672ec: SA2Video::NumModes 0x83c672ec: SA2Video::GetModeInfo ++ 0x83c672ec: SA2Video::GetModeInfo -- 0x83c672ec: SA2Video::GetGPE ++ 0x83c672ec: SA2Video::SetMode ++ 0x83c672ec: DispDrvrSetDibBuffer ++ 0x83c672ec: ClearFrameBuffer ++ 0x83c672ec: ClearFrameBuffer -- 0x83c672ec: DispDrvrSetDibBuffer -- 0x83c672ec: SA2Video::SetMode -- 0x83c672ec: SA2Video::GetModeInfo ++ 0x83c672ec: SA2Video::GetModeInfo -- 0x83c672ec: Bits-per-pixel: 16 0x83c672ec: Adding font resource '\Windows\tahoma.ttf'... 0x83c672ec: **** Signature of FONT File is: '0100'... <== HANGS HERE Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76199
  - 7
    - IPSM speed increase I am currently using IPSM 3.7.030924 hardware is pxa255 based and OS is wince 4.2. I would very much like to increase the speed of reading and writing from IPSM, has anyone tried this. Currently I am trying to gauge speed of reading and writing to IPSM by transfering large files to and from IPSM. Regards Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76190
  - 8
    - MMC/SD Interface Mode Setting Hello, The SDCard driver seems to support two different interface modes: SD_INTERFACE_SD_MMC_1BIT and SD_INTERFACE_SD_4BIT. The fourth bit interface is faster but only compatible with SD cards and not with MMC cards. The question is: Does the SDcard driver do the automatic selection of the interface mode based on automatic detection of the card capabilities, or it's necessary to call SDSetCardFeature, or modify a registry setting, to set the proper interface mode? Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76187
  - 9
    - Not booting on new CF card with DMA I have used CEPC with hive based registy on a PC with Compact Flash on the secondary master with no problem. But the I got new CF cards, and it does not work any more. The old CF card was recongnised a bit different: This says : 0x83fd0800: Atapi!CDisk::ReadWriteDisk> Allocating double buffer [first use] While the new: Atapi!CDisk::ReadWriteDiskDMA> Failed to wait for interrupt; device(0) Here is a printout of the "Working" card 0x83f999ac: non-magnetic media 0x83f999ac: disk transfer rate > 10Mbs 0x83f999ac: removeable cartridge drive 0x83f999ac: not MFM encoded 0x83f999ac: hard sectored 0x83f999ac: number of cylinders : 978 0x83f999ac: number of heads : 4 0x83f999ac: unformatted bytes per track : 0 0x83f999ac: unformatted bytes per sector : 512 0x83f999ac: sectors per track : 32 0x83f999ac: buffer type : dual port; simultaneous transfers supported 0x83f999ac: buffer size : 2 sectors 0x83f999ac: read/write multiple : supported, 1 sectors/interrupt 0x83f999ac: double word IO : not supported 0x83f999ac: LBA mode : supported 0x83f999ac: DMA : not supported 0x83f999ac: PIO cycle timing mode : 1 0x83f999ac: DMA cycle timing mode : 0 0x83f999ac: current size fields valid : yes 0x83f999ac: current number of cylinders : 978 0x83f999ac: current number of heads : 4 0x83f999ac: current number of sectors/track : 32 0x83f999ac: current sector capacity : 125184 0x83f999ac: sectors/interrupt with read/write multiple : 1 0x83f999ac: multi sector setting : valid 0x83f999ac: total user addressable sectors : 125184 0x83f999ac: single word DMA modes supported : 0 0x83f999ac: single word transfer mode active : 0 0x83f999ac: multi word DMA modes supported : 0 0x83f999ac: multi word transfer mode active : 0 0x83f999ac: Atapi!DumpSupportedTransferModes> Supported transfer mode summary: 0x83f999ac: PIO mode not supported 0x83f999ac: multi word DMA mode not supported 0x83f999ac: ultra DMA mode not supported 0x83f999ac: look-ahead not supported 0x83f999ac: write cache not supported 0x83f999ac: S.M.A.R.T. feature set not supported 0x83f999ac: Atapi!CDisk::Identify> Assuming direct-access device (hard disk drive) 0x83f999ac: Atapi!CDisk::InitController> Device responded to identify 0x83f999ac: Atapi!DSK_Init> Initialized SECONDARY MASTER on Drivers\BuiltIn\PCI\Instance\I823711\Device2 0x83f999ac: Atapi!IDE_Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\I823711\Device3 0x83f999ac: DEVICE!RegReadActivationValue0x83fd0800: >>> Loading module mspart.dll at address 0x03C90000-0x03C99000 (RW data at 0x01FD0000-0x01FD04B4) 0x83fd0800: Loading partition driver mspart.dll hModule=83F316F0 0x83fd0800: Driver mspart.dll loaded 0x83fd0800: Atapi!CDisk::ReadWriteDisk> Allocating double buffer [first use] This is the "Not working card" 0x83f99a0c: disk transfer rate > 10Mbs 0x83f99a0c: fixed drive 0x83f99a0c: not MFM encoded 0x83f99a0c: hard sectored 0x83f99a0c: number of cylinders : 980 0x83f99a0c: number of heads : 8 0x83f99a0c: unformatted bytes per track : 0 0x83f99a0c: unformatted bytes per sector : 0 0x83f99a0c: sectors per track : 32 0x83f99a0c: buffer type : unspecified 0x83f99a0c: buffer size : unspecified 0x83f99a0c: read/write multiple : supported, 1 sectors/interrupt 0x83f99a0c: double word IO : not supported 0x83f99a0c: LBA mode : supported 0x83f99a0c: DMA : supported 0x83f99a0c: PIO cycle timing mode : 2 0x83f99a0c: DMA cycle timing mode : 0 0x83f99a0c: current size fields valid : yes 0x83f99a0c: current number of cylinders : 980 0x83f99a0c: current number of heads : 8 0x83f99a0c: current number of sectors/track : 32 0x83f99a0c: current sector capacity : 250880 0x83f99a0c: sectors/interrupt with read/write multiple : 1 0x83f99a0c: multi sector setting : valid 0x83f99a0c: total user addressable sectors : 250880 0x83f99a0c: single word DMA modes supported : 0 0x83f99a0c: single word transfer mode active : 0 0x83f99a0c: multi word DMA modes supported : 7 0x83f99a0c: multi word transfer mode active : 4 0x83f99a0c: Atapi!DumpSupportedTransferModes> Supported transfer mode summary: 0x83f99a0c: minimum multiword DMA transfer cycle time per word (ns) = 120 0x83f99a0c: manufacturer's recommended multi word DMA transfer cycle time (ns) = 120 0x83f99a0c: minimum PIO transfer cycle time w/o flow control (ns) = 120 0x83f99a0c: minimum PIO transfer cycle time w/ IORDY flow control (ns) = 120 0x83f99a0c: PIO mode 0 supported 0x83f99a0c: PIO mode 1 supported 0x83f99a0c: multi word DMA mode 2 and below is supported 0x83f99a0c: >>> multi word DMA mode 2 selected by default <<< 0x83f99a0c: ultra DMA mode not supported 0x83f99a0c: look-ahead supported 0x83f99a0c: write cache supported 0x83f99a0c: S.M.A.R.T. feature set not supported 0x83f99a0c: Atapi!CDisk::Identify> Assuming direct-access device (hard disk drive) 0x83f99a0c: Atapi!CDisk::InitController> Device responded to identify 0x83f99a0c: Atapi!CDisk::Init> Enabled write cache 0x83f99a0c: Atapi!CDisk::Init> Enabled read look-ahead 0x83f99a0c: Atapi!DSK_Init> Initialized SECONDARY MASTER on Drivers\BuiltIn\PCI\Instance\I823711\Device2 0x83f99a0c: Atapi!IDE0x83fd0800: >>> Loading module mspart.dll at address 0x03C90000-0x03C99000 (RW data at 0x01FD0000-0x01FD04B4) 0x83fd0800: Loading partition driver mspart.dll hModule=83F316F0 0x83fd0800: Driver mspart.dll loaded _Init> Activating IDE/ATA device Drivers\BuiltIn\PCI\Instance\I823711\Device3 0x83f99a0c: DEVICE!RegReadActivationValues RegQueryValueEx(Drivers\BuiltIn\PCI\Instance\I823711\Device3\BusPrefix) returned 2 0x83f99a0c: Atapi!DumpRegKey> Drivers\Active\4294967286 0x83f99a0c: Hnd = 00034940 0x83f99a0c: Name = DSK2: 0x83f99a0c: Key = Drivers\BuiltIn\PCI\Instance\I823711\Device3 0x83f99a0c: Atapi!DumpRegKey> Drivers\BuiltIn\PCI\Instance\I823711\Device3 0x83f99a0c: Port = 00033290 0x83f99a0c: DeviceId = 00000001 0x83f99a0c: TransferMode = 000000FF 0x83f99a0c: LookAhead = 00000001 0x83f99a0c: WriteCache = 00000001 0x83f99a0c: DrqDataBlockSize = 00000200 0x83f99a0c: DoubleBufferSize = 00010000 0x83f99a0c: DMA = 00000001 0x83f99a0c: InterruptDriven = 00000001 0x83f99a0c: Dll = atapi.dll 0x83f99a0c: Prefix = DSK 0x83f99a0c: IClass : 0x83f99a0c: {A4E7EDDA-E575-4252-9D6B-4195D48BB865} 0x83f99a0c: Atapi!CPCIDisk::CPCIDisk> device count(2) 0x83fd0800: Atapi!CDisk::ReadWriteDiskDMA> Failed to wait for interrupt; device(0) Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76186
  - 10
    - korean/german language support in keypad driver hello everybody, i have developed a keypad driver (wince 5.0) using MS sample keyboard driver for a 7x5 key keypad. it works ok for US english . i modified the PDD and tweaked the registry for this. I did not modify the MDD. i want to know what i need to do to support other languages e.g. korean/german . appreciate any help regards wm_user. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76184
  - 11
    - WinCE 5.0 system requirement and feature Hi, Do anyone know the WinCE 5.0 basic requirement (such as size of RAM, Flash..etc) and supported features (such as display resolution, color depth)? Would you mind to show me the list if you have? Thanks ! Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76183
  - 12
    - PB (WinCE5.0) not hitting the break points Hello all, I have set a few break points in my code. I'm using PB for WinCE5.0. I download the code via ethernet (its not the cross over connection). I observe debug messages in the PB debug window. I use a serial cable connnection for this. I'm running the debug version of CE. I've verified that I'm executing from RAM, break points are enabled, the code where the break points are set is actually executing. But PB is not stopping at the break points. All was well till a few days ago. I was happily setting break points and PB was stopping at all of them. One day I gave a sysgen and after that this behaviour started. Appreciate any help on this. Regards, --Inder Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76176
  - 13
    - How to import library in Platform Builder? Hi all, I want to use the function of SHAppBarMessage in my application. But I don't know how to import the required library shell32.lib in platform builder. Can anyone help me? thx a lot~ Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76174
  - 14
    - Problem with downloading EBOOT.sre to "ARM INTEGRATOR kit...... 1.Iam using ARM Boot monitor for downloading serially to ARM Integrator board. 2.i have used the command 'M', which is used to "load a Motorola S-record image into memory and run it". 3. iam using a serial cable, and sending the file EBOOT.sre using hyperterminal from my PC (development station)to ARM Integrator board. problem: 1.when iam trying to send file. iam getting as "No Response from Remote System".and connection is not getting established. 2.But as u can see that there is nothing wrong with serial connection as the initial sequence of bootmonitor is being displayed on the hyperterminal , also the boot monitor command prompt is seen. So i feel there is something wrong in the file transfer. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76173
  - 15
    - Locking data Hi, Can anyone provide insights on locking data in Windows CE similar concept to that of HDLock that is able to lock access to the laptop even then it was stolen for data security reasons. The following is an excerpt from HDLock, " Based on two-factor authentication and the government-standard 128-bit advanced encryption algorithm, HDLockT uses a USB A-Key®, along with a personal password, to act as the key to the notebook. The hard drive remains encrypted and inaccessible at system boot up, hibernation or shut down to anyone but the owner of the unique A-Key® and password. HDLockT is essential for businesses that want to protect that sensitive personal and corporate data that may be vulnerable to copy, removal or modification if a user's notebook is lost, stolen or left unattended." thanks, lois Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76171
  - 16
    - oo16550 highspeed I see references to the highspeed serial buffering (isr16550) and I understand how it works. The docs say you can use it (link it) with the ser16550 driver. Is this also available/included for the oo16550? Is the high speed ISR in there by default? I looked at the code and can't tell. The sources for the oo16550 lib does have an include referance that points to the isr16550 directory. If not can I link it in? do I need to specify the two new registry entries (isrdll and isrhandler)? my sources uses: SOURCELIBS= \ $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\com_mdd2.lib \ $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\oo16550.lib \ $(_COMMONOAKROOT)\lib\$(_CPUINDPATH)\serpddcm.lib Does this mean my seral is not as good (fast) as it could be? Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76161
  - 17
    - Access to NDIS Intermediate Driver from user application Hello, We have an NDIS intermediate driver developed for Windows NT. This NDIS IM intercepts packets and sends it to another module for packet processing. The communication between the NDIS IM and packet processing module takes place using callbacks. The user application communicates with the NDIS IM using Device Objects. We need to port the NDIS IM to Windows CE 4.2. How should we go about replacing the device objects in Windows CE? Should we expose a stream driver interface in the NDIS IM or is there any other better way of accomplishing this? Please help! Thanks in advance Kamali Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76160
  - 18
    - CE5.0 TV-style navigation bug? Dear Sir, If my platform with TV-style navigation component when "iesample" or "iesimple" open some web page like http://tw.yahoo.com the mouse can not click any hyper link on it (cursor shape always arrow but hand). If that happened then only keyboard arrow keys and enter key work (move the yellow frame and execute). If I get rid off the TV-style navigation component from my platform then mouse action become normal again. Why? I found if my web page include this description then the problem will happen: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> But some of my page with frameset but not include the description above still met the same problem. Any idea would be very appreciate. Yang Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76157
  - 19
    - MiniportSetInformation and MiniportHandleInterrupt() are serialize Dear, I have an issue of NDIS driver on CE 5.0. My driver needs to wait interrupt from MiniportSetInformation. But, if MiniportISR() is called and it defers packets to let MiniportHandleInterrupt() do rest of works, while MiniportSetInformation() is executing, MiniportHandleInterrupt() is defered until end of MiniportSetInformation(). So, it makes dead-lock that MiniportSetInformation() is waiting interrupt but MiniportISR() is not called until end of MiniportSetInformation(). Did I miss something? Thanks in advance, Woojung Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76154
  - 20
    - How to debug an exception Hi, I have a bug in my driver which results in an Undefined instruction exception AKY=00000049 PC=02ea26c0 RA=02ea2614 BVA=08140690 FSR=000000f5 What does the FSR mean? The instruction at the PC address is 02ea26c0 E59F3060 ldr r3,[pc,#0x60] which seems valid instruction When these come up i was wondering which are the key addresses to look at to find out what is causing it. I'm using PXA255 with WinCE V5.0. Thanks Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76153
  - 21
    - ANN: Windows CE Chat tomorrow Just a note that we'll be hosting an online chat tomorrow concerning Windows CE 5.0! Members of the development team will be on hand ready to answer your questions, so bring 'em on! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Title: Windows CE 5.0 Live Chat! October 25, 2005 9:00 - 10:00 A.M. Pacific time Additional timezones: http://www.timeanddate.com/worldclock/fixedtime.html?year=2005&month=10&day=26&hour=9&min=0&sec=0&p1=234 Do you have tough technical questions regarding Windows CE 5.0 for which you're seeking answers? Do you want to tap into the deep knowledge of the talented Microsoft Embedded Devices Group members? If so, please join us for a live Windows CE 5.0 chat and bring on the questions! Windows CE 5.0 is the operating system that is powering the next generation of 32-bit, small-footprint and mobile devices. This chat will cover the tools and technologies used to develop devices using the Windows CE 5.0 operating system. To join this chat, please log on via the main MSDN chat page at: http://msdn.microsoft.com/chats -- Thanks! Michael Fosmire MVP Lead, Windows Embedded This posting is provided AS IS with no warranties, and confers no rights. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76152
  - 22
    - USB Problem Hi, I'm working on a CEPC platform for a Panel PC based on an SBC83675 board. The board has a Celeron 1.2 gHz processor and uses the VIA VT8606 "Twister-T" chipset. It provides two USB 1.1 ports. I started with the Industrial Controller platform and added the features I needed from there. I can plug a USB 1.1 compact flash reader into the system with no difficulties. However, if I plug in a USB 2.0 compact flash reader, it is not recognized. Debug messages show that the connection process gets to the point where the Usbdisk6.dll is loaded but the process fails shortly after that. The first significant debug message is: BOT_DataTransfer warning(6.7.2.3, RequestLength:8 TransferLength:4 Err:0 UsbErr:0x0, dwTimeout:5000) Up until the failure occurs, the debug messages from inserting the 2.0 device match the debug messages generated by inserting the 1.1 device. Should the CE 5.0 USB driver support working with USB 2.0 devices when the system chipset has USB 1.1 hardware? If I boot the system to MSDOS, it recognizes the USB 2.0 reader properly. Has anyone had success with this configuration? I've searched through the archives and haven't found anything that has improved the situation Thanks, Jim Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76150
  - 23
    - PCMCIA Driver Hi guys, I'm using PB 4.2 to create a WinCE image for a board based on ARM Cirrus 9315. I added Cirrus BSP and PCMCIA Driver included to my image. I added support for CF and FAT because I'd like to use PCMCIA for reading Compact Flash. The problem is that when I plug PCMCIA adapter for CF, wince asks me a PCMCIA Driver ....:-((, but I've already added the driver. Where's the problem? thanx for any suggestions Giuseppe Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76148
  - 24
    - My target sometimes stops to get address from DHCP Hi, on my target, using WINCE 4.2 I have a wireless ethernet made via a PCMCIA card (Cisco aironet 350 series). I have 2 problems: 1) The time needed to get address from the DHCP server is tipically 30-40 seconds. Is possible to reduce this time? 2) Sometimes it happens that the target device shows the message: "Windows CE Networking - DHCP was unable to obtain an IP address. If the netcard is removable, than you can remove/reinsert it to have DHCP make another attempt to obtain an IP address for it. Otherwise, you can statically assign an address" and it's no more able to connect to the server (it get no IP address untill the device is restarted). Can someone tell me which can be the problem? Thank you. Marco. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76137
  - 25
    - hard disk directory not found(help) I have included the drivers for the storage devices from the catalog in wince 5.0 platform builder. but when i boot the os image i dont find the hard disk directory .... please tell me what should i do.... Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76129
- Next
  - 1
    - WINCE - XIP in Flash Hello All, I am trying to execute the WindowsCE minimal kernel, straight from Flash(XIP).Reference BSP is MainstoneII. At present, since the LAN Controller and the CF slot are not enabled, I decided to transfer the kernel image(NK.nb0) using JTAG. For this, I believe I have to modify the config.bib.I did modify it in the following way :- MEMORY ; Name Start Size Type ; ------- -------- -------- ---- RSVD 80000000 000FF000 RESERVED ARGS 800FF000 00001000 RESERVED NK 00100000 01F00000 RAMIMAGE RAM 80100000 01F00000 RAM CONFIG AUTOSIZE=ON KERNELFIXUPS=ON ROMSTART=00100000 ROMWIDTH=32 ROMSIZE=01F00000 Also, I am transferring the Nk.nb0 using JTAG at the address specified in RAMIMAGE, i.e. 0x00100000. After that, I modified the OEMLaunch() function from the EBOOT menu, so that it jumps to this address in the Flash,i.e. 0x00100000. Have I configured the options the right way ... ? If anyone could help me in this regard it would be great help ! Regards, Swapnil. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76126
  - 2
    - Memory configuration Hi At the moment on our hardware xscale pxa255 based hardware I have 64MB RAM (2*K4S561632) and 64MB FLash (2*28F256J3). The hardware has been designed to accept another 64MB of RAM and Flash. Giving me a total of 128KB of Flash and Ram. I can have these extra chips fitted, my question is what modifications would I have to make to wince 4.2, I can't seem to gauge how much time this task would take to complete. Regards Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76123
  - 3
    - Why my target is not taking the IP address Provided by DHCP server Dear Experts, At present we are working on WINCE5.0 ethernet driver for AT91RM9200 platform. My target board sends the DHCP request to DHCP server and DHCP server responds well. But the problem is my target board is not taking the IP address (but the driver received the DHCP response packet) provided by the DHCP server instead, Target is sending the request again and again. We have included the following NDIS_MINIPORT_CHARACTERISTIC Characteristics.MajorNdisVersion = AT91LAN_NDIS_MAJOR_VERSION; Characteristics.MinorNdisVersion = AT91LAN_NDIS_MINOR_VERSION; Characteristics.CheckForHangHandler = NULL; Characteristics.DisableInterruptHandler = At91LanDisableInterrupt; Characteristics.EnableInterruptHandler = At91LanEnableInterrupt; Characteristics.HaltHandler = At91LanHalt; Characteristics.HandleInterruptHandler = At91LanHandleInterrupt; Characteristics.InitializeHandler = At91LanInitialize; Characteristics.ISRHandler = At91LanIsr; Characteristics.QueryInformationHandler = At91LanQueryInformation; Characteristics.ReconfigureHandler = NULL; Characteristics.ResetHandler = AT91LanReset; Characteristics.SendHandler = At91LanSend; Characteristics.SetInformationHandler = At91LanSetInformation; Characteristics.TransferDataHandler = NULL; Characteristics.ReturnPacketHandler = NULL; Characteristics.SendPacketsHandler = NULL; Characteristics.AllocateCompleteHandler = NULL; We are in need of yours kind suggestion as what may be problem in our ethernet driver. Thanks in Advance, Jalvath Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76120
  - 4
    - Target is not taking the IP address provided by DHCP server Dear Experts, At present we are working on WINCE5.0 ethernet driver for AT91RM9200 platform. My target board sends the DHCP request to DHCP server and DHCP server responds well. But the problem is my target board is not taking the IP address (but the driver received the DHCP response packet) provided by the DHCP server instead, Target is sending the request again and again. We have included the following NDIS_MINIPORT_CHARACTERISTIC Characteristics.MajorNdisVersion = AT91LAN_NDIS_MAJOR_VERSION; Characteristics.MinorNdisVersion = AT91LAN_NDIS_MINOR_VERSION; Characteristics.CheckForHangHandler = NULL; Characteristics.DisableInterruptHandler = At91LanDisableInterrupt; Characteristics.EnableInterruptHandler = At91LanEnableInterrupt; Characteristics.HaltHandler = At91LanHalt; Characteristics.HandleInterruptHandler = At91LanHandleInterrupt; Characteristics.InitializeHandler = At91LanInitialize; Characteristics.ISRHandler = At91LanIsr; Characteristics.QueryInformationHandler = At91LanQueryInformation; Characteristics.ReconfigureHandler = NULL; Characteristics.ResetHandler = AT91LanReset; Characteristics.SendHandler = At91LanSend; Characteristics.SetInformationHandler = At91LanSetInformation; Characteristics.TransferDataHandler = NULL; Characteristics.ReturnPacketHandler = NULL; Characteristics.SendPacketsHandler = NULL; Characteristics.AllocateCompleteHandler = NULL; We are in need of yours kind suggestion as what may be problem in our ethernet driver. Thanks in Advance, Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76119
  - 5
    - IPSM Hi I am currently using IPSM 3.7.030924 hardware is pxa255 based and OS is wince 4.2. Is there any merit in moving to Version 3.8.050603, its not clear from the documentation if this actually supports 4.2, it seems to be geared for wince 5.x. Regards Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76117
  - 6
    - Building a debug image using "commandline in Win CE 4.2" Actually i need to build EBOOT in WinCE 4.2 , located at,"D:\WINCE420\PLATFORM\ARMINTEGRATOR\EBOOT". iam using commandline to do this, but after building properly the eboot.bin file is getting upted as release image(in retail folder) instead of debug image(in debug folder). i want a debug image of eboot. can anybody tell me how to get the debug image(eboot.bin) using commandline . thanks anu Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76114
  - 7
    - Atmel AT43DK325 USB development kit and Windows CE Does somebody have experience with the Atmel AT43DK325 USB development kit and Windows CE? (e.g. GCC keyboard application) Any information is welkom. Thanks in advance, Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76110
  - 8
    - Memo pad Hi all, Does anyone know a memo pad-like application for Windows CE 4.2 or 5.0? I want to draw something on the screen and immediately save it, or paste it to a word document. It seems pretty obvious, every PDA has it, but I can't find one for CE. Regards, Piet Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76109
  - 9
    - configuring control panel Hello everybody, is it possible to configure the contents of the control panel by means of environment variables (like in embedded XP). I want to remove the applet "sounds&volume" because I have no audio driver in the system and clicking on this applet show up a message box with unreadable contents. I'm using WindowsCE 5.0 with all available QFEs added. Thank you very much Frank Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76107
  - 10
    - Should EDBG use the same NIC as the one used by eboot? hi i am designing a ethernet debug library for intel 82559 card. i have added the necessary interface to include the library in the EBOOT and the OAL. also, i have removed RTL support from the OAL. now, i am downloading the image with RTL EBOOT. however, after downloading when PCI scans the NICs, it searches for RTL and it does not find the support for it. but again it does not check for intel 82559 card. both the cards are in the CEPC. why the control is not passed to 82559 lib? does it mean that ethernet library should use the same network card as the one used by eboot? anticipating for reply. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76104
  - 11
    - About using VirtualCopy function Hi, When using VirtualCopy function, like below VirtualCopy(pvDest, (void *)(0x64000000/256), 128*1024, PAGE_READWRITE | PAGE_PHYSICAL | PAGE_NOCACHE); Why must divide the physical address by 256? thanks, Stanley Lin Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76103
  - 12
    - debug messages can i get debug messages DEBUGMSG in release configuration when we build image in wince-4.2,or REATAILMSG macro is used for that. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76100
  - 13
    - Display driver Hi, I would like to ask WinCE 5.0 kernel support 24 bits color display? Suppose I have a MCU supports 24 bits color and display driver can output 24 bits color to a TFT LCD panel without any problem. Does the WinCE 5.0 kernel can output all 24 bits color to the driver for display? Thanks, Bryan Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76096
  - 14
    - About Wi-Fi driver Hi, I would like to ask does WinCE 5.0 fully compliance the WiFi standard especially the part of security? Thanks, Bryan Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76095
  - 15
    - Priority inversion in driver Hi, I was wondering if it is ok to have priority inversion in my driver. I have access to my hardware regsiters protected with a critical section. The priority inversion can happen as follows: IST() { While(1) waitforsingleobject() { EnterCriticalSection(&RegCrit) Access I2C registers to clear interrupt etc LeaveCriticalSection(&RegCrit) } } I2C_Write() { EnterCriticalSection(&RegCrit) Access I2C registers etc LeaveCriticalSection(&RegCrit) } The IST (higher priority) could be blocked on this critical section, i've seen in kernel tracker that priority invesrion takes place to allow IST to run, it would only be for very short period. Is this ok or bad design. I felt i had to protect the hardware register access and didn't know a better way. Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76085
  - 16
    - NDIS driver failed when NdisMRegisterInterrupt() Hi, I am writing an NDIS driver for cs8900 on PXA255, for CE.net 4.2. The cs8900 interrupt pin has connected to PXA255 GPIO54, and I want the hardware interrupt connect to SYSINTR_ETHER(SYSINTR_FIRMWARE+10) . I use the cs8900 driver source code which provided by Crystal as a start, according to the guideline document, Iâ??ve added some registry data to the project.reg and build the dll to my NK. Iâ??ve also add some code to the OEMInterruptHandler/OEMInterruptEnable/OEMInterruptDisable/OEMInterruptDone. When the driver execute to the NdisMRegisterInterrupt(), it failed with error code: 0xc0000001(NDIS_STATUS_FAILURE). /////////////////////// Status = NdisMRegisterInterrupt( &(pData->InterruptObject), MiniportAdapterHandle, (UINT)pvMini_Context->pChip->Config.IntLine, // IntLine == 0x1A (UINT)pvMini_Context->pChip->Config.IntLine, // IntLine == 0x1A (BYTE)FALSE, // Installable ISR: False (BYTE)FALSE, // Shared Interrupt: False (NDIS_INTERRUPT_MODE)NdisInterruptLatched // Level or Edge ); ///////////////////////////////////// Any comment is very appreciated! Daric Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76083
  - 17
    - .NET Compact Framework 2.0 on Windows CE 4.2 devices Hi all! Is there support for Windows CE 4.2 (x86) devices in .NET Compact Framework 2.0? When will the QFE containing .NETCF2.0 for CE4.2 be released if that is the case? Thank you! Sincerely // Nicklas Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76074
  - 18
    - PCL Version of Windows CE Hello, which version of PCL is supported in Windows CE 5.0? Regards Peter Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76073
  - 19
    - GetTickCount Problem in Intel BSP for pxa255 We have problems with GetTickCount suddenly jumping ~1165 seconds.(Win CE 4.2) I know the problem dissapears by stubing out OEMIdle(). That is not an acceptable solution for us thou we care a lot about power consumption. I've tried to modify the OEMIdle() and the handling of CurMSec variable but no success so far. Do anyone know if a fix/workaround exists with intact Idle functionality? Thanks Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76072
  - 20
    - WCE problem The screen size of my Windows CE .NET 4.20 have been fixed to 240x320 by the manufacturer, but for some WCE default software screen size is different (240x480) and bigger: why? Mhaxx Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76071
  - 21
    - SD memory Hi, How feasible is programming (or writing a driver with some added functions say from the original drivers) for a SD memory on a CE 4.2 PDA. Well, this is for a possible school project. I have absolutely no idea how SD memory works. thanks, lois Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76068
  - 22
    - PCL-Laser printer with CE I'm using Windows CE. It is not possible to print a written text from Wordpad for example with a HP Laserjet 2200 SN printer. This printer is PCL-compatible how HP has said and I have tested the printer with an old selfwritten DOS-Program which sends directly PCL-commands. From WordPad nothing will be printed with the PCL-Laser settings and with port LPT1. What is the problem? If I connect a HP Deskjet 940 Inkjet printer with the correct printer settings everything is ok! Everything will be printed with the HP 940 from Wordpad. Thanks a lot for your help, Wenching Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76066
  - 23
    - Mouse Coordination simulation Hi Right Now i have 2 devices . One is Slave and other is master . Master device is having IR port and Touch Screen (in put system is there) ,but the slave does not have such input system. Master has to pass Remcon code and Tocuh Screen Coordinate to the Slave. We are using a wired connectioin and using one protocol transferring these information to slave. In case of TouchScreen information ,we transfer 12 bit raw value of x and y. My question is ,once i get this value at slave (using any com port). How can i get these raw coordinated into calibrated one. ..? I hope my question is clear. Regards Manish Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76065
  - 24
    - HELP !!!!........ OS not able to access DMA space (shared with NIC) We are developing a ethernet bootloader for Ethernet card intel 82559 in Win CE platform. present status: 1. We are able to download .bin image of small size. problem : 1. we are not able to download .bin image of larger sizes, it gives us Checksum error when we try to download .bin image of size 23 MB. 2. After we successfully download a smaller .bin image, and when the EthXXXInit(){ethernet card initialization code}is called , we are able to access the device registers(which is I/O mapped).But we are not able to access the Shared memory region(DMA buffer space) staring with 0x803CF0A0. Actually DMA staring address (physical address) used for bootloader : 0x00200000 is working fine.The DMA size used was 20000. somemore explanation for problem 2: Both bootloder and the OS(after downloading) uses the same Ethernet debug library. So here when the bootloader uses this library it uses the device registers (i/o mapped) and shared memory(physical address given above) correctly.But when after the OS gets downloaded and "probably" the Address mapping is enabled so we are getting the address of shared memory as 0x803CF0A0, i think we r not able to access this DMA area as the commands to access the DMA region is not working .At the same time we are able to access the Device registers(i/o mapped). eagerly waiting for ur reply. thanks anu Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76064
  - 25
    - Linking Error Dear Sir I am having a Driver at WinCE...\Drivers\Mydriver . In this driver file (.cpp) i am refering to another T1.c file functions . To compile this file along with driver file i modified sources file and added T1.c in the list of sources = . When i build this driver file my T1.c also get compiled . But it's giving linking error . MyDriver file(.cpp) refers to some functiions defined in T1.c file ..showing unresolved external symbols. Please tell me ,how can we remove this error . Regards Manish Tag: Re: Problem with Monte-carlo profiling - all modules reported as unknown Tag: 76059

Yeah, I'll make sure it gets taken care of. Thanks!

Sue
sloh@microsoft.com (remove "online" from reply-to address)

Now writing to a different blog!
http://blogs.msdn.com/ce_base/
_____________________________________________________________
This posting is provided "AS IS" with no warranties, and confers no rights.
_____________________________________________________________

Top