Welcome,

BE AWARE of the interactivity of the services.

 -----------
|DEL_SERVICE|
 -----------

[non-interactive service]
the delete service searches for a file DEL_SERVICE.cmd in the
%systemroot%\system32\ directory and executes it in a given
interval.
the default interval is one hour (36000 times 100 ms), if you
want to give another interval (in milliseconds) create a
REG_DWORD value named "WaitDuration" under

HKLM\SYSTEM\CurrentControlSet\Services\DEL_SERVICE

It might be, your SCM database is located elsewhere. in this
case you should know where. also, if you recompile the binary
using another name for the service, the script file name will
change and also the key name in the registry.

 -----------
|CMD_SERVICE|
 -----------

[interactive service]
this one is mainly intended to have an interactive process in
SYSTEM context. this has long ago been superseded by CMDasSYS
and RUNasSYS (see my homepage), but it's okay for studying.
and also if you are network-admin, just install it on remote
workstations and start it remotely, providing a privilege
elevation to the user ... ;) okay, joke ... better don't do
that ... only for your purposes.

 ------------
|EXEC_SERVICE|
 ------------

[interactive service]
maybe you know AppToService, which became shareware as I
recognized (I still had the freeware version of it) - well
first of all I don't like shareware and secondly, I think,
that it is even more comfortable to have a script file you
may edit anytime, that executes some non-service program.
well, thus I wrote this little thing. it executes a file named
EXEC_SERVICE.CMD in %systemroot%\system32\ and if the started
program runs in a loop (e.g. seti@home) this will hold the
service up. if you have just some job, that has to be done
on startup - it will also serve well. simply, if the started
program does not block the service, it will stop right after
starting - I think you know about all this ....


Have fun, Assa
