New system, how many WU

[Blue_Gundam2002]

Havn't seen a new post here in a while, so I guess I'll ask a stupid question. I just ordered my new system today from newegg. P4 2.8c, 512md pc 3500, 9800 pro. Can't wait to get the parts in and play UT:2k4 . I'm sure someone here has a system useing a P4 2.8c. About how long does it take to finsh a 400?

[Kov-Ice]

I'm oc'd to a little over that speed. A p639 that size takes a bit under two days. Plus, you'll be able to run two instances with that processor as well. Cool!

[Blue_Gundam2002]

I just got the parts and I'm going to install them as soon as my mother gets home. I have a broken foot so I can't move the case on my own. I hope this computer goes together without any problems.

[Blue_Gundam2002]

How do I run the 2 instances?

[lil Jimmie]

I copied this from the Maximum PC F@H tweaking guide found here

b) Two folds are better than one (Difficulty: Advanced)
For those lucky users with dual-processor machines or rigs with hyperthreaded P4s, you can run two instances of the Console version simultaneously. It's rather involved, but well worth it to see both of your CPUs (or both of your virtual CPUs) being utilized to their fullest. These instructions assume you are running Win2K Pro or XP Pro.

1) First, create two separate directories and dump FAH3Console.exe in each one.

2) Then, you're going to have to make a shortcut to each FAH3Console.exe. Paste the Shortcuts into the Cocuments and SettingsAll UsersStart MenuProgramsStartup folder so that both FAH consoles will startup every time the system boots up.

3) Right click on each shortcut you've created. You'll see the "Target" line: "C:Program Filesetc.etc.FAH3Console.exe"

Now, you MUST add the -local flag, if you haven't already done so here. Remember to add the -local flag for each shortcut. It's also a good idea to add -advmethods and -forceasm.

4) Now, you're almost set. Double click on one of the shortcuts you created. The first time you do, you'll be asked to configure FAH. Aside from your username and Team No. (select team No. 11108 for Team MPC), one of the configuration options is to set the Machine ID for the first FAH3Console.exe program to "1" (when you get to the point where we run the second FAH3Console.exe, you'll need to set the second one's Machine ID to "2").

5) Now that one instance of FAH is up and running, go into your task manager and hit the "processes" tab. You'll see FAH3Console.exe there. Right click on it and choose "Set Affinity" and set it for CPU 0 only (uncheck CPU 1). You'll also see FAHCore_xx.exe running. Set that for CPU 0 too.

6) Now you're ready to run the second console (again, launch it by clicking on your second created shortcut). When you configure it, set it for a different machine ID ("2").

7) In take manager, you'll set the Affinity for your second instance of FAH3Console.exe for CPU 1. Now, this will be tricky as you'll see two FAH3Console.exe's running. You can check which one is the first one by checking the affinity. The new one will have both CPU 0 and 1 checked, while the first one was just set to CPU 0.

8) Do the same thing with the second FAHCore_xx.exe. Set it to CPU 1 only.

9) Now you're running two instances of FAH, and they are taking full advantage of your processors.

10) As long as you don't close out the Console programs, they'll remember their affinity. If you close them, or restart or reboot your computer, you'll need to go back and set the affinity again.