Driver verifier is only available on Windows 2000 and Windows XP. For NT
4.0, you can enable special pool which might help in tracking down this
problem.
Those “red herrings” you refer to may be part of your problem. In my
experience, people who eschew using the checked build because of the
problems they observe with it are overlooking bugs within their own driver.
Can you reproduce the problem on W2K or XP? If so, you can at least run the
driver there (under verifier) and see if it flushes out a problem.
Regards,
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com
-----Original Message-----
From: xxxxx@yahoo.com [mailto:xxxxx@yahoo.com]
Sent: Friday, April 19, 2002 3:52 PM
To: Kernel Debugging Interest List
Subject: [windbg] Re: wrong driver processing IRP (repost with more in fo)
With checked build we found that we had red herrings that got in our way
too much.
Driver verifier I thought was only available on Windows 2000 and above,
this is NT4. Please correct me if I am wrong.
You are currently subscribed to windbg as: xxxxx@osr.com
To unsubscribe send a blank email to %%email.unsub%%