Jump to content
CCleaner Community Forums

Brogan

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Brogan

  • Rank
    Newbie

Profile Information

  • Gender
    Male
  • Location
    Texas City, Texas USA
  1. The major problem you have is non-contentious Free Space, which DF requires in order to manipulate files around until it can move them into their proper place, if DF cannot find a big enough block of free space to put files into it will abort. The first thing you need to do is consolidate all your free space (which you have VERY little of) and about the only way this can be done is to have the disk "Offline" and the only way to do that is to optimize during reboot or from another disk with an optimizer installed on it. You can try the DF- Freespace but I doubt it will do much of anything, you can also try to DF during reboot (do not have the Move Large Files selected), The absolute best way is to DF drive C: from drive D: If you do have a drive D: and Defraggler cannot get the job done I know of another DF'er that will. Brogan
  2. Viper426 , if I read your post correctly you had the Minimum file size set at 10280 (10GB), this means you had to have at least one (1) file => 10 GB before DF could move anything. One thing you need to know about moving large files, DF MUST have enough empty squares at or near the end of drive so that it can move the file as one continuous series of empty squares, or it will not move the file at all. If you have a lot of used squares scattered out all over your disk then you will be lucky to move any files at all, therefore you must move as many scattered used squares as you can to as close to the beginning of the dive as you can, you do this using the Full Defrag without the Move Large Files option. If you have not noticed, DF does not have an Optimize option, this is because the Full Defrag option ALSO Optimizes and will move normal files as close to the beginning of the drive as it can get them but will not move “System” files or files that are “In Use”. When trying to clean up scattered used squares it is best to do it when the drive is “Offline”, I go to my D: drive and Defrag my C: drive from there, this allows some but not all “System” files to be moved, and it makes the defrag a bit faster because it is not having to deal with files that are “in use”. I do not use the “Defrag On Reboot” because it appears to do very little if anything. The bottom line here is when moving large files keep as many used squares away from the end of disk as possible and make sure the Minimum file size is set =< the file size to be moved. When DF cannot move any files it does what you described, and you are correct, When using the “Move Large Files” option it skips the Defrag part. I GUESS because it can’t be moving some files to the end and some files to the begging of drive at the same time I store my C: drive image on drive D: and my D: drive image on drive C: I do NOT want these image files mixed up here and there amongst my regular system and/or program files. Once these image files are put on the disk they are never accessed again until they are replaced, so I always move them to the end of the disk’s, and believe me this can be one heck of a chore at times. Brogan
  3. Thanks mta, it looks like the answer to my question is: That makes my question's #2 & 3 true.
  4. Please overlook my ignorance but I cannot understand exactly what "Minimum file size" means when used with "Move Large Files". 1. Does it mean files smaller than MFS WILL be moved 2. Does it mean files larger than MFS WILL be moved 3. Does it mean files smaller than MFS will NOT be moved 4 Does it mean files larger than MFS will NOT be moved I have worked hard for 84 years just so "Minimum file size" means absolutely nothing when used as an argument to a command. Any clarification on this will be most welcome. Brogan
  5. We have an option to right click on a file and move it to the end of disk, if we had the same option but move it to the FRONT of disk then we could manage our disks much better. If a file somehow gets placed at the end of disk but really belongs at the front, there is NOTHING we can do about it. Brogan
  6. Bug or no bug, why does a Scheduled "FULL DF' remove ALL of my restore points. What it is actually doing is removing *.system files during the df which are files for the restore points. Brogan
  7. Thanks Nergal, I already have my sys. set to show all system files & contents and it's still a no show. The ONLY way to exclude them is to do a manuel defrag and un-check them, however this cannot be done every morning @ 5 AM when DF comes on line and attemps a full DF. There should be provisions in DF to handle files like these. If I attemp a DF with these files included the DF always aborts when it encounters one of these files, so I can only assume all DF's also abort. It could also be part of the problems some people have with incomplete DF'ing Brogan
  8. My system contains two files which are completly hidden and cannot be defraged and causes Defrag to abort. Defrag can find and list these files but follow the path in windows and they do not exist. Have tried adding them to the Exclude list but cannot because windows cannot display them and I cannot type in the file names. These files are: 1. $ObjId:$O 2. $UsnJrnl:$J I am thinking I really need to get these files Excluded. Advice please Brogan
×
×
  • Create New...