Creating WinCE images

I previously added a post on the 24th of February (see "Using Embedded
VisualC to debug a driver") as I was having problems debugging a driver that
is built within the 14MB binary image of the WinCE system, provided to me by
the CPU board vendor (Prolificx).

Hence, I am now left in the unenviable position of waiting for Prolificx to
debug the driver for me, else investing in the necessary software
development platform tools so that I can build and debug the driver myself.

Can anyone advise me on what I will need.

Currently, the only platform tools we have are embedded Visual C++ 4 and
Active Sync. I expect we need a full WinCE SDK or similar. Maybe there are
evaluation/trial kits evailable that would save us paying out alot of money
to simply solve one bug.

Thanks for your help,
Stuart.

Yannick
Tue Mar 01 00:59:06 CST 2005

First, you should have Platform Builder. Evaluation version are available
for free from MS Website (download or CD order)

Next you'll need a BSP for your target. This is something you should obtain
from the manufacturer of your board.

BR

--
----------------------------------------------------------------
Yannick Chamming's (eMVP)
ADENEO (ADESET)
Windows Embedded Manager
ychammings AT adeset DOT com>
http://www.adeset.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

"StuartG" <stuartgalt73@hotmail.com> wrote in message
news:#MjTl0gHFHA.1172@TK2MSFTNGP12.phx.gbl...
> I previously added a post on the 24th of February (see "Using Embedded
> VisualC to debug a driver") as I was having problems debugging a driver
that
> is built within the 14MB binary image of the WinCE system, provided to me
by
> the CPU board vendor (Prolificx).
>
> Hence, I am now left in the unenviable position of waiting for Prolificx
to
> debug the driver for me, else investing in the necessary software
> development platform tools so that I can build and debug the driver
myself.
>
> Can anyone advise me on what I will need.
>
> Currently, the only platform tools we have are embedded Visual C++ 4 and
> Active Sync. I expect we need a full WinCE SDK or similar. Maybe there are
> evaluation/trial kits evailable that would save us paying out alot of
money
> to simply solve one bug.
>
> Thanks for your help,
> Stuart.
>
>