LimpidClock 68k - a clock cycle eater?

[ChaosLord]

I have used LimpidClock for years.  Yes it is not programmed quite right and wastes huge amounts of cpu power

It has been this way for years, sadly

The only solution is to remove LimpidClock.

[ChaosLord]

Originally LimpidClock was set to priority 0 in AmikitOS.

This was messing up the quadrascopes in TotalChaosAGA which run at priority -5

So I filed the following bug report (dug up out of my archives):

April 23, 2008:
Team Chaos presents:

A bug report AmiKitOS vs. Total Chaos AGA


* BUG: Limpid Clock priority is way to high!  It kicks in every 2
seconds and steals all cpu power for .5 seconds.  It totally ruins the
quadrascopes of Total Chaos!
* SOLUTION:  Set LimpidClock priority to -128.  And please ask
  LimpidCLock coder to please please user timer.device and wait for 60
  seconds at a time.  Thank you.  I see no need for LimpidClock task to
  wake up in a panic every 2 seconds.  

-------------------------

After filing above bug report all that immediately happened was they set Pri = -20

[ChaosLord]

More data from my secret archives:

Hi,

I remember it was problem with multiple accessing of ttengine.library.
If two or more programs used it at the same time, crashes may
occurred. In AmiKit, LimpidClock and AmiStarted used ttengine at the
same time so I had to replace LimpidClock with no ttengine version.

Regards,
Jan

Jan spent years trying to get someone to fix ttengine.library but nobody did.

So the bottom line is:
Either don't use LimpidClock or if u insist on using it then use the nottengine version else your system will get corrupted.