Hello,
I'm new to DirectX technologies, but would like to know if DirectX (or
Direct3D) has been ported to WinCE 6.0 And if YES, what version is supported.
Also, would like to get some info on graphics that can be composed using
DirextX/Direct3D for WinCE 6.0 in the form of :

1. How many surfaces can I create at any one time. In the sense that, I have
multiple applications that will update the screen at the same time. For ex: I
could be reading/scrolling a text msg received by the phone module, while at
the same time, I would hve to update the message from the system clock to
display time in HH:MM:SS format. and say, If I increase on the phone vol at
the same time, then, I would have some graphics that would update a statusbar
also? So, as you can see, there are many sub-systems within my application,
that would simultaneously update the screen. Is this possible to achieve in
DirectX/Direct3D. Any example/project would be helpful to this end.

2. Can I get 3D support? And Who proivdes software for enabling 3D graphics.
If for example, I have a reference platform from say CompanyA, then will the
DirectX/Direct3D I download from MSFT website allow me to run 3D apps
developed for PlatformA? Or do I need some additional drivers from companyA
or MSFT or 3rd party to enable 3D support for the hardrware that I have?

Have you looked to http://msdn2.microsoft.com/en-us/library/ms172504.aspx ?

"Deepak" discussions.microsoft.com> escribi

Comments inline below...

CE 6.0 supports Direct3D Mobile. It's a stripped-down version of D3D8/D3D9
on the desktop.

You can create as many surfaces as the Direct3DMobile driver allows you to
create. The exact number is determined by size of the surface, the number of
surfaces, and the available memory pool from which the surfaces are created.
This can vary from driver to driver, but there isn't any limit imposed by the
D3DM API or driver model in this regard.

"Don Crouch" wrote:

I'm cross-posting this question from one of your previous threads:

Hi, so are you sure that the MS D3DM reference driver isn't redistributed as
the standard driver by OEMs after testing then?

HTC has been shipping on their recent HTC TyTN II/AT&T Tilt WinMob device
with a htc_d3dm.dll (in LocalHook) that LoadLibary()s a default_d3dm.dll.

Running the lights.exe from the SDK and some dumping of driver identification:
Desc: Microsoft Direct3D Mobile Reference Driver
Id: 0
Ident: 9c59509a-39bd-11d1-824c-01c04ad90dc8
Name: d3dmref.dll
Vendor: 0