If Client for Microsoft Networks or some similar component is needed to make
the DHCP Client work, why isn't there a dependency that would have alerted
me to this problem when TD resolved dependencies? Oh well, another week
down the drain.
HM
> If Client for Microsoft Networks or some similar component is needed
> to make the DHCP Client work, why isn't there a dependency that would
> have alerted me to this problem when TD resolved dependencies? Oh
> well, another week down the drain.
I've always had similar problems and they seem to be worse with rollup
1. I guess it gets more complicated as they try to break the components
up further.
--
-Mike
This component is bold because it's a macro component and simply depends on
other components to make your jobs as a developer a little easier. If you
instantiate this component in TD's configuration to examine it and click
it's settings node it shows us that it has a dependency on 'Client for
Microsoft Networks' and would satisfy this networking dependency for you
without having to go hunt down the other components.
The reason it's like this and not built into the 'TCP/IP Networking'
component you used is because many embedded devices will reside in
non-Microsoft environments which don't require the Client for MS Networks
service on the client side. So the TCP/IP Networking component is optimized
to be agnostic for the environment it's in. It would appear that your test
environment is probably using an MS DHCP Server so your test machine needs
the extra components in order to function.
I'm a Tester, I would recommend the environment the device is being tested
in is the same as (or as close as possible) to the environment it's designed
for.
You don't need to answer that, it's just a tip. :-)
Take care,
Andy
--
Subscribe to the EW Team's blog for tips/tricks, How tos and announcements:
http://blogs.msdn.com/embedded/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Henry Markov" <h...@hm.net> wrote in message
news:OEJEr7fz...@TK2MSFTNGP05.phx.gbl...
> The reason it's like this and not built into the 'TCP/IP Networking'
> component you used is because many embedded devices will reside in
> non-Microsoft environments which don't require the Client for MS
> Networks service on the client side. So the TCP/IP Networking
> component is optimized to be agnostic for the environment it's in. It
> would appear that your test environment is probably using an MS DHCP
> Server so your test machine needs the extra components in order to
> function.
I can't get DHCP to work in a system using the DHCP server in an ADSL
router without including Client for MS Networks.
Does that make sense to you?
I do not want any MS networking in my image but need to be able to
connect to the Internet with my software without manual configuration.
--
-Mike
I think this issue is illustrative of why XPe is hard to learn and use. You
design a system with everything you actually want and dependency resolution
throws in a lot of junk that you have no intention to use but it silently
leaves something out that makes the system fail. Seems to happen just about
every time.
HM
"Andy Allred [MS]" <and...@online.microsoft.com> wrote in message
news:18181438-9AF2-4A19...@microsoft.com...