LogTick 2.0

Changes, enhancements and problems solved


LogTick 2.0 is shareware ! You can evaluate LogTick 2.0 for 30 days. 
After that time, you're obliged to register. See the 'register.WRI' 
file that came with this package.


Changed:

The DDE link can not be switched off anymore through the configuration 
window. It appeared that this option wasn't very usefull.

The status "Connected" has been changed to "Running".

LogTick 2.0 does not use a .INI file anymore. Therefore, the logtick.ini 
file in the WINDOWS directory can be deleted. LogTick 2.0 uses a 
configuration file which is put in the applications directory.

The INTERNAL DDE commands (transparant to the user) have changed. 
Therefore, also the LogTick Requester program version 2.0 should be used 
to make LogTick 2.0 work. Version 1.x requesters doesn't work with 
version 2.0 LogTick. Obviously, the version 2.0 requester is included in 
the package.

Even when LogTick status is "Running" (previously "Connected"), it's still 
possible to configure LogTick.


Enhancements compared to LogTick 1.1

LogTick can contain 10 different rates. Each rate contains an 'expensive' 
and a 'cheap' rate. With the requester START command, you specify the NAME 
of the rate that you want to use for a session. One of the configured rates 
can be set up as default rate.

The rate values can now also be changed by clicking in the edit-boxes, and
change the values using the keyboard.

LogTick can inform you if a configured amount of time or money has passed. 
This is called alarm (notification). You can be alarmed by a popup window 
or sound. REGISTERED VERSION ONLY !

LogTick can now be triggered by a modem carrier (DCD). This means that 
it's possible to start and stop the LogTick timer without editing the 
logon or logoff scripts. When using this method, the default rate will be 
used to calculate costs.

LogTick now logs eachs session in a logfile. You can define a start and 
ending date on which LogTick calculates the (sub-)total of money spent.


Problems solved:

The PAUSE button could not be triggered by the LogTick requester. 
Issueing the PAUSE command through the requester resulted in the message 
"Server did not accept command". This has been solved.

Under certain circumstances, the LogTick requester (logtickR.exe) 
remained active after starting it with a command parameter. (If logtickR 
is started with the commands 'start' 'stop' or 'pause' logtickR should be 
started, send the command to the server and terminate after that. The 
problem was that logtickR was still an active task according to the task 
manager). This has been solved.

When LogTick had been started before 12:00 AM, and run over 12:00 AM, the 
Total connected time showed a negative number. This has been solved.