| Thread | Last Post | Replies |
|
| Problem in WinCE 6.0 USB Composite Driver | 07 May 2008 16:06 GMT | 1 |
I am Porting USB Composite Driver in WinCE 6.0, I am using Two Composite Client Device(Composite Driver Child Device) 1. USB_Serial Client and 2. Mass_Storage_Device Client
|
| VS2008 PlugIn | 07 May 2008 14:47 GMT | 2 |
do you know if there will be a PB 6.0 Plugin for Visual Studio 2008? Regards
 Signature Javier Grijalba
|
| internal serial ports on CE4.2 vs CE5.0 | 07 May 2008 14:17 GMT | 2 |
I have a PC-104 RF transceiver plug-in module that requires a normal serial port configuration in order to communicate. I had been using the following serial port setup in my platform.reg for CE4.2: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial5]
|
| RTL 8139 is not working on Wince 5.0 | 07 May 2008 13:13 GMT | 1 |
Pls help me if anybody using the rtl 8139 pci card on wince 5.0. Becoz i was tried last 3 weeks, my rtl 8139 card driver is not working. Pls give me the fixed solution . thank you.
|
| IoBase conflict in seiral port | 07 May 2008 12:30 GMT | 4 |
I test WinCE5.0 at x86 platform. One strange thing in serial port confused me. Per my past experience , serial driver get IoBase address according to the IoBase value in platform.reg. [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial2]
|
| setFPEmul() missing | 06 May 2008 21:50 GMT | 5 |
I have migrated our project from CE5.0 to CE6.0 on a ICOP PC104 platform. In 5.0 there was a problem in the init part of the private kernel code that cuased the kernel to essentially crash if power was cycled too quickly on the device. We had a fix for it in the private code. I ...
|
| Unable to dismount | 06 May 2008 20:31 GMT | 2 |
Hi, I am running an x86 CEPC (5.0) with PCI IDE drives configured as follows: [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\PCI\Template\GenericIDE\Device0] "Prefix"="DSK"
|
| Mouse pointer in Windows Ce 5.0 | 06 May 2008 16:27 GMT | 1 |
is there a option in Windows Ce 5.0 to change the mouse pointer for the whole system? There has to be a bitmap somewhere, that can be changed before building my run-time-image!?! Any suggestions? Thanks for help.
|
| Build error after QFE's Jan/Feb/march 2008 | 06 May 2008 15:21 GMT | 7 |
C:\WINCE600\PUBLIC\COMMON\CESYSGEN>NMAKE /nologo C:\WINCE600\PUBLIC\COMMON\OAK\LIB\ARMV4I\RETAIL\0409\wldap32.res 1>nul Copying fulllibc.* NMAKE : fatal error U1077: 'xcopy' : return code '0xc0000005'
|
| new vs. LocaAlloc when determining heap memory size | 06 May 2008 14:44 GMT | 1 |
Using the ToolHelp functions and the Remote Performance Monitor I've been trying to determine the Heap memory size in my application. This does not seem to work when using 'new' to allocate memory from the heap, however when using 'LocalAlloc' I can monitor the changes.
|
| KDBG hangs | 06 May 2008 13:38 GMT | 1 |
Hi everybody I'm still working on my ARM platform trying to bring up the debugger. I'm using a serial port connection for KITL with an interrupt based mecanism. If I disable the debugger, I am able to connect the platform and run remote
|
| dhcp server from ce 5.0 | 06 May 2008 09:28 GMT | 1 |
hi? I have been implementing a NAT device using Ce 5.0. I have 4 lan ports and 1 wan port. And I configured a dhcp server for lan port by following registry setting.
|
| CE5 to CE6 port, Kitl Question | 05 May 2008 19:36 GMT | 1 |
I am porting an existing BSP to CE6 and have followed the migration guide regarding the new Kernel/OAL/Kitl architecture. I have oal.exe and kitl.dll built as well as the rest of the ROM image. I also have the bootloader ported and functional.
|
| WinCE 6.0 link failure | 05 May 2008 18:43 GMT | 1 |
After doing a fresh install of VS 2005 w/ PB 6.0 and after carefully doing all updates in the order listed on the March 2008 update page, I get this error when building a new OSDesign... -------------------------------------------
|
| Problems Disabling Automatic Screen Off for Display Driver. | 05 May 2008 18:28 GMT | 8 |
I have a platform running Windows CE 6.0 and am having some problems having the Display Stay on (it is turning off automatically when I don't want it to.) We basically do not want any idle or inactivity timers to be used by
|