"Test" of JkDefragScreenSaver.scr - Does it Start A REAL Defrag?

[ExLibris]

In the JkDefrag folder is a file called

"JkDefragScreenSaver.scr"

If you right-click on this .scr file, and select "Test", does that unintentionally actually start the real defragmentation process on the system disk?

I already know it DOES start putting data into the file JkDefragScreenSaver.log

I'm concerned if it starts actually defragging drives, because that would go far beyond what "Test" usually means when testing screensavers.

[jeroen]

JkDefrag will do actual work. I'm sorry, but I disagree with your interpretation of what the "test" button should do. I think doing actual work is exactly what Microsoft intended and what all screensavers do, running the screensaver without waiting for the usual timeout and system inactivity so that you can see if the screensaver is properly installed and working. Anything else would be useless. If you are looking at buying a car you don't just look at the outside, you start the engine and take it out for a test drive.

[ExLibris]

I strongly disagree.

The "Test" could analyze and even place information in the log file, but the MOMENT a "Test" starts actually manipulating the disk (in what is probably the most invasive and complicated post-installation disk procedure of all), it has gone far beyond "testing" the screensaver.

While an answer was implied, the question remains unanswered. Does the "Test" function start actually defragging the disk?

[Dredfox]

JkDefrag will do actual work.

Yes, the Preview button runs the screensaver without waiting. It is no different than waiting for the screen saver to start on it's own. This is not a bug with JkDefrag. Microsoft created the Preview button and programmed it to run the screen saver with no wait. You could suggest to them that they add a "verify install" button.

Anytime the screen saver is run, whether it is part of a test or running after a period of no activity, it will move files on the disc. You can specify in the options for the screensaver to run with "-a 1". Add this to the command line options (without the quotes) and anytime the screensaver runs it will analyze the disc without moving files. A log file will be created however.

[jeroen]

While an answer was implied, the question remains unanswered. Does the "Test" function start actually defragging the disk?

I answered the question, my answer was "JkDefrag will do actual work.".

I strongly disagree.

Allright. JkDefrag will first analyze the disk, and that will take some time, usually tens of seconds. During this analysis it does not make any changes to the disk. Just move the mouse and JkDefrag will exit.

[boco]

Windows' screensaver preview option will start the screensaver directly. Screensavers are renamed executable files. Rename it to .exe and you have a program.

At least the 'mini preview' screen doesn't do actual work, though.

[jeroen]

At least the 'mini preview' screen doesn't do actual work, though.

True, when JkDefrag detects it is in the mini preview screen then it will not do anything and immediately jump to the alternate screensaver.

[ExLibris]

With all respect, saying "JkDefrag will do actual work." is not the same as saying something like "Executing the screensaver 'Test' function does actually start defragging the disk."

I very much appreciate your time, the information, and the program, and I sincerely thank you.

If I might make a suggestion (which I'll repeat in a 'suggested features' forum as needed)?
In the "JkDefragScreenSaver" program, you might consider placing a 5 or 10 second 'count-down' pop-up on the screen when the screensaver version activates. It could warn the user with something like "Warning! JkDefrag will begin actual defragmentation of the disk in 10 seconds. Move the mouse or press the 'esc' key to abort."

While an answer was implied, the question remains unanswered. Does the "Test" function start actually defragging the disk?

I answered the question, my answer was "JkDefrag will do actual work.".

edit: added clarifier 'countdown'

[jeroen]

In the "JkDefragScreenSaver" program, you might consider placing a 5 or 10 second 'count-down' pop-up on the screen when the screensaver version activates.

Thanks for sharing your idea, I appreciate it! I have put it in my hat and perhaps in the future I will add such a countdown. But at the moment I don't think so. I think it's just another useless "click me to continue" nuisance, and might in fact scare people into thinking that something dangerous is about to happen. Which is not so.

[cquinn]

With all respect, saying "JkDefrag will do actual work." is not the same as saying something like "Executing the screensaver 'Test' function does actually start defragging the disk."

With all respect, you are complaining about a function of the Operating System, not of JKDefrag.
Windows gives all screensavers the option to be "test run", for the user to determine if the screen they are seeing is an enjoyable customization option, or if they want to try a different screensaver from the list of choices given.   This is the same function as the "preview" option that you get in the Screen Saver Settings dialog.

The normal expectation is that when you launch a screensaver, it will "go to work" right away; blanking the screen,  displaying text or graphics in a changing pattern,  enabling the system security options; and in the case of programs that display pictures from the disk or do other processing in the background, accessing the hard drive to retrieve or update information.
Placing a delay on that process runs counter intuitive to the reason for having a screen saver, since any user activity (and many background actions) will cause the screen saver to stop running and return the user to the desktop or to a login prompt if they so desire that security.

People are more likely to become suspicious of a "screen saver" program that doesn't appear to follow "normal" screen saver actions when it is launched.

One built in delay process that is already available for every screen saver is the countdown timer that the OS starts when it detects the system has gone idle, before attempting to start the screensaver.   That can be set in the screen saver settings dialog.
 
Going back to your original question:

If you right-click on this .scr file, and select "Test", does that unintentionally actually start the real defragmentation process on the system disk?

The simple answer is:  No, the starting of the defragmentation process is fully intentional; the confusion is in how the term "test" is applied in this context.   It is not JkDefrag running in a test mode that does no actions on the system, it is Windows running the screen saver program as a test to make sure it will actually start at the time the screen saver normally is called by the system.