IUnregisterPhysicalConnection interface implements three methods to remove a registered physical connection. The port driver implements this interface. To determine whether a port driver supports the
IUnregisterPhysicalConnection interface, a miniport driver calls the port driver object's QueryInterface method with REFIID IID_IUnregisterPhysicalConnection. The miniport driver is responsible for releasing the
IUnregisterPhysicalConnection object after it is no longer needed. The
IUnregisterPhysicalConnection interface inherits from IUnknown.
In Windows Vista, Windows Server 2003 with Service Pack 1 (SP1), and Windows XP with Service Pack 2 (SP2), the following port drivers support the
Earlier versions of Windows, including the Windows Server 2003 and Windows XP releases, do not support
IUnregisterSubdevice. However, hot-fix packages that contain updated versions of the PortCls system driver (portcls.sys) that support
IUnregisterSubdevice are available for Windows Server 2003, Windows XP, and Windows 2000. For more information, see Dynamic Audio Subdevices.
The three methods in this interface "unregister" physical connections that were registered previously by calls to the PcRegisterPhysicalConnection, PcRegisterPhysicalConnectionFromExternal, or PcRegisterPhysicalConnectionToExternal routines. PortCls supports the three PcRegisterPhysicalConnectionXxx routines in Windows 2000 and later, Windows Millennium Edition, and Windows 98.
The port driver uses the information that it obtains from PcRegisterPhysicalConnectionXxx calls to respond to KSPROPERTY_PIN_PHYSICALCONNECTION property requests.
When deleting a subdevice from an adapter's topology, the driver must unregister the subdevice's physical connections to that portion of the topology. Failure to unregister the subdevice's physical connections can cause memory leaks.
In addition to the methods that
IUnregisterPhysicalConnection inherits from the IUnknown interface,
IUnregisterPhysicalConnection supports the following methods:
Build date: 11/16/2013