Argh, this really needs to be mentioned in an FAQ somewhere:
You must reboot after installing the client for the first time for it to create a registry key needed for it to resume work. If you don't, next time you reboot it'll pick up a new test. No worries if you didn't, though, it's a
2 minute process to instruct the client to continue working on the old test. You haven't lost any work.
AT used to be top of the project for quite a while, then most of the team seems to have lost interest at about the same time as TPR picked up the pace and blew us out of the water. At the moment we're operating at about 60M cEMs/s, down from our high of about 120M. TPR on the other hand is operating at anything up to 500M cEMs/s. The reason the posts have disappeared is that team leader Confused seems to have gone seriously AWOL, with no production or posts for many months now. We're still hanging in there though.
SOB's GUI is hardly a GUI - it's just one progress bar. Any kind of performance hit would be absolutely miniscule, and personally I think it's far more convenient than a CLI. The setup process is an absolute breeze compared to SETI, for example.
MechEng, I have no idea what could have caused your problem other than an unstable install or machine. I have never heard of a similar symptom from anyone else and it's quite mind boggling that you were able to produce it on two separate machines. I'd suggest posting on the project forums, but if as you say you don't really care about fixing it, don't worry about it.
In conclusion we need all the help we can get! The performance gap sounds enormous, but a fast P4 will do 3M cEM/s and even a Celeron will do 2m cEMs/s. The client uses virtually no bandwidth at all, is fully operable with no internet access thanks to Ken_g6's SBQueue, and runs on pretty much any OS you can imagine but Mac
Do give it a go if you can, especially with TAS invading this month. We could seriously make a mark
