AMON is not starting at startup!! --- Error initializing file system monitor... HELP!

Discussion in 'NOD32 version 2 Forum' started by Daunatoru, Nov 8, 2005.

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

    Daunatoru Guest

    Hello ...

    I have installed NOD32 on a computer with the folowing configuration:
    MB: MS6163, CPU: Intel PII MMX at 233Mhz, Hdd:20Gb, PC100 32Mb SDRam, SiS6326(4Mb) video board, Network RTK8139 compatible,Cd-rom, Floppy, OS Win2000Proffesional SP4. No drivers required for MB or video board. (No sound card).

    NOD32 Version: 2.50

    At every boot-up of the computer, or restart, the AMON is not loading. It give an error : "Error initializing file system monitor." ....!!!
    If I open the NOD32 Control panel and start manualy the AMON, after a period of time is starting and runnig ok!!! But if I close the computer (shut down or restart), the same problem.

    I have unistalled and re installed NOD32 three or four times, again and again and again, but the same result.(Deleting or not the ESET directory).

    Please help me ... I have the same problem on other computer aprox. identical but with WindowsXP installed. On bouth it was Win98se and NOD32 it was working fine.

    Onthe other hand I have installed NOD32 on winXP Home and Proff with no problems, but on more powerful (hardware) computers...

    Please help. !!! This computer belongs in a network, and I need the users NOT to be able to stop the NOD32 protection! And like standard user (under Win2000 or XP) is not possible to start the AMON !!!!

    Please help me !!! I am desperate !!!!

    Thank you !!!
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    I thinks 32 MB is very little for Win2000. You should add more memory, otherwise AMON won't start.
     
  3. Daunatoru

    Daunatoru Guest

    Re: AMON is not starting at startup!! --- Error initializing file system monitor... H

    Hi again !

    As I said I have a computer almoust identical, but with 128Mb Ram ... !!! And is the same problem there! Except the OS . There is Win XP. The result ? AMON is not starting !!! The same identical error, "Error initializing file system monitor".. !
    And it has 128Mb of Ram !!

    And another thing .... on Win98se it was working fine !!! With 32 Mb Ram !!!

    Please HELP !!!

    I am desperate ! I was tryed the version 2.50.16 with the same result !!! [AMON not starting].. !!

    o_O
     
  4. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Re: AMON is not starting at startup!! --- Error initializing file system monitor... H

    There is a signifficant difference between Windows 98, Windows 2000 and Windows XP in terms of memory consumption. I'd suggest you add more RAM to see if it makes a difference.
     
  5. alglove

    alglove Registered Member

    Joined:
    Jan 17, 2005
    Posts:
    904
    Location:
    Houston, Texas, USA
    Re: AMON is not starting at startup!! --- Error initializing file system monitor... H

    I have run NOD32 successfully on a WinXP computer with 128 MB RAM, so I know it can work.

    Maybe you have some other program installed on those computers that interferes with AMON? A program that loads on startup?
     
  6. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Re: AMON is not starting at startup!! --- Error initializing file system monitor... H

    A very extensive memory load on slower machines during the startup may also cause the error.
     
  7. Daunatoru

    Daunatoru Guest

    Re: AMON is not starting at startup!! --- Error initializing file system monitor... H

    I know ... are many differences in how win98, win200 and winxp is using the memory. I am not a specialist in this kind of stuff. I just try to workarround this problem and fix it.

    On this computer (Win 2000) the SO was just installed [format hdd->installed Win2000->installed NOD32] =>Result ? AMON is not starting [the error ...etc].

    I have a question ... what command to give to the OS (a shortcut in StartUp) to load manualy the AMON ?? I have searched in the ESET directory for an exe file (like AMON.exe or something ...) but not find anything like that. There are only 3 exe files. (those 3 wich are on every computer).

    So... I suspect the slow loading on the memory for the service used by NOD32 and/or AMON.

    How can I change the order to start the services ? I want to move the NOD32 service to be first loaded (or at least in the first feew services loading). It could be a solution ? Or AMON to be loaded first ?

    Why the AMON is starting if I am starting it manualy ? And why it can not be started from an user-restricted account in WinXp ?

    Is there an answer to that ?

    Another question, ... is it possible tu use an older version of NOD32 of wich the AMON is starting ? Wich version ? Where can I find it ?

    If is not working, what alternative for NOD32 I can use for antivirus protection ? [this option is tottaly not recommended, but if the NOD32 is not working at all ...]

    Any ideas ?

    Thx in advance.
     
Thread Status:
Not open for further replies.