Monitor off; JkDefrag stops

[wsmaal]

Unfortunately I noticed that JkDefragmentScreenSaver stops when XP turn off the monitor of my Acer laptop. It seems that my PC's has the same problem.

JkDefragScreenSaver.log:
18:14:05 Starting, please wait...
18:14:05 JkDefrag v3.24
18:14:05 Date: 2007/09/03
18:14:05 NtfsDisableLastAccessUpdate is inactive, using LastAccessTime for SpaceHogs.
18:14:05 Analyzing disk 'C:\'
18:14:05 Starting JkDefrag for 'C:\'
18:14:05 Phase 1: Analyze
18:14:16 Phase 2: Fixup

[jeroen]

I didn't know that. The screensaver is build using the Microsft screensaver library, so I guess this happens for all screensavers.... I'm not sure I can fix this. Perhaps you can run JkDefrag via the Task Scheduler? There is an option there to only start a task if the computer is idle.

[wsmaal]

I didn't know that. The screensaver is build using the Microsft screensaver library, so I guess this happens for all screensavers.... I'm not sure I can fix this. Perhaps you can run JkDefrag via the Task Scheduler? There is an option there to only start a task if the computer is idle.

That is indeed a more reliable option :-)

[WHRoeder]

This is logical, since there's no point having the screen savers use the cpu when there's no screen. And it gives more cpu time to background processes like Seti@home

Note that you can control the amount of time before blanking the screen via control panel/power options.

[wsmaal]

Note that you can control the amount of time before blanking the screen via control panel/power options.

I know, the time that JkDefrag finished the job is quite variable. I run JkDefrag via the Task Scheduler (at system startup / only system disk)

[byblo]

Or maybe you can build a new screensaver that will be used only as a "launcher" for the main application, which will terminate with some mouse movement detection. Tricky mess but it should work...

[Myriades]

@ wsmaal

The problem u have isn't a problem.
It's a limitation of the epower soft build by ACER
2 solutions :
- disabling or giving a higher value to monitor off option
- uninstall epower management

I also have an ACER laptop, and i uninstall the soft and uses windows system power management that doesn't disable jkdefrag screensaver when stopping the monitor

[aweber1nj]

Perhaps you can run JkDefrag via the Task Scheduler? There is an option there to only start a task if the computer is idle.

OK, I like this option a lot, and I've read a bit about your utility (including the FAQs).  Forgive me for being just a touch skeptical about the way that the app would be killed/exited by the Task Scheduler when the PC comes out of "Idle".

In effect, the app could be launched multiple times per day (whenever the PC is "idle"), and somewhat abruptly killed when the PC starts being used again.

Really and truly safe for our data???

And I have a bit of a newbie question about it: You illustrate running both the cmd-line version AND the "windows version" from Task Scheduler in your FAQ.  Which do you recommend running from Task Scheduler in this way (and if I may ask....why?)?

Thanks, and keep-up the fine work.  This looks great!

AJ

[jeroen]

the app would be killed/exited by the Task Scheduler when the PC comes out of "Idle".

I haven't tried it, but I think the option in the scheduler only applies to starting the particular app. I don't think it will stop the app when the PC comes out of "idle".

Really and truly safe for our data???

It is totally safe to stop JkDefrag at any time in any way you can think of. You can even turn off the PC if you want, although that is not advised because of other applications that may be running.

Which do you recommend running from Task Scheduler in this way (and if I may ask....why?)?

The commandline version uses a bit less resources and is a bit faster than the Windows version. Other than that there is no difference, the core code is exactly the same.

[aweber1nj]

There's actually a check-box on the "Settings" Tab of the Scheduled Task (WinXP; don't know about Vista) that says "Stop the task if the computer ceases to be idle."

I haven't tried it yet, but if you say stopping it in any way is safe, then it seems like a decent option.

Can I assume that it will "pick up where it left off" on the next run, or is that going to just cause it to loop in the first stages of the run and never get to the later stages (because of being interrupted a lot of times)?

Thanks again!
-AJ

[jeroen]

Can I assume that it will "pick up where it left off" on the next run

No, JkDefrag does not remember which disks or which part of a disk it already has done.

[ewieldra]

Can I assume that it will "pick up where it left off" on the next run

No, JkDefrag does not remember which disks or which part of a disk it already has done.

and it's not neccessary .. because when there is no fragmentation .. nothing needs to be defragmentated ..