Just out of curiosity, why would the NOD32 scheduler have a delay of more than a minute in some cases? This is not a big deal, really. But for a while, I had been launching VBScript I wrote with Windows scheduler. Since the script is related to NOD32, I thought I'd try to launch it from within NOD. That's when I noticed how imprecise the NOD scheduler was. - When launching external apps, launch delay was consistantly 47+ seconds beyond the scheduled launch time - When launching a scheduled scan, scan launch ranged anywhere from 23 - 45+ seconds beyond scheduled launch. FYI - when launching an external app, I found that you have to include a working directory (which is usually an opptional thing). Like I said, just curious.