• 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.

New GPU Client 6.20

Thanks, was looking on FCF and somehow missed that.

 
The existing client will continue to work correctly until restarted correct? I hope so, I'm going out of town for the weekend and am leaving straight from work. Wouldn't want my dual 9800gtx rig to be inactive all weekend.
 
tkam said:
The existing client will continue to work correctly until restarted correct? I hope so, I'm going out of town for the weekend and am leaving straight from work. Wouldn't want my dual 9800gtx rig to be inactive all weekend.
Click to expand...

Yes, that's correct.
 
More info! I can only do so much on my smart phone.
 
August 01, 2008
New clients are out (6.20)
We've released new clients (v 6.20). I'll post a more detailed update shortly, but I wanted to get the word out. For those running GPU clients (or other clients with an expiration deadline of August 2), please check these clients out.
Click to expand...

See above quoted from folding.stanford.edu
 
Appears to be two varieties of client

1. standard sys tray
2. service install variety

 
Oh, joy. :rolleyes:
Hopefully written by a different developer than the SMP fiasco.
We may have zero stable clients come Monday.
 
relic said:
Oh, joy. :rolleyes:
Hopefully written by a different developer than the SMP fiasco.
We may have zero stable clients come Monday.
Click to expand...

This one is done by a brand new programmer (uncle_fungus) and hopefully passed a few cycles of closed beta testing unlike the SMP client.

 
There's also a separation between Vista and XP console clients. I went with the Vista console client for now, so far so good.

 
IcedEmotion said:
There's also a separation between Vista and XP clients. I went with the Vista console client for now.

Click to expand...

If you use the systray version, there is no separation between Vista and XP but for the console version, there is one so be careful indeed.

I also updated the GPU2 guide with the new link.

 
We've released new clients (v 6.20). For those running GPU clients (or other clients with an expiration deadline of August 2), please check these clients out.

Here's what's new in the 6.20 client.

* Added Forums to systray menu.
* Support cpu affinity by default, this is related to an nVidia problem and awaits core-side changes.
* Add additional parameters field in advanced preferences - no more shortcut editing!!!
* UNSTABLE_MACHINE count reset after a correctly finished WU, for long-running systems
* Open configuration dialog box when invalid settings detected
* Fixed core launch directory which caused auto-upgrades to fail if core was present in "Program Files"
* Added additional advanced config options to console clients
* Added MachineID selector in systray gui
* Client shows PRCG on results upload
* Passkey now validated for hex content
* Moved service installation to advanced config to prevent inadvertant use
* Log date and time when automatically attempting to upload results.
* Correctly restore system tray icon when shell (explorer.exe) crashes
* Significantly improved queueinfo
* Multiple copies of the client can no longer be started with the same "start in" dir
* Automatically increase packet limit to max size for results that are too large
* Failed uploads will be attempted again using alternative upload port (8080->80 and 80->8080)
* Removed spurious "benchmarking..." messages
* Added extra_parms support to console clients
* Extra parameters are validated at configuration and launch time. Invalid settings will force reconfiguration
* Fixed and updated service installation to allow use of working directories
* Added ATI FireStream 9170 detection
* Compressed Vista icon to reduce size of executable (saves ~ 200kb)
* Updated MyFolding.html to match folding.stanford.edu style
Click to expand...

The full skimmy!

 
Xilikon said:
This one is done by a brand new programmer (uncle_fungus) and hopefully passed a few cycles of closed beta testing unlike the SMP client.

Click to expand...

I hear it gives a 20% boost in PPD but ONLY in FahMon... :rolleyes:;) (Just kidding for anyone not familiar w/Fahmon. Written by the same guy?)

relic said:
We may have zero stable clients come Monday.
Click to expand...

Or sooner depending on how soon ya upgrade. ;)

Snagged all available clients and will be upgrading 2 as soon as the current WUs finish. Looks like a deinstall/reinstall for the systray clients I've been running.

Thanks Sunin and Xil!!

 
The new client has worked without problems so far on a 9800gtx, 2x 8800gt and 8800gts 640. I hope it stays that way through the weekend (going out of town)....


 
OK...I must be a glutten for punishment, I just loaded 6.20 on one of the 8800GTs.
I need a different hobby. ;)
 
Single GPU client boxen won the race so it got upgraded first. Deinstall/reinstall of the systray client in XP32 went smooth and no issues so far in the 40 minutes it's been running.

Dual client boxen has about 20 minutes to go on it's last WU and it's going under the knife as well. The upgrade looks pretty painless so far. *crosses fingers*

 
You don't need to wait for WU's to finish the new version will pick up your existing WU just fine.
 
