Re: CAsyncSocket in service

I have an MFC application that has been running well for a long time.
The client now wants it converted to run as a service, interfacing
with a separate program that provides the user interface. I will have
to do hardware control and support TCP/IP sockets in the service
portion.

I copied over the communications modules from my old application, but
the sockets do not seem to run. While I continue working out just
why, I was hoping somebody here would be able to comment something
like "Oh, no, your approach is wrong -- you have to do such and such."
I am not looking for code, just a push in the right direction.

The specific question is about the message pump. My service runs as a
console program that supports MFC and I use CStrings and MFC
containers with no problem. My CASyncSocket derived class is created
during the InitInstance() of a class derived from CWinThread. The
socket connects but never produces OnConnect() callbacks and the
CWinThread does not seem to be running a message pump. Specifically,
it seems to immediately jump to ExitInstance(). I naively assumed
that a CWinThread user thread would always have a message pump, even
if created within a console program. So, to be very specific:

 1) Can I use a user CWinThread inside a console class?

    2a) If the answer to 1) is 'yes', is there some special stuff I
have to do to make it run?

        3a) If the answer to 2) is 'yes', can you give me some
guidance as to what "special stuff"?

        3b) If the answer to 2) is 'no', then forget it, my problem
lies elsewhere and I have to keep digging to see what kills my
CWinThread thread.

    2b) If the answer to 1) is 'no', can you give me a general pointer
to running sockets under a service? I do have ancient C code using
raw socket function calls that I could drag out, but CASyncSocket
seemed so useful and simple.