Personal computing discussed
Moderators: renee, farmpuma, just brew it!
Geatian wrote:Looks like the 6.22 SMP Beta client expired on Feb 2nd. Change the date on your computer to before that and it should start fine. It would be nice if they released a new client now, but I don't see one on their official download page yet.
Edit: Oh wait, scratch that. Here's SMP Beta client 6.23: http://www.stanford.edu/~kasson/folding ... 32-x86.exe
Not sure what is changed besides a new expiration date, though.
jeffry55 wrote:The only 6.23 folding client I saw at the website is the Windows console "standard" folding client. The Windows SMP is still a Beta version 6.22 which expires today.
jeffry55 wrote:I was thinking the binary file was something that changed the expiration date of the 6.22 SMP client to allow it to continue to run.
lou15214 wrote:If you're using VISTA, right click on the downloaded 6.23 file and check file properties to see if it says that the file came from another computer, give it the appropriate permission and try re-installing.
ReAp3r-G wrote:I'm testing out my system stability at the moment, once the client is up to speed I'll move it over for UGN to use
ReAp3r-G wrote:Apparently a simple restart was all it took to reset the installing error and I'm back into production
Thanks for the concern Fox
I'm testing out my system stability at the moment, once the client is up to speed I'll move it over for UGN to use
Flying Fox wrote:Keep an eye on the production. We don't want the SMP client to impact the GPU client too much after all.
ReAp3r-G wrote:Other days i'd get somewhere above 2500 PPD...both clients are set to use 100% CPU but when I take a look at the CPU usage using the Task Manager and Vista sidebar gadget it's only using 50% actual CPU cycles, so i don't think they're interfering with one another
Flying Fox wrote:Sounds odd. 50% use in Task Manager means only one core is used (I'm assuming we are talking about the E4400 in your sig). Are you running with the -smp switch?
ReAp3r-G wrote:Flying Fox wrote:Sounds odd. 50% use in Task Manager means only one core is used (I'm assuming we are talking about the E4400 in your sig). Are you running with the -smp switch?
great...
Do I have to wait for the currently running work unit to finish before I input that switch line?
Flying Fox wrote:If you don't want to trash it, relaunch it with -oneunit so that it quits after finish thing. Then you can use a different command line. The 6.23 beta -configonly mode gives you the ability to input "default" parameters on the command line so you can put -smp there. I do the same and leave -oneunit for myself from time to time when I know I won't be folding in the following day or so.
What's the ppd just folding the GPU client alone?
ReAp3r-G wrote:It should be ok. Idle is the lowest you can set. You can confirm by looking at Task Manager. Right click on the EXE themselves, move to Set Priority and you will see what the current priority the process is being run at.Oh and another thing, I've already set my priority in the GPU client to slightly higher...should I change the core priority in the SMP client as well? It's set at the default value of [idle]...that should be OK right?
ReAp3r-G wrote:I just noticed the start time of my SMP client and it's been over an hour and it hasn't increased 1% yet
Very very odd...but one good thing is that the system appears to be stable...hasn't crashed since the client got started on the WU it grabbed at 15:06 GMT