CF 2.0 QFE Released

Tutorials Win: Microsoft Windows Forum

- Previous
  - 1
    - PXA255 Intel 2700G Multimedia Accelerator Hi Our current hardware uses PXA255, MediaQ1132 graphics chip running windows ce 4.2. Since MediaQ 1132 has become obsolete (has been for a long while), we are considering replacing it with the Intel 2700G Multimedia Accelerator. Can we use this chip with the PXA255, and are there any wince 4.2 drivers for QVGA display, and other goodies on this chip. Has anyone tried this? Regards Tag: CF 2.0 QFE Released Tag: 76368
  - 2
    - Geode, ATAPI, DMA and Windows CE 5.0 Hello, I read a lot of articles about the GEODE ATAPI DMA problems under Windows CE 4.2. Because of the fact it did not work properly for me I had turned off the DMA feature (Using the SETTINGS registrykey). Now I have created my first Windows CE 5.0 image for my GEODE platform. If I enable the DMA mode, my Windows CE image boots without any problems. But sometimes it happens that file writting or reading creates an error. So my first thought was: DMA troubles. These are my settings: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\GeodeIDE] "IClass"=multi_sz:"{CDDC3621-3512-4b3f-BB6F-B4DD5E061795}" "Prefix"="IDE" "Dll"="atapi.dll" "Order"=dword:2 "Class"=dword:01 "SubClass"=dword:01 "VendorID"=dword:1078 "ConfigEntry"="GenericConfig" ; PCI configuration entry point "Legacy"=dword:01 ; legacy, use Irq for primary and Irq+1 for secondary "Irq"=dword:0E ; 14 "SysIntr"=dword:00 ; SysIntr not specified "DMAAlignment"=dword:10 ; default DMA alignment "SoftResetTimeout"=dword:03 ; ATA/ATAPI spec defines 31s ceiling; this is too long "StatusPollCycles"=dword:100 ; Status register DRQ/BSY polling; 256 poll cycles "StatusPollsPerCycle"=dword:20 ; Status register DRQ/BSY polling; 32 polls per cycle "StatusPollCyclePause"=dword:05 ; Status register DRQ/BSY polling; 5 milliseconds between poll cycles "IsrDll"="" ; not required ; "IsrHandler"="" ; not required "RegisterStride"=dword:01 ; ATA register stride; register block is contiguous [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\GeodeIDE\Device0] "IClass"=multi_sz:"{A4E7EDDA-E575-4252-9D6B-4195D48BB865}" "Prefix"="DSK" "Dll"="atapi.dll" "InterruptDriven"=dword:01 ; enable interrupt driven I/O "DMA"=dword:01 ; enable DMA "DoubleBufferSize"=dword:10000 ; 128 sector (65536 byte) double buffer "DrqDataBlockSize"=dword:200 ; 1 sector (512 byte) DRQ data block "WriteCache"=dword:01 ; enable on-disk write cache "LookAhead"=dword:01 ; enable on-disk look-ahead "DeviceId"=dword:00 ; device 0, i.e., primary master "TransferMode"=dword:20 ; MULTI WORD DMA Can somebody help? Regards Peter Tag: CF 2.0 QFE Released Tag: 76362
  - 3
    - ActiveSync and USB client - Moble 5.0 vs. Pocket PC 2003 Hi, I'm trying to rewrite an application from Pocket PC 2003 to Mobile 5 that uses USB to ActiveSync. There are been some major differences. . . For PocketPC based PDAs (Compaq 3*, HP 55*, ASUS MyPal) we used a driver that offers serial communication via USB. It is found in the registry on [HKEY_LOCAL_MACHINE/Drivers/BuiltIn/USB] and referred to in [HKEY_LOCAL_MACHINE/Drivers/Active] which shows if the driver is activated. The driver is in the file bvd_udc_ser.dll In Mobile 5 the driver used by ActiveSync is in [HKEY_LOCAL_MACHINE/Drivers/BuiltIn/usbfndrv], which means that it is not a pure "stream driver" (with the pre-fix COM). This is a problem for us since the Pocket PC driver is deleted. The driver "usbfndrv" is visible in [HKEY_LOCAL_MACHINE/Drivers/Active] in the registry We hope that it is possible to activate the driver [HKEY_LOCAL_MACHINE/Drivers/USB/FunctionDrivers/Serial_Class] that is in Mobile 5. The problem it that it does not seem to be in the platform build. (since it is not in [HKEY_LOCAL_MACHINE/Drivers/BuiltIn]). The dll that it wants to use is named "serialusbfn.dll" but we do not know if it is in the OS-build. Where can we find "serialusbfn.dll" and do we have to deactivate "usbfndrv" (there is OS call)? Or, can we use the "usbfndrv" API directly to build something like a "stream driver"? Best regards, /hf Tag: CF 2.0 QFE Released Tag: 76359
  - 4
    - How to replace usb full-speed device controller with Hi-speed's on SMDK2410? Dear all: We want to replace SMDK2410's usb Full-speed device controller with Hi-Speed controller. Is it feasible ? The cpu is Arm-based. If I want to change the usb conrtoller, what jobs do I need to do? (...Sorry..I am a software engineer...) Like Step1.... Step2.... etc. What type of controller is suitable and would you mind give me some company product name ? Thx first. Related Links: http://www.samsung.com/Products/Semiconductor/MobileSolutions/MobileASSP/MobileComputing/S3C2410/S3C2410.htm Tag: CF 2.0 QFE Released Tag: 76358
  - 5
    - Does PXA255 have unique device ID Hi, all Does PXA255 have unique device ID? If It has,How can I get the unique device ID? thanks in advance. Tag: CF 2.0 QFE Released Tag: 76357
  - 6
    - BIOS Bootloader Freeze Hello All, I'm attempting to use the x86 Bios Bootloader to load my nk.bin release image from my target system's hard drive. I've partitioned a 502MB primary partition on the hard drive, I've used mkdisk.bat to set up the bootsector, and I have copied and configured boot.ini and nk.bin. However, although the WinCE splash screen loads on boot, the system appears to freeze at that point. I've copied in the stream of error and warning codes which I receive from the serial port at the bottom of this message. I am aware that this is not a new issue; I have seen numerous reports of the same stream of error codes on this newsgroup and on other groups as well. However, I have not seen any postings indicating solutions which worked. A number of people suggested that the problem is rooted in bugs in the bootloader; if so, has anyone successfully built an alternative bootloader which they can share? In any case, my debug output is the following: INFO: code=0x4 // File found INFO: code=0x4 // File found INFO: code=0x4 // File found WARNING: code=0x05 // Unable to reset disk controller ERROR: code=0x1 // Unknown file system ERROR: code=0xD // Failed to read data from storage ERROR: code=0xB // Cannot read record information INFO: code=0x37 // Trying backup image file ERROR: code=0x1 // Unknown file system ERROR: code=0x3 // Couldn't read root directory sector ERROR: code=0x8 // Failed to load BIN image Sincerely, Avi Shmidman ashmid@actcom.co.il Tag: CF 2.0 QFE Released Tag: 76353
  - 7
    - Adding support for NIC cards on cepc Hello all, I'm trying to build a CEPC with a dell dimension 3000. The system has integrated ethernet (Intel Fast ethernet...), and i know from looking around that the intel cards are not ususally compatible. I did find that Intel has released wince drivers for the NIC hardware, but for the life of me can't figure out how to make it work with loadcepc and eboot.bin. There are references in the documentation on adding NIC hardware/vendor IDs to the eboot "table", but the doc is for ce 4.2, and I am using 5.0 (and the process looks like it's changed). Everytime I try to boot the CEPC so I can download an image I get the serial debug error about no supported NIC devices (even though it finds the integrated HW). I guess what I want to know is.. 1) is there a way to add unrecognized NIC device to the Eboot.bin loader that is used with LOADCEPC? 2) Is the driver provided by Intel only for use as "product ethernet" and not as the debug/download system (and to do this do I just add the driver to a cloned copy of the CEPC BSP)? 3) Am I completely insane and should just go use embedded linux? Any help/insight would be greatly appreciated! -Ian Tag: CF 2.0 QFE Released Tag: 76350
  - 8
    - CE 5.0 Q3 2005 QFE doesn't include needed USB 2.0 fix I am experiencing a problem with my USB mass storage device being dropped by the CE 5.0 host. I posted this problem recently, and Mr. David Liao from Microsoft responded : >>>>>>>>>>>> Did you get latest QFE on USB EHCI drivers? Recently, we did fix somthing like this. >>>>>>>>>>>> I see that the Q3 QFE for CE 5.0 is now released, but there is no mention of the fixes to ...drivers/usb/hcd/usb20/ehci/CPipe.cpp., CPipe.h, and trans.cpp. I attempted to install the code modifications in Mr. Liao's post, but was unsuccessful in achieving any USB functionaly at all after making the code changes. Where can I find the QFE that he refers to? I am an OEM Embedded Partner, should I be asking somewhere else? If so, where? Here is a link to the post http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.windowsce.platbuilder&tid=afba6e4a-6884-4315-ae9f-96f967ddddcf&cat=en_US_46d153a0-69a7-4803-92a2-5f4f61ac6579&lang=en&cr=US&sloc=en-us&m=1&p=1 Chuck Tag: CF 2.0 QFE Released Tag: 76347
  - 9
    - USB Problem with CE 5.0 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. Should it be possible to use a USB 2.0 compact flash reader with this configuration? 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. If I boot the system to MSDOS, it recognizes the USB 2.0 reader properly. I've searched through the archives and haven't found anything that has improved the situation Thanks, Jim Tag: CF 2.0 QFE Released Tag: 76346
  - 10
    - How do I change a PUBLIC controlpanel app? Could someone please tell me the correct way to make a change to a file in CPLMAIN--Power.cpp? I don't want to change Public files, so do I copy it the to project dir? How much of the control panel app do I copy so that it still will build correctly. CPLMAIN is referenced form CTLPNL sources file as an include... Thanks for any insight. Tag: CF 2.0 QFE Released Tag: 76342
  - 11
    - Problem with SMBServer on CE 4.2 I have problems during file copy from my desktop (win xp sp2) to a wince4.2 based platform with smbserver active. I just fixed the problem caused by kb 885250 uninstalling it from my XP desktop. The file copy fails reporting an error like: impossible to copy file: path too long. But I'm copying files lik netinfo.exe and savereg.exe in a folder like tools !!!! Thx Alex Tag: CF 2.0 QFE Released Tag: 76335
  - 12
    - recompile a file for ATADISK Hi, I'd like to recompile a file: ATADISK Storage Driver: "system.c" changing dpCurSettings for ATA Disk module. If I add some error (i.e. forgetting a ";" ) when I build my image (in debug) all works with any error, then I suppose that system.c has not been compiled. How can I compile the file? Thanks in advance BR Giuseppe Tag: CF 2.0 QFE Released Tag: 76334
  - 13
    - OALKitlInit: KitlInit failed hello all, i am designing an EDBG library for Intel82559 card with modules: InitDMABuffer, InitNIC, SendFrame, GetFrame, EnableInterrupt, DisableInterrupt, GetpendingInterrupt. it is working upto downloading of the OS. but after that, initialization of KITL is failing. serial debug message is showing error in InitKitl funtion. what might be the condition causing the failure of InitKitl()? the serial debug messages is In Creating name1 In Creating name2 In Creating name3 OALKitlCreateName: Using Device Name 'CEPC8426' KITL: *** Device Name CEPC8426 *** ERROR: OALKitlInit: KitlInit failed CEPC Firmware Init RTC - Status Reg B - 0x02 g_dwCPUFeatures = bfebfbff g_nMtrrCnt = 8 MTRR PhysMask0: 0000000fe0000800 MTRR PhysBase0: 0000000000000006 MTRR PhysMask1: 0000000ffff80800 ................ ........... waiting for reply Tag: CF 2.0 QFE Released Tag: 76331
  - 14
    - WINCE 5.0 CETK fails: internal clientside error Dear Gurus, When I run a OAL Timer Test, the CETK server disconnected abnormally and I get the message below: Posting WM_NETCONNECT(FALSE) message, ErrorCode = 631(0x277) AUTORAS:: Dialer notifies: [2] [Dialer Terminate] Internal Clientside error while trying to reconnect to the server. Clientside will now exit I tried many times, it always occurs on case 121, RTC Latency/Resolution (high priority) I dig into WINCE500/Private/Test/PQOAL/Timers/timerabstraction.cpp, and find that the test thread are running at priority 1, and set the thread quantum to 0. That says, it will never be swapped out unless it is blocked. So I guess the Ethernet thread must be waiting for the end of the test thread and can not respond for the CETK server, is that true? Tag: CF 2.0 QFE Released Tag: 76327
  - 15
    - btscosnd error Hi, I am trying to modify audio gateway codes to comply the handsfree profile. So I move some audio gateway functions into a application and try to run it in application level. In far, the acl connection seems to be ok, but the establishment of sco link fails. After I call OpenAudioChannel, the btscosnd driver try to establish a sco link by calling the InitSco (). In the debug output, the part of reading the device voice setting succeed, but the part of writing device voice setting failed. The error is BT_ERROR_COMMAND_DISALLOWED ( in StatusToError (), it is translated to system error ERROR_CALL_NOT_IMPLEMENTED). If I skip the voice setting writting, it fails in EstablishScoConnection. The debug output is BTSCOSND:: [ERROR] "Call UCT_CONNECT failed 1450" BTSCOSND:: [ERROR] "EstablishScoConnection FAILED 1450" Does anyone knows that if the voice setting writting must be executed? What is the possible reason of the fail of the sco link establishment? Any suggestions would be appreciated. Tag: CF 2.0 QFE Released Tag: 76325
  - 16
    - How to set the taskbar to auto-hide in the application? Hi, I want to ask how to set the taskbar to auto-hide in the windows CE application? Thx~ Tag: CF 2.0 QFE Released Tag: 76323
  - 17
    - Strange problem with NDIS miniport driver Hi all, I have written a NDIS miniport driver for Ethernet NIC on WinCE 5.0. I am able to send and receive data. I am sending ping request from a PC to my device. Everything is fine for first 1001 requests. But after this though I am receiving the correct data to my driver and passing it to NDIS, I am not getting any reply from the NDIS/(TCP/IP Stack). Still I am able to send Ping request from my device to the PC. Anybody has any Idea on this? Any suggestion/tips on this is appreciated. Thanks and Regards, Raghav Tag: CF 2.0 QFE Released Tag: 76313
  - 18
    - controlling Controlpanel apps. Is there a way in PB 5.0 to set what control panel apps will display (setting CPLMAIN_COMPONENTS), without changing the BAT file in PUBLIC\CEBASE\OAK\MISC...? thanks Tag: CF 2.0 QFE Released Tag: 76310
  - 19
    - Serial image download failure Hello, The problem in a nutshell is that the Kernel Debugger in PB 5.0 immediately disconnects after each serial connection attempt to our x86 derivitive device (which does not have an NE2000 compatable ethernet chipset): "The Kernel Debugger is waiting to connect with target. The Kernel Debugger has been disconnected successfully." First of all, the PB target device connectivity options are set as following: Serial download and transport set to 115200/8/n/n/1 on COM 2 (I've tried hardware handshaking as well to no avail) I rang the cable out, it excatly matches the NULL modem cable architecture as given in the PB help. This cable is known to have worked with ActiveSync. The debug text coming out of sboot.bin (via COM1 on the device): "Sending boot request... Waiting for boot ack... failed to receive header signature failed to receive header" If use a terminal program to look at the data coming into COM2 on the PC (out of COM2 on the device), at 115200/8/n/n/1, it looks like: "kITL=BB$CEPC" This seems like a problem in my installation of PB, where it's just not responding to the request from the device. I've done plenty of searching in this group, but to no avail. Any thoughts? Thank you,=20 - Paul Tag: CF 2.0 QFE Released Tag: 76307
  - 20
    - What is Winsock error code 11010? Hello, I'm the same guy who asked all those NDISUIO questions. I seem to have gotten some of it working. When I try to send regular traffic through a configured WLAN interface, I get Winsock error 11010. The last Winsock error code is 11004. The descriptions continue on the page as "OS dependent" error codes (I guess CE is an OS dependency). Counting up from 11004, the one that corresponds to 11010 is "Overlapped operation aborted", which rings a bell given that CE doesn't support overlapped operations, but I was not attempting an overlapped operation. Thanks for your help, CE gurus... Tim Tag: CF 2.0 QFE Released Tag: 76306
  - 21
    - Copying File From Device to PC Hi everyone, I found many source code example on how to copy files from device to a PC but it requires an application on the PC that call the RAPI function. This is not exactly what I want. I need to start the copy process from an application on the Device instead. How do I do that? Regards, Tag: CF 2.0 QFE Released Tag: 76295
  - 22
    - CEPC and OpenGL Hello everybody, IIUC from the Microsoft help it is possible to install WinCE on basically every PC using the generic CEPC BSP!? Or do I usually need drivers or a full BSP? What about OpenGL? Will I be able to use OpenGL also? TIA, ole Tag: CF 2.0 QFE Released Tag: 76294
  - 23
    - mem expanding on pxa270 Memory: I don't know your BSP any better than you, but likely you only have to change a definition in a .inc and/or .h file. The memory timings are configured in a register called MDCNFG (At least for PXA255), maybe you can do a search for that. They will be programmed in assembler code. Get the PXA270 datasheet, read the section on memory timings and consult with your hardware people. Flash: Do you boot from it? Please post to the mailing list only and use a thread until you have all the answers you need. Regards Piet > Hi sir: > I am porting WinCE 5.0 on PXA270. > I am just expanding the memory on our board from 64MB to 128MB, > both SDRAM and FLASH. > I have gone through the source code of BSP.but there are too > much code and no document. So I donnot know > How much time will cost. Could you plz enlight which > issues I should pay attention to ? > Regards, > Jeff Tag: CF 2.0 QFE Released Tag: 76286
  - 24
    - How to adapt remoteadmin Hello, I need a headless device with a web interface to configure it. To use remoteadmin i created a platform on the gateway template. The remoteadmin starts correctly, but how can i remove the settings that i donÂ´t need or add settings? And how can i add individual texts, pictures and menue items? Must i edit the files located in WINCEROOT\Public\servers\oak\gwadmin? Any help out there? Andy Tag: CF 2.0 QFE Released Tag: 76283
  - 25
    - Feature migration problem going from 4.2 to 5.0 I have migrated "my "old 4.2 version of the XSC1BD BSP to 5.0. This was done the following way: I got a new XSC1BD BSP for 5.0 without any ".cec" file. I imported the 4.2 (old) version of my ".cec" file into WinCE 5.0 by usage of "Manage Catalog Items". All looks fine, but when I do drag/drop of features from the Catalog to my Workspace nothing seems to happend. The feature never appeares in my Workspace. This is what the output window says when I drag/drop the "XSC1BD Serial" feature: Updating the feature and driver list for your platform. Added the Storage Devices driver to the platform. Added the Full C Runtime feature (SYSGEN_FULL_CRT) to the platform. Added the Standard I/O (STDIO) feature (SYSGEN_STDIO) to the platform. Added the String Safe Utility Functions feature (SYSGEN_STRSAFE) to the platform. Added the Serial Port Support feature (SYSGEN_SERDEV) to the platform. Added the PNP Notifications feature (SYSGEN_FSADVERTISE) to the platform. Added the Power Management (Minimal) feature (SYSGEN_PMSTUBS) to the platform. Added the Device Manager feature (SYSGEN_DEVICE) to the platform. Added the Memory Mapped Files feature (SYSGEN_NKMAPFILE) to the platform. Added the Message Queue - Point-to-Point feature (SYSGEN_MSGQUEUE) to the platform. Added the Compression feature (SYSGEN_NKCOMPR) to the platform. Added the Storage Manager feature (SYSGEN_STOREMGR) to the platform. Completed the feature and driver list update successfully. Any idea on how I can solve this is highly appreciated? /trond Tag: CF 2.0 QFE Released Tag: 76274
- Next
  - 1
    - OEMAddressTable ... Query ? Hello All, I am trying to run WINCE XIP in Flash using one the EBOOT menu options :- "Launch an existing Flash resident image". I have been able to modify the appropriate bib files and pass the control to the Kernel but it is giving the following output and just hangs in there :- Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 24 2004 at 18:25:00 ProcessorType=0411 Revision=7 sp_abt=ffff5000 sp_irq=ffff2800 sp_undef=ffffc800 OEMAddressTable = 9ca48960 By the way, I am working on MainstoneII BSP. I would like to know as to whether we have to modify the address of the OEMAddressTable when we run the kernel XIP ... in flash or the above output indicates something else ? If anyone could provide me any pointers in this regard ... it would be a great help ... ! Warm regards, Swapnil. Tag: CF 2.0 QFE Released Tag: 76271
  - 2
    - How to port WinCE 5.0 on PXA270 Dear Sir : I am porting WinCE 5.0 on PXA270. I have got the WinCE BSP and set up the platform builder. But I cannot compile and build the WinCE 5.0 BSP ,which is from the agent, the version is 3.01.002,on platform builder 5.0. I have install the catalog and build a new platform,cloning the BSP,but after complete the action,all the items undering "Build OS" is not high light! So I cannot compile and build the platform. What happen??? Is there a step-by-step guide somewhere that tells us how to get WinCE 5.0 running on the Mainstone II (PXA27x)? Went through the web searches and seems like many people have their successes getting this to work... Any help in this regard would be highly appreciated ! Thanks and regards, jeff Tag: CF 2.0 QFE Released Tag: 76266
  - 3
    - How to save wireless settings? Hi, We have a CE client which must use WEP to connect to a specified SSID wireless network, but we don't want end user to input all these information everytime this box is rebooted. Does any knows any simple way to save the wireless settings into registry or profiles which could be used by the wireless lan card? In some other discussion topics, people said that the zero configuration application must be disabled, so the saved registry could be used. But how to disable this zero configuration application? Thanks. Alaska Tag: CF 2.0 QFE Released Tag: 76255
  - 4
    - about DM320's interrupt initialization Hi, DM320TRM1a_1.5 says that we need "Setup the interrupt entry table base register (EABASE)" when initializes interrupt controller. There have a function call: // set interrupt table base address INTC_setIntTableAddress( (char*)&IRQ_Entry, 4); in TI's NoOS demo code) , but in PMC'OAL ,the function call was // set the EABASE for interrupt mapping table INTC_setIntTableAddress((char*)NULL,4); . Could PMC correctly hanlder interrupt by this way? If yes, Why? Thanks! Tag: CF 2.0 QFE Released Tag: 76250
  - 5
    - what it is on HP iPAQ? In the top of the right hand side of the iPAQ PPC, there is a power button which can turn the light of the screen ON and OFF. if you push the button, the screen will be toggled between ON/OFF state. Strangley, I found one problem on this PPC. If I install a dummy stream interface driver(this driver only displays debugging mesages), the screen is OFF forever after I push the power button. Even if I keep pushing the power button, the screen never come back and I must reset the PPC in order to view the PPC. Does anyone has such an experience with this on this device? It sounds very weird to me why the device behave like this? Tag: CF 2.0 QFE Released Tag: 76231
  - 6
    - re: PB (WinCE5.0) not hitting the break points It sounds like your symbols are wrong. I think sometimes if you rebuild while the debugger is connected, the debugger can lock the PDB file so that it's not rebuilt when your exe/dll is. Try rebuilding your module when not connected to the debugger. (I use shift-F5 to disconnect sometimes, and F5 to reconnect.) The other possibility -- if the modules are in ROM, and you did not re-make your image after rebuilding them, then there are different modules in ROM than you have PDB files for in your release directory. (Usually in that case the debugger will pop up a warning that symbols don't match the binary, but if you tell PB to permanently dismiss that warning you may not be seeing it.) If that is the problem, then remaking the image should fix your problem. You can also take a look at this blog post to see how to determine if your symbols are correct. http://blogs.msdn.com/kitlfirst/archive/2005/02/22/377629.aspx 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. _____________________________________________________________ Tag: CF 2.0 QFE Released Tag: 76229
  - 7
    - Re: Problem with Monte-carlo profiling - all modules reported as unknown 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. _____________________________________________________________ Tag: CF 2.0 QFE Released Tag: 76228
  - 8
    - 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: CF 2.0 QFE Released Tag: 76226
  - 9
    - 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: CF 2.0 QFE Released Tag: 76221
  - 10
    - 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: CF 2.0 QFE Released Tag: 76212
  - 11
    - 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: CF 2.0 QFE Released Tag: 76207
  - 12
    - 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: CF 2.0 QFE Released Tag: 76200
  - 13
    - 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: CF 2.0 QFE Released Tag: 76199
  - 14
    - 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: CF 2.0 QFE Released Tag: 76190
  - 15
    - 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: CF 2.0 QFE Released Tag: 76187
  - 16
    - 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: CF 2.0 QFE Released Tag: 76186
  - 17
    - 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: CF 2.0 QFE Released Tag: 76184
  - 18
    - 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: CF 2.0 QFE Released Tag: 76183
  - 19
    - 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: CF 2.0 QFE Released Tag: 76176
  - 20
    - 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: CF 2.0 QFE Released Tag: 76174
  - 21
    - 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: CF 2.0 QFE Released Tag: 76173
  - 22
    - 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: CF 2.0 QFE Released Tag: 76171
  - 23
    - 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: CF 2.0 QFE Released Tag: 76161
  - 24
    - 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: CF 2.0 QFE Released Tag: 76160
  - 25
    - 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: CF 2.0 QFE Released Tag: 76157

Since the "QFE Manager" doesn't seem to have announde it yet:

The PB 5.0 QFE for Compact Framework 2.0 has been released:
http://www.microsoft.com/downloads/details.aspx?FamilyID=90c1a19f-1210-4557-a000-74f8d5b4e1d0&DisplayLang=en

--
Chris Tacke
Co-founder
OpenNETCF.org
Are you using the SDF? Let's do a case study.
Email us at d c s @ o p e n n e t c f . c o m
http://www.opennetcf.org/donate

Top