RE: [NtDev] Driver Verifier Usage

NTDEV
1

RE: [NtDev] Driver Verifier UsageOn Thursday, June 07, 2001 5:28 PM
“Gary Little” wrote:

  1. I believe driver verifier will work (…)

Cool.

  1. You run/start driver verifier from the target. (…)

I’m aware of the !verifier command, but as you say it doesn’t
work nice and smooth all the time… :wink:

  1. Verifier help is reached from within WinDbg’s online help.
    The DDK also has some good information on verifier and gflags.

Thank you, Gary. I’ll check it.

Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com

«Humour and love are God’s answers
to Human weaknesses»

— Original Message —
On Thursday, June 07, 2001 3:08 AM I (Miguel Monteiro) wrote:

Hi,

I would like to try using Driver Verifier (Win2K DDK/dev. environment),
but because I haven’t done this yet I would mostly appreciate if
someone
could give me some quick tips, namely:

  1. May I use Driver Verifier (DV) to test *any* kind of Device Driver
    (e.g. “legacy” kernel-mode device drivers), or is it limited to
    specific
    driver “flavours” (NDIS, WDM…)?

  2. As I understand it, DV runs from the development machine (where the
    DDK and its tools are); wouldn’t it be correct to test the driver in
    the
    target machine, instead? Thus, do I a) Copy verifier.exe to the target
    and run DV from there or b) Do I have to install my driver in the
    development machine :frowning: to test it? This, of course, assumes I would be
    using DV to test “finished”, ready-for-beta-testing drivers (this
    option
    seems a bit “dangerous”, doesn’t it?..). Hopefully, there will be a c)
    “I’m totally missing the point here” option. :slight_smile:

  3. Finally, the reason why I’m posting the above couple of questions is
    simply because I can’t find the verifier.hlp file (although I’m
    positive
    the DDK is correctly and fully installed, as everything else works
    fine)…

:frowning: Ooops.

Thank’s in advance,

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