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

Beta client expire today, infos for updates

Xilikon

Xilikon

[H]ard|DCer of the Year 2008
2FA
Joined
Oct 12, 2004
Messages
15,022
Many folders is aware that the beta clients expire today but not everyone so I'm creating this thread to give all the necessary informations in a single place about the status of each client and the download links :

Linux SMP and uniprocessor :

The client is now out of beta so you can grab the final version (6.02) at http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-Linux.tgz and replace both executables after stopping the client. This version is rock stable so don't worry about issues.

MacOSX SMP :

It's also out of beta so grab the 6.02 version at http://www.stanford.edu/group/pandegroup/folding/release/FAH6.02-OSX-Intel-Console.tgz

Windows GPU2 client :

Version 6.20 is now available and out of beta. There is 3 versions available for download :

-Systray (Windows XP/2003/Vista) : http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-Win32-GPU-systray-620.msi
-Console (Windows XP/2003) : http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-Win32-GPU_XP-620.zip
-Console (Vista) : http://www.stanford.edu/group/pandegroup/folding/release/Folding@home-Win32-GPU_Vista-620.zip

Windows SMP :

-Windows 6.22 beta 2 (expiration date of february 2, 2009) mpich version : http://www.stanford.edu/group/pandegroup/folding/release/FAH6.22beta2-win32-SMP-mpich.exe
--Windows 6.22 beta 2 (expiration date of february 2, 2009) deino version : http://www.stanford.edu/group/pandegroup/folding/release/FAH6.22beta2-win32-SMP-deino.zip

In case you have issues with the 6.22 client, here is the deprecated versions valid until november 2th, 2008 :
-5.91 : http://www.stanford.edu/~kasson/folding/windows/fah-SMP-591.exe
-5.92 (deino) : http://www.stanford.edu/~kasson/folding/windows/fah-SMP-592.exe

There is already a few threads made for those respective clients so post there if you need more informations or help installing the clients. For now, only the Windows SMP is still in beta so you may need to upgrade later.

 
Thanks for the update, on a saturday morning none the less.
gotta admit i have fell out of the loop lately didnt realize the deadline was comming up.

 
I am running one 6.20 systray GPU client, it's crashed once since install yesterday ( which is once more than the 6.12beta8 ever crashed on that machine) but it's only had that one problem. PPD is almost identical, I see little difference for the NVidia GPU it's running on.

The 6.22 SMP client is far less stable than it's 5.91 predecessor but some systems will run it without issue. (None of mine will, although all ran 5.91 very reliably) the biggest problem is with the 2665 WUs. You may be able to run the unstable 6.22 version by cutting the CPU usage to 90%. This reduces the EUEs although it doesn't eliminate them.

I'd suggest everyone install a monitoring proggy like fahspy or fahmon. This release cycle definately doesn't look good for reliability. You'll need to keep a close eye on your folding boxen.
 
Ahh.., does the notfred diskless/headless CD also expire ? I just shut one of my diskless/headless boxen down (thank God for flash drives). It wouldn't work at reboot on my Ubuntu v8.04 main boxen (show up in FAHmon 2.3.2b) until I set the system date back in BIOS. :confused:

I also tested it on a Ubuntu v8.04 boxen and I just set the OS date back, not the BIOS date, and it worked. :D Evidently if you're folding under the Linux OS (I don't know about windose or the Mac OS's) the F@H client only checks the software date. ;)

I agree it's much easier to just upgrade your OS folding client, but to upgrade the notfred CD it'd need a rewrite wouldn't it? Please, someone "chime" in on this, as you can see I'm rather weak in the IT department :rolleyes:

FOLD ON!

 
Thanks for the heads up and compiled info on all the new clients, Xilikon. :)

 
No need to worry about it, from what I can see, just like last weekend the servers are screwed anyway:rolleyes:

 
jws2346 said:
Ahh.., does the notfred diskless/headless CD also expire ? I just shut one of my diskless/headless boxen down (thank God for flash drives). It wouldn't work at reboot on my Ubuntu v8.04 main boxen (show up in FAHmon 2.3.2b) until I set the system date back in BIOS. :confused:

Click to expand...

Your "beta" client may have expired as well. There's a new release version out v6.02. If you've got a log file on your usb stick look at the first few lines for the version info.

If not, hop over to notfreds and setup a new cd. Many new options to choose from and he updated to the release client on July 17. I've been running it with no probs since it came out.

News
17 July 08: Change URL to released (i.e. non-beta) version of 6.02 client. Add support for specifying TFTP server IP if doing static IP config. Add support for specifying interface, if specified and DHCP it will retry continuously in the foreground and not round robin in the background. Add support for doing a login shell, note that this has very few commands available.
Click to expand...

 
After the initial "hiccup" the 6.20 GPU client seems to be running acceptably. I've switched over a third system after several successful WU returned with the first two boxes.

The 6.22 SMP client continues to fail, with no recovery possible, just delete the queue dat and the work directory. I'll be monitoring the WU and deleting every 2665 I receive until they fix the client.
 
relic said:
After the initial "hiccup" the 6.20 GPU client seems to be running acceptably. I've switched over a third system after several successful WU returned with the first two boxes.

The 6.22 SMP client continues to fail, with no recovery possible, just delete the queue dat and the work directory. I'll be monitoring the WU and deleting every 2665 I receive until they fix the client.
Click to expand...

