Hi all,

I was asked if desktop PC mainboards are eligible to use with Windows CE
.NET 4.2 . I made a quick research at www.microsoft.embeddedoem.com about
the supported processors and drivers and BSPs. So far as I understand if a
board has one of the supported processors and there are drivers for certain
chipsets on it (such as audio, video, LAN/WAN, serial, parallel, USB ports,
etc.) , I can use that board with Windows CE .NET 4.2. However I will
probably not get a bsp support since the configurations may vary or the oem
manufacturer may not support embedded operating systems on driver basis.

I will accept opinions about this subject. Any experiences or
recommendations are also welcome. Thanks in advance,

--
Selin Metin
selinm_at_esit_dot_com_dot_tr

Re: Desktop PC mainboard for Windows CE .NET 4.2 by Valter

Valter
Thu Oct 21 08:42:24 CDT 2004

"Selin Metin" <nospam@nospam.com.tr> wrote in
news:egXMYt2tEHA.1472@TK2MSFTNGP10.phx.gbl:

> Hi all,
>
> I was asked if desktop PC mainboards are eligible to use with
> Windows CE .NET 4.2 . I made a quick research at
> www.microsoft.embeddedoem.com about the supported processors and
> drivers and BSPs. So far as I understand if a board has one of the
> supported processors and there are drivers for certain chipsets on
> it (such as audio, video, LAN/WAN, serial, parallel, USB ports,
> etc.) , I can use that board with Windows CE .NET 4.2. However I
> will probably not get a bsp support since the configurations may
> vary or the oem manufacturer may not support embedded operating
> systems on driver basis.
>

If you have all the drivers you need (you are not limited to those
provided by MS, many hardware manufacturers release Windows CE drivers)
you can build your own BSP starting with a clone of the CEPC BSP,
removing the wrong drivers and adding your own.
Some mainboard or SBC manufacturers provide ready-to-use WinCE BSPs for
their boards but usually those are for PC/104 or small form factor
(5,25 or mini-ITX) boards.

--
Valter Minute
vminute@inwind.it (the reply address of this message is invalid)