🚀 go-pugleaf

It looks as though I have 'fixed' it, I'm not sure that 'fix' is the right
word because what I did should not have made a difference to the problem we
have been exploring, let me try to explain...

Previous to opening the socket connection within the Application I perform
the following:

1 - I retrieve settings from an INI file; if not present than I use default
settings (both settings are the same so not having the INI shouldn't have
made a difference); I initially didn't use a INI file and relied upon the
default values.

2 - I checked whether the service was present in the SCManager using
OpenSCManager() and OpenService(); this was found to be present

3 - I then started the service using OpenSCManager() and  OpenService() and
ControlService() to interrogate the state of the service, if the service is
running I than am able to attempt to open Socket connection; service was
found to be running.

4 - I then attempt to open the socket connection; which previously was
causing error 1110???

My fix was to have installshield create the INI file during installation.
Although steps 1 to 3 were returning valid results, it failed for some
reason when using defaulted values (ini not present) and worked when using
an pre-existing INI file even though the values seen through debugging were
identical.

And to really confuse the issue, it worked when I manually installed the
service AND still didn't have pre-existing INI file (therefore was
sucessfull when using the default values)


I think I must have been doing something wrong, but even though it is
working and I know how to make it work, I still can't figure out why it
worked, and now I think I have 'blinking cursor fever' from looking at this
screen too long and am officially giving up in attempting to understand this
any further.

Thanks for your help.