• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

ETO Expansion Download Links, Comments, Questions"

Axenti (Be Raiders) said:
NP M8 i'm glad to do something in return for all the advice i had from everyone :ernae: .... my problem is solved as well i made a mistake on the install so i just get it figured out thanks to grizzly, how was you problem solved anyways???? was it of a bad unzipper ???
Click to expand...

YES GRIZZ IS REALLY GOOD AT PROBLEM SOLVING.
GOOD TO HAVE HIM IN SOH
COMPUTERS AND ME DON'T GET ALONG TOGETHER
BUT I'M GOOD AT VULCHING
GRIZZ JUST LOVES WHEN I STEAL HIS KILL.:d
 
"I had thought MAW was a difficult installation through v1.31. The "new" ETO surpassed its adventures in computer patience. I had ETO from last November as encouraged by MAW members . No problems at that time. Yet as my OS died, was restored and migrated from SP2 to SP3, things became more complicated .
I had early problems with ETO 1.0 due to a cockpit error where I failed to note the option selection on the installer. Without checking the continue message, the installation ended abruptly without an installation. My third attempt discovered this "oversight"and success was achieved. But...
I installed v1.20 without hitch, loaded and launched the initialization run at Level 1 (1936), flew a plane to secure the initialization setup and then moved to step 3 or Firepower.
While I already have v1.08 of Firepower in CFS3 and the ETO v1.0 setup did copy those files, I proceeded with the Firepower ETO patch. After a system reboot, a selection of Level 1, the program went immediately on two attempts to a CTD following the introductory CFS3 video.
Recopying, no clean "do over", v1.0 and v1.2, the program now launches and checks out to Level 3 (1943)
In the end I still have reports on launch of SDK violations due to a marginally constructed plane imported into CFS3 at some time, a wandering DPC Korea F51, "gun" and "searchlight" files already in use. These I can bypass. I did have to eliminate the Tempest MkV as it caused a freeze following the CFS3 video. Moving this plane folder from Aircraft eliminated this problem. Annoyances aside, the program now functions, without the Firepower patch. Now comes the careful addition of planes, Spawns, Missions that will not lead to another file conflict or program breakdown in a fragile program setup. At least I now know that tenacity, sometime brute force recopy in lieu of "clean copy" can eventually restore functionality.

Over"



Man with that many issues I would just delete the three install folders and do a redo. It only takes about an hour or so to install ETO including 1.2 update and it would leave you with a clean non error install and a few lessons learned. No harm in starting over

Just my 2 cents

TW
 
Phil said:
I had thought MAW was a difficult installation through v1.31. The "new" ETO surpassed its adventures in computer patience. I had ETO from last November as encouraged by MAW members . No problems at that time. Yet as my OS died, was restored and migrated from SP2 to SP3, things became more complicated .
I had early problems with ETO 1.0 due to a cockpit error where I failed to note the option selection on the installer. Without checking the continue message, the installation ended abruptly without an installation. My third attempt discovered this "oversight"and success was achieved. But...
I installed v1.20 without hitch, loaded and launched the initialization run at Level 1 (1936), flew a plane to secure the initialization setup and then moved to step 3 or Firepower.
While I already have v1.08 of Firepower in CFS3 and the ETO v1.0 setup did copy those files, I proceeded with the Firepower ETO patch. After a system reboot, a selection of Level 1, the program went immediately on two attempts to a CTD following the introductory CFS3 video.
Recopying, no clean "do over", v1.0 and v1.2, the program now launches and checks out to Level 3 (1943)
In the end I still have reports on launch of SDK violations due to a marginally constructed plane imported into CFS3 at some time, a wandering DPC Korea F51, "gun" and "searchlight" files already in use. These I can bypass. I did have to eliminate the Tempest MkV as it caused a freeze following the CFS3 video. Moving this plane folder from Aircraft eliminated this problem. Annoyances aside, the program now functions, without the Firepower patch. Now comes the careful addition of planes, Spawns, Missions that will not lead to another file conflict or program breakdown in a fragile program setup. At least I now know that tenacity, sometime brute force recopy in lieu of "clean copy" can eventually restore functionality.

