Debojyoti

Thanks for the serise of videos on WInDbg and Driver Verifier. I am finding them very useful in my day to day work.

I have doubt regarding driver verifier. If I am developing a WDF driver of File System mini filter driver or a NDIS filter drivers; is it sufficient just to add my driver on the driver verifier?

For example, If have a FS mini filter driver (which I want to test); do I need to put fltmgr.sys(or any other related drivers) in Driver Verifier driver list?  

@windev and @ChadBeeder , Thanks. I will try out xperf...

@ChadBeeder Actually I am facing a problem with my filter driver. The driver is for volume wide encryption of files.

The driver attaches itself on top of removable media only and it works fine. There is a 6x delay when an USB drive is first attached to the system. Generally it takes 20 - 30 second to install the driver but with my filter driver it takes somewhere about 2 mins. The delay is not the there when the USB drive is plugged into the system from second time onwards.

It's certain that the delay happens for my filter driver but I am not sure how to approch this problem.

Can I find if an USB drive have added any autorun or scripts in the system,after it has been plugged into the system??

@windev I understood the point.

Thanks for your reply. ProcMon is a good tool and I use it in a great extent to get my work done.

It would be nice if you put something on Channel 9 on NetMon (http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=4865).

I am looking forward for the next videos.

Hi,

Nice videos in show.

Process explorer shows what are all the handle (also the File Object associated with it) is held by process. Process monitor shows us the Win32 calls.

Can we combine those two pieces of information? Can we get the handle value returned from CreateFile call (shown in the ProcMon)?