Windows 2000 Driver Verifier

Has anyone used the Driver Verifier in Windows 2000? I’d be interested
to hear what the value was from running it, and if you had to do anything
special to get it to work with your driver.

Regards,

Don Richards

Nathan,
Thanks for your reply.

I am trying to run Driver Verifier on Windows 2000. When I select my
driver on the Settings screen of the Driver Verifier I get a message
indicating a corrupted driver image file. Any ideas what is wrong? I h=
ave
not found any
documentation to give any hints what is wrong when this error is hit.

Here are a few details that may help in determining the problem:

  • my driver is designed to run on both NT 4.0 and Windows 2000
  • my driver is built using the NT 4.0 Checked build facility from the N=
    T
    4.0 DDK
    -my driver is installed in my own product bin directory, not
    \winnt\system32\drivers.

Regards,

Don Richards

“Nathan Nesbit” on 05/09/2000 04:28:09=
PM

To: Don A Richards/Raleigh/xxxxx@IBMUS
cc:
Subject: RE: [ntfsd] Windows 2000 Driver Verifier

Your driver does not need to change or be aware of driver verifier at a=
ll
in order for it to work.

What Driver Verifier does:
=A0=A0=A0=A0=A0=A0=A0 1) Checks that the actions the selected drivers a=
re doing do not
violate any rules
=A0=A0=A0=A0=A0=A0=A0 2) Can (if option is selected) randomly fail pool=
allocations for
testing

An example of #1 is accessing paged memory at a high IRQL.=A0 Without D=
river
verifier you may or maynot get a bugcheck.=A0 This is because the bugch=
eck
only occurs if the page(s) referenced are paged-out.=A0 With driver ver=
ifier
on you will get a bugcheck 100% of the time in this scenerio.

Driver verifier checks for tons of other things as well.

My understanding (and I am NOT a Driver Verifier expert) is that it mak=
es
“random” failures in your driver 100% reproducable.=A0 Thus helping you=
in
your testing to find and eliminate the bugs.

It takes just seconds to try it out.=A0 Run verifier.exe, select your d=
river
and turn it on.=A0 Reboot and do your normal driver tests.=A0 If you bu=
gcheck
then track down and fix the bug.

Enjoy

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Tuesday, May 09, 2000 1:20 PM
To: File Systems Developers
Subject: [ntfsd] Windows 2000 Driver Verifier

=A0 Has anyone used the Driver Verifier in Windows 2000?=A0 I’d be inte=
rested
to hear what the value was from running it, and if you had to do anythi=
ng
special to get it to work with your driver.

Regards,

Don Richards


=

That error is returned if the driver is not in the \winnt\system32\drivers
directory.

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Friday, May 12, 2000 9:32 AM
To: File Systems Developers
Cc: xxxxx@lists.osr.com
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Nathan,
Thanks for your reply.

I am trying to run Driver Verifier on Windows 2000. When I select my
driver on the Settings screen of the Driver Verifier I get a message
indicating a corrupted driver image file. Any ideas what is wrong? I have
not found any
documentation to give any hints what is wrong when this error is hit.

Here are a few details that may help in determining the problem:

  • my driver is designed to run on both NT 4.0 and Windows 2000
  • my driver is built using the NT 4.0 Checked build facility from the NT
    4.0 DDK
    -my driver is installed in my own product bin directory, not
    \winnt\system32\drivers.

Regards,

Don Richards

“Nathan Nesbit” on 05/09/2000 04:28:09 PM

To: Don A Richards/Raleigh/xxxxx@IBMUS
cc:
Subject: RE: [ntfsd] Windows 2000 Driver Verifier

Your driver does not need to change or be aware of driver verifier at all
in order for it to work.

What Driver Verifier does:
??? 1) Checks that the actions the selected drivers are doing do not
violate any rules
??? 2) Can (if option is selected) randomly fail pool allocations for
testing

An example of #1 is accessing paged memory at a high IRQL.? Without Driver
verifier you may or maynot get a bugcheck.? This is because the bugcheck
only occurs if the page(s) referenced are paged-out.? With driver verifier
on you will get a bugcheck 100% of the time in this scenerio.

Driver verifier checks for tons of other things as well.

My understanding (and I am NOT a Driver Verifier expert) is that it makes
“random” failures in your driver 100% reproducable.? Thus helping you in
your testing to find and eliminate the bugs.

It takes just seconds to try it out.? Run verifier.exe, select your driver
and turn it on.? Reboot and do your normal driver tests.? If you bugcheck
then track down and fix the bug.

Enjoy

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Tuesday, May 09, 2000 1:20 PM
To: File Systems Developers
Subject: [ntfsd] Windows 2000 Driver Verifier

? Has anyone used the Driver Verifier in Windows 2000?? I’d be interested
to hear what the value was from running it, and if you had to do anything
special to get it to work with your driver.

Regards,

