Jump to content
CCleaner Community Forums


Experienced Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About galileo

  • Rank
  1. Debug log forwarded by PM. Running XPP+SP3 fully updated+Threatfire+PrevxEdge (no other AV or AS) This particular defrag left only one block showing "0" files - other defrags have left more than one such block. galileo
  2. Degraggler 1.08.132 - after completing a defrag the drive map still shows light blue shaded blocks that are indicated as containing "0" files...this was was said to be corrected with the release of this version...is this still an issue that is awaiting correction... ...? galileo
  3. Keep in mind that defragging is much like solving a puzzle - in order to collect all fragments of a file and order them into one contiguous string there must be at least as much contiguous free space as what the defragmented file requires. So, many times you will have to spend as much time creating freespace as you do defragging. I have frequently run across the same issues as you have...when there are numerous large files. Mine tend to be with multiple hard disk (or partition) image files which are usually in the 2GB to 35GB (yes ...that is 35GB) sizes. I suggest the following method o
  4. Thank you! Is there any chance that your Defraggler code can be modified to actually provide the abilty to defrag pagefiles that are not in-use...???...as in the dual-boot arrangement that I described above. galileo
  5. @MrRon: Thanks....and while your at (chuckles)...take a look at the light blue blocks that are left on your drive map after a defrag is completed...if one re-analyzes and looks at those blocks you will see that Defraggler reports them as containing no file(s)....yet they are still identified on the drive map with the light blue coloring...it would be desirable to have them cleared of any color if they are in fact empty...Thanks again!!! @gunner: This issue here isn't an install issue nor a dependency issue - the partitions are autonomous as far as the active, or in fact each, OS is
  6. @Mr Ron: On dual boot multiple partition installations - i.e. where a dual boot environment consists of the OS (XP in this case) being installed on separate partitions ~ say C and D drives - when using Defraggler to defragment a drive (partition) containing an OS install that is not currently booted Defraggler WILL actually move the pagefile on that drive during the "Defrag" (whole drive) operation. The result frequently is that the pagefile will end up in multiple fragments due to Defraggler apparently attempting to defragment it. Strangely, this is true even if the pagefile was alread
  7. @MrRon: The issue here appears to be the same as discussed in the topic: "Defraggler confused over compressed file sizes". In my cases, the compressed drive uses Windows' native drive/file compression - not a third party compression tool. galileo
  8. 3rd confirmation....Defraggler exhibits this behavior on large capacity drives with numerous large hard drive image files - say half a dozen ~ 5GB to 40GB files. The larger the file size the worse DF functions. Not only is the success of a defrag an issue, the length of time to complete a defrag is also an issue in that DF continues to try to move files around to solve (i.e. complete) the defrag "puzzle". The defrag cycle time can become rather longer that using Windows defrag - which actually seems to do a better job with the large files than DF....assuming there is enough free space for i
  9. Yes, there can be issues (yep, I have read prior postings on this topic... ) with removing KB's from the $hf_mig$ folder - but only in particular circumstances. It is my understanding that those issues are related to file versioning versus file dating. Wherein, MS issues an update or other software containing a file whose date may be newer than the file currently installed but, whose version identifier is older. In those instances the newer "version" is utilized by installing it from the $hf_mig$ folder. This condition is actually related to trapping update errors within MS's own updates
  10. Let's see if we can resurrect this item. For those users who have been methodically updating ever since they got their machines (i.e. those who have not re-installed), their $hf_mig$ folder is typically "huge". I am managing an environment in which many of the machines have 500MB to 1GB sizes for that folder. For a post-SP3 situation, in which an SP3 uninstall is no longer deemed relevant, there is no need to retain either the SP3 uninstall folder or the old KB's that have been superceded by SP3. From a cleanup perspective, it would be very desirable to remove both the SP uninstall and the
  11. Simple command file (2 lines): c:\progra~1\defraggler\df.exe x: shutdown -s -f ...there ya go...put it in the task scheduler if desired or execute manually from a desktop link
  12. @ MrRon & MrG When using "Defrag" or "Defrag Freespace" the result upon completion will frequently leave isolated or stranded used blocks on the drivemap and thus, I am assuming, on the actual drive. The "freespace" is not truly being defragged or "compacted". These stranded blocks are an issue as other files are saved to the drive and - much more importantly - as dynamic pagefile and/or MFT spaces grow these are by necessity fragmented around these stranded blocks. Can this issue be addressed so that freespace is in fact defragged - or alternatively "compacted"...?
  13. @Defraggler Team: Can you shed any light on what is happening with development since the RC2 release Its been a little longer than your usual cycle since the last update.... Thanks! galileo
  14. @MrG RC2 "feels" better (subjectively speaking). The added buttons on the File List tab are a notable improvement - now its clear what one is doing with respect to files. I like the Defrag Folder and Defrag File options. From a performance perspective, I would really like to see options for moving all folders to the front of the drive (ala JKDefrag et al) and for respecting "layout.ini".... The opening screen "Defrag" button still leaves one wondering in what context the "Defrag" would be conducted. Perhaps adding additional button text such as - "Defrag Drive" or "Defrag Partitio
  15. @MrG The more I use RC1 the more I am convinced that something is not right: Scenario #1: select a drive and click Analyze; then View Files; select all the files for defrag; return to the Drive tab; click Defrag....what is being defragged - only the selected files or the entire drive? The defrag seems to run noticeably longer than the previous version for just the selected files. After completing the defrag; Analyze again (no fragmented file are found); click Defrag anyway - a defrag begins....what is being defragged since there were no fragmented files nor was the "Defrag Drive" men
  • Create New...