I noted that in NOD32's Scheduler/Planner that you could schedule scans. At first I assumed, actually just believed it meant scans with NOD32's command line scanner. But then I realized that it said "Run external application." External application. NOD32's command line scanner is not really an external application is it? I have several other security apps with command line scanners; I chose two, Sophos Anti-rootkit is one, and Trojan Remover has FastScan. I scheduled scans with them in the way that I scheduled the scan with NOD32 and it works. So I have three scheduled scans through NOD32. I may add a fourth. It works. I believe that is why the programmers at Eset said Run external application; they figured some geek, or, in my case, pretender to geekdom would see that implementation. I called a friend, fellow member of S.I.N. who has NOD32; he said that he has for some time been scheduling scans with his anti-Trojan, an antispyware, and an anti-rootkit. That confirmed it for me. I haven't asked the folk at Eset yet. I will do that today. What do you think?