Jump to content
CCleaner Community Forums

Willy2

Members
  • Content count

    1,542
  • Joined

  • Last visited

Everything posted by Willy2

  1. Defraggler suggestions

    Defraggler v1.09 has feature where one can look for defragmented files which are smaller or larger than a certain size. I think it bloats the program. It should be omitted. The program has the possibility to defrag selected files and these selected files are moved towards the begin of the the disk. But perhaps it's possible to add a button as well with which one can defrag selected files towards the end of the disk. I don't like the new versions v1.08 and v1.09. In version 1.07 the program automatically detects where the fragments of a defragmented file are located. They show up on the diskmap. Once this file is moved to another directory the file no longer shows up in the map once this file is re-highlighted. In fact, the program rereads the filetable. This feature I DO like very much. But this feature is removed from versions v1.08 and v1.09. In these latest versions the program seem to say the file fragments still are located in the original directory.
  2. Defraggler v1.05

    I have installed Defraggler v1.05 but it seems a number of features in this version doesn't work, doesn't function. e.g. the only language available is english and the option "move files to the end of the disk" also doesn't seem to work. Does anyone else have similar experiences with version v1.05 of Defraggler ? Willy2
  3. Defraggler suggestions

    I installed the latest version (v1.05) today (december 6th) and tried the "Move large files to end of disk" feature but when looking at the drivemap, it seemed it didn't work at all ! Are there specific pre-conditions under which this option will work ? I have specified filetypes and ticked a number of boxes but all to no avail ! More over in this version one is supposed to be able to choose some other language besides English but that wasn't possible either. Did anyone else have similar experiences ?
  4. Defraggler suggestions

    Another suggestion: A "move files towards the end of the drive" option. This could come in the form of a check box option in the filelist. This would enable moving all or selected files towards the end of the drive when defragging manually individual selected files
  5. I came across something weird. I think I have further proof that the option(s) "Defrag freespace" must be recoded/re-programed. The following happened: 1. Before I used the option "Defrag freespace" I had no fragmented files on my drive. but after I used this option I had three (!!) defragmented files. 2. I then manually defragmented these three files. Two files were defragmented without any strange behaviour. But the third file showed some weird behaviour. It was moved from spot X to a place with plenty free space and was defragmented. But apparently the program was satisfied and - according to the drivemap - moved the file back to that very same spot X, this time the filelist said that it was defragmented. It probably wasn't the very same spot were it was "pulled" from but it certainly looked like it.
  6. Defraggler suggestions

    1) Defrag the MFT and directories. Or does Defraggler defrag directories too ? Like CONTIG from Sysinternals does ? 2) Anyone who asks for a option to defrag the registry is unaware that the registry consists of more than one file. These files have names like "software", "system", "security", "sam" and "NTUSER.DAT" and regularly show up in the filelist of Defraggler. The reason why these files show up is that Windows backups these files when a socalled "Recovery point" is created. When all these individual files are defragmented, the entire registry is defragmented as well !! Or defragging the entire "C:\windows" (Windows XP) directory does the trick as well. 3) Add a (simple) "Compact" mode/option: I'll explain below. Situation before compacting: AAAA . . . BBBB . . . CCCCCCC . . DDDD . . . . (A, B, C, D represent occupied diskclusters with clusters from files named A, B, C and D. A dot (.) represents a free cluster) Situation after compacting: AAAA BBBB CCCCCCC DDDD . . . . . . . . . . . . or AAAA BBBB DDDD CCCCCCC . . . . . . . . . . . . 4) I thought the option "Defrag free space" would compact the disk like suggested under 3) but it has different algorithm / a logic of its own. So, perhaps "Defrag free space" and/or "Defrag free space (allow fragmentation)" option could be replaced with a "compact" option ? 5) In order to give Windows more space to operate: Leave always the first free, say 20 MB, 30 MB, 40 MB or 0.5% or 1% diskspace free. I do sometimes get the impression that Windows after a run with Defraggler, Windows is running more slowly, less fast. 6)An option that allows the user to decide whether a filename is to disappear from the filelist with defragmented files after it has been defragmented.
  7. Defraggler debug mode

    I came across something weird. I think I have further proof that the option(s) "Defrag freespace" must be recoded/re-programmed. The following happened: Before I used the option "Defrag freespace" (without "allow fragmentation" !!) I had no fragmented files on my drive, but after I used this option I had three (!!) defragmented files. Then I manually defragmented these three files. Two files were defragmented without any strange behaviour. But the third file showed some weird behaviour. It was moved from spot X to a place with plenty free space and was defragmented. But apparently the program was satisfied and - according to the drivemap - moved the file back to that very same spot X, this time the filelist said that it was defragmented. It probably wasn't the very same spot were it was "pulled" from but it certainly looked like it.
  8. Defraggler debug mode

    This is a follow up on post #18 of this thread. Below in the attachment a zipped file containing a picture which makes it clear what went wrong with the "Defrag free space" options. During execution of one (or both) option(s) some (a lot of (??)) files are skipped. Perhaps these files are designated Hidden, System or Write Protected by Windows XP and therefore skipped by Defraggler ? After I used one (or both) "Defrag free space" option(s), I manually defragged one particular file (in dark blue in the picture). It's clear there's a empty gap right in front of that file. And that is proof files are skipped by "Defrag free space".
  9. Defraggler suggestions

    In Defraggler 1.02.085 there's something odd. In the drivemap one can not see where the file called Pagefile is located. On my computer drive C: has a size of 11 GB and the Pagefile occupies (at least) approx. 300 MB, so it should be visible somewhere in the drivemap. Perhaps it's the intention of the programmakers to NOT show this pagefile in the drivemap any more ? Then of course, the socalled "Drive map legend" should be modified accordingly.
  10. Defraggler debug mode

    Is the loss of free space due to the fact that you have indexed that drive ??
  11. Defraggler debug mode

    Yep, this DEBUG mode is indeed useful because when looking at the map in Defraggler I do get the impression the program doesn't always defrags ALL the the free space. There are two "Defrag freespace" options. 1) "Defrag free space". 2) "Defrag free space (allow fragmentation)". Option 1) defrags the drive WITH (some) additional defragmentation of files. And I do get the impression that it also skips files. Or are these files which are write protected, hidden, system files by the WINDOWS system and therefore skipped by DEFRAGGLE ? This becomes apparent when after one manually defrags individual files. By looking at the map, one can make a guess where defragged files will be placed but sometimes the program seems to have a different opinion and places the files in a different spot. I have added a logfile containing the following actions: 1. "Defrag freespace". 2. "Defrag freespace (allow fragmentation)". 3. Defragged a number of individual files.
  12. Defraggler suggestions

    Suggestions for improvements for Defraggler RC2: 1. Add a color (gray ??) to the columnheader of the filelist in order to indicate on which column the filelist is sorted. On filename, filesize, number of fragments, etc. Omit the color when the files aren't sorted at all. 2. Add to the columnheader of the "Filelist" an arrow pointing down or up to indicate how the defragmented file are sorted (if and when sorted). This in order to indicate an ascending or a descending sorting order. 3. Omit the ""Status" tab. The information on both the number of defragmented files and the number of fragments can be displayed on the right hand side of the 4 buttons ("Analyze","Defrag", etc.). The piegraph depicting the amount of free and used space is simply a waste of programming lines and bloates the program. 4. Create a clear black line or a small divide between the map of the currently active drive and the file list. This line should serve as an indicator where to put the computer mousepointer in order to resize both the drivemap and the filelist. In the current program that's more or less a matter of guesswork.
×