Does the new client require the same installation procedure for two GPUs as the older client?

 
APOLLO said:
Does the new client require the same installation procedure for two GPUs as the older client?

Click to expand...

Yes. I backed up all 3 of the GPU folders, uninstalled, installed the new systray client and checked my shortcuts to make sure it was good. Both GPUs started and are running fine.

If you're running the console clients, I think it's easier as it looks to be a drop-in replacement executable.

 
With the outgoing version, I could game and just take a large performance hit on the gpu client. With the latest version, I'm bsoding right away when I try to play a game.
 
nomad8u said:
Yes. I backed up all 3 of the GPU folders, uninstalled, installed the new systray client and checked my shortcuts to make sure it was good. Both GPUs started and are running fine.

If you're running the console clients, I think it's easier as it looks to be a drop-in replacement executable.
Click to expand...
I didn't even know there was a console version. I'm currently using the sys-tray client. :confused:
 
I need to hire someone to come and switch over all my clients this weekend this is getting stupid.
 
APOLLO said:
I didn't even know there was a console version. I'm currently using the sys-tray version. :confused:
Click to expand...

Yessir. I've only run the systray version as it keeps me from having to run tray-it or something similar on my "daily driver" machine and it's easy to change simple config items. When I get my "folding only" rig running Vista64, I may switch to the console version and see if there's any difference speed wise. Shouldn't be if not farting around with the viewer in the systray version.

Have a single and a dual client setup running for almost 4 hours now without a hitch. Speed wise I don't see any improvement, but I do see less dips in the 2 clients on my daily driver rig while surfing and checking email. But I haven't gamed with it yet so no idea if theres any difference there in my case. So from my observations (on my setup anyway) it looks like some optimizations may have been done. Or not... could be my imagination. It seems to be running smooth though.

 
For those wondering if the new client make a difference in terms of performance, it shouldn't since this is more dependent on the core, not the client. Optimizations should come later.

 
general optimizations? or specific for nvida or ATI?

I'm loving my 8K ppd on my 280GTX, and an extra 4500 from my 8800GTS on my mediabox.... but will be happy with any extra "free" performance.
 
No performance difference.

For single gpu installs just uninstall the old client and re-install the new.
For multi gpu installs uninstall your first installation of the gpu just like single gpu installs.

For your 2nd, 3rd or 4th installations
1. Delete everything under your User name (related to the GPU client) for my vista install it was this:
C:\Users\David\AppData\Roaming\Folding@home-gpu2
EXCEPT your Work directory with all of its content, queue.dat, unitinfo, Fahlog and MyFolding.
Make sure to delete the following
the FahCore_11
amdcalcl.dll
amdcalrt.dll
cudart.dll
client.cfg
2. Find your GPU Client directory under your program directory for my vista install it was
C:\Program Files (x86)\Folding@home\Folding@home-gpu2
and delete the entire directory.

Now intsall the GPU client as you normally would

3. Copy from the new install directory for vista mine was:
C:\Users\David\AppData\Roaming\Folding@home-gpu
Copy the following files: amdcalcl.dll, amdcalrt.dll, cudart.dll, and Fahcore_11 (if it exists, generally does not) into:
C:\Users\David\AppData\Roaming\Folding@home-gpu2

4. Now go under programs and for me under vista it was:
C:\Program Files (x86)\Folding@home\Folding@home-gpu
Copy the entire folder and paste it in C:\Program Files (x86)\Folding@home\
Rename the directory in vista it was called: Folding@home-gpu - Copy
to Folding@home-gpu2

5. If you kept your shortcuts on your desktop, which you should have since I never said delete those you should now be able to fire up both clients. (gpu1 and gpu2, etc)

6. It should go into a config screen for each client and make sure you assign them different machine IDs, etc just like you did when you originally set them up. Note you no longer have to edit the config file to change that. You now have the optionon the last tab at the very bottom to set Machine ID in the config screens!! I generally set >10M yes, Core Priority to Slightly Higher, Saves to 30minutes and check the box to not lock to specific core.

7. After you fill in the needed info in and check the correct boxes your set to go.

8. Troubleshooting: Note when I did this the servers were having issues and only one of my clients was able to download the new 1.08 FahCore_11.exe. So I closed both gpu clients down and manually copied the client to the 2nd directory.


I'll post this over in the gpu config section as well since the Multi GPU upgrade process is a hair trickier!


 
I know I screwed up the install of the SMP last night, but I thought I got the GPU right. This morning, its not going. Is it a work server issue? Here is a bit of my log when I woke up this morning.


Code: 
[10:52:42]   Could not transmit unit 04 to Collection server; keeping in queue.
[10:52:42] - Preparing to get new work unit...
[10:52:42] + Attempting to get work packet
[10:52:42] - Connecting to assignment server
[10:52:42] - Successful: assigned to (171.64.65.106).
[10:52:42] + News From Folding@Home: GPU folding beta
[10:52:42] Loaded queue successfully.
[10:52:43] + Closed connections
[10:52:48] 
[10:52:48] + Processing work unit
[10:52:48] Core required: FahCore_11.exe
[10:52:48] Core found.
[10:52:48] Working on queue slot 09 [August 2 10:52:48 UTC]
[10:52:48] + Working ...
[10:52:49] 
[10:52:49] *------------------------------*
[10:52:49] Folding@Home GPU Core - Beta
[10:52:49] Version 1.08 (Tue Jul 22 08:24:14 PDT 2008)
[10:52:49] 
[10:52:49] Compiler  : cl: Command not found.
[10:52:49] Build host: user-f6d030f24f
[10:52:49] Preparing to commence simulation
[10:52:49] - Looking at optimizations...
[10:52:49] - Created dyn
[10:52:49] - Files status OK
[10:52:49] Need version 109
[10:52:49] Error: Work unit read from disk is invalid
[10:52:49] 
[10:52:49] Folding@home Core Shutdown: CORE_OUTDATED
[10:52:53] CoreStatus = 6E (110)
[10:52:53] + Core out of date. Auto updating...
[10:52:53] - Attempting to download new core...
[10:52:53] + Downloading new core: FahCore_11.exe
[10:52:53] + 10240 bytes downloaded
[10:52:53] + 20480 bytes downloaded
[10:52:54] + 30720 bytes downloaded
*************(downloading suppressed by wheresatom)************
[10:52:55] + 593920 bytes downloaded
[10:52:55] + 604160 bytes downloaded
[10:52:55] + 614400 bytes downloaded
[10:52:55] + 624640 bytes downloaded
[10:52:55] + 634880 bytes downloaded
[10:52:55] + 639010 bytes downloaded
[10:52:55] Verifying core Core_11.fah...
[10:52:55] Signature is VALID
[10:52:55] 
[10:52:55] Trying to unzip core FahCore_11.exe
[10:52:56] Decompressed FahCore_11.exe (1830912 bytes) successfully
[10:53:01] + Core successfully engaged
[10:53:06] 
[10:53:06] + Processing work unit
[10:53:06] Core required: FahCore_11.exe
[10:53:06] Core found.
[10:53:06] Working on queue slot 09 [August 2 10:53:06 UTC]
[10:53:06] + Working ...
[10:53:06] 
[10:53:06] *------------------------------*
[10:53:06] Folding@Home GPU Core - Beta
[10:53:06] Version 1.08 (Tue Jul 22 08:24:14 PDT 2008)
[10:53:06] 
[10:53:06] Compiler  : cl: Command not found.
[10:53:06] Build host: user-f6d030f24f
[10:53:06] Preparing to commence simulation
[10:53:06] - Looking at optimizations...
[10:53:06] - Created dyn
[10:53:06] - Files status OK
[10:53:06] Need version 109
[10:53:06] Error: Work unit read from disk is invalid
[10:53:06] 
[10:53:06] Folding@home Core Shutdown: CORE_OUTDATED
[10:53:10] CoreStatus = 6E (110)
[10:53:10] + Core out of date. Auto updating...
[10:53:10] New core downloaded for this work unit, but still out of date.
[10:53:10] 
Folding@Home will go to sleep for 1 day as there have been 5 consecutive Cores executed which failed to complete a work unit.
[10:53:10] (To wake it up early, quit the application and restart it.)
[10:53:10] If problems persist, please visit our website at http://folding.stanford.edu for help.
[10:53:10] + Sleeping...

It had completed work units 5 and 6 all while trying to upload the results for 4. Should I just delete that one from my work folder??? Also, it says "Core out of date. Auto updating..." and then "New core downloaded for this work unit, but still out of date." is that a stanford mistake or my mistake?


Then I re started the gpu client, hoping that might force something. It started working, but only after a few tries. Here is that log


Code: 
[11:45:32] Loaded queue successfully.
[11:45:32] Initialization complete
[11:45:32] 
[11:45:32] + Processing work unit
[11:45:32] Core required: FahCore_11.exe
[11:45:32] Core found.
[11:45:32] Project: 5007 (Run 9, Clone 126, Gen 35)
[11:45:32] - Read packet limit of 540015616... Set to 524286976.


