I have my WinXP computer configured for powering off the dual monitors after 2 hours of inactivity, whereas BAM is configured for running its screen saver after 15 minutes. Unless I suspend BAM, my monitors will not turn off.

Please advise ...
TIA & Holidays' Cheerios

WinXP (SP2)
Radeon X300 display card
DELL flat panel & Mitsu DP920 CRT

---

If it's a problem with BAM!, report it at the BAM! forums.
BAM! is a 3rd party BOINC Account Manager option.
Any problems with it should best be asked about/reported there.

If you suspect it is a BOINC problem, please tell which BOINC version you use.

---

...

If you suspect it is a BOINC problem, please tell which BOINC version you use.

Thanx for your response! Sorry ... my confusion. I thought BOINC was the account manager(?)

In any case, my version of BOINC is 5.4.11

cheerios :)

---

BOINC is the managing software for all the projects you attach to. The Boinc Manager (GUI) is a graphical tool to help you 'program' BOINC.

A Boinc Account Manager is as I said a 3rd party site through which you can setup your preferences for one or more projects at once. So you don't have to do so through the project's web-space.

Now then, with that out of the way, your monitor problems.
I understand that if you suspend BOINC, that your monitor will power down at the end of the timeout?

When you're working with BOINC, is it set to run always, or only when your computer is idle? And is that videocard really a card, or an embedded videochip on the motherboard?

You have installed the latest drivers for your videocard and if appropriate for your monitor?

---

...
I understand that if you suspend BOINC, that your monitor will power down at the end of the timeout?

Yes ... all is normal, and between the time the screensaver is enabled and when the monitors are supposed to power down, I see the "bouncing BOINC".

When you're working with BOINC, is it set to run always, or only when your computer is idle? And is that videocard really a card, or an embedded videochip on the motherboard?

I have it set to 'Activity=>Run based on preferences" ... without knowing what the preferences are. BOINC provides "Advanced=>Options" but I don't see screensaver options.

However, the screensaver setup offers "settings", for which "go to blank screen" was disabled, and "minutes until blank" set for 5 minutes. I will try enabling the "blank screen" and see what happens.

You have installed the latest drivers for your videocard and if appropriate for your monitor?

Yes ... It's up to date (according to Dell's support).

---

...
I understand that if you suspend BOINC, that your monitor will power down at the end of the timeout?

Yes ... all is normal, and between the time the screensaver is enabled and when the monitors are supposed to power down, I see the "bouncing BOINC".

When you're working with BOINC, is it set to run always, or only when your computer is idle? And is that videocard really a card, or an embedded videochip on the motherboard?

I have it set to 'Activity=>Run based on preferences" ... without knowing what the preferences are. BOINC provides "Advanced=>Options" but I don't see screensaver options.

However, the screensaver setup offers "settings", for which "go to blank screen" was disabled, and "minutes until blank" set for 5 minutes. I will try enabling the "blank screen" and see what happens.

You have installed the latest drivers for your videocard and if appropriate for your monitor?

Yes ... It's up to date (according to Dell's support).

Yes, change the screen saver to "blank screen". There is no point in running the BOINC screen saver. It just slows down the crunching (and breaks the PC if you are (still) running W98). You can easily do that from the desktop properties.

And why not set it to "run always" while you are at it. It will only run when there are no higher priority tasks, so it won't degrade performance when you are running applications.

---

...
However, the screensaver setup offers "settings", for which "go to blank screen" was disabled, and "minutes until blank" set for 5 minutes. I will try enabling the "blank screen" and see what happens.

Enabling "go to blank screen" apparently worked ...

---