Jump to content

romanoff

Bug Fixers
  • Posts

    53
  • Joined

  • Last visited

Everything posted by romanoff

  1. Hi Guys, I would advise you not to modify the executable file as it may lead to unexpected problems. Pagefile.sys defrag was disabled deliberately. Best regards Romanoff
  2. Hi, can you use version 1.20 to generate a /debug log file with this issue present? A screenshot of the drive map after the disk analysis would be also very helpful. Best regards Romanoff
  3. Hi, thanks for reporting the bug. We have successfully reproduced it. It is related to the non-standard DPI value on ypur system. It will be fixed within next releases Best regards Romanoff
  4. Hi, currently the command line version of Defraggler does not have such feature. We plan to add it in future releases. Best regards Romanoff
  5. Hi Guys, we will surely look into this, as this should not happen. Still it is absolutely safe to use 1.19. Best regards Romanoff
  6. Hi Guys, we have worked very hard on this issue. Please download the latest version (1.18.185) as it should fix the problem. Best regards Romanoff
  7. romanoff

    Memory issue

    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
  8. romanoff

    Memory issue

    Hi Guys, Can you please post the debug logs from these situations? The best ones would be /debug4 logs. Best regards Romanoff
  9. Hi, can you please try out the 64 bit version of Defraggler? Best regards Romanoff
  10. Can you please use chkdsk before the defrag to make sure that there are no filesystem errors? If it still does not help, please try out the new 64 bit version of Defraggler. Best regards Romanoff
  11. 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
  12. Hi, I think what you want to do is to run a free space defrag. The best one for the job in your case would be Defrag freespace (allow fragmentation). To run it go to menu Action->Advanced->Defrag freespace (allow fragmentation). Best regards Romanoff
  13. 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
  14. Hi, can you specify which version of Defraggler are you using? Please make sure that you are using the latest release. Best regards Romanoff
  15. Hi, Can anyone else confirm this issue? Edge, can you post the debug log and exception.txt file? To run Defraggler in debug log: http://docs.piriform.com/defraggler/troubl...r-in-debug-mode The exception.txt file should be located in the executable directory after the crash. Thank you, Best regards Romanoff
  16. Hi, Can you check if you have the same issue with other products: CCleaner and Recuva? Best regards Romanoff
  17. Hi, this option is for the internal use of Defraggler. It allows to schedule several defrags at one time. As there is only one Defraggler instance allowed, this option tell the Time Schedule instances to wait for other to finish. Without that option the scheduled instances started later would just quit. Best regards Romanoff
  18. We are working on this. It will be fixed in the next release.
  19. We are working on this. It will be fixed in the next release.
  20. 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
  21. Defraggler has no specific limitations for the disk size, so 4 TB should be working fine. Can you post a debug log? Best regards romanoff
  22. Thank you for the debug log. 4M of files should not be a problem. Can you check if you are not running out of memory? Best regards romanoff
  23. Can you provide the debug log? Thank you Best regards romanoff
  24. We are looking into this Best regards romanoff
×
×
  • Create New...

Important Information

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