[11:45:32] + Attempting to send results [August 2 11:45:32 UTC]
[11:45:32] Working on queue slot 09 [August 2 11:45:32 UTC]
[11:45:32] + Working ...
[11:45:32] 
[11:45:32] *------------------------------*
[11:45:32] Folding@Home GPU Core - Beta
[11:45:32] Version 1.08 (Tue Jul 22 08:24:14 PDT 2008)
[11:45:32] 
[11:45:32] Compiler  : cl: Command not found.
[11:45:32] Build host: user-f6d030f24f
[11:45:32] Preparing to commence simulation
[11:45:32] - Looking at optimizations...
[11:45:32] - Created dyn
[11:45:32] - Files status OK
[11:45:32] Need version 109
[11:45:32] Error: Work unit read from disk is invalid
[11:45:32] 
[11:45:32] Folding@home Core Shutdown: CORE_OUTDATED
[11:45:33] - Couldn't send HTTP request to server
[11:45:33] + Could not connect to Work Server (results)
[11:45:33]     (171.64.65.20:8080)
[11:45:33] + Retrying using alternative port
[11:45:35] - Couldn't send HTTP request to server
[11:45:35] + Could not connect to Work Server (results)
[11:45:35]     (171.64.65.20:80)
[11:45:35] - Error: Could not transmit unit 04 (completed August 2) to work server.
[11:45:35] - Read packet limit of 540015616... Set to 524286976.


[11:45:35] + Attempting to send results [August 2 11:45:35 UTC]
[11:45:35] - Couldn't send HTTP request to server
[11:45:35]   (Got status 503)
[11:45:35] + Could not connect to Work Server (results)
[11:45:35]     (171.64.122.76:8080)
[11:45:35] + Retrying using alternative port
[11:45:35] - Couldn't send HTTP request to server
[11:45:35]   (Got status 503)
[11:45:35] + Could not connect to Work Server (results)
[11:45:35]     (171.64.122.76:80)
[11:45:35]   Could not transmit unit 04 to Collection server; keeping in queue.
[11:45:36] CoreStatus = 6E (110)
[11:45:36] + Core out of date. Auto updating...
[11:45:36] - Attempting to download new core...
[11:45:36] + Downloading new core: FahCore_11.exe
[11:45:37] + 10240 bytes downloaded
***************(downloading suppressed by Wheresatom)*****************
[11:45:39] + 639010 bytes downloaded
[11:45:39] Verifying core Core_11.fah...
[11:45:39] Signature is VALID
[11:45:39] 
[11:45:39] Trying to unzip core FahCore_11.exe
[11:45:39] Decompressed FahCore_11.exe (1830912 bytes) successfully
[11:45:44] + Core successfully engaged
[11:45:49] 
[11:45:49] + Processing work unit
[11:45:49] Core required: FahCore_11.exe
[11:45:49] Core found.
[11:45:49] Working on queue slot 09 [August 2 11:45:49 UTC]
[11:45:49] + Working ...
[11:45:49] 
[11:45:49] *------------------------------*
[11:45:49] Folding@Home GPU Core - Beta
[11:45:49] Version 1.08 (Tue Jul 22 08:24:14 PDT 2008)
[11:45:49] 
[11:45:49] Compiler  : cl: Command not found.
[11:45:49] Build host: user-f6d030f24f
[11:45:49] Preparing to commence simulation
[11:45:49] - Looking at optimizations...
[11:45:49] - Created dyn
[11:45:49] - Files status OK
[11:45:49] Need version 109
[11:45:49] Error: Work unit read from disk is invalid
[11:45:49] 
[11:45:49] Folding@home Core Shutdown: CORE_OUTDATED
[11:45:53] CoreStatus = 6E (110)
[11:45:53] + Core out of date. Auto updating...
[11:45:53] New core downloaded for this work unit, but still out of date.
[11:45:53] - Attempting to download new core...
[11:45:53] + Downloading new core: FahCore_11.exe
[11:45:54] + 10240 bytes downloaded
**************(downloading suppressed by Wheresatom)****************
[11:45:56] + 639010 bytes downloaded
[11:45:56] Verifying core Core_11.fah...
[11:45:56] Signature is VALID
[11:45:56] 
[11:45:56] Trying to unzip core FahCore_11.exe
[11:45:56] Decompressed FahCore_11.exe (1830912 bytes) successfully
[11:46:01] + Core successfully engaged
[11:46:01] Deleting current work unit & continuing...
[11:46:05] Project: 5007 (Run 9, Clone 126, Gen 35)
[11:46:05] - Read packet limit of 540015616... Set to 524286976.


