KWSN Orbiting Fortress

[JerWA]

For anyone that's curious 6.6.37 and 6.6.38 are no better behaved than 6.6.36. I didn't test .37 much, but .38 has debt issues and tries to run multiple instances of MW which doesn't work/help (i.e. it pauses CPU tasks and tries to run 9 or more MW WUs at once, ignoring all app settings). And it still has the progress bug where MW units marked "Running" that aren't actually getting any resources still increment their run timers, so the manager thinks they're all going to take hours to finish.

Ran 6.6.20 for the last 2 days and found it to be too unpredictable. It tried to keep MW running but rarely let more than 1 MW WU run at a time, ignoring all app settings.

Still having the most luck with 6.4.7 and a script to reset debts.

Officially unofficial there will be no inbuilt ATI support until 6.10 or 6.12, around the end of the year. But, given their current problems with inbuilt CUDA support, that may not really help much.

The admin for MilkyWay said they're looking into the "non CPU intensive" flag to see if it can be faked client side, since the current implementation only allows project-wide use (i.e. would include marking the CPU apps which would break things).
_________________

Stats: [BOINC Synergy] - [Free-DC] - [MundayWeb] - [Netsoft] - [All Project Stats]