- Nov 21, 2007
- 165
- 0
- 0
Well, I completely understand what's going on, but I still like the pretty screen. The report's also vastly helpful. Why should I defragment when the most fragmented files are cookies and firefox cache?
Originally posted by: Goldfish4209
Well, I completely understand what's going on, but I still like the pretty screen. The report's also vastly helpful. Why should I defragment when the most fragmented files are cookies and firefox cache?
Originally posted by: bsobel
1) It ships with Vista
2) Vista schedules a boot time defrag for startup performance at idle times
3) Vista schedules a whole disk defrag weekly
4) This all happens without the user doing ANYTHING.
If you say 'this isnt a feature of Vista' your just now arguing for arguings sake.
Bill
Originally posted by: Nothinman
No because the defrag will run automatically while I'm not using the machine.
Actually it does. However, if you manually start a defrag, it will not stop when you start using the machine. Only the scheduled defrag will stop on activity.Originally posted by: jonmcc33
Originally posted by: Nothinman
No because the defrag will run automatically while I'm not using the machine.
Does it "automatically" stop when you start using it again? I don't think it does...
Originally posted by: stash
Actually it does. However, if you manually start a defrag, it will not stop when you start using the machine. Only the scheduled defrag will stop on activity.
Vista Defrag FAQ (not that you will actually read it, but maybe others will): <a target=_blank class=ftalternatingbarlinklarge href="https://blogs.technet.com/filecab/articles/440717.aspx">https://blogs.technet.com/f......ticles/440717.aspx</a>
Defrag always uses low priority CPU and disk I/O except when defragging the MFT (to prevent long blocking periods on the MFT). The type of defrag you choose (scheduled or manual) makes no difference. Using low priority CPU and disk I/O does not prevent Defrag from using more system resources when you are not using the computer, such as when the scheduled defrag runs overnight. You can see this by running the command-line version of Defrag with just your Task Manager running. Defrag will eventually take a lot of resources, but if you start doing something else on the computer, Defrag will back off. This means that the defrag process will be slower when you use the computer, but then again, you won?t notice the same hit on performance as you did using the Windows XP Defragmenter.
You're reading that wrong. The defrag process will be slower because it stops defragging when the machine is in use.it DOES NOT stop the defrag if you start using applications. It just slows the defrag down.
My computer seems sluggish, as if the scheduled defrag is running and slowing down the computer as I work. How can I check to see if Defrag is running?
If you are using the computer, the ScheduledDefrag task should not be running. You shouldn?t see Defrag.exe or Dfrgntfs.exe in Task Manager, though you might catch Dfrgntfs.exe running for the couple seconds it takes to close after user activity is detected. (Note that these .exes run under SYSTEM, so you can?t see them in Task Manager without clicking the Show processes from all users button.) If, however, you started Defrag manually, then Defrag.exe and Dfrgntfs.exe will appear in Task Manager and won?t stop when user activity is detected. This manual defragmentation should not cause a significant impact on user activity thanks to defrag?s use of low-priority I/O and low priority CPU.
Originally posted by: stash
You're reading that wrong. The defrag process will be slower because it stops defragging when the machine is in use.
Defrag always uses low priority CPU and disk I/O except when defragging the MFT (to prevent long blocking periods on the MFT). The type of defrag you choose (scheduled or manual) makes no difference. Using low priority CPU and disk I/O does not prevent Defrag from using more system resources when you are not using the computer, such as when the scheduled defrag runs overnight. You can see this by running the command-line version of Defrag with just your Task Manager running. Defrag will eventually take a lot of resources, but if you start doing something else on the computer, Defrag will back off. This means that the defrag process will be slower when you use the computer, but then again, you won?t notice the same hit on performance as you did using the Windows XP Defragmenter.
Originally posted by: Goldfish4209
Oh, and when I run the command line defragger it tells me access is denied, even when I run as administrator. Any ideas on this?
Originally posted by: Goldfish4209
command prompt, defrag.exe. I put in <C:> -a [-v] and it says access is denied.
Actually, I'm already looking into getting linux and messing with it.
Originally posted by: Goldfish4209
command prompt, defrag.exe. I put in <C:> -a [-v] and it says access is denied.
Actually, I'm already looking into getting linux and messing with it.
I thought he was doing that to avoid generating emoticons or something, but good catchp.s. Stash, side note. Defrag <c:> gives invalid parameter, Defrag <c:> -a gives access denied...
Originally posted by: Nothinman
Yea, it's still licensed from Executive Software IIRC.