You can find ClamWin's Advanced Preferences by right clickon the icon in the system tray. Select Configure ClamWin, and you will see the Advanced Preferences tab. You will see the Additional Command Line Paramaters input block near the midle of the page.

Regards,

OK. Now I've isolated a directory of under 300 MB where the error
LibClamAV Error: [platform] FindFirstFileW() failed (3)
appears many times,
PLUS, the error
FindNextFileA(): No such file or directory
appears three times as well.

What options exactly do I need to use to gather what is needed to troubleshoot this? Do NOT use 'leave temps'?

Thanks.

no I don't need leave-temps, but --debug output
thanks

(continued next message....)

(part 2, continued from previous message...)

(continued on next message...)

(part 3, continued from previous message...)

ok looks like the problem is with vmware shared folder path syntax \\.host and something
I'll try to reproduce the problem

Thanks for reporting

hmm bad news for now, FindFirstFileW() is not able to open such filename, > MAX_PATH because it's technically a device path,
currently I'm not aware of any prefix to add to make it works ;(, perhaps explorer and cmd are also not able to handle such paths
so I think it's not a big deal , you should anyway scan host files from host and not inside the guest

I've removed your log because this thread was unreadable
and I have already reproduced it

as far I known there are no way to handle paths > 260 chars using vmware shared folders, the only solution is to map to a local drive

So, a local drive doesn't have the same length limitations of the network path? It should be easy to do a 'net use' command to test this.

Thanks!