Intro Download and install Frequently Asked Questions Tips and tricks

Homepage







© J.C. Kessels 2009
MyDefrag Forum
May 25, 2013, 05:37:07 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Screensaver ignoring 4 hour limit  (Read 1835 times)
Iangh
JkDefrag Senior
****
Posts: 34


View Profile
« on: December 02, 2007, 05:15:16 am »

I'm using the screensaver and have it set not to run within 4 hours of the last operation.

However, when I bring the PC out of standby the screensaver runs without regard to the 4 hour limit.

Is this how it should operate?

Ian
Logged
Iangh
JkDefrag Senior
****
Posts: 34


View Profile
« Reply #1 on: December 02, 2007, 09:33:09 am »

I have it working now.

Before, I was copying new JkDefrag versions into a folder called JkDefrag in order to save messing about with having to change the scheduler.

Now, I copy the JkDefrag version folder over complete so that in Program Files there is now a folder called JkDefrag-3.31. From that folder I copied the screensaver files to system32.

Don't know why it's working (Jeroen probably does) but it is now waiting for 4 hours on both PCs unlike before when it was defragging after every wake.

Ian
Logged
jeroen
Administrator
JkDefrag Hero
*****
Posts: 7155



View Profile WWW
« Reply #2 on: December 02, 2007, 03:11:24 pm »

I'm not sure why you are copying the program, but it should not affect the timeout. The screensaver will store a timestamp in the registry just after it has finished a complete run (and just before it starts the alternate screensaver). When it starts up again it checks if the current time is more than NN hours past the timestamp. If not then it does not run, and does not update the timestamp. The timestamp is reset when you open the settings of the screensaver.
Logged
Iangh
JkDefrag Senior
****
Posts: 34


View Profile
« Reply #3 on: December 02, 2007, 10:29:21 pm »

I copied JkDefrag to a folder called JkDefrag as this meant I didn't have to change the file name in the scheduler to reflect the latest JkDefrag build, JkDefrag-3.N. We have it on 3 PCs so it made upgrading easier.

For some strange reason deleting JkDefrag from Program Files and copying the latest folder, JkDefrag-3.31, to Program Files and copying the screensaver files from there to system32 gets the screensaver working.

I had the fault on the two PCs I was testing so something strange must have happened.

Personally, I also don't see why there should be a problem with changing the folder name to plain JkDefrag.

Ian

Logged
jeroen
Administrator
JkDefrag Hero
*****
Posts: 7155



View Profile WWW
« Reply #4 on: December 03, 2007, 12:06:22 am »

Well, if it works now then sweet. The name of the folder does not matter in any way, it is simply not used. But the screensaver files MUST be in the Windows folder, somewhere else and they will not be used. Also note that the screensaver is standalone, it does not use the "jkdefrag.exe" executable. So when you upgrade it is not enough to only copy the new files to your JkDefrag folder, you must also upgrade the screensaver files in the windows folder.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.5 | SMF © 2006-2008, Simple Machines LLC Valid XHTML 1.0! Valid CSS!