Re: KITL and NDIS sharing NIC on hive-based registry build leads to hang
- From: "Dean Ramsier" <ramsiernospam@xxxxxxxxxx>
- Date: Wed, 4 Oct 2006 09:21:29 -0400
You can't load both kitl and the NDIS miniport driver for the same hardware
at the same time. If you load the virtual miniport driver (vmini) it will
sit on top of your kitl connection and provide your applications with NDIS
support. Vmini is typically a part of your image by default.
If the question is how to configure the platform so they don't both load at
the same time, that's a different issue. PCI based implementations have a
mechanism that works well automatically. Other mechanisms could include
something as simple as wrapping the reg entries that load the miniport
driver with the IMGNOKITL env variable. Or you could have some kind of
mechanism that modifies the registry at run time in kitl enabled builds. Or
whatever else you can think of that makes sense for your device...
--
Dean Ramsier - eMVP
BSQUARE Corporation
"dave" <dave@xxxxxxxxxxxxxx> wrote in message
news:OuCMtI05GHA.3644@xxxxxxxxxxxxxxxxxxxxxxx
It seems when I build hived-based registry image with both
KITL and a NDIS driver using the same NIC. Once the NDIS
driver is successfully initialized the target will hang.
If I remove the NDIS driver from the image the problem
goes away.
Are there known workarounds to this type of a problem
so that I can keep both KITL and NDIS working at the same
time?
There don't seem to be any recommendations for this type
of problem in the PB hived-based troubleshooting. There is
one reference to KITL but it seems unrelated.
.
- References:
- Prev by Date: Re: I/O, I/O, I'm so confused 'ya know
- Next by Date: Re: problem in inclusion of Aygshell
- Previous by thread: Re: KITL and NDIS sharing NIC on hive-based registry build leads to hang
- Next by thread: NTLMSetUserInfo
- Index(es):
Relevant Pages
|
