Clam Sentinel 1.8 is now available for downloading at the Sentinel page on Source Forge at https://sourceforge.net/projects/clamsentinel/ on the web.

I am using Sentinel on Vista without any problems that I have noticed. It appears that this problem is just on your computer. What is your OS? Sentinel is supposed to use the path to clamwin.conf that is on your computer. See below--perhaps something is wrong there. Does anything look strange to you?

### Path of the directory that contains the file ClamWin.conf

;***** on Windows 98/ME
;PathClamWin=C:\WINDOWS\Application Data\.clamwin\

;***** on Windows NT/XP/2000, Vista, Windows 7
PathClamWin=%APPDATA%\.clamwin\

I have pointed the Sentinel developer, Andrea Russo, to this thread.

Regards,

ClamWin 0.95.3 and Sentinel 1.7.0.0 were tested on several computers running os Windows XP Pro SP3 (NT5.1.2600).

experiments show that ClamSentinel has the bug:
ClamSentinel is not processing the strings of ClamWin configuration file (%appdata%\clamwin.conf)
if the configuration file values contain system variables.
this bug can result ClamSentinel malfunction.

ClamSentinel was used with default configuration - ClamSentinel.ini
[Params]
PathClamWin=%APPDATA%\.clamwin\
DirToScan=c:\
NoScan=%USERPROFILE%\Recent\
...

ClamWin was used with custom (fully functional and tested a lot on hundreds of computers)
universal configuration - clamwin.conf
[ClamAV]
...
kill = 1
priority = Low
logfile = %systemroot%\system32\logfiles\_clamscan.log
freshclam = %systemroot%\system32\clamwin\bin\freshclam.exe
scanarchives = 0
clamscan = %systemroot%\system32\clamwin\bin\clamscan.exe
maxscansize = 10
includepatterns =
maxfiles = 100
scanole2 = 1
quarantinedir = %systemroot%\system32\clamwin\@
maxlogsize = 2
moveinfected = 1
enablembox = 0
scanrecursive = 1
database = %systemdrive%\public\clamdb
...

both ClamWin and ClamSentinel support the using of system variables in their configuration files (e.g. %systemroot%, %appdata%, etc).
it means that ClamWin supports the using of system variables in clamwin.conf
and ClamSentinel supports the using of system variables in ClamSentinel.ini,
but ClamSentinel can not parse clamwin.conf correctly if it contain system variables (like in pasted above clamwin.conf example).

as a result ClamSentinel couldnt provide to clamscan.exe all the necessary for work parameters like database, quarantinedir, logfile, etc.
naturally ClamSentinel gui front-end works well in this case but it take no action at all.

both ClamWin and Sentinel support the using of system variables in their configuration files and
its very useful feature cause it allows to make universal ready-to-work configuration files without need to rewrite them or generate new ones for every system.
but when they work in pair ClamSentinel is able to "understand" values containing system variables inside own ClamSentinel.ini, but ClamSentinel is unable to "understand" values containg system variables inside clamwin.conf.

Thank you for looking into this. I believe Sentinel had some problems parsing configuraltion when it first came out. It looks like they were not all fixed, however. Evidently this is not a problem for someone on a stand-alone computer like me, but it you are on a network or in other special cases, it will be a problem. I'm sure the developer will address it promptly.

Regards,

This problem has been fixed into the new Clam Sentinel version 1.9.

Thank you,
aru

thank you, great work!
ClamSentinel 1.9 has not problems with system variables and process clamwin.conf options correctly.

ClamSentinel testing is going on and allready running on various machines. all results are still positive.