Re: Win32forth.exe deleted by McAfee VirusScan Enterprise
- From: rickman <gnuarm@xxxxxxxxx>
- Date: Sat, 9 Apr 2011 13:51:37 -0700 (PDT)
On Apr 6, 6:03 pm, Albert van der Horst <alb...@xxxxxxxxxxxxxxxxxx>
wrote:
In article <dea8f096-9029-415e-9d34-7c59b6c50...@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Brad <hwfw...@xxxxxxxxx> wrote:
Hi All,
Here's something I didn't see coming. After a company upgrade to
Windows 7, I needed to re-install Win32forth version 6.12. McAfee
automatically deleted the following files:
Win32forth.exe detected as: W32/Autorun.worm!js Virus
Setup.exe Artemis!C957BA89FE49 Trojan
I had to manually copy them from another machine. Fortunately, nothing
was found after manually initiating a scan.
In the Dutch Forth Chapter we are investigating Forths (choosing
a successor for the ancient 16 bit chforth.)
We too observed an objection from a virus detector during installation.
It suffices to temporarily disable it during installation,
a feature that is present in most virus scanners.
With the growth of the virus databases those false positives
will occur more and more often.
That is a funny way to look at it. The AVS algorithms are not dumb.
If the developers are told of the false positives they should make
changes to prevent that. I use Sophos and when I report problems to
them they always take the reports seriously and I get a personal
reply... from a person... really! I can only assume they appreciate
the feedback.
And yes, one of those reports was about Win32Forth...
Rick
.
- References:
- Win32forth.exe deleted by McAfee VirusScan Enterprise
- From: Brad
- Re: Win32forth.exe deleted by McAfee VirusScan Enterprise
- From: Albert van der Horst
- Win32forth.exe deleted by McAfee VirusScan Enterprise
- Prev by Date: Re: gforth GLFW Framework Code Addendum 01
- Next by Date: do any forth appserver support continuations?
- Previous by thread: Re: Win32forth.exe deleted by McAfee VirusScan Enterprise
- Next by thread: POL
- Index(es):
Relevant Pages
|