Remote Hooking (Windows CE 5.0)

Send Feedback

Remote hooking is intended for:

  • Drivers that access hardware co-processors that require synchronized access.
  • OEM installations.

In the remote hooking model, the driver is loaded into the GWES.exe process space. This is intended to be the same driver DLL that is being used as the system's display driver.

Microsoft® Direct3D® Mobile uses protected server libraries (PSL) cross-process calls to call the display driver. The Direct3D Mobile middleware takes the GWES lock before calling the driver, which ensures that all calls into the driver are synchronized.

A remotely hooked driver is identified by a string setting, see Direct3D Mobile Driver Registry Settings.

See Also

Driver Interactions with the Direct3D Mobile Middleware | Display Driver Security

Send Feedback on this topic to the authors

Feedback FAQs

© 2006 Microsoft Corporation. All rights reserved.