How to prevent an NDIS intermediate driver from being loaded at startup?
- From: "ken" <ken@xxxxxxxxxxxxxxx>
- Date: Tue, 6 Dec 2005 18:55:41 +0100
I developed an NDIS intermediate driver with the emulator 4.2.
Now I want to try it on an iPaq with its standard retail OS and a WLAN card
that is actived "on click".
I do not want the driver to be loaded at startup since I wouldn't have any
idea what to do when the iPaq constantly crashs on startup. I guess I would
have to ship it to HP?
As far as I know to load an NDIS IM there needs to be an entry in HKLM\Comm
with its name. Unfortunately, this automatically results in it being loaded
at startup.
Can I make any indication that I want to have it loaded on demand,i.e. when
the WLAN interface comes up or I make an explicit
IOCTL_NDIS_REGISTER_ADAPTER?
Maybe by restricting the \Parms\UpperBind parameter? Maybe I can set the
group to something else than NDIS?
Thanks for any hints,
ken
.
- Follow-Ups:
- Re: How to prevent an NDIS intermediate driver from being loaded at startup?
- From: Paul G. Tobey [eMVP]
- Re: How to prevent an NDIS intermediate driver from being loaded at startup?
- Prev by Date: Re: Message Hooking
- Next by Date: Re: How to prevent an NDIS intermediate driver from being loaded at startup?
- Previous by thread: Re: Message Hooking
- Next by thread: Re: How to prevent an NDIS intermediate driver from being loaded at startup?
- Index(es):
Relevant Pages
|