5 replies to this topic

[Anthonyk747]

Hi, I noticed that for the moment there are only 2 options for Priority of the Defraggler, in reference to the computer using CPU in certain places. By default it's set to normal, but can be placed in "background." I just thought that you should add the ability to have it set to be on "Above Normal" and "High" for those users that prefer running it at those settings. Granted, I already do this every time I open Defraggler and run it on my computer via Windows Task Manager, but I thought it'd be more convenient to have the ability to have it set already when it's opened up.

[Super Fast]

This would be very cool. Especially for low power computers where a little extra OOMPH!!! would speed things up.

Prior, I had thought it may not be that much noticeable, but on second thought, I think low speed computers may definitely see a boost from this.

[Asphyxium]

in the meantime, you can create a .cmd file containing "start /high c:\(directories containing df)\defraggler.exe".  double click it and you're done.

double check this is the correct syntax, as i've never done it myself and only briefly saw it in a .cmd file.

[Super Fast]

I tried that from an elevated command line, but it didn't work for me.

[Alan_B]

Super Fast, on 13 October 2012 - 10:36 PM, said:

I tried that from an elevated command line, but it didn't work for me.

So many ways it could fail to work :-
It made no difference to speed of defragging ;
It never launched defraggler.

"start /high c:\(directories containing df)\defraggler.exe"

I do not feel like testing the above.
It might possibly work but it does not comply with the specified syntax,
which should be conformed to with

start "title" /high c:\"(directories containing df)\defraggler.exe"

N.B.  The full syntax options are shown in response to the command

START /?

You can observe the priority level with Windows Task Manager.

I would NOT expect defragging to run at anything less than maximum speed at ANY TIME unless the system had other things that needed doing.
i.e.  Even if defraggler was set to /LOW priority it would still use all the CPU cycles it needed because "System Idle Process" is just a name of wasted CPU cycles that are begging to be used.

[Super Fast]

Alan_B, on 14 October 2012 - 03:11 AM, said:

start "title" /high c:\"(directories containing df)\defraggler.exe"

I attempted your suggestion, but it failed to work. What ended up working for me is:
<sub>Run low -> cmd /c start "runlow" /low "C:\Program Files\CCleaner\CCleaner.exe"
Run high -> cmd /c start "runhigh" /high "C:\Program Files\CCleaner\CCleaner.exe"
* To run high instead of low, replace both instances of low with high (as shown in red). Interestingly, cmd /c start "runlow" /low "%ProgramFiles%\CCleaner\CCleaner.exe" also worked.</sub>