• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Graphical Client Crashes after finishing WU

C

chileman

Gawd
Joined
Jun 15, 2004
Messages
793
Ok, I'll admit I'm new to F@H, but I'm pretty pumped about it. I've got my 3 machines working on it and using EMIII to monitor it. Anyway, I run the graphical client cause I like to watch the pretty picures. But every time I finish a WU the program crashes (get a MS error report screen). Below are my 3 machines.

2100+ 768mb GForce 6600GT (XP Pro SP2)
2 GHZ P4 Mobile 512mb Radeon 7500 (XP Pro SP 2)
1 GHZ Celeron 384mb Radeon 7200 (XP Pro)

All my machines do it, and it really sucks when they finish a WU while I sleep aren't doing anything the rest of the night until I can restart the app. I know some of you will just tell me to run the console, but I'd rather not. Maybe there is an answer looking me in the face I missed in the forums.

Any help would be appricaited!

 
have you tried displaying the protein in ball and stick configuration? Next make sure the client is minimised. It is a known issue.

If probelm still persists, I recommend you move to console. There is a monitoring program called Electron Microscope 3 that also displays the protein for you.

Good luck and welcome to the [H]orde. :)
 
I do leave the display up 24/7 on most of the machines just for show. I do use EMIII. Maybe I'll just have to minamize the clients. And I'll change it from random to ball and stick.

 
remember, you waste CPU cycles displaying the protein, so keep it minimised and you get done with the proteins faster.
 
i installed it on my computer 8 months ago or something.. and keep it minimized to the tray and it works fine.. sometimes i crash explorer and the system tray icon dissappears.. but i only click on it once a month anyways.. no reason too..

also.. i had the console version on a celeron @ 1.13ghz.. and it took 10 times longer to do a wu than my xp-m @ 2 ish ghz...
 
scottatwittenberg said:
i installed it on my computer 8 months ago or something.. and keep it minimized to the tray and it works fine.. sometimes i crash explorer and the system tray icon dissappears.. but i only click on it once a month anyways.. no reason too..

also.. i had the console version on a celeron @ 1.13ghz.. and it took 10 times longer to do a wu than my xp-m @ 2 ish ghz...
Click to expand...
well, that depends on several things: RAM, the protein (how hard it is), the type (gromacs, tinker), and , of course, GHz = t3h important in folding, so that's understandable...

but, the console version *is* faster than the graphical version. by a good deal. (at least on my pII it made a huge difference)

 
I think you guys have convinced me to switch to the console version. I'll do it as soon as they finish the WU they currently have. 2 of the 3 have 2500frame Gromacs that should be spit out in about a day. Thanks guys.

 
chileman said:
I think you guys have convinced me to switch to the console version. I'll do it as soon as they finish the WU they currently have. 2 of the 3 have 2500frame Gromacs that should be spit out in about a day. Thanks guys.
Click to expand...
good choice :)

we need to outproduce the Aussies!

 
chileman said:
I think you guys have convinced me to switch to the console version. I'll do it as soon as they finish the WU they currently have. 2 of the 3 have 2500frame Gromacs that should be spit out in about a day. Thanks guys.

Click to expand...

I am glad you have decided to switch. I have never used the graphical which means I have only used the console and I have never had any problems with it.

That said, I'm not sure everything the graphical can do but between using the -configonly switch with the console and EMIII I don't think there is anything the graphical can do that the combination of those two can't. The main reason I have seen that most people want to use the graphical is to watch the protein draw as it is being worked. EMIII can also do this. (although I have it turned off since I like to save as many cycles as I can.)

 
Ok, I went ahead and made the switch, I copied the "work" folder from the graphical client into a new folder with the console version, reshared the folders and EMIII is giving time estimates of about 1/2 of what it was giving with the graphical client. I think [H] needs to do a review of each client and see which is faster. Take the same work load and precess it with the same machine and make graphs and everything, then put that information on the [H] F@H site so when new users (like me) come by they know the difference! Maybe this has already be done.
 
i think most of us just (rightly) assume the console is faster

we'd do the tests, if it weren't for the fact that it could risk us folding slower, and that risks a faster OCAU overtake ;)

 
You'll also want to add -forceasm to the registry entry, if you search for this you should find a lot of relevant threads. This is most of the reason the console client is faster, unless I miss my guess.
 
You must log in or register to reply here.
Back
Top