How to Disable Ethernet

I am adding an NDIS driver to a PXA255 board. OS is winCE
4.2 I want to make sure that nothing else accesses the
91C96 ethernet chip other than my driver. To do this I
modified "OEMKitlInit" to only return FALSE to disable
KITL. In addition, under platform settings->build options
I unchecked "KITL" & "CE Target Control support".

With KITL supposedly turned off and no ethernet drivers
added to the build I am still seeing constant access to the
91C96 chip. The TX light is constantly going & the
interrupt is constantly going.

QUESTION : what else is accessing the 91C96? Have I
properly disabled KITL?

The following environment variables are also set:
BSP_NOSHAREETH=1
KERNELNOSHAREETH=1
BSP_NOSERIAL=1

Thanks in advance for any help -Jeff
.

Relevant Pages

  • Re: "No .rel file found for module "
    ... Do you have the debug output from loading with KITL enabled? ... Bruce Eitman (eMVP) ... I2C driver when it is launched through KITL. ... I thought maybe it was the registry data too, ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... What would happen if using KITL and Shell.exe? ... I don't know the exact answer, but it might just reject the dll on the board ... Driver cannot be unloaded. ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... the only debug message that came out was "11290 ... worth noting it occurs both on KITL and non-KITL loads, ... remove the driver from the _FLATRELEASEDIR ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... Loading the image without KITL still does not ... register the I2C driver. ... "Dean Ramsier" wrote: ...
    (microsoft.public.windowsce.app.development)
  • Re: "No .rel file found for module "
    ... loading it with and without KITL, ... Is it possible that the debug nature of KITL allows the driver to be loaded ... "Dean Ramsier" wrote: ... I2C driver when it is launched through KITL. ...
    (microsoft.public.windowsce.app.development)