Hi Matthew,
The registration process is showing successful but audiodg.exe is getting
crashed. And if I restart the audiosrv or physical machine, I am unable to
see the apo dll in audiodg.exe's associates modules list(This can be view
through resource monitor). So it might me privilege issue if the path is
"user desktop directory".
Regards,
Rajendra
On Tue, Mar 5, 2019 at 2:38 PM Matthew van Eerde <
dmarc-noreply@xxxxxxxxxxxxx> wrote:
- I already changed the APO CLSIDs
OK, good. Just making sure.
- It was not working
Please elaborate on “not working”. What is the behavior your observe?
Logs might also help:
https://blogs.msdn.microsoft.com/matthew_van_eerde/2017/01/09/collecting-audio-logs-the-old-fashioned-way/
*From: *Rajendra Sethi <rajendra.sethi11@xxxxxxxxx>
*Sent: *Tuesday, March 5, 2019 12:50 AM
*To: *wdmaudiodev@xxxxxxxxxxxxx
*Cc: *Etienne Dechamps <etienne@xxxxxxxxxxxx>
*Subject: *[wdmaudiodev] Re: Why my apo dll is only loads from
c:\windows\system32
Hi Matthew,
Thank you for your suggestion.
It's getting registered after keeping the DLL in OS Directory i.e,
C:\. It was not working when i tried the registration from user Desktop
directory. And I already changed the APO CLSIDs .
On Mon, Mar 4, 2019 at 6:32 PM Matthew van Eerde <
dmarc-noreply@xxxxxxxxxxxxx> wrote:
Every bug report should contain three things – what you did, what you
expected to happen, and what actually happened.
You have two of the three. What actually happened?
Is the audio engine loading the version of the .dll in
C:\windows\system32? Is it trying to load the version of the .dll in the
other location, but failing? If it is failing, what is the error code?
Whenever you make a copy of the sample APO, it is very important to change
the APO CLSID. Otherwise, if your driver ends up on the same system as
someone else’s, your APO CLSIDs will collide, and there is no good possible
outcome. You will need to change the CLSID in both the APO implementation
and in the COM registration in the .inf.
*From:* wdmaudiodev-bounce@xxxxxxxxxxxxx <wdmaudiodev-bounce@xxxxxxxxxxxxx>
on behalf of Rajendra Sethi <rajendra.sethi11@xxxxxxxxx>
*Sent:* Monday, March 4, 2019 4:03:12 AM
*To:* Etienne Dechamps
*Cc:* wdmaudiodev@xxxxxxxxxxxxx
*Subject:* [wdmaudiodev] Re: Why my apo dll is only loads from
c:\windows\system32
Hi Etienne,
Thanks for the suggestion.
Regards,
Rajendra
On Mon, Mar 4, 2019 at 4:59 PM Etienne Dechamps <etienne@xxxxxxxxxxxx>
wrote:
The Windows Audio Engine service that loads APO DLLs runs under
limited privileges and doesn't have access to large parts of the
filesystem.
To solve this problem, either make sure that service has the necessary
filesystem ACLs to access your APO DLL, or move the DLL to some
location the service has access to.
Pointing the Process Monitor tool to the audiodg.exe process is a good
way to troubleshoot this kind of problem.
On Mon, 4 Mar 2019 at 10:32, Rajendra Sethi <rajendra.sethi11@xxxxxxxxx>
wrote:
swapapo project from different location(not c:\windows\system32). But I am
Hi All,
I am trying to load the apo dll which is a copy of windows sample
not able to load the dll.
I am registering the DLL using regsvr32 "Location\swapapo.dll".
Any suggestions?
--
Thanks And Regards
Rajendra Sethi
--
*Thanks And Regards*
* Rajendra Sethi*
--
*Thanks And Regards*
* Rajendra Sethi*