Hi,
I am testing Clam Sentinel 1.5 on my Win98SE, but it seems, that real-time protection does not work ...
I am coping some EXE file from E: to C:,D: but no scan is performed ... also Logs/Real-time scan is empty
Part of my clamsentinel.ini:

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

Where may be problem ? (I use side by side with ClamWin also Eset NOD 32 Antivirus)

TIA
-Laco.

So should Win 98 users still use ClamSentinel version 1.2?

BTW, for Win 9x/ME users, BitDefender Free Version 10 build 247, still provides very good on access, P2P, email and registry protection from viruses, worms, trojans, spyware and other garbage WITH AUTO UPDATE ENABLED! One problem is that one must accept the default settings, and the only way to turn off this AV is to disable it and reboot. This with Kerio Personal FW ver 2.1.5 and the old System Safey Monitor makes Win 98 VERY safe.

Dave

Yes, on Win98SE don't detects all filesystem changes, see the previous messages.
If you copy the files from the MSDos shell, or by some programs like winzip these changes are not detected (but you can configure winzip for to scan the files extracted with ClamWin).
If you copy the files with a ctrl-c ctrl-v or by a save to file dialog normally these changes are detected.
Is a limitation of the api used actually by ClamSentinel on Win98.
If I can I will try to build a vxd service for to trace all on Win98.

Aru

No. Version 1.5 works like version 1.2 (or better) on Win98.
Inside the program there are two different methods for detect filesystem changes: one for Win98SE/ME, and one for Windows 2000 or more.

I have developed Clam Sentinel principally for use it on my win98 machines, so you can be sure that new version will continue to works also on win98.

bye,
Aru

Thank you aru.

When I start using this can I ask you for help?

Yes, this works !
(previously i tested it with Total Commander and copying does not trigger scanning)


Yes I understand.

It will be very good if functionality of Clam Sentinel will be sometime / somehow merged into ClamWin ...
What do you think about idea working together with CalmWin developers to integrate some/all functionality of Clam Sentinel into ONE product ?

Thanks
-Laco.

Surely!

aru

aru, Thanks for this app.

Dave

Hi all,

The new version Clam Sentinel 1.6 is available.

Now temporary files saved by ClamScan aren't scanned.

There was a problem with usb stick because the monitor opens an handle to the device so the Safe remove did not work, now when the program detects the request of remove close the handle.

bye,
aru

Although I don't use it yet I just want to say thank you.

[quote="lacak"]

After some months is ready the vxd driver for Win98 that detects all filesystem changes.
I have also fixed some little things.

The new version 1.7 is available from sourceforge from now!

bye,
aru

[quote="aru"]

Can you let me have all the necessary links so that when Avast eventually drop their support for Windows 98 i can then jump onto ClamSentinel and ClamWin.

I want to make sure I download the correct stuff, and only you guys know the correct ones.

I will probably require some tuition as what I need to do to get both up and running together.

I ask as things might have changed and my memory isn't so good these days.

Thanks in advance.

Surely.

https://clamsentinel.sourceforge.net/

bye,
aru

Do I still need to configure an ini file, and if so how is it done, I remember being totally confused the last time about this.

Also can the installation be done with my current AV Avast program already running, or does that need to be un-installed first?

The settings file ClamSentinel.ini released with the exe is configured for Win2000 and more.
For to change it for run correctly on Win98 you must to change the ;===========Paths Settings ====== section: you must uncommented the sections for Win98 (delete the ; on the first of the line) and comment with a ; at the begin of the line the section for Win2000 and more.

On my pc runs ClamWin+ClamSentinel and Avast togheter, the only thing is to change into the ClamSentinel.ini the section NoScan this for don't scan avast temporary files.

Here the final result:

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

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

;***** on Windows NT/XP/2000, Vista
;NoScan=%USERPROFILE%\Recent\

;***** on Windows 98/ME
NoScan=C:\WINDOWS\Recent\,C:\Program Files\ALWIL SOFTWARE\AVAST4,C:\WINDOWS\TEMP\ASWUPDSUM.INI

bye,
aru