No call to MiniportHalt

NTDEV
1

Hello All,

I implemented significant chunks of my NDIS miniport and have decided to
test the cleanup routines of my driver. I try to disable the device from
the Device Manger but see no calls to my MiniportHalt function (device
manager waits forever. I expect this because I’ve seen this work okay
when I first started writing this miniport and had the driver “shell” in
place.

Am I missing something important?

Thanks
Ravi

2

Typically, it’s because you have OIDs or xmit packets pending. Make sure you
complete all of them.

Calvin Guan, Windows DDK MVP
Software Engineer,?NT Driver
ATI Technologies Inc. www.ati.com
?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Murty, Ravi
Sent: April 11, 2005 11:12 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] No call to MiniportHalt

Hello All,
I implemented significant chunks of my NDIS miniport and have decided to
test the cleanup routines of my driver. I try to disable the device from the
Device Manger but see no calls to my MiniportHalt function (device manager
waits forever. I expect this because I’ve seen this work okay when I first
started writing this miniport and had the driver “shell” in place.
Am I missing something important?
Thanks
Ravi

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

3

Calvin,

I don’t pend any of my OIDs for sure.

As for xmits, how does NDIS know that the driver completed a packet? I am guessing this happens when I call NdisMSendComplete() on a packet I receive in the PacketArray in MiniportSendPackets? Is this right?

Thanks
Ravi

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Calvin Guan
Sent: Monday, April 11, 2005 8:25 AM
To: Windows System Software Devs Interest List
Subject: RE: [ntdev] No call to MiniportHalt

Typically, it’s because you have OIDs or xmit packets pending. Make sure you
complete all of them.

Calvin Guan, Windows DDK MVP
Software Engineer,?NT Driver
ATI Technologies Inc. www.ati.com
?
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Murty, Ravi
Sent: April 11, 2005 11:12 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] No call to MiniportHalt

Hello All,
I implemented significant chunks of my NDIS miniport and have decided to
test the cleanup routines of my driver. I try to disable the device from the
Device Manger but see no calls to my MiniportHalt function (device manager
waits forever. I expect this because I’ve seen this work okay when I first
started writing this miniport and had the driver “shell” in place.
Am I missing something important?
Thanks
Ravi

Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: unknown lmsubst tag argument: ‘’
To unsubscribe send a blank email to xxxxx@lists.osr.com

4

> -----Original Message-----

From: xxxxx@lists.osr.com [mailto:bounce-206224-

[snip]

As for xmits, how does NDIS know that the driver completed a packet? I am
guessing this happens when I call NdisMSendComplete() on a packet I
receive in the PacketArray in MiniportSendPackets? Is this right?

You’re right.

Calvin Guan, Windows DDK MVP
Software Engineer, NT Driver
ATI Technologies Inc. www.ati.com