TheTwistedOne,

Can you be a little more specific?

Isn''t COM taken care of within the real DirectX dll? If so, why
should I be worried if it works behind the scenes?

Wayfarer

I think this is what TwistedOne is refering to:
In order to get the functions in the "fake" dll to be run, you have to implement and register all the interfaces that the normal DirectX dll will implement. However, because the IIDs are then registered to the "fake" dll there''s no way to get the entry points into the normal dll at runtime. You can''t probe the IUknown::QueryInterface on the IIDs, because the interface is pointing the "fake" dll.

I suppose you could get around this by manually identifying the entry points to each API function in the DirectX DLLs and explicitly binding to each one (either at runtime with LoadModule, or with some compile time hack). However, this would bind you to one specific DirectX version.