Don Richards




You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

Bob,
Thanks very much! I copied my drivers to that directory, updated the=

registry, and the Driver Verifier is now doing its job.

Regards,

Don Richards

Bob Depelteau @lists.osr.com on 05/12/2000 09:38:00 AM

Please respond to “File Systems Developers”

Sent by: xxxxx@lists.osr.com

To: “File Systems Developers”
cc:
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

That error is returned if the driver is not in the \winnt\system32\driv=
ers
directory.

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Friday, May 12, 2000 9:32 AM
To: File Systems Developers
Cc: xxxxx@lists.osr.com
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Nathan,
=A0 Thanks for your reply.

=A0I am trying to run Driver Verifier on Windows 2000.=A0 When I select=
my
driver on the Settings screen of the Driver Verifier I get a message
indicating a corrupted driver image file.=A0 Any ideas what is wrong? I=
have
not found any
documentation to give any hints what is wrong when this error is hit.

Here are a few details that may help in determining the problem:
- my driver is designed to run on both NT 4.0 and Windows 2000
- my driver is built using the NT 4.0 Checked build facility from the N=
T
4.0 DDK
-my driver is installed in my own product bin directory, not
\winnt\system32\drivers.

Regards,

Don Richards

“Nathan Nesbit” on 05/09/2000 04:28:09=
PM

To:=A0=A0 Don A Richards/Raleigh/xxxxx@IBMUS
cc:
Subject:=A0 RE: [ntfsd] Windows 2000 Driver Verifier

Your driver does not need to change or be aware of driver verifier at a=
ll
in order for it to work.

What Driver Verifier does:
=A0=A0=A0=A0=A0=A0=A0 1) Checks that the actions the selected drivers a=
re doing do not
violate any rules
=A0=A0=A0=A0=A0=A0=A0 2) Can (if option is selected) randomly fail pool=
allocations for
testing

An example of #1 is accessing paged memory at a high IRQL.=A0 Without D=
river
verifier you may or maynot get a bugcheck.=A0 This is because the bugch=
eck
only occurs if the page(s) referenced are paged-out.=A0 With driver ver=
ifier
on you will get a bugcheck 100% of the time in this scenerio.

Driver verifier checks for tons of other things as well.

My understanding (and I am NOT a Driver Verifier expert) is that it mak=
es
“random” failures in your driver 100% reproducable.=A0 Thus helping you=
in
your testing to find and eliminate the bugs.

It takes just seconds to try it out.=A0 Run verifier.exe, select your d=
river
and turn it on.=A0 Reboot and do your normal driver tests.=A0 If you bu=
gcheck
then track down and fix the bug.

Enjoy

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Tuesday, May 09, 2000 1:20 PM
To: File Systems Developers
Subject: [ntfsd] Windows 2000 Driver Verifier

=A0 Has anyone used the Driver Verifier in Windows 2000?=A0 I’d be inte=
rested
to hear what the value was from running it, and if you had to do anythi=
ng
special to get it to work with your driver.

Regards,

Don Richards




You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

=

It would still have worked in the other directory. It just sends the bitch
message for no reason. Make sure that you use the stress test in
conjunction with the verifier in your testing it does a good job finding
bugs that won’t show up anywhere else.

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Friday, May 12, 2000 1:18 PM
To: File Systems Developers
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Bob,
Thanks very much! I copied my drivers to that directory, updated the
registry, and the Driver Verifier is now doing its job.

Regards,

Don Richards

Bob Depelteau @lists.osr.com on 05/12/2000 09:38:00 AM

Please respond to “File Systems Developers”

Sent by: xxxxx@lists.osr.com

To: “File Systems Developers”
cc:
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

That error is returned if the driver is not in the \winnt\system32\drivers
directory.

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Friday, May 12, 2000 9:32 AM
To: File Systems Developers
Cc: xxxxx@lists.osr.com
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Nathan,
? Thanks for your reply.

?I am trying to run Driver Verifier on Windows 2000.? When I select my
driver on the Settings screen of the Driver Verifier I get a message
indicating a corrupted driver image file.? Any ideas what is wrong? I have
not found any
documentation to give any hints what is wrong when this error is hit.

Here are a few details that may help in determining the problem:
- my driver is designed to run on both NT 4.0 and Windows 2000
- my driver is built using the NT 4.0 Checked build facility from the NT
4.0 DDK
-my driver is installed in my own product bin directory, not
\winnt\system32\drivers.

Regards,

Don Richards

“Nathan Nesbit” on 05/09/2000 04:28:09 PM

To:?? Don A Richards/Raleigh/xxxxx@IBMUS
cc:
Subject:? RE: [ntfsd] Windows 2000 Driver Verifier

Your driver does not need to change or be aware of driver verifier at all
in order for it to work.

What Driver Verifier does:
??? 1) Checks that the actions the selected drivers are doing do not
violate any rules
??? 2) Can (if option is selected) randomly fail pool allocations for
testing

