problems with new screensaver features

[brm]

Hi!

I wish you happy new year and thank you for great defrag solution.

I have some problems with new screensaver features.

1.) In the list of screensavers to be started after JkDefrag finished are not listed all installed screensavers.

2.) Chosen screensaver is not started after JkDefrag.

3.) It would be nice to have possibility to set also zero hours to start again

Thanks for your work!

[jeroen]

1.) In the list of screensavers to be started after JkDefrag finished are not listed all installed screensavers.

Cal you tell me which screensavers and where I can download them?According to Microsoft all screen savers must be called "%SystemRoot"/system32/*.scr". What are the filenames of the screensavers that are not listed by JkDefrag?

2.) Chosen screensaver is not started after JkDefrag.

JkDefrag starts screensavers by executing the following commandline (you can simulate it by entering it in the "run" box in the start menu), in this example the Windows "beziers" screensaver. See http://support.microsoft.com/kb/182383 for more information about this commandline. I am guessing that the screensavers you are having problems with do not follow this standard? If you can tell me how they need to be started then maybe I can work it into JkDefrag.

Code:

cmd /c c:\winnt\system32\ssbezier.scr /s

3.) It would be nice to have possibility to set also zero hours to start again

Do you mean that the screensaver should loop? Or always start defragging whenever the screensaver kicks in, as it was with the previous version?

[brm]

1.) In the list of screensavers to be started after JkDefrag finished are not listed all installed screensavers.

Cal you tell me which screensavers and where I can download them?According to Microsoft all screen savers must be called "%SystemRoot"/system32/*.scr". What are the filenames of the screensavers that are not listed by JkDefrag?

I don't know whether it is the official feature, but windows list in its dropdown list also files matching "%SystemRoot"/*.scr". Anyway, if you support only "%SystemRoot"/system32/*.scr", it is good enough for me. I just needed to know. when I copied all *.scr from %SystemRoot to %SystemRoot/system32, all screensavers are listed.

2.) Chosen screensaver is not started after JkDefrag.

JkDefrag starts screensavers by executing the following commandline (you can simulate it by entering it in the "run" box in the start menu), in this example the Windows "beziers" screensaver. See http://support.microsoft.com/kb/182383 for more information about this commandline. I am guessing that the screensavers you are having problems with do not follow this standard? If you can tell me how they need to be started then maybe I can work it into JkDefrag.

Code:

cmd /c c:\winnt\system32\ssbezier.scr /s

cmd /c c:\winnt\system32\ssbezier.scr /s or in my case cmd /c c:\windows\system32\ssbezier.scr /s works fine, but my screensaver does not start after JkDefrag (any screensaver). I don't have any idea about the reason.

3.) It would be nice to have possibility to set also zero hours to start again

Do you mean that the screensaver should loop? Or always start defragging whenever the screensaver kicks in, as it was with the previous version?

I meant the second one, but this is really not important.

[jeroen]

windows list in its dropdown list also files matching "%SystemRoot"/*.scr".

Ah! I didn't know that. I will add this path.

but my screensaver does not start after JkDefrag

Pity! Please let me know if you find out more. Perhaps there is something on the website of the manufacturer of the screensaver?

I meant the second one

OK, I will add zero as an option in the next version of the screensaver.

[brm]

Please let me know if you find out more.

I have found, that it works fine, if I start JkSCR manually. Then after defrag is finished, OtherSCR is started. But when JkSCR is started by the windows, OtherSCR is not started and normal windows screen appears.

[jeroen]

Version 3.5 is now available. Please let me know if it fixes the problem!

[BongMong]

I'm using 3.5 and, as with 3.4, it won't run the secondary screen saver. It will go to black if set though, which is OK, but if I set it to run Starfield Simulation it just returns to the desktop.

I am using Win2Kpro though. Perhaps it works with XP only?

[jeroen]

I'm very sorry to hear that. It's a pity that it doesn't work for you as it should, and I have no ideas on how to fix it. I will keep looking at it, but since I cannot repeat the problem I doubt if I'll be able to solve it. If someone has a golden tip then please let me know!

[brm]

I'm using 3.5 and, as with 3.4, it won't run the secondary screen saver. It will go to black if set though, which is OK, but if I set it to run Starfield Simulation it just returns to the desktop.

I am using Win2Kpro though. Perhaps it works with XP only?

Unfortunatelly, it still doesn't work on XP SP2 Pro

[jeroen]

I have just released version 3.6, and I am hoping it will fix this problem. Please let me know!

[brm]

I have just released version 3.6, and I am hoping it will fix this problem. Please let me know!

Good news, Jeroen! On XP SP2 this version works perfectly.

[jeroen]

Good news, Jeroen! On XP SP2 this version works perfectly.

Thanks for the feedback! I'm glad to hear the problem is now fixed. It was caused by a totally weird bug in the Microsoft screensaver library, and I couldn't be sure my workaround would solve the problem for everybody.