Problems with AMON

Discussion in 'NOD32 version 2 Forum' started by sir_carew, Apr 1, 2004.

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

    sir_carew Registered Member

    Joined:
    Sep 2, 2003
    Posts:
    884
    Location:
    Santiago, Chile
    Hello People,
    I'm having a strange issue.
    When I clic on NOD Control Center and later press on Stop boton in AMON, AMON stop, but when I press on Start AMON can't initialized or started. However if I restart the PC, AMON will start perfectly. It only happend if I clic on stop botton and try to start it without restart windows. I know it isn't normal.
    Why AMON can't start?
    If I shutdown other process like my Firewall and later I try to start it, it start without any problem, so the problem is NOD and not windows.
    Thanks for any help.
     
  2. Stan999

    Stan999 Registered Member

    Joined:
    Sep 27, 2002
    Posts:
    566
    Location:
    Fort Worth, TX USA
    What OS? I can Stop and then Start AMON without a problem using WinXP Pro.
     
  3. DiGi

    DiGi Registered Member

    Joined:
    Jul 24, 2003
    Posts:
    114
    Location:
    in the middle of nowhere
    Don't "STOP" AMON - use only [x] scanner active checkbox... It will work as you expect...
     
  4. sir_carew

    sir_carew Registered Member

    Joined:
    Sep 2, 2003
    Posts:
    884
    Location:
    Santiago, Chile
    Problem Fixed

    Hello,
    I've discovered the problem.
    Is the first time that I've that issue, and I recently installed Sygate Pro and Norton Utilities 2002, so I disabled each services of that programs and restarted Windows and the problem is now fixed, it's Norton Utilities, without the services NOD can't be unloaded from memory and can started again without restart windows! :D
    Which is the program that cause conflicts?, NU or NOD?
    Thanks
     
  5. anders

    anders Eset Staff Account

    Joined:
    Oct 25, 2002
    Posts:
    410
    The problem is that there is no common interface for file-intercepting drivers to load/unload themselves. Because of that, most drivers can't _really_ unload if something else is loaded after it.

    There is no real reason to unload it. As mentioned before. Just disable it by unticking the checkbox.

    Best regards,
    Anders
     
Thread Status:
Not open for further replies.