It replaces the System Idle Proccess with its own, and uses that to do calculations on workunits. It runs a "Low" priority, so when something else needs the processing power, it will just slow down and let that process use it.
You should install something like a "Work unit server" on your machine, download ~500 units @ a time, have everyone install it, and have Team "OpnNetwk".
It replaces the System Idle Proccess with its own, and uses that to do calculations on workunits. It runs a "Low" priority, so when something else needs the processing power, it will just slow down and let that process use it.
You should install something like a "Work unit server" on your machine, download ~500 units @ a time, have everyone install it, and have Team "OpnNetwk".
No, it was before the service... I just started running it as a service YESTERDAY. It was the command line at the time, then I moved to the GUI and would just exit it I thought it would get really hot.
Something wasn't right there... I still think that Team OpnNetwk would be fun there. Maybe if he ran it only as a work unit dispensing server, if that's possible...
Comments
Yea, 48C isn't anywhere worrying area, mine average 50 - 55, spiking to 65C sometimes.
~Duff
Mine is always like 15-20%
-Q
SETI@home closed:
-Q
You should install something like a "Work unit server" on your machine, download ~500 units @ a time, have everyone install it, and have Team "OpnNetwk".
-Q
SETI@home would KILL his under-cooled CPU...
OR just use it as a WUS
OR Use MBM5 + The Spy...
-Q
I did, i set it to stop at 65*C.... it didnt stop
-Q
-Q
-Q
Others are even worse than mine.