This "Context"=1/SERVICE_INIT_STOPPED is incredibly confusing. I'm sure
you're not the first person to get thrown by this (though you're the first
to complain). I've created a blog post at
http://blogs.msdn.com/cenet/archive/2005/12/14/503768.aspx to discuss in
detail for posterity's sake. It should explain how to get your service into
a stopped mode and why you're seeing this behavior with context=1. The
short answer is don't do that. Sorry for the confusion here.
BTW I'm out over Christmas break tomorrow so I can't answer any further
questions you have until '06.
--
John Spaith
Software Design Engineer, Windows CE
Microsoft Corporation
Check out the new CE Networking Team Blog at
http://blogs.msdn.com/cenet/.
This posting is provided "AS IS" with no warranties, and confers no rights.
You assume all risk for your use. © 2003 Microsoft Corporation. All rights
reserved.
<tmeese.TakeThisOut@gmail.com> wrote in message
news:1134541323.766064.91430@g43g2000cwa.googlegroups.com...
> Hello,
>
> I've got an application that I've made into a network service. It runs
> fine as a service as long as the Context value is zero. If I set it to
> 1 (I understand that this loads the service, but does not start it),
> the load does not even work and gives an error of 0x57. If I keep the
> Context value at zero, I'm able to load and start the service manually,
> but I would like the option to have it automatically start based on
> Context being 1 or 0, which it seems is what is intended by these
> values. BTW, I am setting the Keep registry value to 1.
>
> Any suggestions from the CE networking community would be much
> appreciated.
>
> Thanks,
>
> Tim Meese
>