***Scheduler problem***

[ssj100]

I notice by default that the "startup scanner" in the Scheduler is now set to run every time it is triggered (in previous versions of NOD32, there was a "run once maximum in 24 hours). I wouldn't have thought it was necessary to have it run every time though (that is, I thought running once every 24 hours would have been more than sufficient).

I also note that there is an option to not run the task if the computer is under battery power. Regarding this issue, I have tried unticking the option so that the task will be run even if the computer is under battery power. Unfortunately, the tick comes back once you click OK and complete the setup, so it will always not run the task in a battery powered computer. The only way I found is to delete the task and re-schedule it completely. Not a big problem, but I think it is a bug nonetheless.

Anyone can reproduce this please and comment?

Thanks.

[Marcos]

-{ Quote: "I notice by default that the "startup scanner" in the Scheduler is now set to run every time it is triggered (in previous versions of NOD32, there was a "run once maximum in 24 hours).
" }-

This was a sort of bug in previous versions. For security reasons, these files must be rescanned each time a newer update is issued or if another user logs on. Anyway, these scans are run in the background with as lowest priority as possible so you shouldn't notice them running.

-{ Quote: "I also note that there is an option to not run the task if the computer is under battery power. Regarding this issue, I have tried unticking the option so that the task will be run even if the computer is under battery power. Unfortunately, the tick comes back once you click OK and complete the setup, so it will always not run the task in a battery powered computer.
" }-

Good observation. We'll do our best to fix this in the upcoming v4 build.