http://slashdot.org/article.pl?sid=03/10/15/0815228
Worth reading... interesting comment here I think you guys should consider (who have boxes that do nothing but seti with their HDD when 'idle'):
"I did something similar too. I didn't like the hard drive constantly running so I ran the executable off of a network share at work so my home computer wouldn't get its drive hit. "
That'd be pretty easy to set up... just map one server drive on all your clients and make the service on your machine point to 's:\seti1\seticli.exe'... then the next to 's:\seti2\seticli.exe, etc...
Or with setidriver, put a shortcut in the startup folder to 's:\sd1\setidriver.exe', 's:\sd1\setidriver.exe', etc.
I think I'm gonna do this on the work machines (My home machines are mostly using the HDD's all the time anyway).
Worth reading... interesting comment here I think you guys should consider (who have boxes that do nothing but seti with their HDD when 'idle'):
"I did something similar too. I didn't like the hard drive constantly running so I ran the executable off of a network share at work so my home computer wouldn't get its drive hit. "
That'd be pretty easy to set up... just map one server drive on all your clients and make the service on your machine point to 's:\seti1\seticli.exe'... then the next to 's:\seti2\seticli.exe, etc...
Or with setidriver, put a shortcut in the startup folder to 's:\sd1\setidriver.exe', 's:\sd1\setidriver.exe', etc.
I think I'm gonna do this on the work machines (My home machines are mostly using the HDD's all the time anyway).