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:
-
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…)? -
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
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.
-
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)…
Ooops.
Thank’s in advance,
Miguel Monteiro
xxxxx@criticalsoftware.com
www.criticalsoftware.com
«Humour and love are God’s answers
to Human weaknesses»
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