Okay, there seems to be alot of confusion.. Maybe i can explain it better than epix.
Back in the good old days, we went around to the computer labs on campus, and manually loaded setidriver on every PC. When the lab consultants (i'm one of them. hehe) decide that a PC is acting up or is too full of non-supported programs (aim, yahoo, etc), he/she will Image the computer to the original state. When the computers got imaged, we lost alot of partially done WUs, which was a big pain.
We then decided to use a server on the network to store all of the seti clc and driver files. We login to that computer over the network, and start it up. All of the files reside on the server, but the actual processes are taking place on the computer lab machines. Again, this is so we won't lose WU's when the computer got imaged.
Then the bandwidth problems hit.
We decied to run setiqueue so we can have a buffer between us and Berkeley. This would also run on the same machine where all of the CLC files were residing. But in addition to the bandwidth problem, the lab staff was closing seti, because of the icon in the system tray. We experimented a bit and found a program called rundhide, which "hides" the clc client. It shows up in processes as "System Resources" and we renamed the clc client to "rundll.exe" so that people wouldn't be the wiser if they saw it running.
All in all, this setup worked, until we decided to hit hard. The server is a pentium 120 with 32 mb ram. From running setiqueue AND having all of the clients connect to this server, it performed well. We tried to upgrade the ram recently, but it wasn't working too well with the ram. We're going to try a fresh install here in a bit, but we'll see.
I hope that helps everyone understand what's going on.
update: As for the actual bandwith usage, it's neglegible. We have a gigabit backbone with a 10 mbps connection for the server. it works fine in that respect.
Back in the good old days, we went around to the computer labs on campus, and manually loaded setidriver on every PC. When the lab consultants (i'm one of them. hehe) decide that a PC is acting up or is too full of non-supported programs (aim, yahoo, etc), he/she will Image the computer to the original state. When the computers got imaged, we lost alot of partially done WUs, which was a big pain.
We then decided to use a server on the network to store all of the seti clc and driver files. We login to that computer over the network, and start it up. All of the files reside on the server, but the actual processes are taking place on the computer lab machines. Again, this is so we won't lose WU's when the computer got imaged.
Then the bandwidth problems hit.
We decied to run setiqueue so we can have a buffer between us and Berkeley. This would also run on the same machine where all of the CLC files were residing. But in addition to the bandwidth problem, the lab staff was closing seti, because of the icon in the system tray. We experimented a bit and found a program called rundhide, which "hides" the clc client. It shows up in processes as "System Resources" and we renamed the clc client to "rundll.exe" so that people wouldn't be the wiser if they saw it running.
All in all, this setup worked, until we decided to hit hard. The server is a pentium 120 with 32 mb ram. From running setiqueue AND having all of the clients connect to this server, it performed well. We tried to upgrade the ram recently, but it wasn't working too well with the ram. We're going to try a fresh install here in a bit, but we'll see.
I hope that helps everyone understand what's going on.
update: As for the actual bandwith usage, it's neglegible. We have a gigabit backbone with a 10 mbps connection for the server. it works fine in that respect.