2665 is all I ever get on my windoz boxen :eek: Is there a reason we don't want to just use the deprecated version 5.91 until they work the bugs out of the new version? I installed 6.22beta 2 on one of my 6 SMPs. I need to see it run ok before I start converting my farm over.

 
HighYield said:
2665 is all I ever get on my windoz boxen Is there a reason we don't want to just use the deprecated version 5.91 until they work the bugs out of the new version?
Click to expand...
The new version allegedly supports the A2 core, but since it hasn't been released yet, it doesn't really matter for now. Just run the 5.91 version until the kinks are worked out with the new client or the new core is released, whichever comes first. ;)


 
Well, we are talking about far less then 'talented' programmers. Use the 6.22 if you can, at least they can continue with the "beta" testing. In 11 or 12 revisions perhaps we'll be out of beta and have a half-stable client to run. ;)
 
What is the difference in the SMP clients between deino and mpich? It seemed like the deino is the only x64 supported one...

And now that i'm new to v6.xx, is anyone bothering with passkeys?
 
Schro said:
What is the difference in the SMP clients between deino and mpich? It seemed like the deino is the only x64 supported one...
Click to expand...
I think I saw it mentioned in another thread that the Deino version eliminates the problems of the client suspending during network timeouts.
 
DEINO is more robust when it come to networking hiccups handling but the problem is that it's only supported under x86, not x64. MPICH is running faster and work under both versions but are more sensible to network issues.

For the notfred CD, just download the latest since it include the new final 6.02 Linux SMP client :)

Stability wise, Linux 6.02 SMP and 6.20 GPU2 systray/console clients are very robust for me, not a single crash (beside one when I upgraded).

 
I wish I had seen the deprecated 5.91 at 12:10am saturday morning when I rebooted my pc to find out my client expired and installed the 6.22 client. I woke up this morning to find that the first of 2 smp clients crashed at 100% with the "MISSING WORK FILES" error. The 2nd one just finished 2 hours ago...and after completing 100% it too gave the dreaded missing work files error. More work and time lost!! The best part is, even after clearing queue.dat and work files....neither client will run now and my box is crashing whenever I open Firefox!!!!! Thanks Stanford :|

 
If you have troubles installing the GPU-2 client, try another one. For example, if you cannot get the Systray to work, try the console.

With Vista, you can try to disable or turn off UAC (User Access Control). Sometimes this is necessary.
 
I went out of town for a week and came back to the expired beta, anyway, I installed the new systray client last night. I've noticed when the screensaver comes on... even though its the blank screen SS, it goes from doing 1% a minute to like 1% every 3 minutes. And then this morning I woke up to it locked up.

So far... not good. :(

 
chrisf6969 said:
I went out of town for a week and came back to the expired beta, anyway, I installed the new systray client last night. I've noticed when the screensaver comes on... even though its the blank screen SS, it goes from doing 1% a minute to like 1% every 3 minutes. And then this morning I woke up to it locked up.

So far... not good. :(

Click to expand...

Try to update the driver to 177.41 or 177.66 to see if that helps.

 
Pocatello said:
If you have troubles installing the GPU-2 client, try another one. For example, if you cannot get the Systray to work, try the console.

With Vista, you can try to disable or turn off UAC (User Access Control). Sometimes this is necessary.
Click to expand...

Actually I have found the console for GPU to be so easy to install you have to think you did it wrong. It doesn't care which windows you use and is remarkably stable.

Give it a shot, it's the one thing stanford has done right in a long while;)

 
Xilikon said:
Try to update the driver to 177.41 or 177.66 to see if that helps.

Click to expand...

I got this message:

[19:34:35] Folding@home Core Shutdown: UNSTABLE_MACHINE

But my videocard isn't overclocked..... at least not by me.
I hadn't looked at the clocks yet, as I was going to let it run for a little while to make sure everything was good first. Anyway, MSI has the "stock" clocks at 620 core, 1080 memory & 1296 shader. I was thinking maybe they have the core pushed too hard.

Going to try updating the drivers, as I was using 177.35.

I notice while I'm on the computer F@H Mon reads about 5900PPD, but then I walk off, and the screensaver kicks in it drops down to like 2000PPD. For some reason when its "idle" its goes from doing a frame in a minute +, to 3 minutes. Is there anything I can do to force the 3D clocks. My guess, is its dropping to 2D clock mode or something.

I tried the console & systray... but do the same thing.
 
chrisf6969 said:
I got this message:

[19:34:35] Folding@home Core Shutdown: UNSTABLE_MACHINE

But my videocard isn't overclocked.

Going to try updating the drivers, as I was using 177.35.
Click to expand...

I think I am using 177.35 without problem. :confused: Good luck! :)
 
I think MSI overclocked the GTX 260 too much.

I reduced the core to stock 576Mhz (from 620), and the memory to 1050 (from 1080) and things seem to be ok. It could be that I also changed the screen saver from "blank screen" to a 3D screensaver. (it stays in 3d clock mode?)
 
is it normal for the 9800GX2 to rip through a step in 2 minutes?
 
it looks more like im ripping in 1:30 give or take a second or two. still nice to see it go. Once I build a dummy dongle for the second monitor connection, ill be zooming
 
my 8800GT at 1700 did it in about 1min 23 sec per 1%
my gtx260 at 1350 does it in about 1min, 2 sec, I think

difference of about 25%... which is why I get about 6000 PPD instead of 4800.

Though the GTX seems to be more affected when I use the computer.
 
Depending on the WU I range from 1:30 to 1:20 on both the 9800gx2 and 8800gt. The 9800 is at 1750, the 8800 is at 1850.

 
got my time down 10 seconds. ill spend more time tomorrow getting it streamlined. thanks for your help xilikon
 
On my work computer,I just set the windows time/date to 8/1/08 started up the client, then returned the date back to normal. So it lets me use the expired BETA client with out the hassle of uninstalling & reinstalling a new client. I know I'm lazy, but just an idea for some others out there like myself.


 
You must log in or register to reply here.
Back
Top