- what stop the MiniportHalt function to be called?
- Posted by tianjun on September 6th, 2004
what stop the MiniportHalt function to be called?
the NIC miniportdriver will not quit!!
Thanks,
Tianjun
- Posted by Alexander Grigoriev on September 6th, 2004
If you have sent packets not returned to NDIS. This usually happens when the
hardware gets stalled.
"tianjun" <Tianjun@zcom.unimis.com> wrote in message
news:OhXZhD7kEHA.3104@TK2MSFTNGP14.phx.gbl...
- Posted by tianjun on September 7th, 2004
Does it the only reason? It seems the all packets has returned to NDIS.
"tianjun" <Tianjun@zcom.unimis.com> дÈëÓʼþ
news:OhXZhD7kEHA.3104@TK2MSFTNGP14.phx.gbl...
- Posted by Stephan Wolf [MVP] on September 7th, 2004
Any pending query/set information requests?
The "ndiskd" debugger extension offers some commands that will help
you figure out about pending resources, see e.g.
http://groups.google.com/groups?thre....microsoft.com
Stephan
---
On Tue, 7 Sep 2004 13:32:20 +0800, "tianjun" <Tianjun@zcom.unimis.com>
wrote:
- Posted by Alireza Dabagh [MS] on September 7th, 2004
What did you do that now you expect it to get Halted? Did you disable the
device? What protocols are bound to the device?
In addition to outstanding send requests mentioned in another post, make
sure there is no OID requests pending and there is no app (including your
custom app if you have one) has a handle to the device. If you have a
private protocol installed, the problem might be with a protocol not closing
the adapter. If you have a firewall installed that hijacks NDIS and/or
stacks entry points and private structures, the problem might be there.
-ali
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"tianjun" <Tianjun@zcom.unimis.com> wrote in message
news:OhXZhD7kEHA.3104@TK2MSFTNGP14.phx.gbl...
