- Aug 27, 2002
- 6,790
- 23
- 81
I know most of you knew this, but for those of you who didn't (like me) and you new guys, the CLI kicks the GUI's butt!!!
For my test I used the benchmark wu from http://www.teamlambchop.com/bench/benchfile.htm
On my AMD 2600 with Win2k sp4, SETI GUI 3.08 & SETI CLI 3.03, it took the SETI GUI 3 hr 41 min to finish the wu, with the SETI CLI it only took 2 hr 36 min!!! That's more than an hour faster...
To setup the CLI: http://www.gygabite.com/smokeball/sigline.htm
& the new version of SetiDriver: http://www.wakeassoc.com/SETIDriver/
(thanx to Confused for the links!!!)
For my test I used the benchmark wu from http://www.teamlambchop.com/bench/benchfile.htm
On my AMD 2600 with Win2k sp4, SETI GUI 3.08 & SETI CLI 3.03, it took the SETI GUI 3 hr 41 min to finish the wu, with the SETI CLI it only took 2 hr 36 min!!! That's more than an hour faster...
To setup the CLI: http://www.gygabite.com/smokeball/sigline.htm
& the new version of SetiDriver: http://www.wakeassoc.com/SETIDriver/
(thanx to Confused for the links!!!)