Re: Question about FILE_OBJECT
- From: Steve Dispensa <dispensa@xxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 17 Jul 2006 22:09:31 -0500
On 7/17/06 7:24 PM, in article
1153182298.161678.91190@xxxxxxxxxxxxxxxxxxxxxxxxxxxx, "anton bassov"
<soviet_bloke@xxxxxxxxxxx> wrote:
One of these requirements is that it has
to register itself as miniport driver with NDIS library. Any driver
that does so cannot expose regular Dispatch interface, for the simple
reason that miniport driver's functions are not supposed to be called
by anyone,apart from NDIS library. Opening file handle requires
IRP_MJ_CREATE's handler. Therefore, you cannot open a handle on NDIS
IM.
I missed the original post, but would NdisMRegisterDevice() work for the OP?
Apart from this, NDIS IM may pose quite a few other problems. For
example, NDIS IM often
fails with virtual adapters.
I haven't had this experience. IM driver installation is sensitive, but I
haven't noticed anything in particular with (well written) virtual
miniports. Could you share your experience?
In order to avoid all these troubles, you
can hook NDIS calls, instead of writing NDIS IM.
No, please don't do that. It'll just create a support nightmare. The 9x
PCAUSA hook driver is another thing altogether; on NT+, IM drivers should
obviate the need for hooks.
-sd
.
- References:
- Re: Question about FILE_OBJECT
- From: Doron Holan [MS]
- Re: Question about FILE_OBJECT
- From: John S
- Re: Question about FILE_OBJECT
- From: Doron Holan [MS]
- Re: Question about FILE_OBJECT
- From: John S
- Re: Question about FILE_OBJECT
- From: anton bassov
- Re: Question about FILE_OBJECT
- From: John S
- Re: Question about FILE_OBJECT
- From: anton bassov
- Re: Question about FILE_OBJECT
- Prev by Date: Re: Recommended Approach for Redundant File/Directory Existence check
- Previous by thread: Re: Question about FILE_OBJECT
- Next by thread: Converting FILETIME into two DWORDS
- Index(es):
Relevant Pages
|
