IMON WinSock shim conflicts with ESI Undelete 5

Discussion in 'NOD32 version 2 Forum' started by wti, Aug 3, 2005.

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

    wti Registered Member

    Joined:
    Aug 3, 2005
    Posts:
    1
    *
    eset TS --

    I've purchased a one-year license for nod32 v2 and have discovered a
    conflict between IMON's WinSock shim and Executive Software's Undelete 5
    (fully licensed server and/or workstations editions, *not* trialware/timebomb ware).

    Undelete 5 uses a client-server interface between the UdServe process (that actually intervenes in the normal windows file deletion routine) and the NetUnd process (the desktop GUI that end users go through to access/manipulate deleted files intercepted by UdServe).

    Blessedly, IMON does not prevent UdServe from intercepting deleted files. UdServe continues to send protected deleted files to the appropriate Recovery Bin folder(s).

    Unfortunately, IMON totally clobbers the inter-process communications between UdServe and NetUnd, making it impossible to access/manipulate files contained within a Recovery Bin.

    Disabling IMON will restore the disrupted IPC.

    I've already tried excluding *all* Undelete executables (service, GUI, command line executables) in the IMON setup, without any relief. The only interim solution is to completely disable IMON.

    Is there a work around that I was unable to find by searching this forum?

    Or is eset going to find a way to make IMON co-exist constructively and peacefully with ESI Undelete? The problem is with IMON's WinSock shim.

    Thanks for your time and attention to this matter.


    *-- w
     
  2. Blackspear

    Blackspear Global Moderator

    Joined:
    Dec 2, 2002
    Posts:
    15,115
    Location:
    Gold Coast, Queensland, Australia
    Hi wti, welcome to Wilders.

    With this issue can you please send an email to support@eset.com and place a link to this thread. If you do not hear from Eset within 3 days (allows for weekends), please advise us here...

    We would appreciate if you could keep us in the loop with your progress, as we all learn this way…

    Cheers :D
     
Thread Status:
Not open for further replies.