Re: Problem starting service
- From: brettm@xxxxxxxxx
- Date: 31 Mar 2006 09:11:14 -0800
We also confirmed with MS that the netlogon services are blocked
reading for a netready event to be signaled from TCP. We don't know the
magic code to replicate this behaviour in our own solution, but decided
on this approach as a work around:
- We no longer DISABLE the zeroconfig service. Instead we leave it to
- We set the zeroconfig registry settings to tell zero config NOT to
manage wireless for this adapater (same as checking the checkbox in the
wireless configuration dialog)
- We let zero config load at boot time and once it has loaded and
signaled the event, we shutdown the zero-config service so that we can
now manage the adapater.
The registry settings you need are under :
There are GUIDs for each of the installed adapters. For each adapter
entry, there is a registry value called 'ControlFlags'.
If bit 0x8000 of the ControlFlags value is set, then Wzc is enabled for
that adapter, if it's cleared, then Wzc is disable for that adapter.
Hope this helps - not a perfect solution, but it's working great for us
- Prev by Date: Re: Wdf Workitem
- Next by Date: Re: Dynamically loading binaries in Kernel mode.
- Previous by thread: Re: Problem starting service
- Next by thread: Re: Windows cannot load driver..