Try and try as we may, we are unable to build an XPe image with basic
networking support but WITHOUT the DHCP client active. We utilize a
"custom" DHCP/Bootp solution, and need to have the DHCP client
disabled, but as of now, the only way to accomplish this is to load
the .slx into TD, update any components that have been patched, check
all dependencies, and then as the very last step, disable the DHCP
Client component and build without a dependency check.

We do get an error during FBA about DHCPCSVC.DLL being missing, but we
just continue and all works OK.

Is it going to be easier to enable/disable DHCP in future versions of
XPe?
We are running on SP1.

Ann

In TD (with advanced mode to view the component resources), expand the
node for the dhcp client service component, locate the file resource
and *disable* that file resource. That file will no longer come into
the runtime yet the component will still be in the SLX.

As long as no other services or features depend on the existence of
that file, you're good to go! <grin> Note, that you'll still be
populating the reg resources for the component as well but you can
disable them too, if you have the patience.

--
Andy
This posting is provided "AS IS" with no warranties, and confers no
rights.

Well... I think if they disable the file resource they still get the missing DLL FBA error.

How about changing (setting) [HKLM\SYSTEM\CurrentControlSet\Services\Dhcp],"Start" value upfront to disable the service?

--
Regards,
KM, BSquare Corp.


> In TD (with advanced mode to view the component resources), expand the
> node for the dhcp client service component, locate the file resource
> and *disable* that file resource. That file will no longer come into
> the runtime yet the component will still be in the SLX.
>
> As long as no other services or features depend on the existence of
> that file, you're good to go! <grin> Note, that you'll still be
> populating the reg resources for the component as well but you can
> disable them too, if you have the patience.
>
> --
> Andy
> This posting is provided "AS IS" with no warranties, and confers no
> rights.

hmm, my understanding of the question was how to keep the component
from coming back into the config everytime they run check dependency
and that it was ok for them to ignore the fba error when the file is
missing. in any case your solution is also valid.

--
Andy
This posting is provided "AS IS" with no warranties, and confers no
rights.

Andy,

You must be right and from Ann's question it does seem that they can live with the error.
It is just that I personally hate to have FBA errors :-) Not to mention that I usually run FBA without myself watching the process
and click OK or Cancel on any possible error :-)

--
Regards,
KM


> hmm, my understanding of the question was how to keep the component
> from coming back into the config everytime they run check dependency
> and that it was ok for them to ignore the fba error when the file is
> missing. in any case your solution is also valid.
>
> --
> Andy
> This posting is provided "AS IS" with no warranties, and confers no
> rights.