Another (Dreaded) Idle Full System Scan Question/Observation

I finally bit the bullet and moved up to NIS2009 from NIS2008 last week. So far I've been quite impressed with the drastically reduced footprint of the program. It might just be my imagination, but it seems like the boot-up time of my system has greatly decreased as well.

 

The only "issues" I've had so far all seem to relate to, or are exacerbated by, the lack of any way to determine if, or more importantly when all the various idle time tasks are due to, or ready to, run. I know that the CPU monitor shows the last time the tasks ran and the outcome, but there isn't any way (that I have yet to find) to know when that last run time should be considered "stale", and the tasks are due to run again.

 

I understand that there's no way to pinpoint the exact next run time due to all the factors involved (system usage, CPU load, etc.), but just a simple "Due to Run" status message would be sufficient. That way, you're not left wondering: Is it going to run? Is it time for it to run? Should I be worried yet that it hasn't run? Is there a problem I don't know about because it doesn't seem to have run? Etc.

 

Ok, now to my question/problem. If my understanding is correct, the Idle Full System Scan should run periodically, as configured in "Settings". When time, and the system goes "idle", it should run automatically until either finished or is interrupted by user activity. If it is interrupted, I would assume (and hope) that the scan is really "suspended", and resumes where it left off at the next idle time. Is my understanding of the process correct?

 

The only reason I ask this question is because: if you look at the entry for the Idle Full scan on the CPU Usage window, the status shows as "Cancelled" when a scan is interrupted, but when the system next goes idle, it changes back to running. To me, when something is "Cancelled", that means it's aborted and must start over from the beginning the next time it runs. If that isn't the case here, perhaps they should consider changing the status message to something like "Paused" or "Suspended". It might not sound like a big deal, but changing it would keep folks like me from wasting time by looking for the cause of a problem that really doesn't exist. :smileyvery-happy:

 

Leevis