How to use driver verifyer?

NTFSD
1

Hi
I work with a new tool on Windows 2000:verifyer. I give to verifyer the
task to verify my filter driver ,I must restart ,but my system crush with
BSOD at boot time with a code specific to verifyer.
My filter driver works fine.
What happened? What internaly verifyer does?
Thanks

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

> I work with a new tool on Windows 2000:verifyer. I give to verifyer the

task to verify my filter driver ,I must restart ,but my system crush with
BSOD at boot time with a code specific to verifyer.
My filter driver works fine. What happened? What internaly verifyer does?

Many errors are seen by Driver Verifier that will never cause a BSOD in
common or uncommon work.
Tell us what the error is, and we can help You a little more.

–
Regards, Dejan M. CEO Alfa Co. www.register.co.yu and www.alfaunits.co.yu
E-mail : xxxxx@alfaunits.co.yu ICQ# : 56570367
Professional file&system related components and libraries for Win32
developers.
Alfa Units - #1 file and system handling units for Delphi.
Alfa File Monitor - #1 file monitoring system for Win32 developers.
Alfa File Protector - #1 file protection and hiding system for Win32
developers.

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

Driver verifier turned up a number of snafus in my driver that, realistically,
would occur in real life only if I stressed the driver on a 486 with 32 meg of
memory . Of course, I eliminated them anyway.

Microsoft semi-officially recommends that you first test with all settings ON
except “low memory simulation”. If all goes well, retest with all settings
OFF but with “low memory simulation” on.

Neil Weicher

> ----------------------------------------------------------------------
>
> Subject: How to use driver verifyer?
> From: xxxxx@email.ro
> Date: Sat, 13 Jan 2001 12:49:58
> X-Message-Number: 1
>
> Hi
> I work with a new tool on Windows 2000:verifyer. I give to verifyer the
> task to verify my filter driver ,I must restart ,but my system crush with
> BSOD at boot time with a code specific to verifyer.
> My filter driver works fine.
> What happened? What internaly verifyer does?
> Thanks

—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

4

Hi
Can you please tell me where can I download or purchase this verifyer and
also
a one for NT ?
Thanks

xxxxx@email.ro wrote:

Hi
I work with a new tool on Windows 2000:verifyer. I give to verifyer the
task to verify my filter driver ,I must restart ,but my system crush with
BSOD at boot time with a code specific to verifyer.
My filter driver works fine.
What happened? What internaly verifyer does?
Thanks

You are currently subscribed to ntfsd as: xxxxx@neptune.co.il
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

5

> Driver verifier turned up a number of snafus in my driver that,
realistically,

would occur in real life only if I stressed the driver on a 486 with
32 meg of
memory . Of course, I eliminated them anyway.

Or a high end server machine being slammed with day-peak load … !

> Microsoft semi-officially recommends that you first test with all
settings ON
> except “low memory simulation”. If all goes well, retest with all
settings
> OFF but with “low memory simulation” on.

Treating the special IRQL as a standalone test also has merit; it swings
all paged data/code to transition lists on raises to DPC level so we can
catch the places where paged stuff is touched above DPC … quickly.
This imposes a bit of a performance penalty because of the number of
transition faults that will occur to re-validate the pages.

Bottom line is to mix it up, run it frequently, and track down all the
issues.

Since the verifier (%WINDIR%\system32\verifier.exe in answer to another
question) is simply part of the system as of Windows 2000, it behoves us
all as developers to use it before our customers do: they will. It is as
excellent a diagonstic tool for product support as it is for a code
developer, its just a matter of doing it before or after the fact.

Everything the verifier flags is a very bad bug, its just a matter of
not crashing the machine because of the phase of the moon (paged data at
DPC), corrupting pool that won’t be touched for a few days, not having a
filter driver doing XYZ above you and so forth. All of 'em are real and
can/will cause grief down the road.

—
You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

6

> Everything the verifier flags is a very bad bug, its just a matter of

Looks like the MmGetSystemAddressForMdlSafe thing (which verifier complains)
is a broken compatibility with NT4 driver binaries and thus not good.

Max

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

7

Daniel Lovinger wrote:

Since the verifier (%WINDIR%\system32\verifier.exe in answer to another
question) is simply part of the system as of Windows 2000

Is there a Verifier for WinNT or something similar ? becouse that’s the
one I need asap.
Regards,
Daniel A.

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

8

Forget binary compatibility with NT4, especially in the realm of
filesystems. Last time I looked at the issue–which I admit was during the
W2K release candidate phase–you couldn’t use structured exception handling
in a driver that is binary compatible between W2K and NT4. The problem with
exception handling is that somebody shuffled the exception handling runtime
routines between a static library and the kernel between NT4 and W2K. Since
a fair number of the cache manager routines throw exceptions rather than
returning an error code, you cannot write a correct filesystem driver that
is integrated with the cache manager AND binary compatible between NT4 and
W2K.

-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Monday, January 15, 2001 1:59 AM
To: File Systems Developers
Subject: [ntfsd] re: How to use driver verifyer?

> Everything the verifier flags is a very bad bug, its just a
matter of

Looks like the MmGetSystemAddressForMdlSafe thing (which
verifier complains)
is a broken compatibility with NT4 driver binaries and thus not good.

Max

You are currently subscribed to ntfsd as: xxxxx@nsisw.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

9

The driver verifier is not presently available on NT4. I would
recommend that you port your driver to Windows 2000 (something you
probably need to do eventually anyway) and do your verifier testing
there. Anything it finds will be applicable to your NT4 version of the
driver as well.

Neal Christiansen

-----Original Message-----
From: Danny [mailto:xxxxx@neptune.co.il]
Sent: Monday, January 15, 2001 2:03 AM
To: File Systems Developers
Subject: [ntfsd] re: How to use driver verifyer?

Daniel Lovinger wrote:

Since the verifier (%WINDIR%\system32\verifier.exe in answer to another
question) is simply part of the system as of Windows 2000

Is there a Verifier for WinNT or something similar ? becouse that’s the
one I need asap.
Regards,
Daniel A.

You are currently subscribed to ntfsd as: xxxxx@Exchange.Microsoft.com
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com

10

Win2000 is quite new form me.
Could you kindly specify what are the basic steps for porting an NT filter
driver into a Win2000
system.I think this is something many could use.

Neal Christiansen wrote:

The driver verifier is not presently available on NT4.  I would
recommend that you port your driver to Windows 2000 (something you
probably need to do eventually anyway) and do your verifier testing
there.  Anything it finds will be applicable to your NT4 version of the
driver as well.

Neal Christiansen

-----Original Message-----
From: Danny [mailto:xxxxx@neptune.co.il]
Sent: Monday, January 15, 2001 2:03 AM
To: File Systems Developers
Subject: [ntfsd] re: How to use driver verifyer?

Daniel Lovinger wrote:

Since the verifier (%WINDIR%\system32\verifier.exe in answer to another
question) is simply part of the system as of Windows 2000

Is there a Verifier for WinNT or something similar ? becouse that’s the
one I need asap.
Regards,
Daniel A.
 

You are currently subscribed to ntfsd as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntfsd-$subst(‘Recip.MemberIDChar’)@lists.osr.com