AMON not scanning when "scan all files" is enabled

[sukarof]

I noticed all of a sudden that AMON wasnt scanning files in realtime at all.
After a bit investigation I noticed that if I disable "scan all files" (in extension editor) AMON scans files in realtime. But as soon as I enable it, AMON stops scanning...
Any ideas of what has happend?

When in "scan all files" mode I only have *.txt as an exclusion. Because otherwise AMON slows down the startup of Totalcommander and some other programs, AMON scans the Processguard log-file everytime TC is started. I have tried to exclude the scanning of Processguard log-file in AMON setup, but it doesnt help - it still keeps scanning the log file. So thats why I disabled the realtime scanning of .txt-files, thats the only way of stopping AMON to scan the log-file.

NOD32 Antivirus System information
Virus signature database version: 1.1013 (20050301)
Dated: den 1 mars 2005
Virus signature database build: 5314

Information on other scanner support parts
Advanced heuristics module version: 1.012 (20050206)
Advanced heuristics module build: 1077
Internet filter version: 1.002 (2004070
Internet filter build: 1013
Archive support module version: 1.025 (20041221)
Archive support module build version: 1106

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.3
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.3
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.3

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 1024 MB
Processor: AMD Athlon(tm) 64 Processor 3200+ (2010 MHz

)

[NOD32 user]

Try just explicitly identifying the txt files you want excluded and see if it works then (full path including drive letter and case sensitive) - I'm wondering if the leading * makes it an exclusion match for everything since it looks like the exclusions are set up for explicit entries. I'd be interested to hear what difference that makes if any.

[sukarof]

I'm wondering if the leading * makes it an exclusion match for everything since it looks like the exclusions are set up for explicit entries. I'd be interested to hear what difference that makes if any.

You were right. When I deleted the *.txt from exclusion I could use the "scan all files" feature - it scans everything again. And now I can exclude the processguard log-directory for some reason, it didn´t work earlier when I tried...strange.
I guess this goes to the computer-archive X. Sometimes problems solves them selves for some reason.....
Many thanks for your input NOD32 user!
Never could have figured it out my self

[NOD32 user]

Glad to be of assistance and thanks for letting us know how it went