Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!rutgers!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: frisk@rhi.hi.is (Fridrik Skulason)
Newsgroups: comp.virus
Subject: Re: TSR Virus Detector (PC)
Message-ID: <0007.9105141317.AA10748@ubu.cert.sei.cmu.edu>
Date: 12 May 91 09:25:06 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 36
Approved: krvw@sei.cmu.edu

esaholm@utu.fi (Esa Holmberg) writes:
>RADAI@HUJIVMS.BITNET (Y. Radai) writes:
>
>>  The programs which I compared were F-LOCK, FSP, SECURE, TSAFE, and
>
>	I'm afraid you have tested a wrong program; F-DRIVER
>	would be the actual resident virus tester of the F-PROT
>	package, and not F-LOCK. I wonder, what the results
>	would look like with F-DRIVER instead of F-LOCK ?

Well, no - Y. Radai tested the correct program - the important
question was not how effective the programs were against KNOWN
viruses, but rather how effective they were against the methods used,
and how effective they would be against new viruses using those
methods.

I had a version of F-LOCK which was able to stop all the viruses from
accessing the system directly, but I removed that feature in version
1.08, (I think) as it conflicted with some programs, including my
cache program.

Besides - I don't currently put much emphasis on the F-LOCK part of my
package, for two reasons - it does not work with Windows (F-DRIVER
will), and it is being rewritten for version 2.0

Regarding version 2.0, which was originally scheduled to be released
two months ago - I have been seriously considering to change the name
of the product.  The most likely new name is taken from the Greek
mythology, 'Argus' - the name of the hundred-eye all-seeing giant.

Any suggestions ?

- -frisk

Fridrik Skulason                 Technical Editor of the Virus Bulletin (UK)
(author of F-PROT)               E-Mail: frisk@rhi.hi.is    Fax: 354-1-28801