> Why do I need a printer spooler for dhcp?
This problem has frustrated me too. I found that the print spooler can
be removed after FBA and DHCP client continues to work.
--
- Mike
thanks, and it was your post that gave me the hint to add the print
spooler. My hope was that WES has cleaned up dependencies, but not in
this case :-(
DR
"JojoS" <jstra...@web.de> wrote in message
news:698aaffc-732f-4686...@c9g2000yqm.googlegroups.com...
> I have a similar sized image that includes core networking and a DHCP
> client and there is no print spooler in my configuration, either
> explicitly added or added by dependency checker.
Are you using FP2007 or later?
Is it possible for you to share either the SLD or build log so we can
see what components you used?
> I have not used WES
> yet. Are you saying that WES is worse in this respect that XPe since
> WES needs the print spooler for the DHCP client to work?
That's the only way I could get DHCP client to work on XPe. I'm not
using WES.
--
- Mike
I started a thread on this problem (under a different pseudonym) in August
2007 and after review I see that you participated in that thread.
Remarkably, one of the MS guys argued that it was sensible for all
dependencies to be resolved in an image that includes the DHCP client but
for the client not to be able to get an IP address! His position was that
through some inspired insight I should have known that the "TCP/IP
Networking with Client for Microsoft Networks" was needed. It was
interesting to me that after a thorough MSDN search I could not even find a
definition for "Microsoft Networks." Since I had assumed this included
capabilities such as Network Neighborhood it never seemed appropriate or
necessary for my application.
By chance I needed to build for a new target yesterday and I decided to
download and use the eval WES. For this target, a Shuttle xPC "shoebox"
computer, I again found it necessary to add "Client for Microsoft Networks"
in order to make the DHCP client behave.
So in summary, for reasons unknown to me, sometimes the DHCP client does the
right thing for me without "Client for Microsoft Networks" and without
"Print Spooler" but in other cases it does not. If you are still interested
in details of the former let me know through my email at yahoo.com. The
user name spelled backwards is jnhblhr.
DR
"Mike Warren" <miwa-not...@or-this-csas.net.au> wrote in message
news:xn0gb1ge...@news.microsoft.com...
I will ask my contacts at Kontron if they approve of making this component
generally available. If so, I will upload it to XpeFiles. It wouldn't be a
bad idea for MS to look at this component and add something very similar to
the product.
It makes me wonder whether there are other simple methods of eliminating a
lot of dead weight in XPe images. Although I haven't looked closely at this
component, I think it consists of some registry entries, etc.
DR
"Mike Warren" <miwa-not...@or-this-csas.net.au> wrote in message
news:xn0gb1ge...@news.microsoft.com...
> I will ask my contacts at Kontron if they approve of making this
> component generally available. If so, I will upload it to XpeFiles.
It would be nice to see what they did and whether it can be adapted to
more general use.
I'm at the point (see my other post) where I contemplating going back to
SP2 and losing all the benefits of the later updates just so I can
build working images again. This is /very/ frustrating. I really miss
Slobodan and Konstantin. :-(
--
- Mike