SETI.EXE, a way of providing mutex semaphoring for setihome when launched
by setihome monitors or other methods.  It also provides a means for GUI
applications to configure SETIHOME sessions along with definable process to
execute before and after each client session.

Run seti.exe from the command line for usage, for example:

SETI.EXE v.12 (0201570699) (c) AiG (UK)[ch/Ellie].
This program is designed to be run and controlled by supported SETIHOME.EXE
monitoring applications to provide crude mutex support for client sessions.
To ensure reducing the risk of having multiple copies of setihome.exe running,
please use this 'wrapper' program. For more information on enabling your
program to utilize its features, or suggestions to improve on it please
contact: ellie@Cee3.demon.co.uk.

Usage:
 seti.exe
        ³
        ÀÄ/VIO/parameters/owner/preprocess/postprocess/logfile/
            ³       ³       ³       ³       ³           ³
            ³       ³       ³       ³       ³           ÀÄ session logfile
            ³       ³       ³       ³       ÀÄ process to run after client
            ³       ³       ³       ÀÄ process to run before client
            ³       ³       ÀÄ owner app of this session
            ³       ÀÄ standard command line parameters for setihome.exe
            ÀÄ VIO screen attributes
Example:

 seti.exe /NORMAL/-nice 1/ELLIE/BackupLog.cmd/NONE/setisession.log/



Notes:

VIO -   currently NORMAL or MINIVIO.  The seticlient.exe detects the presence
	of 4OS2 and subsequent versions will offer increased functionality with
	this in mind (like choosing where SETIHOME will display, how big,
	with/without title bars etc etc...)

Pre/Postprocess processes MUST be VIO mode programs.  Furthermore, these
programs MUST NOT 'return' or 'EXIT'.  I had a version which allowed PM
programs to be 'START'ed and allowed for return codes to be returned.
Seems to have gone astray!

The mutex mechanism is a simply by means of a file (SETIHOME.MUX in the SETI
directory) held open for the course of the session which is then closed.
This is a lot faster than creating/deleting files for seticlient.exe and
for third party apps checking the mutex.  Furthermore, there is no need to
tidy up orphaned mutex files at startup as OS/2 will close (and thus release)
the mutex on shutdown.


LESETI v1.  Command line tool to start and stop an Ellie S@H object
            with Object title message support.
LESETI START or STOP [Message]
        ³        ³     ÀÄ Optional message for desktop object
        ³        ÀÄ to stop Ellie's s@h client and update desktop object
        ÀÄ to start Ellie's s@h client and update desktop object

LESETI returns:    0 for successful completion
                   2 Unable to locate Ellie components
                   3 Unable to find SETIHOME.MUX mutex sem4 file
                   4 Unable to find kill component in Ellie directory




Feedback welcome..

Clive (et@Cee3.demon.co.uk)