2nd File System Shield bug: scan-on-write always on

[Theblob]

I'm talking about this option:

http://oi38.tinypic.com/4se16d.jpg

even when I switch it off, Avast still pops an alert when I try to create/write a bad file


to test this I first had to disable scan-on-read, as well as scan-on-execute (because of the read/execute bug ) so that I could access the file

then I just try to move or copy the file somewhere else (ie. write it), and Avast pops up even tho scan-on-write is disabled!


so basically its impossible to disable scan-on-writing

that's another big bug, cause Avast scans every exe file on write (if not on read too) even if we don't try to run the file. that's another big performance hit there cause it causes unnecessary HDD activity :/

[CraigB]

Any reason to start another topic about the same thing, you could have added this to your other thread http://forum.avast.com/index.php?topic=122185.0

[Theblob]

Any reason to start another topic about the same thing, you could have added this to your other thread http://forum.avast.com/index.php?topic=122185.0

what "same thing" 

u saying there aint no difference between Read (1st topic) and Write (2nd topic) ?

the 1st topic is about scan on read/run bug (a file is run when you double-click on it, reading a file means accessing, like when you right-click to read its properties or open it with notepad or a hex editor),  the 2nd topic is about scan on write bug (a file is written when you create a file, or move it or copy it)

reading running & writing are 2 completely different actions in fact its possible to read a file without writing it and its also possible to write a file without reading it

File Shield has 2 different bugs and both are bad cause they slow down system a lot


ps. you in the development team? when are u guys gonna fix the bug?