LimpidClock 68k - a clock cycle eater?

[bloodline]

Why not set it to -120 priority (or even lower if you are feeling fruity), that way almost everything on your system will block it from executing.

-Edit- just thought, it would be trivial to write a calendar app yourself... You could do it in BlitzBasic in a few minutes and set it to only update once every hour or something

[bloodline]

As Bloodline said, set it to a much lower priority so that absolutely everything gets preferential treatment from Exec. Yes, it'll use CPU cycles, but only if another application doesn't need them. As soon as one does, LimpidClock will just stop working.

I don't see a problem with something using CPU cycles that nothing else needs.

Think of it how things like how Windows etc. treat memory: if the CPU is idle, then it's wasted. You can't throttle back the 68060, it's going to do however many cycles per second, regardless of whether you use them or not. Personally I think the full grunt of any CPU should be thrown at every task in order to get it done as quickly as possible, so you should really be getting extremely small spikes of 100% CPU usage... Actually, just thinking about it that's probably what's happening, just averaged out over a second or so to 1.5%...

Yeah, as far as I know the 060 doesn't really have much in the way of power saving features, and certainly none that would be upset with 1.5% load... Just set the priority super low and be happy