Over
Click to expand...

:kilroy:Phil,

ETO was never test-installed over FirePower. A lot of the specifically-modded ETO files will destroy some FP files.

FirePower should not be installed over ETO for the same reason.

Here's your safest and quickest bet:

1. Delete everything: both CFS3 (Including FP) and ETO installs.

2. Reinstall CFS3, update fully (3.1 and 3.1a), then start it up and set everything the way you choose. Thenm shut the game down.

3. Install CFS3 ETO Expansion 1.0 per installation instructions.

Note: Be sure to not lose all five icons that will be set onto your desktop somehow. Personally, I make a folder on the desktop named CFS3 ETO Expansion. Then put those five icons into it.

4. Start CFS3 ETO Expansion 1.0 and set everything the way you want it.

5. Now make sure that ETO is started in Era 1 and exited. Then set the Spawn Selector to 1, Stock Spawn Mode.

6. Install CFS3 ETO Expansion Cumulative Update Rev 1.20. Start it up and make sure everything is set properly.

7. Now install you FirePower into your stock CFS3.

8. After that, go into Program Files/Microsoft Games, and look for your Combat Flight Simulator main game folder and simply re-name it to reflect that it is now FirePower.

9. Now go into your CFS3 ETO Expansion main game folder and look for a file named "MultiCFS3.exe". Then copy it (do not cut and paste, but copy and paste only) into your new FirePower install and run it. This will enable you to create two new folders in your Application Data/Microsoft and My Documents folders. When you run the FP install next, those two new folders will be created in the Application Data/Microsoft and My Documents folders.

