A
Art
| Well, I'm glad to see you're interested in looking at the
| possibilities. It's been a long time since I've used KAVDOS32. I'm
| pretty sure it uses (relies on) the INI and PRF files if no switches
| are set. Setting command line switches override the PRF option
| setting(s) IIRC. It is confusing, and I used to run checks on sample
| files to make sure I had the options set the way I wanted them.
|
| Basically, just modify the default PRF settings, changing some of
| the No settings to Yes. I rarely used the redundant scan setting
| but you would, of course, if you want to scan just a folder with
| the most paranoid setup options. I believe with KAV, that setting
| causes it to scan the entire file ... and it takes much longer.
| Heuristics are on by default.
|
| Let me know if you continue to have problems with settings.
| I'll be happy to try to help.
The Multi-AV Vendor scanning tool has now been updated to use the Kaspersky Command Line
Scanner and is available through the menu.
The latest version of the Multi AV scanning tool is now available at..
http://www.ik-cs.com/programs/virtools/Multi_AV.exe
Good. I'll not be downloading it unless you're looking for critiques.
My idea was to offer just a small d/l of a KAVDOS32 Kit. To that end,
I did work up a model which does a install in the sense that the
registy is modified to yield a right click option for scanning either
a file or a folder while in Windows Explorer.
I view this KAVDOS32 kit as being for preventative use. Users who
have some other av would benefit from the ability to scan downloads
on-demand and detect malware/spyware/adware in install/setup files,
for one thing.
However, that sort of thing is really covered by KASFX. It's just that
when using that, the user doesn't get the benefit of seeing KAV
scanning all the objects contained ... and in some cases, see the
multiple malwares "within" the containers. If the scanner simply
issues a "ok" mesage, the user has no clue as to whether or not
KAV was actually able to scan within the container. Safe hex dictates
that if KAV can't scan within a container, you delete the container
and say "screw it"
So that's why I've been seriously considering doing a KAVDOS32
"safe hex and prevention" kit. We shall see. Sometimes I think it's
a big waste of time since most users won't use it or understand the
idea.
Art
http://home.epix.net/~artnpeg
Free antivirus:
http://www.ik-cs.com/programs/virtools/KASFX.EXE
http://www.claymania.com/KASFX.EXE
http://tinyurl.com/azzkc