need a good defrag to go with kis7...

As I stated earlier, you have to add the PD modules to the trusted zone.

 

That's comparing apples and oranges.

You have to state which verson of each program.
And, more importantly, you have to set the options in each program to as similar as possible.

 

short of th two issues i mentioned with chkdsk and defrag imo there is almost no spped diference between nod and kis

 

Comparison is valid only if options are set the same.

Try running the Office Stuff Examples with Nod and KAV 6 and KAV 7.

 

ill try it out. so you say nod is really that much faster with this application?? hmm

what is this office stuff program also? does it work with ms office and does it change anything etc.. i dont like installing stuff i dont know what it is. thanks

nevermind i saw the description.. ill try it out

 

No, I was saying that speed comparisons are not useful unless both products have same settings.

The office stuff program was created to demonstrate that a particular feature in KAV 6 was useless, and misleading. As a result the feature was dropped for KAV 7.

I expect that the same result will occur if DMON is enabled in NOD.
I discussed this in the NOD forum in early 2006.

 

ahh okay i see i dont really see any difference between them on my ofice machine here, i have now tried it with both and honestly see little to no difference in ess and kis. i uninstalled kis just to test ess and i really cant tell using them both.

 

I chose KAV over NOD because:

1. KAV is oft available free, or low price, after rebates.
2. This is a showstopper. NOD license begins on date of purchase. With KAV, and other AV, I can stockpile them until needed, especially when I see a good price.
3. The DMON feature turned me off.

 

nice to hear that. i really like kis so far it had afew quirks to work out but overall it running great.

i was using nod 3.0 when using the office test so not sure if dmon would have been a issue or not there

 

For the Office test, DMON needs to be enabled.
I do not recall to which version of NOD32 my comments were originally applied about one year ago. Could have been version 2, but I do not recall.

If the DMON issue does not exist in version 3, then the folkes at ESET, like the folkes at Kaspersky, likely saw my example and fixed things accordingly.