Matthew,
Thanks for the quick reply. I have run ApiValidator.exe from the command
prompt and it only complains about DriverCallback not InterlockedIncrement /
InterlockedDecrement:
ApiValidation: Warning: API DriverCallback in winmm.dll is not a supported
universal API.
I'm not trying to make a Universal driver, as we can only run on desktop PCs
(we make a PCI Express card!), so how can I get around this failure in the
HLK?
I guess another question is, why is ApiValidator in HLK complaining about
our use of InterlockedIncrement / InterlockedDecrement when those clearly
were OK for our competitors driver?
Thank you,
David A. Hoatson
Lynx Studio Technology, Inc.
<http://www.lynxstudio.com/> www.lynxstudio.com
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Matthew van Eerde
(Redacted sender "Matthew.van.Eerde" for DMARC)
Sent: Friday, June 07, 2019 12:38 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: HLK ApiValidator Failure
After searching the webs, this article might help you, especially the "link
to onecoreuap.lib" part.
https://docs.microsoft.com/en-us/windows-hardware/drivers/develop/validating
-universal-drivers
_____
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> <wdmaudiodev-bounce@xxxxxxxxxxxxx
<mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx> > on behalf of Matthew van Eerde
<dmarc-noreply@xxxxxxxxxxxxx <mailto:dmarc-noreply@xxxxxxxxxxxxx> >
Sent: Friday, June 7, 2019 12:34:49 PM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] Re: HLK ApiValidator Failure
Sorry, I am not familiar with ApiValidator.
You can follow these steps to troubleshoot HLK failures in general:
https://docs.microsoft.com/en-us/windows-hardware/test/hlk/user/troubleshoot
ing-windows-hlk
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.micr
osoft.com%2Fen-us%2Fwindows-hardware%2Ftest%2Fhlk%2Fuser%2Ftroubleshooting-w
indows-hlk&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7C86af9e80caee4a
7a73b708d6eb7f4d51%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636955329339
830107&sdata=NbaM2O7pVddmfm6Kg77y%2BGdZAebdzeJFOTBy2dLYmUE%3D&reserved=0>
In particular you can go to https://support.microsoft.com/
<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsupport.m
icrosoft.com%2F&data=02%7C01%7Cmatthew.van.eerde%40microsoft.com%7C86af9e80c
aee4a7a73b708d6eb7f4d51%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6369553
29339840119&sdata=AIBKHceQiShlC6k9EmwWVNcnB1%2BYSKpwyMYdjtbwP2Q%3D&reserved=
0> > Support for business > Get started > Select the product family:
"Developer Tools" > Select a product: "Windows Driver Kit (WDK, HLK)" >
Select the product version: "Hardware Lab Kit for Windows 10".
You should open a separate support case for each failure, and provide an
.hlkx file containing the failing log.
From: David A. Hoatson <mailto:dhoatson@xxxxxxxxxxxxxx>
Sent: Friday, June 7, 2019 11:21 AM
To: wdmaudiodev@xxxxxxxxxxxxx <mailto:wdmaudiodev@xxxxxxxxxxxxx>
Subject: [wdmaudiodev] HLK ApiValidator Failure
Hello,
Hopefully Matthew can shed some light on this.
I am trying to get through the HLK tests and the first one that fails is
ApiValidator. It is complaining that we are calling InterlockedIncrement /
InterlockedDecrement and DriverCallback. Both InterlockedIncrement and
InterlockedDecrement are called from Combase.cpp because we have an ASIO
driver that uses COM. Other drivers that also have ASIO are using
InterlockedIncrement / InterlockedDecrement and have passed HLK.
DriverCallback is used for our Mixer UI and is completely unrelated to audio
streaming.
Why is the ApiValidator complaining about these calls and how to I get
around it?
Thank you,
David A. Hoatson
