This is a bug that KAV has, but F-Secure, McAfee, and Norton don’t have…
When my defragger is running, Avast goes crazy, trying to scan every file being defragged. (I use O&O defrag and PerfectDisk; both exhibit this behavior).
These two programs use the Win32 Defrag API
Running XP Pro.
One of the things Avast does is scan files that are acccesed. When you do a defrag, Avast is “chasing” the defrag operation.
Why not just shut it down until you finish the defrag?
and besides, the defrag operation will run a little bit faster!
You can’t always get every program to work with eveything else.
I have had similar trouble running Disc scan with certain programs running. No biggie. I shut them down, do what needs to be done and reboot.
Good luck 
That’s what I’m doing right now… disabling Avast, defragging, then enabling, but
Norton and McAfee both do NOT chase after defragged files! Can we make Avast the same?
I’ve just encountred this issue as well with O&O and Avast.
Turning Avast OFF really isn’t a solution specially when you have your defrag utility on scheduled defragmentation.
This would be a major concern for users who run scheduled defrags like I do. Besides remembering to turn ON/OFF an AV really isn’t a good idea.
hope this is addressed on next release.
techie101 is right. I have O&O Defrag too but I think you have a NTFS partition and not a FAT32, am I right?
O&O Defrag works perfectly with avast on FAT32 partitions… 
BINGO!
yes! I have NTFS.
hhhmmm…i foresee that this problem will not be too difficult for the developers to fix.
the source of the problem sees to have been isolated.
O&O/Avast/NTFS
great forum indeed!
BTW. I’m running O&O as a stand-alone instead of a snap-in to the XP MMC console, I wonder if that has any bearing on this issue.
No, certainly not. The behavior of O&O defrag is the same if it is a stand-alone or if it´s a MMC console either in XP and 98.
Guys, could you please try an updated driver?
Download it from http://cat.asw.cz/~vlk/aswmon2.sys (Windows XP only!!!), and put into \windows\system32\drivers. Then reboot and see what happens.
Please let me know the results.
Thanks,
Vlk
BTW: jdong, you’re talking about Win32 defrag APIs. I indeed know these APIs but the problem is that the APIs are called after the file is opened, ie. the defragmenter first opens the file (which triggers the scan), and then uses the APIs… I don’t see much options here to recognize what the program is really going to do (instead of recognizing the well-known defragmenters, of course…).
Vlk.
thanks for the effort.
Unfortunately…I still get the Error: ‘chdsk problem’ with the new .sys file.
still no defragging. :-[
WinXP Pro SP1
O&O Defrag Pro 4.0
Avast! 4.0 Pro
NTFS
(2 partitions on a 60GB Seagate ATA V)
OK I guess we’ll test it here in our lab.
Sorry for the driver - it was a shot to the dark…
I hope there is a trial of O&O Defrag available…
Thanks,
Vlk
yup…you can check out a fully functional trial version of O&O defrag pro here.
Vlk, the driver works fine in FAT32 ;D
OK folks, I think we’ve fixed it. At least with O&O Defrag 4 Trial it now works perfectly even on NTFS volumes.
Whoever wants to try, please use the following links:
For Windows XP/2003: http://cat.asw.cz/~vlk/aswmon2.sys
For Windows NT/2000: http://cat.asw.cz/~vlk/aswmon.sys
Just place the downloaded file to \windows\system32\drivers, and reboot the machine.
And please, let us know! 
Thanks
Vlk
Vlk.
Object not found.
the download links don’t lead to the file.
thanks.
Oops sorry - I hate these Linux case-sensitive filenames… :-[
Please try again
Vlk
:-* :-* :-* :-* :-* :-* :-*
IT WORKS!
Thanks!
WinXP Pro SP1
O&O Defrag Pro 4.0
Avast! 4.0 Pro
NTFS
(2 partitions on a 60GB Seagate ATA V)