Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
More Info on Driver Writing and Debugging
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Best Of
Re: Virtual PCIe driver
Not without unreasonable effort, no. It depends how complicated your device is. If you are religious about using the HAL macros to access your registers (like READ_REGISTER_ULONG), you can replace those macros with calls to an emulation library. It isn't quite the same thing, but it can help you get the register sequencing right.
It may be possible to implement such a thing using a Hypervisor app, but in my opinion, that's way more trouble than it's worth.
Re: Does $scmp() $sicmp() $spat() take Expressions ?
Re: WFP verifier issue
Hey, I know this is a very old thread, but I thought it's worth asking the question here. I have encountered the same issue with the driver verifier.
Could you please tell me how can I add exception for this? Verifier detects violation on my driver only if "Pool tracking" is only, and only for localRedirectContext field. Can we somehow enable "Pool tracking" but tell the verifier to ignore memory for the field localRedirectContext ?
Any help greatly appreciated! 
khayk
Re: Extended validation code signing certificate
Different Certificate Authorities sell EV Certs with different validity periods.
During the Cert’s validity period you can use it to sign code. When the cert’s validity period ends, the code will still be signed (and drivers signed will still load), but you no longer use the (now expired) cert to sign additional drivers.
Peter
Re: Extended validation code signing certificate
A code signing certificate is issued to a COMPANY, and you use it to sign an executable (for example) to "prove" who wrote the code. As long as the certificate is valid (they DO expire) you can use that certificate as many times as you want.
Peter
Re: What is the right way to include new Hardware ID in already existing inbox inf file
Re: Bug with RtlIsNtDdiVersionAvailable?
I guess my one option is to do RtlGetVersion and check against the build number.
I will write my own version of RtlIsNtDdiVersionAvailable while I am at it, since MSFT cannot deliver one that works.
Re: Handling cancel request in Driver
General guidance on this should be don't support cancelation at all, or use the KMDF cancelation support. I know how to do it correctly ‘manually’ aka the old way, but this is still the rule I work by.
Operations that don’t access hardware, don’t switch thread context or can’t effectively be cancelled once initiated should just not support cancel at all. For example if your driver synchronously computes the next 100 digits of PI from a previous estimate, then there is no need to even attempt to support cancel. But if you driver has sent and async command to read the next 100 blocks off of a SAN volume via an MPIO provider, where a cancel command exists, cancel should be supported and a cancel command sent - understanding that cancel might be sent after the whole command has completed
MBond2
Re: Distinguish between Applications connecting to device
If it were me, I'd register a device interface with a reference string, and have the property page open that instead. Then, your IRP_MJ_CREATE handler can check the file name to see if it's your special client.