| Personal background |
|---|
I was the owner of a small sign shop and a computer network service company in the middle of Michigan. We had several machines that run 24/7 with our files and design programs, and since they would be idle most of the time, we thought this would be a good use for the idle cpu's.
At the end of 2003, I was activated from my U.S. Army Reserve Unit in support of Operation Iraqi Freedom, which is also when the packets stop being returned.
I would have liked to have continued the seti@home, but since I was not @home, the military frowned on this, or other applications being ran on the systems...
Now that I have returned, the computers are being slowly fired up and the client updated to resume the project participation. |
| Thoughts about SETI and SETI@home |
|---|
We first saw seti@home when we bought a used dual PII-500 machine from a customer, which had an older seti@home client running on it. We let the cycles run out that he had loaded and then installed the new client with our name as the user. Since then, we put the client on all the machines that we add or replace.
I have joined the US Army Reserves grouping, since I am a proud member, it was not active, and I did not see a local Fire Fighting group to join...
|
| Your feedback on this profile |
|---|
| Recommend this profile for User of the Day: |
I like this profile |
| Alert administrators to an offensive profile: |
I do not like this profile |
|
|
