[QUOTE=PrimeCruncher]The problem is that there's no way to know when the monitor goes into powersave. Writing a screensaver really wouldn't be worth the effort, especially considering that the target environment for this is a computer that randomly changes the screensaver..[/QUOTE]
I believe a global message WM_SYSCOMMAND with a SC_MONITORPOWER is sent when powersave is started.

The "randomly changes the screensaver": by a program or the user changes it himself? If the latter it would only be part of the options for this yet-not-written screensaver.


[QUOTE=PrimeCruncher]The only thing here that looks good is the second to last link; the others are platform-specific, which I'm trying to avoid. And the last one is for writing a screensaver, which has been proposed several times on this board and shot down every time.[/QUOTE]
Yes it was for writing a screensaver :wink:
Will try to find some good discussions why a screensaver solution would be bad... (off searching)

[QUOTE=lunna]I believe a global message WM_SYSCOMMAND with a SC_MONITORPOWER is sent when powersave is started.[/QUOTE]

I just tried that... odd, I could've sworn I tried it before and it didn't work. But in any case that makes coding this program a whole heck of a lot easier. :smile:

[QUOTE=lunna]The "randomly changes the screensaver": by a program or the user changes it himself? If the latter it would only be part of the options for this yet-not-written screensaver.[/QUOTE]

By a program I believe, but you can ask crash893 to be sure.

[QUOTE=lunna]Yes it was for writing a screensaver :wink:
Will try to find some good discussions why a screensaver solution would be bad... (off searching)[/QUOTE]

No need, I can tell you. Basically, Prime95 is designed to capture ALL SPARE cycles and not interfere with normal operations. A screensaver kind of goes against the point.

not to mention the prime95 screensaver is boreing as hell


when i said randomly changes his wallpaper i ment manualy althogh i think i have seen programs that will do it for you


is tehre anyway we could use the pre built ( run program even when useing laptop battery power) to fool it into not running and then prority 10 when we trick it into thinkits back on ac or something like that

[QUOTE=crash893]is tehre anyway we could use the pre built ( run program even when useing laptop battery power) to fool it into not running and then prority 10 when we trick it into thinkits back on ac or something like that[/QUOTE]

Maybe, but I'd rather not mess around with system settings and such. Plus that kind of eliminates this program as a possibility for people running it on laptops. I don't think we need to do that though; given that we now know we can detect when the monitor goes into powersave (and also when it comes out apparently, I coded another test app to make sure), if we can integrate the SOM script we're good to go.

any update?

It's nearly done but there's still one bug I haven't ironed out. It's weird. The SOM script won't execute when I'm executing it in real-time, but when I step through it during debugging, it works fine! Trying to determine what the problem is...

Okay, after some more work, I think the SOM script just isn't working when the screensaver is running. Danath, have you tested the script while the screensaver is running?

Boy all this stuff sounds quite complex! You sound like you guys know your way round a PC.....How's this for an idea..?

Why not design a screensaver that has a timer built in? It kicks in after 5 min but the timer kills it at 30min when the monitor powers off?

Is this possible, I know nothing about programming screensavers.....

Cheers, Mark

[QUOTE=Bundu]Boy all this stuff sounds quite complex! You sound like you guys know your way round a PC.....How's this for an idea..?

Why not design a screensaver that has a timer built in? It kicks in after 5 min but the timer kills it at 30min when the monitor powers off?

Is this possible, I know nothing about programming screensavers.....

Cheers, Mark[/QUOTE]

Part of the problem is that the user of the borged computer wants his computer to stay EXACTLY the way it is or he won't run Prime95, period. Killing the screensaver kicks the computer out of 'sleep' anyway, and I also know nothing about programming screensavers.

[QUOTE=Bundu]Boy all this stuff sounds quite complex! You sound like you guys know your way round a PC.....How's this for an idea..?

Why not design a screensaver that has a timer built in? It kicks in after 5 min but the timer kills it at 30min when the monitor powers off?

Is this possible, I know nothing about programming screensavers.....

Cheers, Mark[/QUOTE]

the reason being that you would have to use just 1 screen saver

the orgional insperation for the idea is my freind who enjoys the eyecandy of his new 9600 video card but also likes to help my team out

so i said there must be a way to kick prime into high gear when the montior goes into powersaver

Finally I have some spare time to post here.

[QUOTE]Okay, after some more work, I think the SOM script just isn't working when the screensaver is running. Danath, have you tested the script while the screensaver is running?[/QUOTE]
If you mean the script that changes the Prime95's priority (that I attached to one of my previous posts) - yes, it works also when the screensaver is running. Note that it might not work properly if there are other windows (besides the Prime95's window), the titles of which contain "Prime95" - I guess it's understood why. Also, you can remove the first line of the script (or change it to "Enabled"), to see the messages describing the errors that could appear while executing the script.

At some moment I realised that I was wrong when I said (in one of my previous posts - #54) that terminating the screensaver will wake up the monitor. My fault is that I tried it under Win95 only (yes, I was using also such an old OS at that time). I apologize for misleading you, I should've checked it on other OSes first. :redface: Win98/2000/XP have the screensaver/monitor power management functions implemented differently from Win95, so that terminating the screensaver (either by closing its window, or by killing its process) does not cause the monitor to exit the off-state, beginning with Win98 and above. Another correction of my words: the screensaver window's title is "Screen Saver" in Win95/98, but in Win2000/XP the title depends on the screensaver.

I plan to post here a solution soon...