Any solid reasons for running v6?

[Jesse_V]

V7 has unified the v6 clients, has extended their capabilities, and made everything much simpler. V7 seems to be the recommended client for Windows, Linux, and for OS-X 10.6+. Given all operating systems and all architectures, is there any solid reason to run v6 instead of V7?
IIRC, v6 can perform GPU folding under WINE while V7 cannot, so that's the only reason I can think of.

Also, does anyone run v6? Any estimates on how many informed people still run v6?

[Grandpa_01]

I run a mix of both all rigs have both installed, I run mostley v7 on Windows because CPU / GPU folding is easier on v7 but I run v6 on the bigadv rigs on Ubuntu 10.10 because I can monitor it with HFM I do run v7 on 1 Linux smp rig though most of the time.

[bollix47]

...I run v6 on the bigadv rigs on Ubuntu 10.10 because I can monitor it with HFM...

Just to avoid any confusion HFM.net does monitor both v6 and v7 clients on Windows and Linux.

[uncle fuzzy]

The desktops are v7, but the laptops still have v6. They don't fold that often, but when they do I like the complete control I get with v6. v7 seems to want to do its own thing, which is fine on a dedicated system, but not on an occasional folder.

The main "thing" is starting when Windows starts. It's better now that I found pause-on-start, but I still don't want a computer that I regularly turn on and off to even think about folding unless I explicitly tell it to. Sort of the same reason I haven't used a v6 service install in years.

Start with Windows is a good thing in a less monitored system. If something happens and you get a reboot, you only loose a few minutes of folding. I'll sometimes fold over the weekend on the laptop. With v7, I'd uninstall it when I was done so it wouldn't fold when I turned it on on Tuesday. Pause-on-start gets around that, but I still don't like it.

[Jesse_V]

The desktops are v7, but the laptops still have v6. They don't fold that often, but when they do I like the complete control I get with v6. v7 seems to want to do its own thing, which is fine on a dedicated system, but not on an occasional folder.

The main "thing" is starting when Windows starts. It's better now that I found pause-on-start, but I still don't want a computer that I regularly turn on and off to even think about folding unless I explicitly tell it to. Sort of the same reason I haven't used a v6 service install in years.

Start with Windows is a good thing in a less monitored system. If something happens and you get a reboot, you only loose a few minutes of folding. I'll sometimes fold over the weekend on the laptop. With v7, I'd uninstall it when I was done so it wouldn't fold when I turned it on on Tuesday. Pause-on-start gets around that, but I still don't like it.

I kind of feel the same way. Personally, I'm not much of a fan of running F@h as a service, but that's me. There's a shortcut to FAHControl in your startup folder, and that causes F@h to launch during startup. I've disabled that for my laptop's Windows partition, but I did add FAHControl to the Startup Applications in Linux Mint. IIRC, you choose whether you want that behavior or not during the installation, and afterwards you can add/remove the FAHControl shortcut to change that behavior after the fact.

[RoomateoYo]

I use v6 because it allows me to run multiple clients seperately with the task manager. The desktop shuts down when a smp unit completes. The laptop chages power profiles when the gpu clent is started and stoped, this allows me to control the temps on the cpu.

[Napoleon]

Well, I loved the v6 Windows SMP console client after Deino/MPICH got ditched. Just one executable, you could drop it anywhere you liked, no installation, just some simple config dialogues and you were good to go. So very hands-on approach. Then again, I'm a bit old fashioned and happen to think that occasionally (although rarely, these days) a GUI just gets in the way.

Having said that, I'm all for v7, it's a major step forward in my book. No more v6 for me. If I want to get reacquinted with a console, I can go play with my recent CentOS 6.3 Minimal install with a tarball release of FahClient v7.2.9. As it happens, I'm more than happy to just monitor it remotely via FahControl once I've launched the executable manually. That's just about enough of TUI / SSH console to satisfy my archaic urges.

The "start manually" option is what I really care about. I don't like to reboot "just because", and outright detest unscheduled reboots. Since it isn't much of a nuisance when compared to things that led to a reboot, I want to launch FAHClient manually, and I want it to just sit still (pause-on-start) until I explicitly tell it to start folding, via FahControl. I do not want FAHControl running when I'm not there to admire the sheer beauty of it. In that vein, I don't have much use for screensavers either. My pushbutton finger is just fine, thank you very much.

I can get all that and then some with v7, and that's what counts. The fact that my way isn't the default way bothers me... not.

