Scan on File Download

Not sure about Miranda, but command line usage should be the same:

http://portableapps.com/node/5767#comment-31657

I think the "--mode" and "--path" parameters are necessary.

I have no clue about Miranda's possibilities to handle relative paths or about your directory structure, but if %f is the variable for the downloaded file to scan, then the command should look something like that:

..\ClamWinPortable\ClamWinPortable.exe --mode=scanner --path=%f --close

That way you can be sure to use the portable version.

Though I don't think that using clamscan.exe does any harm, it's parameters are far more complicated:

..\ClamWinPortable\App\clamwin\bin\clamscan.exe --bell --database="%YourDrive%\PortableApps\ClamWinPortable\Data\db" %f --log=%YourDrive%\PortableApps\ClamWinPortable\Data\log\ClamScanLog.txt

You could skip the "--log" part, but "--bell" is recommended, as the window closes immediately after scan. And the parameters contain absolute paths (change %YourDrive% to your needs)

For more information about clamscan.exe's command line usage run clamscan.exe --help.

Thanks for the replies.

I tried using in Win XP the following

..\PortableApps\ClamWinPortable\ClamWinPortable.exe --mode=scanner --path=%f --close

but Miranda seemed to have difficulty and ClamWinPortable never starts. If I add the drive letter, it works fine.

I have to double check, but I think I was getting a message that the file was unable to be accessed when I tried the above in Win ME.

If the ..\ does not work, I suppose that Miranda cannot handle a relative path in this field? I would have to manually change the drive letter whenever the drive letter is assigned a different letter?

Odd, but the drive letter for the location for where transferred files are located changes. I wonder if that occurs because the location is within the MirandaPortable directory structure? If so, would that be a function of MirandaPortable or Miranda? I ask because I figure to have a more positive response here than with the Miranda devs for this particular, small issue.

Thanks again.