An example of #1 is accessing paged memory at a high IRQL.? Without Driver
verifier you may or maynot get a bugcheck.? This is because the bugcheck
only occurs if the page(s) referenced are paged-out.? With driver verifier
on you will get a bugcheck 100% of the time in this scenerio.

Driver verifier checks for tons of other things as well.

My understanding (and I am NOT a Driver Verifier expert) is that it makes
“random” failures in your driver 100% reproducable.? Thus helping you in
your testing to find and eliminate the bugs.

It takes just seconds to try it out.? Run verifier.exe, select your driver
and turn it on.? Reboot and do your normal driver tests.? If you bugcheck
then track down and fix the bug.

Enjoy

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com]
Sent: Tuesday, May 09, 2000 1:20 PM
To: File Systems Developers
Subject: [ntfsd] Windows 2000 Driver Verifier

? Has anyone used the Driver Verifier in Windows 2000?? I’d be interested
to hear what the value was from running it, and if you had to do anything
special to get it to work with your driver.

Regards,

Don Richards




You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)


You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)

We’ll address that.

The verifier is trying to figure out if your driver links against a port
driver so it can automatically turn on against that at the same time.
The error message is … misleading.

-----Original Message-----
From: Bob Depelteau [mailto:xxxxx@OTG.com]
Sent: Friday, May 12, 2000 11:48 AM
To: File Systems Developers
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

It would still have worked in the other directory. It just sends the
bitch message for no reason. Make sure that you use the stress test in
conjunction with the verifier in your testing it does a good job finding
bugs that won’t show up anywhere else.

-----Original Message-----
From: drichard@us.ibm.com [ mailto:drichard@us.ibm.com
mailto:drichard ]
Sent: Friday, May 12, 2000 1:18 PM
To: File Systems Developers
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Bob,
Thanks very much! I copied my drivers to that directory, updated the
registry, and the Driver Verifier is now doing its job.

Regards,

Don Richards

Bob Depelteau @lists.osr.com on 05/12/2000 09:38:00 AM

Please respond to “File Systems Developers”

Sent by: xxxxx@lists.osr.com

To: “File Systems Developers”
cc:
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

That error is returned if the driver is not in the
\winnt\system32\drivers
directory.

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com
mailto:drichard]
Sent: Friday, May 12, 2000 9:32 AM
To: File Systems Developers
Cc: xxxxx@lists.osr.com
Subject: [ntfsd] RE: Windows 2000 Driver Verifier

Nathan,
Thanks for your reply.

I am trying to run Driver Verifier on Windows 2000. When I select my
driver on the Settings screen of the Driver Verifier I get a message
indicating a corrupted driver image file. Any ideas what is wrong? I
have
not found any
documentation to give any hints what is wrong when this error is hit.

Here are a few details that may help in determining the problem:
- my driver is designed to run on both NT 4.0 and Windows 2000
- my driver is built using the NT 4.0 Checked build facility from the NT

4.0 DDK
-my driver is installed in my own product bin directory, not
\winnt\system32\drivers.

Regards,

Don Richards

“Nathan Nesbit” on 05/09/2000 04:28:09
PM

To: Don A Richards/Raleigh/xxxxx@IBMUS
cc:
Subject: RE: [ntfsd] Windows 2000 Driver Verifier

Your driver does not need to change or be aware of driver verifier at
all
in order for it to work.

What Driver Verifier does:
1) Checks that the actions the selected drivers are doing do not

violate any rules
2) Can (if option is selected) randomly fail pool allocations
for
testing

An example of #1 is accessing paged memory at a high IRQL. Without
Driver
verifier you may or maynot get a bugcheck. This is because the bugcheck

only occurs if the page(s) referenced are paged-out. With driver
verifier
on you will get a bugcheck 100% of the time in this scenerio.

Driver verifier checks for tons of other things as well.

My understanding (and I am NOT a Driver Verifier expert) is that it
makes
“random” failures in your driver 100% reproducable. Thus helping you in

your testing to find and eliminate the bugs.

It takes just seconds to try it out. Run verifier.exe, select your
driver
and turn it on. Reboot and do your normal driver tests. If you
bugcheck
then track down and fix the bug.

Enjoy

-----Original Message-----
From: drichard@us.ibm.com [mailto:drichard@us.ibm.com
mailto:drichard]
Sent: Tuesday, May 09, 2000 1:20 PM
To: File Systems Developers
Subject: [ntfsd] Windows 2000 Driver Verifier

Has anyone used the Driver Verifier in Windows 2000? I’d be
interested
to hear what the value was from running it, and if you had to do
anything
special to get it to work with your driver.

Regards,

Don Richards




You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)


You are currently subscribed to ntfsd as: xxxxx@otg.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)</mailto:drichard></mailto:drichard></mailto:drichard>