Exclude doesn't mean anything to NOD32

Discussion in 'NOD32 version 1 Forum' started by marti, Jan 23, 2003.

Thread Status:
Not open for further replies.
  1. marti

    marti Registered Member

    Joined:
    Mar 25, 2002
    Posts:
    646
    Location:
    Houston, Texas, USA
    I'm currently running the beta, but I first noticed the problem exists in the released version.

    NOD causes my system to freeze when I call up the Trojan Hunter program or use the TH live update feature. Super freeze when I call up the JV16 Power Tools program.

    Somewhere in one of the NOD forums, a poster said that it's the way that some programs are packed.

    I put the entire folders for TH and JV15 Power Tools into the "exclude" area, but AMON ignores that list.

    Exclude should mean DON'T scan the files in that folder when I call up the program, but obviously, the word "exclude" has a different meaning to the ESET programmers.

    Can someone please explain why AMON is ignoring the items listed in the exclude section. The only way I can use the two programs mentioned above it to turn off AMON. One of these days, I'm going to forget to turn it back on...

    (I'm running Win98SE)
     
  2. Technodrome

    Technodrome Security Expert

    Joined:
    Feb 13, 2002
    Posts:
    2,140
    Location:
    New York
    I usually exclude .exe files. I did exclude MWsnap3 folder and it works the way it should.

    No problem here.

    Try exclude .exe files and see if it works that way
     
  3. marti

    marti Registered Member

    Joined:
    Mar 25, 2002
    Posts:
    646
    Location:
    Houston, Texas, USA
    Same exact behavior; everything freezes for a long time before the program executes.

    I have tested this by putting the AMON screen on the desktop and watching it scan the files.
     
  4. paladin1

    paladin1 Registered Member

    Joined:
    Nov 16, 2002
    Posts:
    2
    Don't have Trojan Hunter installed; but I've never experienced anything like that while running JV16 Power Tools. Have Win98SE and WinXP in a dual-boot, with NOD32 and JV16 on both OS's.

    Hope you find a cure,
    paladin1
     
  5. marti

    marti Registered Member

    Joined:
    Mar 25, 2002
    Posts:
    646
    Location:
    Houston, Texas, USA
    Here's thread in the beta forum:
    http://www.wilderssecurity.com/showthread.php?t=6105

    hayc59 says:

    this i am sad to say is an old problem, and was hoping it would be fixed in the newer version 2.0.
    but i have to turn off Imon to get jv16 powertool to work!
    i have it in my excluded folder but still stalls on me everytime i have Imon running!!!
     
  6. jan

    jan Former Eset Moderator

    Joined:
    Oct 25, 2002
    Posts:
    804
    Hi marti,

    please see this thread:

    http://www.wilderssecurity.com/showthread.php?t=6113

    Thanks for your patience and understanding :)

    jan
     
  7. tosbsas

    tosbsas Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    789
    Location:
    Lima, Peru
    This is definitly a problem with Nod and upx-packed executives, especially when your speed is under 350 mhz

    Only way out I found on my old win98se system was temporarily disable Amon and than enable it again afterwards. Doesn't hurt too much and changes everything.

    In Nod2 things look better on my computer, but 1. I use win2k now and have loads more or RAM, but still these upx compressed.exes are a problem for nod.

    Maybe jan - you can remark that in faq. How do I know its that?? I had a program sent to me by a prgrammer in two versions upx-packed and asp-packed - the difference in opening was awesome :)--((

    Ruben
     
  8. Very interesting... I had a frrezing problem off and on, when I installed jv16 power tools last week, and cleaned the registry, the freezing problem went away.. But it would freeze up on Windows\Fonts...
    I installed the new version of jv16 power tools and that wrecked my computer. I could not burn cd's any more..plus the freeze ups were back.. So, I reinstalled the registry back ups, and uninstalled jv powertools, and tried regseeker, and the freezeups were still there.. Then I uninstalled regseeker, I installed Regcleaner, and the frrze ups were gone!

    AAAAAARRRGGGGHHHHH! :D

    SO, now NOD32 (the official release) works great! I don't know about the beta...

    Thought this post may help out a bit...
     
  9. hayc59

    hayc59 Guest

    Marti..its still a problem and still a pain in the rear!!
    it has not been addressed and i see it not ever happening!!i posed this question a long time ago before the beta was even a thought, and never got a resolution other than try excluding the file or folder(and the same thing keeps happening)
    and now that i have TrojanHunter 3.1 and Jv16 all excluded in Amon it still does the same stall and freeze!! i dont think and should not have to turn Amon 'off' to accomplish my task! so waht gives?? someone at Nod should come up with the correct answers?? because it does not do this with any other file/folder or .exe program.. ;)
     
  10. sig

    sig Registered Member

    Joined:
    Feb 9, 2002
    Posts:
    716
    FWIW, I recall excluding The Cleaner folder from Amon scanning and I still had to disable Amon to prevent the hang when I updated or scanned with The Cleaner. (This is in reference to the release version of NOD. I haven't tried the beta.)
     
  11. jan

    jan Former Eset Moderator

    Joined:
    Oct 25, 2002
    Posts:
    804
    Hi all,

    we are collecting more similar problems like these and working on fixing them in upcoming Betas.

    rgds, :)

    jan
     
  12. spy1

    spy1 Registered Member

    Joined:
    Dec 29, 2002
    Posts:
    3,139
    Location:
    Clover, SC
    Well, I hope that whatever you do to "fix" the conflict/problems between the various programs and AMON doesn't impact AMON's functioning negatively in any way.

    While whatever problem there is with not being able to exclude a particular program from scanning should definitely be addressed, if there's some kind of terminal conflict involved then simply turning AMON off while using said programs seems to be the most effective work-around.

    The problems between AMON, JV16PT and TC have been well-known and documented on various forums for years (I know, I posted a lot of them myself).

    It never really occurred to me to try to exclude the programs from scanning - I simply turned off AMON while I was using them.

    In conclusion - the "won't exclude" problem aside - Eset shouldn't have to change AMON's function in any way, just to make it "play nicely" with some other program.

    Definitely not if doing so would adversely impact AMON's ability to do it's job, protection-wise. Pete
     
  13. jan

    jan Former Eset Moderator

    Joined:
    Oct 25, 2002
    Posts:
    804
    Hey spy1,
    Yes, we want to do it like that - the protection is for sure the most important. Anyway, we'll have feedback from you here ;)

    Best wishes, :)

    jan
     
Thread Status:
Not open for further replies.