F-Prot 3.16a - *New version released!*

Well just to update you on my(muf) situation with F-Prot. I ran their debugger that they sent me, e-mailed it back. I have just got an e-mail from tech support saying they could not resolve it and do not know why i get the slowdowns. They say that they think something is conflicting, but do not know what. I closed down all running application's and it still did it. My 30 trial is over with F-Prot so i could not test it again anyway. It's really pi ssed me off this. I really wanted to go with F-Prot. Damn, damn and double whammy damn!!

You may say good things about their support. But to reply by saying they don't know what's causing it and giving up is just submissive and not what you'd expect from such an established and respected company like Frisk. Well at least they tried.

I have purchased nod32. Not by choice, but by neccessity. It's a good AV, but my first choice was F-Prot. Ah well, such is life. I'll just have to accept that F-Prot "3.16a" doesn't like my system.

muf

 

Mmm.. I have some other goodies running as background threads as well.. ZoneAlarm PRO, SpyBot, Mailwasher, InCD (Nero), Acronis, B9.. just to name a few. I'm glad it wasn't any of those..

erik

 

You did what I did, ending processes in your Windows Task Manager? If not, what a pity your trial license expired..

erik

 

what about the emailing on version 4, anything new?

 

How is this AV in terms of detection rates? I downloaded it thinking it was F-secure. The good news is that it is light on resources, similar to AntiVir PE.

 

Detection rates are very good but probably not quite on par with KAV or McAfee for overall protection.
https://www.wilderssecurity.com/showthread.php?t=59554
http://www.virusbtn.com/vb100/archives/products.xml?frisk.xml

 

Just a update on F-prot 3.16a version. Since their fix on the scan engine everything is running flawless on my pc. My platform is ME. Like most members I have elected not to run the Scheduler. I have not noticed any slow down or freeze up on my pc since then. The following is technical data right from F-prot home page for your review.
-------------------------------------------------------------------------
Antivirus 3.15b.


MAJOR ENHANCEMENTS
------------------

3.16a:

This new version 3.16a is released to fix a critical bug in the
"archive bomb" detection and handling that surfaced in version 3.16.

3.16:

Version 3.16 contains a major overhaul of the virus scanning
engine (new engine version 3.16.1). These changes improve its
detection capabilities of known malware as well as unknown malware
by means of heuristics. The engine can now better detect and
handle executable packers that are often used by malware authors
to conceal their malicious code.

This version includes a more generic JPEG GDI+ exploit detection
(Microsoft Security Bulletin MS04-02 than the previous version.
It also includes EMF/WMF image format exploit detection (Microsoft
Security Bulletin MS04-032).

The single-user and trial product packages perform an Internet
update of the virus signature files during the install process.
It is therefore important to do the install while on-line. For
the multi-user product package system administrators should be
aware of the need to update the virus signature files after
post-install configuration.

The DOS scanner is now no longer installed on NT/2000/XP/2003.
If version 3.16 is installed as an upgrade then the previous DOS
version is removed. The DOS scanner is not suitable for use on
the NTFS file system, now more popular as the result of increased
use of Windows XP. The Command-Line Scanner (fpcmd.exe) should be
used instead of the DOS scanner.

The install now always integrates F-Prot Antivirus with Explorer.
This can be turned off by using the /NOHOOKSHELL option for the
setup.

All executables that are encrypted in ZIP archives are now
reported as "could be a suspicious file (encrypted program in
archive)" but where previously reported as "could be a security
risk".

Archive handling has been improved and is now more consistent.
Version 3.16 also includes detection against so-called "archive
bombs", archives that are constructed in such a way that a
seemingly innocent file will expand tremendously, consuming all
available memory and CPU on the computer. A part of this change
is that the scanners now only scan to a certain number of levels.
Of particular note is that the Command-Line Scanner (fpcmd.exe)
only scans by default to a depth of 5 levels. This can be changed
by using the command-line switch /ARCHIVE=N where N can be 1 through
99, or 0 for infinite. If the limit is exceeded then it will exit
with a new exit code 10 (some files were not scanned; in this case
because maximum archive level was reached). The OnDemand Scanner
scans an infinite number of levels by default but this behaviour
can be changed using the same command-line switch. The RealTime
Protector scans to a depth of one level by default.

Another new exit code has been added to the OnDemand Scanner and
the Command-Line Scanner, exit code 9. This exit code indicates
that some files were not scanned, e.g., encrypted files, because
of unsupported/unknown compression methods, because of
unsupported/unknown file formats, corrupted or invalid files.

Both exit code 9 and 10 indicate that some files were not scanned
and, therefore, they can not be guaranteed to be clean. The
difference between them is that if exit code 10 occurs then some
settings can be changed (e.g., increase the maximum allowed
archive depth) and the scanner might be able to scan the file.
If, however, exit code 9 occurs then the scanner is not able to
scan the file.

A complete list of the exit codes can be found at
http://www.f-prot.com/support/windows/fpwin_faq/65.html


MINOR ENHANCEMENTS AND BUGFIXES
-------------------------------

In some cases scanning files that were compressed using
unsupported/unknown compression methods resulted in an IO error.
This has now been fixed.

An IO error sometimes also occurred when scanning a part of an
archive that had been split into multiple parts. The scanner now
reports this as an invalid file.

When scanning Java class files (that are normally inside JAR
archives) the previous version reported "Not scanned (unknown file
format)" when scanning an unsupported/unknown format class file
with default scanning options. In version 3.16 this is only
reported when the /LIST command line switch is used.

RAR archive formats 1.5, 2.0 and 2.6 are supported and format 2.9
is partially supported. Format 2.9 is only supported when it is
not a solid archive and when the RAR Virtual Machine and the PPM
model are not used

 

Nothing new. In my reply back to them, I asked if these problems were holding up the release of v4 and if we would see a beta shortly after these issues with 3.16a are fixed.

The problems on my system weren't bad, and everything is still perfectly usable.

They sent me a link to a debug scanner and I ran it. The log file has been sent to them. I also gave them some additional info about the problem.