PDA

View Full Version : Problems with AMON


sir_carew
April 1st, 2004, 10:04 PM
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.

Stan999
April 1st, 2004, 10:15 PM
-{ Quote: " quoting: sir_carew link=board=39;threadid=26638;start=0#msg154035 date=1080875053]
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.
" }-

What OS? I can Stop and then Start AMON without a problem using WinXP Pro.

DiGi
April 2nd, 2004, 02:40 AM
Don't "STOP" AMON - use only [x] scanner active checkbox... It will work as you expect...

sir_carew
April 2nd, 2004, 04:04 PM
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

anders
April 3rd, 2004, 04:40 AM
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