Originally Posted by nmsuk
Attachment 5040I did get the W7 Defragger to at least perform an analysis last week after reading your response, but it always comes back with 0% defragged. Today I looked again first with W7, and then went over to XP and did an analysis. THEY CERTAINLY DON'T PROVIDE RESULTS THAT AGREE. I have attached screen shots - Drives F, G, and L were all reported under XP as "Do NOT need defrag" (but do have some defragmentation as can be seen by the red bars), BUT the H drive is reported by XP as "Should defrag". The XP screen shots were taken immediately after leaving W7 boot. Nothing had been writen to drives F,G,H, or L in the interim.Attachment 5042Attachment 5041Attachment 5039
Attachment 5043
Last edited by cherrio; 01-25-2010 at 10:58 AM. Reason: move images out of the text area
I am sorry the attachments are all spread throughout the text. I added them after my post so don't know how to get them to show up at the end only.
Would it make any difference if you ran disk defragment through command line?
How To Defragment Disks From Command Line in Windows 7 - HowToInWindows.com
It is impossible to compare results of XP and Windows 7 defraggers, as they work with different criteria. You might like to try and plough through this doc, Engineering Windows 7 : Disk Defragmentation ? Background and Engineering the Windows 7 Improvements
particularly note the
"(Quote) In Windows XP, any file that is split into more than one piece is considered fragmented. Not so in Windows Vista if the fragments are large enough – the defragmentation algorithm was changed (from Windows XP) to ignore pieces of a file that are larger than 64MB. "
Here is some lighter reading, which might answer your question on 0% fragmentation.
Improve performance by defragmenting your hard disk
This is why I stilll prefer a 3rd party defrag utility called Auslogics Disk Defrag
Last edited by reghakr; 01-26-2010 at 04:16 AM.