RE: [ntdev]WinDbg in Win2000

>

Thanks for the help from all of you.

Now I can see my driver symbols. But I still have problem with source
debugging.

Actually, I have successfully set my breakpoints and the program
did stop in
those breakpoints. But, when the program is stoppped, most of the
time, the
corresponding source code (opened already) is not popped up. And
some times,
if I am lucky, I have the soprce code popped up with the line
high-lighted,
but when I press F10 for single-step, I don’t see the high-light line
moving. Is this a “FEATURE” of Win2000 WinDbg??

Feature. Windbag is hideously broken. Hello Microsoft! I’ve had much better
luck running windbag from an NT4 system than from a W2K system, and also
much better luck using a command line setup rather than a ‘workspace’.

Another question: When I install my driver, the following message appears.
“The Miscrosoft digital signature affirms that software has been
testedwith Windows and that software has not been altered since
it was tested.
The software you are about to install does not contains a Microsoft
digital signature, …”
Is this expected? Any thing wrong?

If you want this message to go away you need to run your driver through
WHQL. Good luck. Otherwise ignore it.

Another question: When I debug my USB driver, I unplug my USB
device and the
driver only receives IRP_MN_SURPRISE_REMOVE irp, no IRP_MN_REMOVE_DEVICE
follows. I returns STATUS_SUCCESS in IRP_MN_SURPRISE_REMOVE irp. What’s
wrong?

If I take this literally then you are doing the wrong thing. Set
Irp->IoStatus->Status to STATUS_SUCCESS (why?), pass the Irp down the stack
and return whatever IoCallDriver returns. Do not complete the IRP in your
function driver. If the bus driver doesn’t see the IRP then I’m guessing
that is why you never see the IRP_MN_REMOVE.