Don't think at this time we have a solution for your W98SE machine(s), where you have confirmed that later Windows OS versions happily run. Wait till BOINC 6 comes out using a different graphics set up. Screensavers, particular the 3D active once are demanding and considerable ram at times AND CPU cycles.

If you know BOINC interferes, hit the 60 minute snooze button or set BOINC to only run when mouse/keyboard have not been used say for 15 minutes. It will stop soon as the mouse is moved or keyboard operated.

Because of the many permutations in configurations and software combinations and different user practices it is why BOINC has these multiple set-up features to ensure that contributors can participate in pretty much any hardware/software combo, thus visit the Advanced Menu, Preferences screens and play with the settings, or abandon the idea.

Oh, UD advertised the slogan "Screensaver / Lifesaver". BOINC can be set to run only when a screensaver would be active, but without the screensaver.

AND, you did know that the order for it to work properly with screensaver is to make sure a certain sequence takes place:

1. BOINC to start computing resuming from busy/pause, say 5 minutes
2. Screensaver to start AFTER the computing has resumed, say 6 minutes
3. Display / Energy saving features not to start until after 1/2, say 15 minutes.

Finally, have you tried it with a blank screensaver?

If all drivers for video are up to snuff too, i think we've reached a point for the white towel to be thrown in the ring, but if reading PII, PIII's run by others successfully, it would be a pity to do that without trying a bit more.

ciao

The projects I've concentrated on are HCCancer and FAidsAH. If the issue is project-oriented, I'd be interested to hear about it.

The slower machine is still running. It generated an explorer.exe fault, unattended, some time overnight, which I cleared manually. The work unit appeared to be processing, regardless, and no messages are generated. I've never seen this fault on this machine, and never recovered so painlessly from the fault on other machines. Usually I'd expect to lose keyboard / mouse control of open GUIs, shortly thereafter. Not this time.....no GUIs were open.

Screensavers are dissabled, by default in these machines. The slow machine had no power saving functions enabled, not even the monitor's power saver. With simulators or crunchers accessed through a KVS, there's no point.

The 750mhZ PIII W98 2ed machine continues to process the work unit.

RL

I've rechecked the definition of graphical user interface (GUI) and window, and am pretty sure I'm using these terms correctly.

The use of 'window'ing may be one element of a GUI. The GUI is the combination of various elements and techniques used by a SW package to allow non-keyboard text-line interfacing to the user/operator. Others include drop-down menuing, keyboard and mouse response, 'help' menus, text spelling/replacement, linking etc.

When single program 'freezes' it may be unresponsive through it's particular GUI, while others remain responsive through their own. I think you must understand what I mean and will have experienced the effect in varying degrees.

I am not dealing with any hardware issues that were not present prior to conversion from UD to BOINC. If you are aware of hardware issues that are specifically BOINC-dependant, then perhaps these can be listed for the illumination of all users currently dealing with this same transition.

The same might be suggested for established OS issues that are BOINC-dependant. Somebody must be keeping track somewhere, or there wouldn't be a point to rev6.

Slower system still crunching away.

RL

Hey there.

Just another update on my situation. I just noticed that Spinhenge.com is using my processor sometimes up to 99%, causing my system to stop responding. So might I suggest that there might be a problem with this projects implementation? Anyway, I removed this project, and now I can use the system again.

Cheers,
Jan-Willem

Burping cow! After I posted my previous post, I added climateprediction and guess what? I had to reboot twice since that. So I guess I found the real culprit. I'll report to them, and thanks for all the support here.

Cheers,
Jan-Willem