[Grandpa_01]

...I run v6 on the bigadv rigs on Ubuntu 10.10 because I can monitor it with HFM...

Just to avoid any confusion HFM.net does monitor both v6 and v7 clients on Windows and Linux.

Have you tried to set it up on Ubuntu 10.10 on v7 I have tried but failed several times

[k1wi]

The main "thing" is starting when Windows starts. It's better now that I found pause-on-start, but I still don't want a computer that I regularly turn on and off to even think about folding unless I explicitly tell it to. Sort of the same reason I haven't used a v6 service install in years.

Start with Windows is a good thing in a less monitored system. If something happens and you get a reboot, you only loose a few minutes of folding. I'll sometimes fold over the weekend on the laptop. With v7, I'd uninstall it when I was done so it wouldn't fold when I turned it on on Tuesday. Pause-on-start gets around that, but I still don't like it.

Took me a while to work out how to configure the pause-on-start for individual slots... That bugged me for a long time and it takes a bit of digging around and a shot to actually work it out.

But, it made me think that it would be very good if there was a built in 'viewer' from which to view the help files/FAQ. At the moment all I see from the actual client is a link to the forums for those seeking help. Perhaps once the current FAQs have been tidied up and 'help' isn't spread across several sites (see http://foldingforum.org/viewtopic.php?f=27&t=23290). Pressing 'F1' should do something!

Here is my favourite example of a built in document viewer, from the STATA software package, but I guess the help button could at least just fire up a new page in the default internet browser.

[Jesse_V]

k1wi, in-program help already exists to some degree in V7. Open FAHViewer and click the red and white flotation ring on the right.

[mmonnin]

...I run v6 on the bigadv rigs on Ubuntu 10.10 because I can monitor it with HFM...

Just to avoid any confusion HFM.net does monitor both v6 and v7 clients on Windows and Linux.

Have you tried to set it up on Ubuntu 10.10 on v7 I have tried but failed several times

I monitor v7 in a local VMWare/Linux install and a remote native Linux computer.

I add these lines to the linux config.xml file and use the IP of the Linux computer/VM in HFM.

Code: Select all

<command-allow v="127.0.0.1 192.168.1.1-192.168.1.149"/>
<command-allow-no-pass v="127.0.0.1 192.168.1.1-192.168.1.149"/>
<command-port v="36330"/>

[Nathan_P]

For me its v7 or v6 on windows and v6 on linux, still smarting from my last attempt to get v7 to work on ubuntu

[mmonnin]

10.10

Code: Select all

mkdir fahv7; cd fahv7; wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahclient/debian-testing-64bit/v7.2/fahclient_7.2.9-64bit-release.tar.bz2; tar -jxvf *.tar.bz2; rm *.tar*; mv fahclient_7.2.9-64bit-release v7; cd v7; ./FAHClient --configure

12.04

Code: Select all

sudo apt-get install libssl0.9.8; mkdir fahv7; cd fahv7; wget --no-check-certificate https://fah-web.stanford.edu/file-releases/beta/release/fahclient/debian-testing-64bit/v7.2/fahclient_7.2.9-64bit-release.tar.bz2; tar -jxvf *.tar.bz2; rm *.tar.bz2; mv fahclient_7.2.9-64bit-release v7; cd v7; ./FAHClient --configure

These to start as service:

Code: Select all

sudo gedit /etc/rc.local
cd /home/ *user_name* /fahv7/v7; ./FAHClient

Those 3 lines plus editing the config.xml are the only things I do to get FAH running in Ubuntu.

**Code portions taken from a guide on OCN**

[Jesse_V]

V7 installs relatively smoothly in Linux Mint 14, I just download the .deb file and double-click on it. The Package Installer GUI installs everything, and I can follow the instructions in the installation guide. There's an option at the beginning to autostart F@h: enabling it creates a service, which I don't like so I usually disable it. Linux Mint 14 is based on Ubuntu 12.10.

[bruce]

I've installed V7 on Windows many, many times and only occasionally on Linux and OX-X but perhaps there should be an advanced installation option to start FAHClient but to wait for a manual start of the FahCores (do not start folding). (Adds PAUSE-ON-START='TRUE' to each slot.)

That would be the wrong option for the newbie who doesn't want to figure out how to start folding, but for the advanced Donor who doesn't know how to find pause-on-start it might be a good choice.

I think this is off-topic, though, since the original question was about solid reasons to keep running V6.