Avast and Network Copy Performance?

[rbeane]

OldDog-On your XP, High is the same as normal on Vista.  So essentially there is no normal on Vista, just high with regards to this. I would prefer the option of only having Avast on Vista scan the same unchanged file only once during the copy, just like normal on XP.

[DavidR]

The Standard Shield sensitivity settings should be the same as they should be independent of OS they are the same be it on Win9x through Vista, see image.

Does yours not look the same ?

[rbeane]

Yes they look the same, but if on XP (according to OldDog) avast only scans the src and tgt under High vs. only scanning the src under normal, then Vista's normal setting behaves the same as XP's high setting by scanning both during a copy.  This isn't a visual issue it is a code execution issue.

[DavidR]

I don't think there is any essential difference in how avast acts between the two OSes with the same sensitivity settings.

I would say it is possibly something that Igor or Vlk said in an earlier post about how Vista acts when you open a folder, e.g. trying to access the icon in the file, etc.

[olddog]

DavidR,

I think what Stuck@home meant is that his Normal setting is acting the same in Vista as the High setting is acting on my XP.

Stuck@home,
As a last thought, could you set your Standard Shield on Low, then click on Customise, then select the Scanner(advanced) tab. The radio button in the Scan Created/Modified files should be on "Only Files with selected extensions" and not on "All files".  (On High, this should be reversed). If this is not toggling correctly on your installation, or on Vista, then it would explain the problem.

[rbeane]

I don't have XP to compare, but according to Igor and confirmed by olddog, XP scans the src and tgt when copying on High, but not on normal.  Vista as I stated earlier scans the src and tgt when copying on normal.

[rbeane]

Olddog- I don't have an option for Low. Under normal it is set to scan only files with selected extensions. It toggles it the other way when set to high. But interestingly, the extension list under scan created/modified files does not contain jpg's, so I don't know why it is scanning them when copied.

[olddog]

Stuck@home,

Apologies - where I said Low, I should have said Normal. I have Normal/High/Custom. OK, one last thing. If you untick the "Scan Created/Modified files" then it definitely shouldn't scan them, and if you also go to the advanced tab and select "Show detailed info on performed action", you might be able to see exactly what it is scanning.

[rbeane]

With the scan created/modified setting unchecked it stil scans every file twice.  Once on the \\tgtcomp and once on the \\Srccomp.  You can see the files listed on the on-access scanner message. I don't need to reboot for these setting changes do I?

[olddog]

Stuck@home,

No you shouldn't have to reboot. If it is showing that the .jpg files themselves are being scanned during creation (write) on the destination PC with these settings, then I think there is probably nothing we can do at our level to take this further. I would hope that perhaps either Igor or Vic could look into this further to clarify just what it is scanning during the write process in Vista.   

[DavidR]

DavidR,

I think what Stuck@home meant is that his Normal setting is acting the same in Vista as the High setting is acting on my XP.

I'm aware of what Stuck@home meant and that doesn't change my reply after he made what he meant clear, avast doesn't change how it processes files when set to Normal (there is no Low in the Standard Shield sensitivity), so it would appear to be how Vista opens/processes folders/files for copying as mentioned by Igor/Vlk. What that is I have no idea as I don't use Vista

[rbeane]

DavidR - It does seem odd that Avast appears to be ignoring its own settings(specifically scan modified/created files) under Vista. If vista is handling files differently than XP, maybe there is some minor code changes that Alwil can do to compensate.

[DavidR]

Hopefully Vlk or Igor who have now contributed to this topic can try and set-up a test system to try and replicate it. If they can replicate it then perhaps there is something they can do, if they can't than that is a whole different ball game.

[rbeane]

It seems like this might not be an isolated incident, but a potential opportunity for vista specific improvement if the developers can investigate this behavior.  Could vlk or igor comment on whether they believe there is reason for further testing?

[rbeane]

Bump....Please let us know whether this is a real issue or expected behavior.