Hello,

I want to talk directly to the direct3d drivers without going through the
COM direct3d api, I want to directly call D3dContextCreate,
D3dDrawPrimitive2 etc. functions that are exposed by the driver. I want to
reinvent the wheel, just as the COM d3d api usermode dll is one alternative
to get to the driver, I want to make my own alternative. However I don't
know how to do this. It all starts with an application in usermode loading
my usermode dll providing an alternative to the COM api. How does my
usermode dll penetrate into the kernel driver ?

This is on xp

I have downloaded the ddk, but haven't found an answer, it seems it's mostly
targeted at writing the driver, not on how to program the 'other end'

thanks,

--
Sigurd Lerstad

What is the need of this?

D3D COM calls are going to GdiEntry10, GdiEntry11 and similar entry points
in user-mode GDI, which in turn performs the syscalls to kernel-mode GDI/GRE.

Why do you want to bypass this?

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com

"Sigurd Lerstad" <sigler@bredband.no> wrote in message
news:%235vFjhpCIHA.3940@TK2MSFTNGP05.phx.gbl...

"Maxim S. Shatskih" <maxim@storagecraft.com> wrote in message
news:eTVs2rpCIHA.5600@TK2MSFTNGP04.phx.gbl...
I would imagine that the COM calls add layers of indirection and virtual
function calls, hurting performance somewhat (if the CPU is the bottleneck,
which with Direct3D is doubtful).

Or maybe the OP just wants to learn about DirectX internals.

"Sigurd Lerstad" <sigler@bredband.no> wrote:
Unlike GDI, the Direct3D APIs are a very thin layer on top of the driver.
There is actually very little overhead between the application and the
driver. That's one of the beauties of D3D.
--
Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc.