| Previous | Next |
| ERROR_GRAPHICS_OPM_VIDEO_OUTPUT_DOES_NOT_HAVE_OPM_SEMANTICS | ERROR_GRAPHICS_OPM_INVALID_CONFIGURATION_REQUEST |
ERROR_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED
Protection level support does not imply signaling-command support
ERROR_GRAPHICS_OPM_SIGNALING_NOT_SUPPORTED is returned when the driver does not implement the ACP/CGMS-A signaling GUIDs used by Configure or the COPP-compatible query path. These commands carry television-standard and aspect-ratio data in addition to the protection level itself.
Differentiate this result from OUTPUT_DOES_NOT_SUPPORT_ACP or OUTPUT_DOES_NOT_SUPPORT_CGMSA. Here the missing capability is the signaling interface, so repeatedly changing the requested level cannot make the command valid. Log the exact command GUID, semantic mode, connector type, and advertised protection types; then update the display driver or choose an output path whose miniport implements the required signaling contract.
What proves an unsupported signaling interface
- The GUID placed in
OPM_CONFIGURE_PARAMETERS.guidSetting. - Whether the call used OPM Configure or COPPCompatibleGetInformation.
- Driver support for the corresponding get and set signaling requests.
- The television standard and aspect-ratio masks supplied by the caller.
References
- Microsoft: list of OPM command GUIDs
- Microsoft: ACP and CGMS-A signaling payload
- Microsoft: Configure method contract
Looking for a different code? Search another status or error code.