service startup differs from XP Pro

[Roger Levy]

At startup my service must determine the IP addresses that have been assigned
via DHCP to two gigabit ethernet interfaces and then it starts broadcasting on
these interfaces. The service works correctly in XP Pro/SP2. Correct operation
depends on IP addresses being available. However with XPe/SP2 the service fails
to startup correctly because the DHCP client service does not complete prior to
my service's need of IP addresses. In fact I have determined that the DHCP
client protocol never starts until my service finishes its initialization, i.e.
reports SERVICE_RUNNING status to the SCM. This occurs even when I delay
reporting SERVICE RUNNING for one minute or more. In other words the DHCP
client service always executes in serial and after my service. Since I have not
placed my service in a load ordering group I believe my service should always
load after all standard services so I am at a loss to explain this behavior.

The major difference between the two XP environments is that the XPe system is a
minlogon, command shell environment. Should this have any impact on service
start order? I have seen the following sequence of events when the XPe system
boots:
1. Initial Windows splash screen and progress bar.
2. Blue startup screen until my service sends SERVICE_RUNNING. If I put
multiple minute delays into my service then the blue screen remains for multiple
minutes.
3. Command prompt.
4. DHCP protocol executes about 3 seconds after command prompt appears.

What could be responsible for the DHCP client service waiting for my service to
complete initialization?

Roger

 

[Roger Levy]

I tried serveral things with load dependencies to solve this problem but to no
avail. As a sanity check I returned to SP1 and the problem vanished. I think I
recall KM or some other expert saying in this NG that DHCP was extensively
rewritten for SP2. Does anyone have details? Also what is the mechanism by
which bug reports can be sent to the right people in MS? This problem seems odd
in that it does not appear in XP Pro/SP2.

I have no need of security features because my machines will on a fully isolated
network. Does that mean I really have no need of SP2? I don't know of anything
SP2 gave me other than a 50% footprint increase even with the firewall
disabled. On the other hand I don't know if it will be acceptable to my client
to be told that the current XPe does not properly support our application so
this problem may push me in the direction of open source alternatives.

Roger

 

[KM]

Roger,

The only way to report bugs for the product I know of is this web page:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx.
Although I think PSS may be more useful to you since you need a quick fix but not a QFE.

From the description you gave I don't think you really need to move to SP2. You can make sure to install all the SP1's QFEs, though.
For the footprint with disabled firewall you really need to turn off autoresolving dependencies in TD and try removing some
components you don't need (I know it is sometimes hard but it is the only way available to you now on SP2 where many network
components will try to bring in the entire firewall).

Regarding your issue I have only a guess and I wasn't posting it hoping for MS folks replies. Since there was no reply from MS, I
can only think that your own service uses some network APIs (you mentioned it tries to check IP address assigments) and therefore it
loads up IP helpers and/or some other network components. This may prevent DHCP client from being loaded until your service is up
and running since all [many] the network components are tight and dependent on each other in SP2 because of the new firewall code
added.
Again, this is just a high level guess but you can easy verify it by commenting out all the network related calls in your service
code, removing all linked network related libraries and double checking the new compiled binary's do not import any network related
dll. Then try to test the system and see whether the DHCP start is again postponed or not.

KM

PS. I never said DHCP was rewritten for SP2. I'd rather think it was not. However, there are definitely some misbehaviour of the
DHCP client on XP Pro SP2 that I (and some other folks) have noticed here.