Forums | MacLife

Actually, no.  The molar is staying as is.  It's performing quite well as my server (and with 90 days uptime since I moved).

The computer getting the "heat" is a G3 Desktop model that I have in my entertainment center.  I use it as a DVD player, MP3 player, game system for my daughter, and of course, Folding@home.

Hey ArtemisG3,

With that G4, you'll be ready when Gromacs comes.

Bye for now,

Bert

This will be my first G4 processor.  I suppose it will actually fold slightly slower than my iBook 700, until Gromacs maybe.

Welcome to my bro, MikeCarrillo is in the house.
With the PC I built for him, (Mikes an Amgia geek)

Who have you got to join our team? name names

So, could someone point me to the right place to get two units folding at once? I can run two consoles, right? (ie., no GUI) Please say 'yes'.

Here's some instructions, courtesy of the maccentral forums.  Edited to correct the new client version and team number.

The idea is that you need a folder for each instance of f@h.

For example, I created a Folding1 folder and a Folding2 folder in my Home folder.

Place a copy of the OSX-3.24 file in each folder.

Open up 2 terminal windows.

Change the directory for each window.
In window 1 paste: cd Folding1
In window 2 paste: cd Folding2

Paste the following in both windows to allow the client to run in its new folder:
chmod +x OSX-3.24

On the first run of each client make sure that you give them separate machine #s. You need to answer "Y" to the advanced options to enable this. Start each client from its own directory with the local flag like this: ./OSX-3.24 -local (the -local tag tells the client to create all the files it needs within the same folder as the core.)

This is how you do it.

In Terminal window 1 paste the following line:
./osx-3.24 -local

The following appears:
Configuring Folding@home...
User name [Anonymous]? ArtemisG3
Team Number[0]? 18
Ask before fetching/sending work [no]? no
Use proxy [no]? no
Change advanced options [no] (yes/no)? y
Core Type [no-pref] (no-pref/fah/gah)?
Core Priority (idle/low)?
Machine ID (1-4) [1]? 1

In Terminal window 2 paste the following line:
./osx-3.24 -local

The following appears:
Configuring Folding@home...
User name [Anonymous]? ArtemisG3
Team Number[0]? 18
Ask before fetching/sending work [no]? no
Use proxy [no]? no
Change advanced options [no] (yes/no)? y
Core Type [no-pref] (no-pref/fah/gah)?
Core Priority (idle/low)?
Machine ID (1-4) [1]? 2

Working good. Now, if I could just get the Terminal app to actually QUIT from the command line. I suppose I could write a script to find the PID of the Terminal and then kill it...

To start up Folding, I created the following in TextEdit:

cd /Users/akinsfamily/FAH1
./FAH324 -local &
cd /Users/akinsfamily/FAH2
./FAH324 -local &

I saved it is StartFAH. A little chmod +x StartFAH action and I can execute it from a shell. Get Info and tell OSX to open this file with Terminal, drag it to the Login items window, and it should be ready to rock.

Yep...quiting Terminal keeps folding away, so I need to kill terminal automatically.

Oh, what the heck.  Here's what your applescript should probably look like.  I realized that you included all the pertinent info.

do shell script "/Users/akinsfamily/FAH1/FAH324 -local > /dev/null 2>&1 &"
do shell script "/Users/akinsfamily/FAH2/FAH324 -local > /dev/null 2>&1 &"

Just save this as an application.

That's weird.  When I log out, folding quits.  There's something wrong with that applescript.

Well, cool and Thanks again, AG3!

I (currently) do not log out, so I shouldn't have this issue. I will implement your script when I get home today.