[11:46:05] + Attempting to send results [August 2 11:46:05 UTC]
[11:46:07] - Couldn't send HTTP request to server
[11:46:07] + Could not connect to Work Server (results)
[11:46:07]     (171.64.65.20:8080)
[11:46:07] + Retrying using alternative port
[11:46:08] - Couldn't send HTTP request to server
[11:46:08] + Could not connect to Work Server (results)
[11:46:08]     (171.64.65.20:80)
[11:46:08] - Error: Could not transmit unit 04 (completed August 2) to work server.
[11:46:08] - Read packet limit of 540015616... Set to 524286976.


[11:46:08] + Attempting to send results [August 2 11:46:08 UTC]
[11:46:08] - Couldn't send HTTP request to server
[11:46:08]   (Got status 503)
[11:46:08] + Could not connect to Work Server (results)
[11:46:08]     (171.64.122.76:8080)
[11:46:08] + Retrying using alternative port
[11:46:08] - Couldn't send HTTP request to server
[11:46:08]   (Got status 503)
[11:46:08] + Could not connect to Work Server (results)
[11:46:08]     (171.64.122.76:80)
[11:46:08]   Could not transmit unit 04 to Collection server; keeping in queue.
[11:46:08] - Preparing to get new work unit...
[11:46:08] + Attempting to get work packet
[11:46:08] - Connecting to assignment server
[11:46:09] - Successful: assigned to (171.64.122.74).
[11:46:09] + News From Folding@Home: GPU folding beta
[11:46:09] Loaded queue successfully.
[11:46:11] + Closed connections
[11:46:16] 
[11:46:16] + Processing work unit
[11:46:16] Core required: FahCore_11.exe
[11:46:16] Core found.
[11:46:16] Working on queue slot 00 [August 2 11:46:16 UTC]
[11:46:16] + Working ...
[11:46:16] 
[11:46:16] *------------------------------*
[11:46:16] Folding@Home GPU Core - Beta
[11:46:16] Version 1.08 (Tue Jul 22 08:24:14 PDT 2008)
[11:46:16] 
[11:46:16] Compiler  : cl: Command not found.
[11:46:16] Build host: user-f6d030f24f
[11:46:16] Preparing to commence simulation
[11:46:16] - Looking at optimizations...
[11:46:16] - Created dyn
[11:46:16] - Files status OK
[11:46:16] - Expanded 45255 -> 246265 (decompressed 544.1 percent)
[11:46:16] Called DecompressByteArray: compressed_data_size=45255 data_size=246265, decompressed_data_size=246265 diff=0
[11:46:16] - Digital signature verified
[11:46:16] 
[11:46:16] Project: 5217 (Run 2, Clone 62, Gen 57)
[11:46:16] 
[11:46:16] Assembly optimizations on if available.
[11:46:16] Entering M.D.
[11:46:24] Working on p5217_supervillin_e1
[11:46:25] Client config found, loading data.
[11:46:25] Starting GUI Server
[11:47:30] Completed 1%
[11:48:32] Completed 2%
[11:49:34] Completed 3%
[11:50:37] Completed 4%


It seems to be working fine now, but I am about to go to work. I have a feeling it might crap out while I am there. Is this just a servers issue on stanford's side? Or did someone accidentally allow the wrong work units into the work server?

 
Server http://171.64.122.76:8080 seems to be borked, I also have a issue uploading some units myself and a report has been made on FCF.

About the Core_Outdated issue, it may be because you have another copy of FahCore_11.exe somewhere else so you must delete it as well.

 
Xilikon said:
About the Core_Outdated issue, it may be because you have another copy of FahCore_11.exe somewhere else so you must delete it as well.
Click to expand...

I found that exact thing actually. It is in the folder with my current work folder and the like. There is no other core in that folder though. If I remove FahCore_11 will it stop my client?

 
Wheresatom said:
I found that exact thing actually. It is in the folder with my current work folder and the like. There is no other core in that folder though. If I remove FahCore_11 will it stop my client?

Click to expand...

Stop the client, delete this then rerun. It should download the correct one but if it still doesn't work, look for a 2nd copy in the installation folder as well.

 
Well, my 4870 appears to have picked up a little bit of performance with this new client, but nothing too spectacular. Overclocked to 790/1100 and running project 4715 (R8, C13, G41) and (still) utilizing pretty much all of one core of my 3.5GHz E6750, I'm getting right around 2570PPD.
 
You must log in or register to reply here.
Back
Top