THGC Needs You -Team 40051

Page 77 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Toggle sidebar Toggle sidebar
The SMP client has been in the same version since I started using it in January. When your client expires, just download whatever is available at the time and use it for the next two months. I've run into that situation at least once before.

I was expecting a new version last month, as there was a note about the coming version 6 on the folding@home news page.

3/29/2007 Major stats overhaul: Monday April 2
We are going to take the stats down for several hours at 10am pacific time on Monday April 2 (this coming Monday). We need to make updates to the stats system for v6 and test that these updates are working. When we go back on-line, we will hopefully have the upgdraded stats working and would then be ready to launch v6.
Click to expand...
 
Completely off track question. How can I send WU's manually? I've a queue of 4 WU's on each core that have backed up and aren't being sent because the server keeps returning Error 503. It is becoming rather annoying, I am missing about 2k points lol.
 
G'day,

Error 503 indicates that the F@H server is busy. Try stopping then restarting teh F@H client several times until the work unit is sent. Otherwise Look at the F@H Forum page to see if F@H servers are having any problems. The forum can be found at the link below:http://forum.folding-community.org/

Currently F@H isn't having problems with their servers. I found that I had lots of 503 errors if I turned on the large memory option in the client. Try turning that option off and see if your units get sent more frequently.

You can test the conenction to the servers by using the following URLs, Thse may change depending on what work unit server you are assigned to:
http://171.65.103.162:8080/ ?
http://171.65.103.162/


Cheers
Lyall
 
Same here, with XP updates. I have my updates set to install only once I give the okay, so I'm aware that the computer is going to nag at me until I give it the reboot. I find this feature more annoying when I'm actually working. I want my work machine to be as up-to-date and secure as possible, so updates are automatic (or was it the admins that set that up?). Anyway, sometimes I need to leave the computer crunching numbers for a while, and before I do that I have to make sure it's not going to be rebooting itself.

I don't know why they went with this design. What are the reasons for not just letting you know you need to reboot once, and leaving it at that? Anyway, I'm sure this particular topic could be a separate thread if we really want to delve into it.
 
Ah I think that is what is f***in with my damn gaming computer. I didn't think they did it to XP but now that you mention it it explains alot of issues. My computer can't restart, the BIOS locks up and doesn't POST correctly (no one knows why). When I got back after going home for 5 days my computer was locked up and had a dead USB bus.... I blame Bill. As soon as I turned it off and back on again it was working.

So these auto reboots really screw me over... I really don't like them. 🙁

I can just see a late night of gaming and BAM my comp reboots bc Bill decided it needed to. 8O

Edit: it is taking me 60 sec to post once I hit the submit button, but every other website works perfectly... damn forumz.
 
If you have any non-gaming computers running folding@home, you might consider using a different OS than Windows to avoid "BIll" if you're unhappy with the product. My only folding machine that's using windows is a laptop, and that's only because it's a 32-bit part (Yonah) and the SMP client for 32-bit hasn't come out for Linux yet.
 
supposing you use the console version (you say 2 cores, so that's why i assume it):

the true manual way... open command prompt (start-->run-->cmd) and go to the directory where folding at home is and then type in "FAH504-console.exe -queueinfo" or whatever your client is called and -queueinfo after it

if it says something about a conflict, ignore it and try again, should go away

type "fah504-console.exe -send xx (-verbosity 9)" where fah504... is your console again... and verbosity 9 is optional (without the brackets)... simple as that, if it still doesn't go, then there's something with your network or stanford is having problems
 
@Ara
The send xx flag is great. You beat me to it.

@Rest
If you don't want the machine to automatically restart then thurn that off (I have auto updates set to download updates and they only update when I do it manually). Even when I do that it doesn't restart until I click okay.
 
Alright 1 WU went through, the rest got errors.

FAH Queue Log WU 01 [Core 1]



FAH Queue Log WU 04 [Core 1]



FAH Queue Log WU 05 [Core 1]



FAH 2 Queue Log WU 01 [Core 2]



I guess the server just hates me. I tested the server address and it says "OK" so should I clear out the queue?

Config is set to use IE settings and generally works, it is just these particular WU's for some reason. I actually just sent one in a few hours ago.

Thank you for the "-send XX" advice. 😀
 
I'm actually really enjoying thouse 1760's. They actually go faster for me than the 1500 point ones. I think that is project 2604 that goes really well. 2605 still gives me a good PPD but not as good.
 
I'll look out for it. Thanks. Right now I only have one SMP machine going.

I have folding running on 2 other machines that have Dual Cores (my borothers and my grand mothers) but neither one will handle watching the SMP console and restarting if progrerss stops or making sure it is always up (not closing the console, or restarting it if they do).

When the SMP comes out of Beta or gets ready to work as a service I will set them up with it.

The other issue is that they have Vista. I know that the SMP client can run on Vista but I have not yet been able to get it working.
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom