Jump to content

romanoff

Bug Fixers
  • Posts

    53
  • Joined

  • Last visited

Posts posted by romanoff

  1. Hi,

     

    I see that some things need to be explained.

     

    In order to use more sophisticated layout algorithms, Defraggler needs some knowledge about the structure of file system on the specific machine it is going to defrag. This data is gathered in memory in a highly efficient data structure. Unfortunately if the file system is large and complicated (has a very large number of files, fragments or a very deep folder tree) the memory consumption increases.

     

    After the drive is analyzed the file system structure information is cached in memory (that's why you are able to switch between analyzed drives and see the list of fragmented files etc.), so after analyzing several drive the cumulative memory consumption may be large.

     

    Best regards

    Romanoff

  2. Hi,

     

    currently you can use the schedule to do the job. Just create schedules for drives you would like to defrag in some close time from each other (e.g. 5 minutes). Several instances will be created. Please notice that only one instance at a time will defrag. The rest will wait - so the jobs run sequentially.

     

    Just make sure that before the schedule starts you don't have any other instances of Defraggler (Defraggler.exe of df.exe) running.

     

    Best regards

    Romanoff

  3. Hi,

     

    Apparently it is an issue with Win7 icon cache.

     

    To fix it, go through the following steps:

     

     

    1. Close all folder windows that are currently open.

     

    2. Launch Task Manager using the CTRL+SHIFT+ESC key sequence, or by running taskmgr.exe

     

    3. In the Process tab, right-click on the Explorer.exe process and select End Process

     

    4. Click the End process button when asked for confirmation.

     

    5. From the File menu of Task Manager, select New Task (Run…)

     

    6. Type CMD.EXE, and click OK

     

    7. In the Command Prompt window, type the commands one by one and press ENTER after each command:

     

    CD /d %userprofile%\AppData\Local

    DEL IconCache.db /a

    EXIT

     

    8. In Task Manager, click File, select New Task (Run…)

     

    9. Type EXPLORER.EXE, and click OK.

     

     

    The solution is after http://www.sevenforums.com/graphic-cards/2...-heres-fix.html

     

    Best regards

    Romanoff

  4. I just downloaded defragler and ran it for the first time. It started consuming LOTS of GDI objects. The count of its objects kept monotonically increasing till it was over 3,200, over ten times larger than the next highest user! I stopped the defrag at about 50% complete and restarted defragler. It still started acquiring lots of GDI objects, but, because some of the disk was already defragged, it got further. On the third time, it finished successfully. Note I am using Iarsn's, Task Manager to determine this. I am running XP home, SP3 on a 2 GHz P4 system with 1.5 GB RAM, and a 60 GB drive that is about 40% used.

     

    We are working on this. It will be fixed in the next release.

  5. Hi,

     

    The issue you have described is unlikely to be caused by Defraggler. For moving the files Defraggler uses Windows API calls and what is more important all data about the disk is taken from the operating system, so it is perfectly safe to use. The problem of bad clusters is handled by Windows and it is transparent for Defraggler. So as long as NTFS itself is aware of the bad cluster there will be no problems.

     

    It is a very good practice though, to run chkdsk before the defrag. Especially if you have a faulty disk or you perform risky activities such as powering off the machine while it is working.

     

    Best regards

    Romanoff

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.