Jump to content

plb

Members
  • Posts

    3
  • Joined

  • Last visited

About plb

  • Rank
    Newbie
    Newbie
  1. Updating to eset version 9 solved the problem.
  2. When disabling temporarily eset real-time protection of files, py2exe succeeds. When enabling real-time protection, py2exe aborts with an error "RuntimeError: BeginUpdateResource", triggered by its "build_executable" procedure at the line : add_resource(ensure_unicode(exe_path), mfest, RT_MANIFEST, mfest_id, False) eset does not signal any threat. There is no mention of py2exe in the eset log files.
  3. py2exe is an application generating executable file from python sources. As mentioned at hxxp://stackoverflow.com/questions/21848033/access-denied-using-py2exe, eset nod32 has to be deactivated before running py2exe. When eset nod32 is running, errors "BeginUpdateResource ... " occur during the py2exe process. Is there a way to setup eset nod32 not to conflict with py2exe ?
×
×
  • Create New...