I'm having problems building an image after installing the 4.2 QFE
updates. This happens on both the evaluation and the full version which
I recently purchased. If no updates are installed, the image builds
fine.

I have a device that is running Windows CE 4.2 with the certification module
(OEMLoadInit/OEMLoadModule)enabled. There are different sets of
public/private keys. I have signed the .exe and .dll files used by the
Remote Tools (process viewer, registry editor, etc.) with a "trust" ...

I'm trying to figure out how PB projects choose where the output files
go and are named.  For example if I create my own project named TEST it
outputs as TEST.exe.
Fine... but I'm using the Emulator and it uses ddi.dll as its display

I have some question on the system timer.
1.The global scheduling variables, dwReschedTime in PB4.2.
 Is the kenel set the dwReschedTime value and keep it change by the
thread scheduling algorithm ?

I did have a perfectly working PB platform to which I added various things
from the Catalog, now when I Sysgen it I get errors (see below a snippet
from build.log). It seems to be requiring the Fibre API which I also added
from the catalog. What am I missing?

I have some queries related to the SD-Card (Memory).
Background Information :-
Processor        :- Intel PXA270.
Reference BSP :- MainstoneII from PB 5.0

platform :smdk2410
I want to create a chinese NK.nb0 ,but it made a about 29M nk.nb0, My
device only hase 32M Nanflash, I cann't write it to Nanflash  using DNW.exe
.  after I upgrade my kernel file , It did not show any error message ,  but

I have built CE5 for CEPC (Pent.III), am able to boot nk.bin from
harddrive, but for some reason it does not see the network card. The
card is there and is OK, since if I create an image with KITL, I can
eboot it without problem, yet when I use ldr to boot from HD, Windows

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

I have written a socket application like echo server to test my NDIS
miniport driver.
I have TCP client runs on Windows XP and echo server running on WinCE.
TCP client application continuously sends some known pattern. On echo

I have created a new project where i have to call some of Assembly functions
(Instructions x86 processor related) please note that the assembly file is a
separate .asm file and i dont want to use inline assembly program in my C
code.

I met a big problem on my mips32 wince 5.0 tiny kernel platform, please help
me!
1)When load filesys.exe, exception 004 occus. The following is the debug
message:

We are Bangalore, India based product company. We are wanting to purchase
the WinCE 5.0 for building custom target image for a TI OMAP platform.
Could you please let me know who is the right person to contact in APAC
sales for this. I understand that there is a qualifying process ...

 We are starting a new platform development. We are planning to use WinCE
5.0, and we will like to know what is the most recommended JTAG probe for
real hardware debugging via the microprocessor JTAG interface. We Know the
ARM Multi-ICE and the EPI Majic probe, and they say they ...

Some background:
My build environment:
Visual Studio 2005 and Platform Builder 5.0.
This article: