|
08-02-2003, 03:17 PM
Check the readme for Autokick and it explains why the system utilization goes to 100%. In essence, the clock cycles just aren't running under the "system idle process", so they are counting towards CPU utlizization even though Autokick ins't using the CPU. In retrospect, I should have just used the Windows API to run my timer events, because Visual Basic does it differently and that is what is causing this.
You should not have any noticeable impact on performance from Autokick and your processor will be idle 98% of the time. The biggest impact occurs during read / write operations to your hard drive and those only happen when you first start Autokcik or close it.
ck
|
Threaded Mode