FiveTech Support Forums

I have a program that I run on a server that provides automatic updates and completes other tasks. Until now it has been installing in the Startup menu and has worked out fairly well. However on some servers it won't activate on a reboot unless there is an operator to authorize it.

The IT guys tell me it needs to be a "service". I'm using an installer that will let me create a service from an .exe, though it is not currently correctly activating the program.

So here is my question, for discussion. Is anyone else creating a FWH / xHarbour or Harbour, executable to run as a service ? If so, what guidelines are you following ?

Thanks for the info and ideas any can share on this topic.

Tim

Look

viewtopic.php?f=17t=30062p=171474hilit=run+as+a+service#p171446

&&&

I already read that thread. It describes how to install it, but I'm using Actual Installer and may be able to do the installation right in my setup program.

My question was about the actual service .exe built with FWH. Has anyone done this and discovered issues we need to consider in the process of building the .exe.

Tim

I will try this again:

1) My installation software can actually register an application as a service. It installs it correctly.
2) The application written with FWH and xHarbour, which used to be run with Startup in Windows, will not start as a service even when installed and showing on the services list.

My question:

Should a service NOT be a Windows program ? Should it be built as a console app ? If I do build it as a Windows program, what do I need to avoid ? Can we have it display on the Task Bar as it did when run in the Startup folder ? Can we interact with it ( ie. popup menu ).

Thanks.

It would appear Robb has experience with this. I asked in the other thread if he can provide the sample he mentioned. I seem to have a problem getting harbour contribs ...

Tim