STiKTime
==========================================================================

STiKTime is used in conjunction with CoSTa and STiK to keep track of how 
long you've been online.

STiK currently does not make this information available externally but 
does zero its cookie when disabled. This feature is used by STiKTime to 
calculate online time. Naturally, it will over-estimate if you leave STiK 
enabled whilst not really connected.

As Nos writes its connection and disconnection times into nos.log, 
STiKTime does also. You do not have to be using Nos though. This method 
was originally used to fool CoSTa into thinking Nos had connected. 
STiKTime still does this but CoSTa now knows about STiKTime.

                          STiKTime & CoSTa
                          ----------------

In CoSTa's call registration box you need to specify the telephone 
number(s). STiKTime is a special case - enter ...

vv-STiK-vv

... as the telephone number! For the curious, this was where Nos wrote its 
telephone number.

                                STiKTime
                                --------

Will run as a program or accessory - rename as .PRG or .ACC accordingly. 
When running as a program, datafiles will be stored in the current 
directory. When running as an accessory, datafiles will be stored in the 
root of the boot drive.

Once running, click on "Locate NOS.LOG" and find nos.log, or whatever file 
CoSTa has been set to scan. The file STIKTIME.DAT will be saved, this 
contains the path to your chosen file.

When the main window is closed, the file STIKTIME.POS will be stored so 
that next time the program runs, the windows appear in the same place. If 
the screen resolution has changed then the windows are re-centred.

A checkmark appears against the relevent "enabled" / "disabled" items 
telling you what STiK's status is. The rule is simple: when STiKTime 
detects the STiK cookie value changing it writes into nos.log; it writes 
"connected" info if STiK is going from disabled to enabled, and 
"diconnected" info if STiK is going from enabled to disabled.

                                Problems
                                --------

If STiK drops the line for some reason, you should disable STiK. This will 
cause STiKTime to write the "disconnected" info into nos.log so that the 
duration remains correct.

If a program crashes badly and you have to reset without dropping the line 
then try to enable STiK before running STiKTime because you do not want it 
updating nos.log with an erroneous "disconnected" as the modem is still 
online.

                                Changes
                                -------

The 1.0 version was much more complex. Written specifically for my own 
use, it performed tasks which were undesirable on some systems. The checks 
for HSMODEM's DRVIN and MFP cookies have been removed because this limited 
potential users to ST(E) machines with HSMODEM of course.

Code to recover from resets with modem up / down have been removed as they 
were only relevent to the way I work and could be detrimental call 
costing-wise, on other systems. Similary, code to deal with STiK crashing 
has been removed as STiK is now very stable.

Pug has been removed. Many bells and whistles have gone with it but the 
program is much smaller, and I do not have to maintain seperate program 
and accessory versions.

Apart from fixing any serious bugs in this version, I can't see there 
being any more. STiK should be writing its own log file soon.

                                Warranty
                                --------

None at all, expressed or implied.

                               Copyright
                               ---------

G. F. Harrison
122 Stanley Road
Forest Fields
Nottingham
NG7 6HP

guy@swampdog.demon.co.uk

                              Registration
                              ------------

Not required, FreeWare. An email would be nice though just to get an idea 
of how many users there are. :-)