Whiplash

I have an older PC where I noticed 2 bugs in Speccy: 1. https://i.imgur.com/vtPRpMx.png It should be: Total memory slots 4 Used memory slots 3 Free memory slots 1 2. https://i.imgur.com/w35THGa.png It should be: OpenGl Support 4.6

You didn't understand it. It would run Quick defrag only once per day. But it would check idle time whole day, and do it first time it happened. That way I'll forget that Defraggler even exists, which is what I like.

Mistake.

I just hope that this isn't some OS's problem/bug (I'm using XP on this PC).

And I actually miss a lot one more thing there too. After you chose "Start defrag only if computer is idle for: X minutes", you should have one more additional rule there: "If computer has not been idle that long, retry for up to: X minutes" This shouldn't be hard to do since that option already exists inside of Window's Schedule Tasks. By default, Defraggler is setting 60 minutes there, but I would like to have a bigger number there (like 720 minutes). I know, I can already increase it manually trough the Schedule Tasks, but it's not that intuitive. Basically, I want ability to set Defraggler permanently checking the idle time from the Startup to the Shut Down. Now I can't do it also because of the problem I described HERE. Anyway, I'm using XP on this PC. I'll add this suggestion to first post for better preview.

I've noticed that Scheduling isn't working if you combine "At Startup" option with additional condition "Start defrag only if computer is idle for: x minutes". Same problem probably remains if you combine "At Logon" with the same additional condition. I tried "At Startup" without any additional condition - and that one works.

Good point, I guess. But, well - I would be happy with pause (stop) and defrag restarting too. But then it should care about another thing. I mean, it would be bad if Defraggler pauses (stops), interrupted, and then waits 5 hours in process to re-scan and restart defrag. It would be perfect if Defraggler could stop defrag as it already does, but remember that it was interrupted and start again as soon as system is idle again for X minutes.

1. As you know, as an additional condition for scheduling you can set: "Start defrag only if computer is idle for: X minutes" "Stop the task if computer ceased to be idle" But the option that I'd like to have is actually: "Pause the task if computer ceased to be idle" And defraging should continue as soon as computer is idle again for the defined time. Notice that "Stop the task if computer ceased to be idle" and "Pause the task if computer ceased to be idle" shouldn't be able to be chosen (checked) together. Only one of them should be enabled. 2. System Tray icon should appear when Defraggler starts scheduled defrag process. And it should disappear once that process is finished. That will help me to know when Degraggler is in action and when HD crackling is caused by some other thing. Now, whenever I hear HD crackling, I have to open Task Manager to see if df.exe is maybe running. 3. And I actually miss a lot one more thing there too. After you chose "Start defrag only if computer is idle for: X minutes", you should have one more additional rule there: "If computer has not been idle that long, retry for up to: X minutes" This shouldn't be hard to do since that option already exists inside of Window's Schedule Tasks. By default, Defraggler is setting 60 minutes there, but I would like to have a bigger number there (like 720 minutes). I know, I can already increase it manually trough the Schedule Tasks, but it's not that intuitive. Basically, I want ability to set Defraggler permanently checking the idle time from the Startup to the Shut Down. Now I can't do it also because of the problem I described HERE.

Now I did, and the same pop-up appears again. I guess I'll have to live with that. Anyway, this doesn't happen when running CCleaner or Speccy.

I tried reinstalling already, of course. That didn't help. This happens only when starting DF. After I press OK, it opens normally with everything working well.

In past days I'm getting an error info when running Defraggler. It says this "This application failed to start because propsys.dll was not found. Re-installing the application may fix this problem". After I press OK, defraggler starts and runs normally. But I would still like to fix that error to avoid such pop-up window.

I guess so. Here: http://img14.imageshack.us/img14/2616/deff1.png http://img18.imageshack.us/img18/1731/deff2p.jpg

I'm not sure if it's bug or not, but drive map doesn't show me the page file blocks. It's only the case for C: drive. D: works ok. I have 4000 MB of paged files on both of drives (8000 overall). I'm not sure when this started to happen exactly. I just know it worked well before. I didn't change any color settings there.

I have the same problem since last 2-3 versions released. But I didn't see it as a big problem. It always shows "no data" for C: at startup, but then I click on D: and again on C: and drive map appears. So, it's not that big problem to go back to earlier versions.

Well, I actually got one weird problem while doing it over the previous version. It happened with this last version v2.14.706. After I did that, it said that I need to restart my PC. It was weird for me cause it never asked that with earlier versions while I was installing them. But, anyway, I decided to restart it immediately. But after I did that, I saw the desktop and then in few secs my screen became blue saying that PC will restart in order to prevent itself from a damage. After few unsuccessful restarts, I got a message like: The system has recovered from a serious problem. A log of this error has been created. Error signature: BCCode: A, BCP1: EB532A8, BCP2:000000FF, BCP3: 00000000, BCP4: 806BB1BE, OSVer: 5_1_2600, SP: 0_0, Product: 768_1. But, actually, seems like PC isn't recovered totally. I'm still getting some random restarts with the same blue screen. That never happened before while I was installing Defraggler after uninstalling previos version first. I installed CCleaner few times over the old versions, and this problem didn't appear there. It never asked me to restart my PC.