NDIS IM & NdisMDeregisterDevice
- From: "TarasCo" <taralex@xxxxxxxxx>
- Date: 13 Dec 2006 07:12:13 -0800
As I know, i should call NdisMDeregisterDevice in MiniportHalt routine
when last miniport is halted (
http://groups.google.ru/group/comp.os.ms-windows.programmer.nt.kernel-mode/browse_thread/thread/1d8ee27725dd24c2/b8e565e360364c61?lnk=st&q=NdisMDeregisterDevice+Unload&rnum=1&hl=ru#b8e565e360364c61)
Then my driver will be unloaded. But if client app has opened handle on
my device, driver is still in memory. I can understand why. When app
close the last handle i suggest calling driver Unload routine, but
driver is still referenced. I can notify app about stop, but I think
when app handle such notify it will be late. What sould I do?
.
- Follow-Ups:
- Re: NDIS IM & NdisMDeregisterDevice
- From: soviet_bloke
- Re: NDIS IM & NdisMDeregisterDevice
- From: Thomas F. Divine
- Re: NDIS IM & NdisMDeregisterDevice
- Prev by Date: Re: question regarding load-balancing intermediate driver
- Next by Date: Re: NDIS IM & NdisMDeregisterDevice
- Previous by thread: Re: Support for multiple boards
- Next by thread: Re: NDIS IM & NdisMDeregisterDevice
- Index(es):
Relevant Pages
|
Loading