BACKGROUND:
MS Windows 7 SP1 x64 Pro and Home Premium. Also intending MS Windows 10,
Pro.
I used ClamWin for a few years as adjunct to Windows Defender mainly to
scan one or two isolated downloads but also in case Defender got
temporarily munged. But around February this year the signature updates
stopped. Someone posted a workaround with some substitute program files
at the ClamWin forum* but I decided I would try ClamAV's own official MS
Windows port (no GUI) so I installed "Traditional executable installer
that will install ClamAV in the "c:\Program Files\ directory", x64. I
am not using clamd.
* http://forums.clamwin.com/
THE QUESTION:
I don't want scan on access, just clamscan.exe to be invoked against
specified files via selecting them in Windows Explorer or similar e.g.
FreeCommander XE and then using Explorer context menu's sendto to direct
them to clamscan.exe. This works, but the cmd box which opens does not
stay open / static after the last message is printed to screen by
clamscan.exe. User may watch the output in real time and check if "OK"
comes up against specific files but I would prefer to do unattended
momentarily especially if more than a couple of files.
Are there any settings to tweak somewhere to accomplish this? I see there
are:
freshclam.conf
and
clamd.conf
but seemingly no *.conf for the executable clamscan.exe. Nothing in
folder conf_examples
(As for freshclam.exe I have created a Desktop icon to run it as
Administrator which works and one can monitor its progress in the cmd box
that opens, but again that closes on program termination - it's worked
every time over the last 3 months since installation so I have not
explored the logging capabilities, but ideally the cmd box should remain
open until dismissed by user).
I briefly investigated whether this is an MS Windows cmd box setting but I
can't find one offhand. There is cmd /k for MS Windows batch files but I'm
not using a batch file because it gets complicated if more than one file
is ot be selected and scanned (and seemingly parameters/arguments are
limited to nine: %1 to %9. In the 1990s days "DOS lets batch files
examine up to nine options typed after a batch file name at the DOS
prompt.") I've assumed modern cmd likewise.
There are probably more complexities with batch files which I don't want
to investigate at this time. I had tried the setting change for cmd in
Registry as per "Leonard" comment here
https://www.itechtics.com/3-ways-to-prevent-command-prompt-from-closing-after-running-commands/#comments
without changing the first line regarding batch files, but it made no
difference; the box just closed on program termination. (The Registry
value fwiw was changed to /k "%1" %* which I've changed back to default
of same ie. omitting /k).
How is this retention of open cmd box accomplished? Is there a
clamscan.conf which can be created to achieve this? (None I see in the
distribution). I haven't yet looked into logging options but it would be
inconvenient to use it routinely to check for positives; it's more
efficient to see the output of clamscan.exe and if toxic, discard the
scanned file and seek another source.
Or one for the developer list?
Regards,
Robert Jones
THIS E-MAIL AND ANY ATTACHED FILES ARE CONFIDENTIAL AND MAY BE LEGALLY
PRIVILEGED. If you are not the addressee, any disclosure,
reproduction, copying, distribution or other dissemination or use of
this communication is strictly prohibited. If you have received this
transmission in error please notify the sender immediately and then
delete this e-mail. All liability for viruses is excluded.
[email protected]
SDF Public Access UNIX System - http://SDF.org
_______________________________________________
clamav-users mailing list
[email protected]
https://lists.clamav.net/mailman/listinfo/clamav-users
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/contact.html#ml