10.. Now it is actually safe to install stock CFS3 again, and update it, of course. Now you have a comp[lete FirePower install, an ETO full 1.20 install, and a new vanill CFGS3 install.

11. Now go into your FirePower install anda copy these four folders into your CFS3 ETO Expansion main game folder's aircraft folder: B_17_share, b_17f, B_17G, and B_24J.

12. Make sure ETO is set to Era 1 and exited, and the Spawn Selector is set to 1, Stock Spawn Mode. Now install FirePower_USAAF_Heavy_Bombers_2eto.exe.

You should be good to go now. Good luck and have fun.:d
 
zaraspook said:
towards the end of the eto install program 1.0 do i type cfs3 eto expansion in the box or leave it as is.
Click to expand...


:kilroy:Zaraspook, when the MultiCFS3 starts, yes, you do. Type CFS3 ETO Expansion, followed by several underscores, "_". The line you're typing in that little box has to be the same length as the line right under the little box.:d
 
grizzly50 said:
:kilroy:zaraspook, not all caps: Cfs3 eto expansion_______ :d
Click to expand...

rgr on that
most everythings ok with the eto 1.0 but the mission builder does not start up
i'm using a clean cfs3 udated to the 3.1a
do i need the mission pack update to with the clean cfs3. If not then somethings not right
tried new downloads of eto 1.0 but still cannot get the mission builder to start
 
zaraspook said:
rgr on that
most everythings ok with the eto 1.0 but the mission builder does not start up
i'm using a clean cfs3 udated to the 3.1a
do i need the mission pack update to with the clean cfs3. If not then somethings not right
tried new downloads of eto 1.0 but still cannot get the mission builder to start
Click to expand...

:kilroy:Zaraspook,

Look on your desktop for the MB icon, if it's not there go into your CFS3 ETO Expansion main game folder and look for this file: CFS3 ETO Expansion Mission Builder, not CFS3 ETO Expansion Mission Builder.ico.

Also, check properties on the Mission Builder to see if "Target:" and "Start in:" pathways are correct for your install.

The former is your Mission Builder. Can be a bit confusing.

Note: When using MB, start ETO in the Era you choose to build a mission in and exit. When you start the MB, it will be set to that Era, too.

I hope this helps.:d
 
in my main eto expansion folder there is a url file for mb.when i click it i get a pop up box saying-this application has failed to start because jpeg.dll was not found. re-installing the application may fix this problem.:help:
 
zaraspook said:
in my main eto expansion folder there is a url file for mb.when i click it i get a pop up box saying-this application has failed to start because jpeg.dll was not found. re-installing the application may fix this problem.:help:
Click to expand...

:kilroy:Zaraspook, Google jpeg.dll, and look for a repair program. There several out there. If that doesn't work, delete your ETO (all three folders, from Program Files/Microsoft Games, Application Data/Microsoft, and My Documents, then re-install ETO.

This is the first time I have seen this problem.:d
 
When i left click the cfs3 eto expansion xml file located in the main eto ex folder then right click properties my target says "microsoft games\cfs3eto expansion\\mb\mb.exe"

start in: Says c\program files\microsoft games\cfs3 eto expansion

when i click find target: It sends me to c\program files\microsoft games\cfs3 eto expansion\mb where there are 9 files being--help--common.dll--mb read me--mb--sound.dll--cfsres.dll--imguix.dll--mission builder eula and mb xml document. I tried left clicking all these files but no mission builder would start. When i click the mb file i get a message " this application has failed to start because jpeg.dll was not found.


The eto game itself works fine
just can't seem to get mission builder to run
 
zaraspook said:
When i left click the cfs3 eto expansion xml file located in the main eto ex folder then right click properties my target says "microsoft games\cfs3eto expansion\\mb\mb.exe"

start in: Says c\program files\microsoft games\cfs3 eto expansion

when i click find target: It sends me to c\program files\microsoft games\cfs3 eto expansion\mb where there are 9 files being--help--common.dll--mb read me--mb--sound.dll--cfsres.dll--imguix.dll--mission builder eula and mb xml document. I tried left clicking all these files but no mission builder would start. When i click the mb file i get a message " this application has failed to start because jpeg.dll was not found.


The eto game itself works fine
just can't seem to get mission builder to run
Click to expand...

did u install mb BEFORE you installed ETO? the mb is a seperate download form ms and u must install after installing cfs3.
 
zaraspook said:
When i left click the cfs3 eto expansion xml file located in the main eto ex folder then right click properties my target says "microsoft games\cfs3eto expansion\mb\mb.exe"

start in: Says c\program files\microsoft games\cfs3 eto expansion

when i click find target: It sends me to c\program files\microsoft games\cfs3 eto expansion\mb where there are 9 files being--help--common.dll--mb read me--mb--sound.dll--cfsres.dll--imguix.dll--mission builder eula and mb xml document. I tried left clicking all these files but no mission builder would start. When i click the mb file i get a message " this application has failed to start because jpeg.dll was not found.


The eto game itself works fine
just can't seem to get mission builder to run
Click to expand...

this is exactly whats showing
 
Z

The target: and start in: has to match the path exactly including quotes and case of letters.

target: "C:\Program Files\Microsoft Games\CFS3 ETO Expansion\mb\mb.exe"

start in:"C:\Program Files\Microsoft Games\CFS3 ETO Expansion\"

If the above is your path to your ETO install just copy and paste into the appropriate boxes of your MB.exe.

zaraspook said:
this is exactly whats showing
Click to expand...
 
Which B-24 Variants are included in the ETO (D,H,J...???)

Jack
 
lost in ETO land

Hi, guys.

Okay, so I've been out for a while. Here is a totally dumb question. What the heck is ETO anyway? I have been reading and reading these threads but cannot seem to find out what it really does. I can't even find out what ETO stands for - some sort of acronym I guess? is there some central website for ETO that describes it in detail together with some screen shots, etc? OFF has such a site. What about ETO? I want to know what all ETO does.

Thanks!

SaA :sheep:
 
You must log in or register to reply here.
Back
Top