Typically these things are monitored with filter drivers. A few
questions:
Why do you want both URB’s and IRP’s? For the most part these are
differing level things, in that you deal with IRP’s to a point where the
URB’s are generated.
Why in the world would you do this with WDM instead of KMDF. Most
of the filter driver is going to be PnP/Power bookkeeping if you do WDM,
but that is exactly what KMDF will take care of for you.
> Dear All, > > We are developing MFC based application to test USB Mass Storage Devices. > Application will access USB Mass Storage Device using Kernel Mode Client. > > We are developing WDM based Kernel Mode Driver for the same. > > One of the requirement of application is to capture all IRPs and URBs which > are travelling in stack. > > Can anybody put light, How application like USBLyzer capture this > information and How this information is communicated to application for > Display? > > Thanks in advance!! > > Regards > Sunil
The filter driver is KMDF which simplifies it a whole bunch.
On Sat, Sep 18, 2010 at 5:50 AM, Sunil Kumar wrote:
> Dear All, > > We are developing MFC based application to test USB Mass Storage Devices. > Application will access USB Mass Storage Device using Kernel Mode Client. > > We are developing WDM based Kernel Mode Driver for the same. > > One of the requirement of application is to capture all IRPs and URBs which > are travelling in stack. > > Can anybody put light, How application like USBLyzer capture this > information and How this information is communicated to application for > Display? > > Thanks in advance!! > > Regards > Sunil > > > > > — NTDEV is sponsored by OSR For our schedule of WDF, WDM, debugging and > other seminars visit: http://www.osr.com/seminars To unsubscribe, visit > the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer