[clamav-users] MS Windows Explorer Context Menu sendto (clamscan.exe) - how to keep cmd box open to view results?

[RW Jones]

Thanks for the input and in particular the heads-up on logfiles which imo 
is the key to a simple, elegant solution which avoids batch files and 
tiresome cmd box typing.  I did some more research after the replies to my 
post but it's been interrupted by other stuff; so as the following works 
for me, I'll go with the following as one possible solution.


(In neither case will the cmd box stay open by using the settings in (A) 
and (B) below but the ***objective of seeing program output*** is in each 
case secured by viewing the log file in the chosen location, while in the 
case of clamscan.exe also preserving the convenience of selecting 
multiple, even non-contiguous, operand files in Explorer and sending them 
to clamscan.exe via its Context Menu's sendto). I've assumed Administrator 
privileges are required to do all the following whether or not that is 
actually so.  Adjust filenames/locations to taste; also the following 
assumes a default ClamAV installation.


~~~

(A) freshclam.exe desktop icon settings:

Create a desktop icon for freshclam.exe using one or other of the various 
means available.
Right click the desktop icon and set Properties as:

"C:\Program Files\ClamAV\freshclam.exe" --log=c:\[some-folder]\freshclam.log

Start in: "C:\Program Files\ClamAV"

After running via clicking the desktop icon, freshclam's log of operations 
is found in your 'favourite' / convenient directory which you specified as 
per the above.  Likewise the results of scanning files by clamscan.exe are 
logged in the location chosen as per the below.


(B) clamscan.exe and Explorer/ Context Menu sendto settings:

Add clamscan.exe to the sendto list in Explorer's Context Menu using one 
or other of the various means available.

Navigate to view:

C:\Users\[admin]\AppData\Roaming\Microsoft\Windows\SendTo\clamscan.exe.lnk

Right click clamscan.exe.lnk and set Properties as:

"C:\Program Files\ClamAV\clamscan.exe" --log=c:\[some-folder]\clamscan.log

Start in:  "C:\Program Files\ClamAV\"

~~~

Freshclam alerted me to new ClamAV version 0.103.3 so I've also updated to 
that.

Interesting to read concerning ClamWin's creative versioning; I'd just 
decided to go with ClamAV's own MS Windows version as closer to source so 
to speak.

The Windows 7 machines were of course hardened using a couple of programs 
designed for the purpose as well as utilising modiified HOSTS etc etc.; 
the plan having been to upgrade to a dual-boot with the next Debian major 
release, stable/Xfce/nonfree when it emerges in July or August. (The i386 
/ w32 version of current runs pretty well on a travelling laptop with only 
a celeron 1197.030 MHz processor and 2GB RAM). Maybe I'll consider devuan 
but offhand I don't know what its release timing will be following on the 
new Debian major version.

ClamAV is also going on the Windows 10 laptop.


Regards,


Robert Jones



On Sun, 20 Jun 2021, G.W. Haywood via clamav-users wrote:

> Date: Sun, 20 Jun 2021 16:29:41 +0100 (BST)
> From: G.W. Haywood via clamav-users <clamav-users at lists.clamav.net>
> To: RW Jones via clamav-users <clamav-users at lists.clamav.net>
> Cc: G.W. Haywood <clamav at jubileegroup.co.uk>
> Subject: Re: [clamav-users] MS Windows Explorer Context Menu sendto
>     (clamscan.exe) - how to keep cmd box open to view results?
> 
> Hi there,
>
> Disclaimer: I don't generally use Windows, and my experience of it is
> more or less limited to fixing problems that clients have had with it.
> That said, they've had a lot of problems over the years, and I know a
> lot more about it than most Windows users, but I don't by any means
> consider myself a "Windows expert"...
>
> On Sun, 20 Jun 2021, RW Jones via clamav-users wrote:
>
>> BACKGROUND:
>> MS Windows 7 SP1 x64 Pro and Home Premium.  Also intending MS Windows 10, 
>> Pro.
[snip]








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.

rwj at SDF.org
SDF Public Access UNIX System - http://SDF.org