[wdmaudiodev] Re: MSVAD sample and Audio engine traces

  • From: Rashee Chadha <rashee182@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Tue, 6 Mar 2012 17:33:12 -0800

Thanks Mathhew ! Its installed now :)

There were further references to this vaddyn.sys in the inf file which I
removed.

Can you please tell me how I can enable some traces of portcl.sys,
audioeng.dll and audiokse.dll.  And does the sample include some test which
I can execute to see the audio playback/record functionality?

On Tue, Mar 6, 2012 at 5:10 PM, Matthew van Eerde <
Matthew.van.Eerde@xxxxxxxxxxxxx> wrote:

>  Build all of the missing MSVAD files and put them next to the .inf prior
> to installation.****
>
> ** **
>
> The error below may be due to a cached version of the .inf which still
> includes a reference to vaddyn.sys.****
>
> ** **
>
> *From:* wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:
> wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Rashee Chadha
> *Sent:* Tuesday, March 6, 2012 4:59 PM
>
> *To:* wdmaudiodev@xxxxxxxxxxxxx
> *Subject:* [wdmaudiodev] Re: MSVAD sample and Audio engine traces****
>
>  ** **
>
> Yes. And If I remove the refernce of this sys file from inf, I get such
> errors :****
>
>  ****
>
> Driver package references a missing external file
> 'C:\Windows\system32\drivers\vaddyn.sys'. Error = 0x00000002****
>
>  ****
>
>    Installing NULL driver!
> !    dvi:                A NULL driver installation is not allowed for
> this type of device!
> !!!  dvi:                Cleaning up failed installation (e0000219)
> !!!  dvi:           Default installer: failed!
> !!!  dvi:           Error 0xe0000219: The installation failed because a
> function driver was not specified for this device instance.****
>
> However this file is not generated as a part of this package.****
>
> On Tue, Mar 6, 2012 at 4:50 PM, Matthew van Eerde <
> Matthew.van.Eerde@xxxxxxxxxxxxx> wrote:****
>
> All files that are referenced anywhere in the .inf need to be present for
> the driver to install, even if they are not used for the given device.****
>
>  ****
>
> *From:* wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:
> wdmaudiodev-bounce@xxxxxxxxxxxxx] *On Behalf Of *Tim Roberts
> *Sent:* Tuesday, March 6, 2012 4:42 PM
> *To:* wdmaudiodev@xxxxxxxxxxxxx
> *Subject:* [wdmaudiodev] Re: MSVAD sample and Audio engine traces****
>
>  ****
>
> Rashee Chadha wrote: ****
>
>   ****
>
> I have just started working on WDM audio drivers. I am referring to the
> MSVAD sample driver which comes with the DDK.****
>
>  ****
>
> I used the devcon utility to install this driver (on a Win7 VMWare Virtual
> Machine):****
>
>  ****
>
> *devcon install msvad.inf *MSVADSimple*****
>
>  ****
>
> *Initially I got the error of missing cat file. On commenting out this
> dependancy from inf file, I get yet another error of missing vaddyn.sys
> file.*****
>
> *This sys file was not generated when I built the entire MSVAD solution.**
> ***
>
>
> Did you change the INF?  The INF in the sample maps the *MSVADSimple
> device identifier to vadsimpl.sys.  It does not have the name "vaddyn.sys"
> anywhere.  If you changed that name in the INF, then you have to change the
> name of the binary that you build.
>
>
> ****
>
> *Additionally I would like to capture
> traces for audioeng.dll,audiokse.dll and portcl.sys. This would help me in
> understanding the call flow from the audio engine upto the sample miniport.
> *****
>
> *Which setting I need to do in order to achieve this.*****
>
>
> I'm not convinced that such traces are available.****
>
> -- ****
>
> Tim Roberts, timr@xxxxxxxxx****
>
> Providenza & Boekelheide, Inc.****
>
> ** **
>

Other related posts: