View Full Version : two things of fold?
since i have an dual core can i run 2 things of fold@home, one on each core?
Mark620
03-10-06, 06:27 AM
yes.
but the second instance needs to be renamed and have its own directory...
it wont let me, i put it on my other hdd and it says theres an instance of it already running and i tryed renamein the .exe but that didnt work ethier
glasslicker
03-10-06, 06:43 AM
Which version are you using ?
The easiest way I found if not using Wedo's one click is to make one folder and two sub folders.
On the same drive within "Programs" I create FAH. Within FAH I create FAH1 and FAH2.
I then DL the console (Im using 5.04) twice, once in each sub folder. Fire up the console in FAH1, selecting your flags. Then fire up the console in FAH2 and make sure you change the Machine ID to # 2.
It sounds like (speaking with great ignorance) you are running RAID and your RAID config is showing both drives as one big drive or you are mirroring ?
Someone way smarter than me will come along and help.
You can either edit the 2nd instance client.cfg and change machineid to two or start the console with the -config or -configonly flag (ie run c:\program files\FAH\FAH2\FAH50x-Console.exe -configonly or add the flag to the target line of the shortcut) and change it there.
since i have an dual core can i run 2 things of fold@home, one on each core?
Like you, I have an A64X2 3800, and I keep two FAH console's, working two completely separate, WU cores.
You NEVER want to copy files from one Folding directory, into the other, and start it up, without making critical changes to the config file, first. You might get the error message you received, or you might even have two instances running exactly the same Work Unit, and constantly getting into each other's way. Result? It runs more than twice as slow, if it even runs at all.
If you are VERY CAREFUL, you can edit the config file in Notepad BUT the config file is NOT a regular Windows/DOS text file. It looks funny, and you MUST be careful of the little funny shaped characters in the file. Don't accidentally delete one, or give it the wrong number of spaces, even.
After changing your machineID to 1 and 2, save your config file AS A config.cfg file NOT as a config.TXT file. If you do, notepad will change the config file into a Windows/DOS text file, automatically and goof it up.
Before you edit the config file, shut down the console program, which will shut down the core it's controlling in about 6 seconds. If the console isn't shut down first, it will automatically overwrite the config file, and change your settings right back to what they were, before. :D
I have my dual core set up with one console getting advanced methods and big packets, and the other core getting big packets, but not advanced methods.
With 1 Gig of RAM, I've experimented and found this set-up the best for the way I like to use my computer. All my other settings are the default values.
Let me know if you'd like to see my config file. (I run both instances, as a background or service, program).
Any other questions, fire away! :p
Adak
Wiggles
03-10-06, 10:49 AM
Wedo's one-click for duals worked for me. Unzip the file to the desktop if you wish, edit the configs with notepad (name, bigpackets yes/no, etc...) and then run the executable. Does all the work for ya.
Adak also has a good point. I run 2GB of ram, so both of my instances run advmethods and bigpackets. You might want to try out what he suggested. Or, run both w/ advmethods and one with bigpackets, and the other without.
Make sure you're not trying to use two instances of the graphical client, or one instance of the graphical and one of the console.
Running two console clients with each client having its own directory and own machine ID number is essential.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.