What you would do is make up a "software component hardware ID" for your APO.
It would begin with APO\....
An IHV that wanted to use your APO would put an AddComponent line in their .inf
that referenced your APO.
INF AddComponent Directive - Windows drivers | Microsoft
Docs<https://docs.microsoft.com/en-us/windows-hardware/drivers/install/inf-addcomponent-directive>
You would author a driver package which was targeted to this hardware ID,
certify it, and put it on Windows Update.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> On
Behalf Of Wayne
Sent: Monday, November 22, 2021 1:19 AM
To: wdmaudiodev <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [EXTERNAL] [wdmaudiodev] Re: How to verify software component aginst
WHCP without hardware?
Some people who received this message don't often get email from
brocean@xxxxxxxxx<mailto:brocean@xxxxxxxxx>. Learn why this is
important<http://aka.ms/LearnAboutSenderIdentification>
Hi! Tim:
Thanks for your kind reply.
The APOs will be installed with a specific hardware, such as HDAudio
device, USB audio device.
My question is when qualifying the APOs in WHCK, and submitting WLK
signature for catalog file, is the software itself acceptable? Or the APOs
should be associated with a hardware by an IHV(independent hardware vendor) to
be qualified WHCP?
We are not IHV, don't have any hardware products. We sold only software, and
wanna have our algorithm certified by WHCP.
Best Regards.
Wayne Wang
On Mon, Nov 22, 2021 at 2:40 PM Tim Roberts
<timr@xxxxxxxxx<mailto:timr@xxxxxxxxx>> wrote:
On 11/21/21 1:24 AM, Wayne wrote:
Some sound effects are to be implemented in APOs, which will be
shown as software component in the device manager after installed.
Could the APOs be verified against WHCP alone without any hardware
audio device, and get signed or get a logo?
