although I have set the RS to scan created/modified files according to extension list, the RS doesn’t act up, if I write eicar.com from editor or unpack it from an encrypted ZIP.
it does scan on opening with editor or touching the eicar.com file in Explorer though… (scan-on-open is fed with the default list, as well as scan created…; basic page: default settings…)
W2k-SP4 plus all critical patches; AMD 2000+ with dial-up
and eerhhmm… I copied the new, larger VPU-files from the avast-setup-folder of an avastly updated PC(version #259 I think) with fast inet to this one with slow inet; and then ran avast’s prog-update.
took a while ( so I don’t know if avast didn’t download everything again, or just the #260…?),
but then it finished seemingly without problems…
was this evil …? ;D ;D
After the recommended reboot the versionnumbers and everything else looked ok to me…
???
scanning of ALL files on write brings only minor improvements (RS-provider stopped and restarted after setting the options; I’ll try it with reboot later…)
-still nothing from RS when writing from wordpad/notepad
SOMETIMES when writing from (encrypted) zip archive:
1st unpack → nothing
2nd unpack with overwrite over the 1st eicar.com-file → alert; choice delete → pretends to delete, but doesn’t delete…
Well that stinks. The updater must have someone missed installing the drivers (maybe because of the twisted updating method you used?). Anyway, just copy the *.sys files from setup\inf to system32\drivers and reboot – this should have been done by the updater itself…
You’re appearently using the 4.0.235 drivers so no wonder the situation has not changed.
P.S.:
device=C:\PROGRA~1\AntiVir\Avast4\aswmonds.sys
in system32\config.nt
OK,
after a reboot both writing from editor and zip is scanned,
when scan-on-write is set to “all files”
I’ll experiment a bit with the options & rebooting:
to see whether I can make it work
with scan-on-write only for the ext-list…
Well well well much ado about nothin’, it seems;
works with extlist now, too… don’t know why not before
(works only after reboot. I’m quite sure I DID reboot quite a few times after the update, though…)
I’ll monitor this…
P.P.S.: in advanced-Exclude there is
C:\WINNT\temp*.tmp
Is this a default setting, or one of my own invention ??
In both cases, I don’t deem it sensible…
so… somewhen after checking manually for program updates (no new results) avast tells me a couple of minutes later, it needs to reboot…
so being a good boy I do this, and now i have
aavm and aswmon with dates of 11.09.03 and version number of 4.0.191.0
in system32\drivers
same as in setup\inf (which alas, I think I didn’t copy during my manual “update” )
the version numbers in setup\inf and system32\drivers are correct ?
or do I need to fiddle some more ?? or a complete reinstall ?
Sorry about this…
