- 7-Zip Portable
- AbiWord Portable
- Audacity Portable
- ClamWin Portable
- Command Prompt Portable
- FileZilla Portable
- GIMP Portable
- KeePass Portable
- Miranda IM Portable
- Mines-Perfect Portable
- Mozilla Firefox, Portable Edition
- Mozilla Sunbird, Portable Edition
- Mozilla Thunderbird, Portable Edition
- Notepad++ Portable
- Nvu Portable & KompoZer Portable
- On-Screen Keyboard Portable
- OpenOffice.org Portable
- Pidgin Portable
- PokerTH Portable
- PuTTY Portable
- Sudoku Portable
- Sumatra PDF Portable
- Virtual Magnifying Glass Portable
- VLC Media Player Portable
- winMd5Sum Portable
- More apps...
Command Line only ClamWin Portable?Submitted by Schadenfroh on December 20, 2007 - 3:21pm.
Hey, I am trying to minimize the size of clamwin portable and operate it with a .cmd script file (located on a USB flash drive) Is there a compilation of ClamWin Portable without GUIs that iscommand line driven only? I tried just using command line arguments, but I get errors when trying to update using freshclam "cannot parse config file .\clamd.conf", any thoughts on how to update using the command line in ClamWin Portable? I can scan using: "ClamWinPortable\App\clamwin\bin\clamscan.exe --database=ClamWinPortable\Data\db --tempdir=%temp% --recursive %systemdrive% --log=ClamWinPortable\ClamResults.txt" While I have you bothered, anyway to keep it from detecting files that are large? IE: Detected Oversized.zip? Thanks guys! ( categories: )
|
Command Line only ClamWin Portable - response
papahoward - March 29, 2008 - 11:25pmI'm using the latest .92 version in the command line (dos) mode and have been fighting the same battle. However, I think I found a solution, or at least I am no longer getting the error about "cannot parse". Mine was a problem with syntax using --exclude. I found you cannot use a wildcard with exclude. When I used "--exclude=*.jpg", I got the parse error on every line in the log. The syntax that worked was --exclude=.jpg, and it truly excluded all jpeg files. I also found you cannot use quotes with --exclude. Another thing that kept getting me in trouble was the path I used for the location I was scanning could not end with a \. While C: would work, C:\ would not, and the same held true for longer paths like c:\pictures. If it ended in a \ it bombed. It would run, but would say 0 files scanned. I finally figured it out after two days of frustration. While some parts of the command line syntax follow the rules of DOS, other parts do not. I hope this helps. Good luck.