NOD32 conflicts

Discussion in 'NOD32 version 2 Forum' started by philosopher_dog, Jan 12, 2004.

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

    philosopher_dog Registered Member

    Joined:
    Jan 12, 2004
    Posts:
    1
    Greetings: I was impressed by NOD32's claim to being the lean mean
    virus checker, but after installing it my system went wonk-o. I was
    getting the error "windows drive not ready" after boot. This referred
    to a drive A on my machine that's modular and not currently installed.
    After canceling this message all hell breaks loose. Programs are
    unresponsive and hang, but are loaded in the background, and I can't
    get into control panel or any diagnostic parts of w2k. Thing is, the
    program was running nicely at first, getting along with everything,
    and then I installed a few more programs yesterday and this morning
    the mess started again. I tried uninstalling the other programs that
    seemed to cause the issue to no avail. Only removing NOD got the
    system back. I must say that tech support has been less than
    responsive so far. If you have suggestions about how I might solve the NOD32
    problem and get it running or a better program I might give a try to,
    please respond. I suspect I might have something loading that's
    conflicting with NOD, but I'm not sure how to narrow it down.
    Suggestions welcome. Thanx.
    Steven
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,376
    Hello,

    there were two reason why you were not give a swift response: 1. that problem has not been reported yet, 2. registered users are prioritized

    The only reason that might be responsible for such a behaviour is that there are some leftovers of the programs you've recently installed. Since you have Win2000, it will probably be impossible to revert to a backup copy unless you have some special utility allowing this installed.We need to discuss it with the developers and will let you know then.
     
Thread Status:
Not open for further replies.