Installing Fire Power W/ETO, PTO

B

Barnstorm

"Molon Labe"
Greetings All,
I have a "clean" install of CFS3 and am running OFF BH&H w/o any probs. I want to run the T.O.'s and FP if possible. I have the Multi.exe tool, but FP does like its install folder messed with. And installing FP would "corrupt" the CFS3 sourse files (?)

Some notes...I am also running FSX, installed under C:\, as is the OBDSoftware (OFF). COmputer Pilot Mag had a piece about Win7 and FSX not running well in the (x86) file. I don't know.

Any one running this config, I would appriciate a "heads up". My system specs:

Thanks....

Windows 7-64
Intel 7i 860
ASUS P7P55D
ATI 5850 1 G
3 Seagate 1TB HD #RAID 5
1 Seagate 1.5 TB HD Backup
8 G System RAM
Corsair 750W PS
 
Hello Barnstorm,

I've been running 64-bit Windows 7 since it was released. Make sure your 'clean' CFS3 install is patched up to 3.1a using the patches from MS - you probably had to do this for BH&H anyway.

ETO makes its own installation folder from your 'clean' CFS3.1a, as does MAW and PTO iirc. Be sure to get the ETO Installation Guide from the Warbirds Archive here at SOH - it's in the CFS3 Other section, because you will have to edit some files to install successfully in 64-bit Windows 7. You'll also need to turn the User Access Control (UAC) off while installing.

So far so good, you will now have 'clean' CFS3.1a and ETO, MAW etc. You can now install Firepower and it won't screw up the others. Once a Firepower installation is finished and tested, you can rename the game folder and reactivate it with MultiCFS3.exe - just copy MultiCFS3 to your Firepower game folder and run it. That won't screw up Firepower.

I have CFS3, MAW, ETO all installed to the default Program Files (x86) location and have no problems, but I also have the UAC in Win7 turned off. If you prefer to keep the UAC on, installing to another location is one way to avoid the UAC's paranoia.
 
Thanks for the prompt reply, hairyspin. I was getting FUBAR'd not remebring the T.O.'s create their own CFS3 folder. But, if I was to have installed FirePower first, then the T.O.'s, they would have failed...correct?
 
Correct, Firepower will especially mangle ETO.

If you already have Firepower installed, rename the installation folder and use MultiCFS3 to reactivate it as described, then reinstall a fresh copy of CFS3, patch to 3.1a and proceed from there.
 
No, was just re-installing software after a HD failure, and thought I remembered something about FP trashing the CFS3 file for future add-ons... and knew SOH folks are always available to respond to the SOS.:salute:
 
You must log in or register to reply here.
Back
Top