Export (0) Print
Expand All

Direct3D Mobile Driver Registry Settings (Windows Embedded CE 6.0)

1/6/2010

The registry stores information necessary to configure the system for applications and hardware devices. The registry also contains information that the operating system continually references during operation.

Ee484822.note(en-US,WinEmbedded.60).gifNote:
The default registry values vary depending on which components are included in your run-time image. For more information, see Default Registry Settings.

Locally hooked drivers are loaded into a Microsoft® Direct3D® Mobile application's process space. For more information, see Local Hooking. You identify a driver as being locally hooked with the registry key HKEY_LOCAL_MACHINE\System\D3DM\Drivers\LocalHook. Set the value of this key to the fully qualified name of the driver, which includes the complete path.

Remotely hooked drivers are loaded by GWES.dll within the nk.exe process space. For more information, see Remote Hooking. You identify a driver as being remotely hooked with the registry key HKEY_LOCAL_MACHINE\System\D3DM\Drivers\RemoteHook. Set the value of this key to the fully qualified name of the driver, which includes the complete path.

You can enable debug zones for debug configurations when developing a Direct3D Mobile driver. Debug zones are not registered until the driver's dynamically linked library (DLL) is loaded, but the DLL is not loaded until you start the application. As a result, the easiest way to enable your driver's debug zones is by using registry settings for either your development workstation or on your target device. For more information, see Debug Zone Registration.

When you set a debug zone on the development workstation by using the HKEY_CURRENT_USER\Pegasus\Zones registry key, the debug zone is activated when the application or DLL is loaded. If the application or DLL is already loaded, you must unload it and reload it, or reset the target device for the debug zone to take effect.

When you set a debug zone in the target device's registry under HKEY_LOCAL_MACHINE\DebugZones, the zone is activated the next time the application or DLL is loaded.

Whether you set the debug zone from the development workstation or the target device, the following table shows the Direct3D Mobile debug zone values.

Zone Bit

Errors

0

Parameter Checking

1

Memory Allocation

2

Synchronization

3

Messages

4

Reference Counting

5

Community Additions

ADD
Show:
© 2014 Microsoft