exclude file from on demand scanner

[cupez80]

how to exclude files from being scanned by on demand scanner module ? if i exclude files within AMON setting it won't be scanned by realtime but still scanned via on demand.

[Brian N]

You can't. Not yet anyways, maybe in ver.3

[Brian N]

The [removed] parameter is for testing purposes only.
{QUOTE-> Hi Brian,

I had to remove your post as it was refering to the [removed] parameter. The parameter was meant to serve for our internal purposes only as it does not do exactly what would the user expect from it according to its name. Unfortunately, it made it to the help files by error and it will be removed in future installers. <-QUOTE}So it's up to you if you wanna have a go at it ;)

[Marcos]

Please refrain from advising people to use that parameter as it does not do exactly what it's supposed to do! It was made only for purposes of the virus lab and using it might expose your computer to risk.

[cupez80]

hmmmmmmm.... can eset give some update or patch to do that (exclude files from on demand scanner) ? :D it would be very usefull....

[nameless]

{QUOTE-> [December 10th, 2005]Please refrain from advising people to use that parameter as it does not do exactly what it's supposed to do! It was made only for purposes of the virus lab and using it might expose your computer to risk. Unfortunately, it made it to the help files by error and it will be removed in future installers. <-QUOTE}
And yet reference to the [censored-but-not-so-secret] command line switch still exists in the 2.51.26 installer posted now, August, 2006. And as a result here I was--until reading this thread--looking at that installer's help file, trying to figure out how to exclude files, wasting my time, like an idiot.

Someone ought to get around to removing it from the help file...

[NOD32 user]

{QUOTE-> And yet reference to the [censored-but-not-so-secret] command line switch still exists in the 2.51.26 installer posted now, August, 2006. And as a result here I was--until reading this thread--looking at that installer's help file, trying to figure out how to exclude files, wasting my time, like an idiot.

Someone ought to get around to removing it from the help file... <-QUOTE}IMHO there is still great value in the mention of it in documentation for as long as it is parsed by the application. Perhaps the decsription of this un-named NOD32 feature could be adjusted at some time, at least until it no longer exists.

Not so long ago a big software company that makes operating systems and office productiviy suites was in trouble because they had 'undocumneted' features in their products. If I remember they were required in judgement to either document or remove these features.

AFAIK, ESET has not had the same requirement imposed upon them, but it seems if put to that same test they would already comply.

Cheers :)

[nameless]

~snip~ Blackspear Marcos already said the /exclude switch should be removed from the documentation. I wasted my time because it hadn't been. So propose notional amateur legal theories all you want, but the docs do need to be changed. Change it to say "The /exclude switch is there, but doesn't work. Our bad." I don't care.

[NOD32 user]

{QUOTE-> ~snip~ Blackspear Marcos already said the /exclude switch should be removed from the documentation. I wasted my time because it hadn't been. So propose notional amateur legal theories all you want, but the docs do need to be changed. Change it to say "The /exclude switch is there, but doesn't work. Our bad." I don't care. <-QUOTE}That sounds like a nice idea.
I'm sorry to hear you wasted some time.
Recently there was a thread here (http://www.wilderssecurity.com/showthread.php?t=142157) that covered a workaround.

Cheers :)

ps. I posted your suggestion into the Future Changes to Nod32 thread here (http://www.wilderssecurity.com/showpost.php?p=816383&postcount=496).

[ivanwong]

NOD32 can exclude some files or directories for monitoring.
Can I use "%systemroot%\dir" instead of long path like: "C:\Windows\dir" in the setting ???

[NOD32 user]

{QUOTE-> NOD32 can exclude some files or directories for monitoring.
Can I use "%systemroot%\dir" instead of long path like: "C:\Windows\dir" in the setting ??? <-QUOTE}Hi ivanwong,
I'm guessing that you're referring to exclusions in AMON.
It is necessary to specify any exclusions explicitly for AMON and to be certain it is best to exclude using two entries, one each for LFN and SFN format since AMON takes notice of the name the file or folder was accessed by.

{QUOTE-> In the case of folders with long name exceeding 8 characters, you might need to exclude both the short and long folder path (e.g. C:\Program files\Eset as well as C:\Progra~1\Eset). <-QUOTE}

If you would like more information there is a past discussion of this here (http://www.wilderssecurity.com/showthread.php?t=69207), or feel free to ask.

Cheers :)

[Brian N]

All this will be alot easier in v3, trust me