Jump to content
CCleaner Community Forums

Willy2

Experienced Members
  • Content Count

    1,559
  • Joined

  • Last visited

Posts posted by Willy2


  1. - When you hit the "Stop" button then all changes made by DF up to that point will remain intact.

    - When your computer/CPU is "sleeping" then DF will be "asleep" as well. The program won't close but it won't continue to defrag as well.

    - Defragging the system folders first would certainly increase the succes of an upgrade, IMO.

    - When you upgrade from Vista to Win 7 then the Win 7 installation program will place all Vista system files/folders (like "c:\program files", " c:\programdata", "c:\users") in a separate folder called "c:\Windows.old". These files won't be moved or removed (physically). You have to manually delete these files if you want.

    - You can tell DF to move all system files (see folders mentioned above) towards the beginning of the drive. Add all the folders on your HD to the exclude list (in the "options" menu) but don't add the folders & files that have to be moved towards the beginning of the drive, to that same "Exclude" list. then select "Defrag Free space".

    - I went one step further. I also moved all non-system folders & files to the end of the drive as much as possible. DF has some options to achieve that.


  2. - You don't need to defragment a SSD because there are no moving parts in a SSD, it's all in chips. On a HD information can be scattered all around the drive and then it will take (comparitively) much more time to read that information. The read/write head needs to re-position itself before it can read all the parts of the info.

    - If you have installed the Win 10 partition on that SSD then I assume it won't give a warning at all. However, I have a (removable) USB SSD drive and then Defraggler does give a warning before I start to defragment that SSD drive.


  3. - Quite simple. It simply means that the file grows bit by bit and that it's being written to disk in bits and pieces as well, over a (comparatively) long time. How the bits and pieces are scattered is an indication of what spots on the drive the read/write head has visited during that write process.

    - I see this happen with a lot of other files as well. E.g. large files that are being downloaded by a downloadmanager.


  4. - Sometimes deleting all System Restore Points (SRP) won't help. Then one has to switch off the "System Restore point" feature in Windows and switch it on again. Only that way one can free up all disk space. Although I wouldn't recommend to do that in the first instance.

    - Yes, the combination of DEFRAGGLER and VSS (used for making SRPs) can lead to some unpredictable results. As you have seen. DEFRAGGLER seems to - somehow - trigger the VSS subsystem in Windows. It also has been reported that DEFRAGGLER deletes SRPs.

    - Although I also know that when one's HD gets filled too much, Windows will automatically delete one or more SRPs.


  5. - I assume that MalwareBytes "absorbed" the technology into it products. Time to download JRT one more time. I hope the old algorithm will continue to work in the (near) future.

    - JRT is for 2 (or 3 ??) of my programs too aggressive. It forces me to re-install those programs again. Have to be very choosy when I want to use it.


  6. - Found something else that can be improved. When the user has clicked on "Analyze" then I think the program should open the "File list" tab (either before or after finishing the analysis). Currently that's not the case. Now DF keeps the active tab (e.g. "Search", "Health") open.

     

    - The behaviour, as descibed in the previous post, only occurs when I tell DF to save the settings in an *.ini file. I have done that because I have two copies of DF installed. Each with different settings (think:  files in e.g. the "Exclude"list ). See the attached file for a zipped up copy of that *.ini file.

    Defraggler.zip


  7. - Yes, DF still has a number of bugs. As a daily user of DF I have come across these bugs and reported them. And moving files "flawlessly" to the end of the drive is not "one of the strong points" of DF. I can't prove anything but I do get the impression that somehow Windows itself interferes with the program. Or perhaps some other program/Service interferes with Defraggler.

    - I could imagine that after a socalled "Clean boot" of Windows Defraggler would do its job(s) much better. Because then Windows is started with only the most essential Windows Services and programs. Perhaps then DF works much better ?


  8. A follow up on the "Windows Defender" problem/bug (see also previous posts).

     

    - In a thread on "BleepingComputer" I came across this SPECCY snapshot from a Win 7 system.

    http://speccy.piriform.com/results/U5U22OfLXWg37BF1XModA7W

     

    This snapshot reports the user has the Windows Defender disabled. And that's logical because he/she has MS Security Essentials (MSE) as an anti virus program. When a user installs MSE then it automatically disables Windows Defender and the Windows Defender Service.

     

    - But on my Win 7 system I have disabled the Windows Defender Service and I didn't install MSE but nonetheless SPECCY reports that Windows Defender is "Enabled".

     

    Conclusion: SPECCY pulls up the wrong info from the wrong spot and then - of course - draws the wrong conclusion. To be fixed in a/the next SPECCY version !!!!


  9. - Re-installed Win 7 SP 1 some 10 days ago and I am still busy moving files from selected folders (e.g. "c:\windows") to the beginning of the drive but DF isn't "cooperating too much". Because when I remove that folder from the "Exclude" list then DF does remove that folder (for a while). But after a new restart that folder is back in the "Exclude" list. It's driving me nuts. Talking about reliability. Grrrrrrrrrrrrrrrrrr ......................


  10. - Makes perfect sense.

    - But then I would expect that the feature "Move files to end of drive" would also take LOTS of time to perform that task. Seems that that feature ("Move files to end of drive") uses a different algorithm. Don't know what to make of it but the difference is too large to "remain under the radar".

     

    (I use the program every day to keep all non-system files away from the beginning of the C: drive)


  11. - Came across another ugly thing that can be improved in DF v2.21.

     

    - Unintentionally I added all the folders except one (or two ??) of my C: drive to the list of folders that were to be excluded from defragging. Those one or two folders contained about 60 MB of data. Then I told DF to "Defrag Freespace" my C: drive. It took DF some two hours to perform this operation. And that for a mere 60 MB of data !!!!

×
×
  • Create New...