I'm just posting this here so that I can put it in my sig. I was a folding n00b 4 days ago, but I've learned a little from the CC folding for OCN.
Before starting ensure that Virtualization is enabled in your BIOS.
1. Get the latest Virtual Box here
Currently it's at 4.1.14
2. Get the Linux FAH VDI (virtual disk image) for Virtual Box
Linux64_FAH-1.4.1.7z < notice the .7z, that's a 7-zip compressed file. You will need to save the 7z file somewhere and extract it with WinRAR (7zip will not work it appears). When you are done, there will be a "Linux64_FAH.vdi" file extraced.
3. Install VirtualBox and start it
4. Create a new VirtualBox machine:

Note below, 12GB is not required, 3072 (or 3GB) will work fine, 4GB is optimal IMHO

Note below, navigate to where you extracted the .VDI file and use it as an existing VDI:


Now, before starting the machine, click on the gear icon (settings) and make it look like this:
Note, the number of processors assigned to the VM defaults to 1, also, in the Network Adapter section, "Attached to" defaults to NAT. So, must change:
In System->Processor : processors defaults to 1, set to 12 for SB-E
In Network->Adapter 1 : "Attached to" defaults to NAT, switch to Bridged.
(the screenshot below shows running, yours should say stopped at this point)

Once everything is right, go ahead and start the machine.
Make a note of the IP address the Linux image says to use.
Now, type that IP address into a browser window and you should get the FAH config screen. configure it according to the OCN Chimp Challenge Settings like so:

Click submit and the image will reboot itself.
Once it's rebooted at the linux prompt type one of the following commands to start FAH:
Basic/no Unix knowledge:
./fah6 -verbosity 9 -bigadv -smp 12
Advanced Unix users:
nohup ./fah6 -verbosity 9 -bigadv -smp 12 &
tail -f nohup.out
Now to monitor with HFM.NET you can map a network drive to the IP of the vbox instance I.E. \\192.168.1.110\fah, then when you add a client to HFM.NET simply point it at that drive.
EDIT: 3GB is fine for the Virtual Machine. 4GB is optimal IMHO.
EDIT: If you need to use the computer at all, open Windows Task Manager, find the VirtualBox.exe process and set the priority to low.
Before starting ensure that Virtualization is enabled in your BIOS.
1. Get the latest Virtual Box here
Currently it's at 4.1.14
2. Get the Linux FAH VDI (virtual disk image) for Virtual Box
Linux64_FAH-1.4.1.7z < notice the .7z, that's a 7-zip compressed file. You will need to save the 7z file somewhere and extract it with WinRAR (7zip will not work it appears). When you are done, there will be a "Linux64_FAH.vdi" file extraced.
3. Install VirtualBox and start it
4. Create a new VirtualBox machine:

Note below, 12GB is not required, 3072 (or 3GB) will work fine, 4GB is optimal IMHO

Note below, navigate to where you extracted the .VDI file and use it as an existing VDI:


Now, before starting the machine, click on the gear icon (settings) and make it look like this:
Note, the number of processors assigned to the VM defaults to 1, also, in the Network Adapter section, "Attached to" defaults to NAT. So, must change:
In System->Processor : processors defaults to 1, set to 12 for SB-E
In Network->Adapter 1 : "Attached to" defaults to NAT, switch to Bridged.
(the screenshot below shows running, yours should say stopped at this point)

Once everything is right, go ahead and start the machine.
Make a note of the IP address the Linux image says to use.
Now, type that IP address into a browser window and you should get the FAH config screen. configure it according to the OCN Chimp Challenge Settings like so:

Click submit and the image will reboot itself.
Once it's rebooted at the linux prompt type one of the following commands to start FAH:
Basic/no Unix knowledge:
./fah6 -verbosity 9 -bigadv -smp 12
Advanced Unix users:
nohup ./fah6 -verbosity 9 -bigadv -smp 12 &
tail -f nohup.out
Now to monitor with HFM.NET you can map a network drive to the IP of the vbox instance I.E. \\192.168.1.110\fah, then when you add a client to HFM.NET simply point it at that drive.
EDIT: 3GB is fine for the Virtual Machine. 4GB is optimal IMHO.
EDIT: If you need to use the computer at all, open Windows Task Manager, find the VirtualBox.exe process and set the priority to low.


















