LogTick 3.1 Changes, enhancements and problems solved

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


Changed:

The timer-engine has dramatically changed. LogTick 2.0 used to have
a maximum of 10 rates, with 2 subrates each. LogTick 3.1 is unlimited 
in the use of rates, you can add as much as subrates to one rate as 
you like.

The PAUSE button has been removed. The pause feature was incompatible 
with the new timer-engine.

The command syntax of the LogTickR Requester program has been changed. 
The start-command is enhanced with the ability to specify an ISP-name. 
Also, a comma is used to separate the command parameters. This does 
affect your dialing script if you used LogTick 2.0 !

Starting the LogTick timer by server or requester will NOT disable the 
carrier detection. This allows you to use the DEFAULT values for modem 
use, and specifying different values for requester use without having 
to alter the default values.

The INTERNAL DDE commands (transparent to the user) have changed. 
Therefore, also the LogTick Requester program version 3.0 should be 
used to make LogTick 3.1 work. Pre 3.0 version requesters don't work 
with version 3.1 LogTick. Obviously, the version 3.0 requester is 
included in the package.

Enhancements compared to LogTick 2.0

LogTick 3.1 phone-rates can be configured more flexible.

LogTick 3.1 can be used to calculate the Internet Service Providers 
costs.

LogTick 3.1 can be configured to play sound files on certain events.

LogTick 3.1 can be configured to start up at user-defined co-ordinates.

LogTick 3.1 can be configured to be 'always on top'.

The LogTick log has been improved to reflect the ISP costs.

In the LogTick log, multi-selections can be made.

Problems solved:

Although this was not a real LogTick problem:
LogTick 2.0 showed very long connection time when the system-time was
set backwards. LogTick will now ignore this change in time.

LogTick 3.0 sometimes bombed out with overflow errors. This has been
resolved