You can read up on the Declarative, Componentized, Hardware Support App (DCH)
design principles here:
DCH Design Principles and Best Practices - Windows drivers | Microsoft
Docs<https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/dch-principles-best-practices>
If you were to include an AddComponent directive in your own .inf, then you
would still have to solve the problem of how to get your .inf deployed to the
desired systems in such a way as is compliant with the DCH principles.
From: wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx> On
Behalf Of Wayne
Sent: Tuesday, November 23, 2021 10:15 PM
To: wdmaudiodev <wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: [EXTERNAL] Re: How to verify software component
aginst WHCP without hardware?
You don't often get email from brocean@xxxxxxxxx<mailto:brocean@xxxxxxxxx>.
Learn why this is important<http://aka.ms/LearnAboutSenderIdentification>
Hi Matthew:
Thanks for your guidance, and I found that most AddComponent directives was
put in an extension.inf file.
Could the extension.inf with the directive AddComponent in be included in my
driver package? Then I can associate the APOs to many mainstream sound cards.
Is this kind of driver package acceptable by WHCK and get certified?
Best Regards.
Wayne Wang
On Tue, Nov 23, 2021 at 12:58 AM Matthew van Eerde
<dmarc-noreply@xxxxxxxxxxxxx<mailto:dmarc-noreply@xxxxxxxxxxxxx>> wrote:
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://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-hardware%2Fdrivers%2Finstall%2Finf-addcomponent-directive&data=04%7C01%7CMatthew.van.Eerde%40microsoft.com%7C0ceadca12fb54185b64c08d9af11d064%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637733313913768728%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=m%2BCE8iKJzZ3%2FXYS3P8%2Fto1gQ%2FKuHtoQi4qfmMoMGpgs%3D&reserved=0>
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<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>
<wdmaudiodev-bounce@xxxxxxxxxxxxx<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx>> On
Behalf Of Wayne
Sent: Monday, November 22, 2021 1:19 AM
To: wdmaudiodev <wdmaudiodev@xxxxxxxxxxxxx<mailto: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?
