No I did not change the inf file except for commenting out this line : CatalogFile=msvad.cat I guess you suggested earlier that there may be some "ETW tracing events" built into the audio engine. But I am not sure how to capture such events. On Tue, Mar 6, 2012 at 4:42 PM, Tim Roberts <timr@xxxxxxxxx> wrote: > 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. > >