Originally posted by jelloshotsrule
now what?
Alright. The big difference between F@H 2 and 3 is how they store your work data and config files.
F@H3 <- ~/Library/Folding@home
F@H2 <- Current Directory
In the PC version of F@H, there is a local switch where you can run two instances of the client rather painlessly on the same machine. This is to get around the fact that their binary is not multithreaded.
This switch that works on the PC, but does not do anything AFAIK on the Mac. Folding control was able to take advantage of the current directory creation of data and config. Now, I don't know how they'll make it run multiple instances.
The way to run multiple instances is to have unique client ID's. These are given and stored by the F@H servers to identify the processors doing the work for them. This data is stored in a file called
client.cfg
Since F@H3 stores all the files in the same place, 2 folding apps will look at the same client.cfg file and just use the same CPU. If there was some way to change the location of the files, the problem would be solved. But I do not know of any way to do this.
So basically, with F@H2, you run the client 1 time, delete the config file, and duplicate it in another directory. When you run the 2nd app in another directory, it makes a different client ID and the second processor is allowed to work
MA4l's program doesn't work w/3.0. Even if it did, the program fails to run properly on Jaguar. All it really does is script the process that I do manually.
So it looks like we'll have to do it through CLI.
Here are the steps:
o create 2 new folders, F@H1 and F@H2
o drop the binary in F@H1
o change directory to F@H1
o excecute binary in F@H1
o wait 'till it dowloads core, and starts folding
o ctrl-c the binary to terminate execution
o drag the binary and newly created core file to F@H2 (leave everything else)
o open new terminal window
o change directory to 2nd folder
o excecute binary in F@H2
=Reference=
cd [pathname] has the same effect as double clicking on a folder.
control + c at the same time terminates a program (like a force quit)
to run a program you navigate to it's directory and type in it's name.
If I were on my desktop and had a file I wanted to execute, I can do it in a number of ways:
Code:
/Users/bakerc/Desktop/F@H3.bin
This is an absolute address. It starts from the root level of the hard drive, /, and works it's way to the file.
The ~ represents /Users/bakerc. This saves typing.
With F@H2, you want to be in the same directory as the binary. It will create it's files in your current directory. So if you were on your desktop and ran it somewhere else, the files would litter the desktop. So it's a good idea to make a folder and run it there.
Back to my previous example. After making a folder F@H1 on the desktop and dropping the binary in it, you can type:
Code:
cd ~/Desktop/F@H1/
./F@H3.bin
This will run and create the files in F@H1, on the desktop. The . stands for /Users/bakerc/Desktop/F@H1 This saves typing.
If anything is still unclear, I can just give you code to type in so you don't have to learn all this. Whatever suits you.
