Imon strike ?

Discussion in 'NOD32 version 2 Forum' started by Melkor, Dec 9, 2003.

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

    Melkor Guest

    OK comrades, this I can confirm:

    IMON DOES slow down everything that is related to the Net - and clicking 'Repair' in the Imon setup tab & rebooting changes nothing. Neither does running the 'WinsockFix.exe' (& rebooting).

    Before 2.000.8, only firewalls such as Outpost & ZA (possibly others) took a (very very) long time to start, browser & the rest work fine.

    But the advent of 2.000.8 seems to have only compounded the problem. :mad:

    Now IE, Outlook Express, Firewalls and atom-time clock synchronizers take 'hours' (on a P4 or Athlon scale) to start. Clicking 'quit' in the Imon window to terminate Imon solves all these probs, but then again, it's more of a concession - rather Imon enabled & stay safe.

    So the questions are:

    1) Was 2.000.8 tested before being released ?

    2) How long till the IMON issue is adressed ?

    3) How long till version 2.000.8 (hopefully fixed) is available for download ?
  2. Melkor

    Melkor Guest

    ...actually, running 'WinsockFix.exe' does solve the problemm too - by disabling automatic launch of Imon at windows startup, so it comes to the same thing as switching Imon off manually using the 'Quit' button...

    BTW, gets even stranger, but when Imon is enabled, "with time" it becomes even IMPOSSIBLE to launch the browser (but other apps such as Outlook still work, though slowly) - and at that point disabling Imon does NOT solve the problem - a reboot is needed!!! :mad:

    I fear we may well have come across a nasty little bug in Imon that could well be beyond the scope of even those who released the 2.000.8 version. For now (& perhaps 4ever), the only solution is to revert back to previous version :'(
  3. Paul Wilders

    Paul Wilders Administrator

    Jul 1, 2001
    The Netherlands

    Be assured the techs from Eset are aware of the fact, certain users do encounter problems. This isn't a moderator issue.

    Since many do report all is working just fine, it's fair to assume this isn't a general issue - and therefore it's not that evident at first hand to determine a culprit.

    In a complicated situation like this (works perfect for many, others encounter problems), most probably the Lab is working overtime. I'm convinved as soon as a culprit has been found, Eset will act accordingly.


Thread Status:
Not open for further replies.