Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by francois

  1. Just updated to beta and updates problems are gone, thanks guys!
  2. Installed beta and still have to disable the firewall to update EIS...
  3. I'd like to add that my EIS license is due in about two months and I'm seriously considering to another product right now. This is frankly unacceptable...
  4. Good morning. Can we expect to get a fix for the updates not working soon, please? Having to disable the firewall to get updates seems an important bug to me. Thanks in advance and best regards, François
  5. Good morning. Got the update yesterday night, and the french language disappeared from the language packs! Please put it back! Best regards, François
  6. Thanks for your help, but I already installed something else. Best regards, François
  7. Good morning. I understand this is not a critical bug, but any news on this issue, please? Best regards, François
  8. Hi again. Did that and saved the logs. (had to reboot in safe mode to zip them) Here's the link for the logs: http://rapidshare.com/files/2990786955/Logs.zip Thanks! François
  9. Thanks. I'll be back on the matter during the week-end. Best regards, François
  10. Hi. Running OA 6 (latest release) in limited free mode. Furthermore I've disabled the HIPS components so I'm running the Firewall only. Tonight, before installing two software updates, I disabled the Firewall from the right click menu of the tray icon. The check box disappeared from the side of Firewall, but the icon didn't change to alert me OA was disabled. (since the only component running had just been turned off) Seems a small bug to me. Or at worst the program may offer a choice of delays to have the FW automatically back on again. (15min, one hour, manual, until reboot)
  11. Thanks Christian. This is the german site. The installation file is the same I'd get on the french site? Thanks again! François
  12. I'm sorry to say I regret having enabled the installation of beta versions. Since then I'm having reboots, blue screens, etc. How can I go back to the officiel release? Uninstall and reinstall? Is a cleanup necessary? (for instance with registry keys) TIA!
  13. Hi Fabian. Yes, SP3 installed. Doing a custom scan. (see picture) And yes, EAM is allowed in Outpost. Upgraded to this morning. Will see if it helps. Best regards, François
  14. Any news on this issue? Having similar problems. (and no ELF files either)
  15. Any news Lynx? I have the same issue with also the same setup. EAM regularly hangs during a custom scan. (this morning on a PDF file which was not new) Wondering if I should update to beta...
  16. I have a question about this setup. (EAM and OA Premium FW) Is it better to disable the HIPS component of OA, letting EAM take care of the bahaviour? The two programs seem to overlap each other, as far as I can judge. (but maybe I'm wrong) Thanks in advance! François
  17. Thanks Lynx. To be sure I fully understand (with my limited english): In my example, the detection is a Trace.File object. In that case, specifying the file in the whitelist doesn't work and I need to use the Detection name instead? If so, I'm not fully comfortable with this. The reason is that maybe another file can produce the same Detection and be a real threat. (the file mentioned has been sent several days ago as a false positive to Emsisoft's lab but it has not been removed from the detection database yet) Thanks again, but I think I'll stop using this software as it's more a has
  18. Still doesn't seem to work. Question: one of my items is a file, but detected as a Trace. Is the whitelist supposed to work with that kind of detection too? Whitelist: c:\windows\system32\DWSPY32.DLL c:\program files\national instruments\signal processing start-up kit\dfd\dfd.exe c:\program files\national instruments\signal processing start-up kit\spt application.exe C:\PROGRAM FILES\Zebra Technologies\Zebra Setup Utilities\Driver\ZBRN\ZebraFD.exe Logfile attached. (I stopped the scan when the file was detected) Command-line was: C:\Program Files\a2cmd>a2cmd /smart /l /WL=whitel
  19. Thanks Lynx. I'll check all this again monday when I'm back to work. (ths is going on on my office PC) Best regards, François
  20. Thanks Lynx. Strange that putting the filename into the whitelist doesn't work here. Can you please try this?: Put your trojan file into "c:\program files". Then do the scan but use the /smart option, not the /f=[...] one. Thanks again, François
  21. Thanks Lynx. What I was trying to say (and maybe failed because english is not my primary language, as many people) is that the doc doesn't help when it comes to writing the whitelist. There's no example at all. Maybe a whitelist sample could be included with the program. The program is great, don't get me wrong! Reading your previous answer again, it seems we can't whitelist a single file with its filename. We need to use the detection name. On the other hand, Christian Peters from Emsisoft told me I could use the filename. That's contradictory, and it doesn't work here, thus this thr
  • Create New...