It ‘works fine’ on NT4 because there is no ‘driver verifier’ halting the
system at a bugcheck on NT4. It is however not ‘working fine’, it is a bug
on NT4 and W2K. Do not ever set Irp.IoStatus.Status to STATUS_PENDING. Not
all software defects are detected.
Mark Roddy
xxxxx@hollistech.com
www.hollistech.com
603 321 1032
WindowsNT Windows 2000 Consulting Services
-----Original Message-----
From: xxxxx@exgate.tek.com
[mailto:xxxxx@exgate.tek.com]
Sent: Monday, March 26, 2001 12:06 PM
To: NT Developers Interest List
Subject: [ntdev] Re: NT device driver may not work on windows 2000, wh
y?
HI, Thanks for the replies to my earlier question. It turns out to be IRP
problem. I interpreted the blue screen message. It looks like this:
BugCheckCode (0xc9): DRIVER_VERIFIER_IOMANAGER_VIOLATION
Error Code (0x6): Issue IoCompletRequest() when Irp->Status ==
STATUS_PENDING.
So I am confused, why it works fine on NT 4, but not NT 5? Can anybody
explain this to me?
Thanks,
zhongsheng
-----Original Message-----
From: Mathias Ellinger [mailto:xxxxx@Ellisoft.de]
Sent: Sunday, March 25, 2001 10:53 PM
To: NT Developers Interest List
Subject: [ntdev] Re: NT device driver may not work on windows 2000, why?
Hello,
why you returns with STATUS_PENDING ?
where is the completion from IO Control request ?
elli
You are currently subscribed to ntdev as: xxxxx@exgate.tek.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
You are currently subscribed to ntdev as: xxxxx@stratus.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
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