It is a simple two part stand-alone installation.

Part 1 is here:
160InstallationPart1

The file you download is named "UAW160.exe" and it is a 7-zip self installer.
It must not be run in an existing EAW installation or it will ruin that installation.
Choose a place to run it, on one of your hard disks or maybe on the desktop.
When you run it it creates a "UAW160" folder, which has the minimum files and folders for a working installation test.



Make sure that your joystick is plugged in before you run the eaw.exe.
Otherwise you will get a serious cockpit shake and will not be able to control your aircraft.

When you run the "eaw.exe" (maybe with your own "eaw.ini") it should give you the UAW default ETO theatre and aircraft.
This will be a test to see if your system works

If you only wanted to try the equivalent of the 1.2 ETO theatre and planeset there is nothing more to do

Part 2 is here:
160InstallationPart2

The file you download is named "UAW160Part2.exe" and it is another 7-zip self-installer
Put it in the "UAW160" folder when you know that your Part1 installation is working, and run it there.
You will then have an installation with many theatres and planesets



You can run the "PlaneSetExeTheatreSwitchV3.exe" to choose your planeset, exe and theatre



There is also the "PSM160SpecialSmallSreen.exe" program.
This is similar to the "PlaneSetExeTheatreSwitchV3.exe" program and you can use it as an alternative.
However "PSM" is an abbreviation for "Planeset Maker", and this program allows advanced users to edit existing planesets, or even make new ones



*****************************************************
Added to this thread for users' reference
*****************************************************
Some time ago I received a PM from a player about the "PlaneSetExeTheatreSwitchV3.exe" generating this error message when he tried to run it:

Run-time error 713 Class not registered. MSSTDFMT.DLL

I hit this problem a few weeks ago when I was away in Lyon and I tried to run the "PlaneSetExeTheatreSwitchV3.exe" on my new laptop.
When I got back I made a VisualBasic installer program for the "PlaneSetExeTheatreSwitchV3.exe", which correctly installs the "MSSTDFMT.DLL" file during the installation process.

"MissionEdPackage.exe" is available here:
Mission Editor Runtimes

If you get that error then download it, and run it on your desktop.
This will create a folder named "MedPackage" and in this folder there is a "Setup.exe" file.


Run the "Setup.exe", let it install the program anywhere (as the reason for running it is to install the missing file), but do not let it overwrite newer versions of files with older ones.

Re-boot and the "PlaneSetExeTheatreSwitchV3.exe" should now work.

Jel

Thanks Mr.Jelly

I really do not understand the contention that 1.6 is difficult to install and run. Setting up the basic game is no more difficult than it was setting up the original game from the CD, and it gives you the much enhanced 1.6 European theatre.

If you want other theatres you can have them. But even installing those scenarios already pre-packaged in 1.6, and swapping between them, or swapping available aircraft sets, is far more easy than setting up additional theatres was with the original version of EAW.

Those who have been here long enough will remember the fun with EAW-Stab, and the DOS type managers that went with Paulo Morais' Turning Point in Europe, DOM's Attack in the West, my original Dunkirk, and the Finland and Spain scenarios. Compared, the 1.6 selector is a real doddle.

I had troubles at first installing 1.60..But settled down and followed Jellys instructions step by step..1.60 went in very easily and got the base 1.60 install running well..Then took the next steps to expand it one step at a time and testing after each step and ended up with a well working 1.60 setup..Then had to figure out the interface but again one step at a time and a few questions here and now I'm very comfortable with it all,,Same with other versions..If you want to fly it ,,It's worth a bit of time ..I can do a full install in under 20 minutes,,Not bad compared to installing IL-2 with their BAT mod That takes 45 minutes and downloading 10 torrents and installing each reboot and testing after each one...Installing EAW and the varients is easy if the instructions are followed ,,In the end you have something you enjoy flying ..I agree with Moggy the old stuff was a lot more complicated to get going..Don't need a tutorial I just ask here ,,Don't think new pilots will be turned off ,,I don't see many new pilots flocking here seems it's mainly us old farts humping the load

Just tried the Part1 installation instructions...
First, with Intel NUC (i7 with inbuilt Intel GFX) and Fedora Linux (Kernel 5.2.9/Wine 4.14)
Installation goes OK, and running eaw.exe gets me the options screen with the picture of the 2 planes.
Pressing 'Instant Action' gives slow updating and corrupt GFX in D3D mode, and even slower and more corrupt in software rendered mode.
The Glide option was greyed out, even when I had copied across the glide2x.dll from a working game. Glide is usually the way to go on LInux, so will try it again when I find out how to 'activate' it.

Second, on a Win7 machine (i7 with Nvidia GTX1060 GFX)
Installation OK, but first run results with nothing happening onscreen, but Task Manager shows eaw.exe running and taking up about 17MB of RAM.
I killed that process and ran it again, and this time the screen with the two planes appears, but corrupt. Pressing 'Instant Action' gave a CTD.
Tried again and went to the Graphics options, and Glide seemed to be already selected but as there are no Glide drivers installed with the game it may explain the previous crash.
So, explicitly selected DirectX and this time 'Instant Action' got me into the air. The terrain has a horrible shimmering effect towards the horizon though. Performance seemed good.
Again, would probably need to set up Glide to see the game at its best.
Glide is only relevant for 3D, so why the options screens are so corrupt on Win7 I have no idea, but they 'work' OK.

EDIT:
The corrupt option screens are problematic in Campaign mode, where you have to hold down the right mouse button to find out where to click to do stuff.

Things to consider:

Code was added years ago to circumvent the 7217 error. The trade-off was a stuttery mouse.
Instant missions rely on files generated from single missions. If no single missions have been flown then there will be problems.
For a few years our exes have been using Glide3

The exes run well with Win10, but even I have problems flying single missions or campaigns in Win7 because of corrupted screens, especially the target/home base selection map.
For some reason there is no problem at all with multiplayer.
Those old registry fixes which worked on XP and earlier cannot be applied to Win7.
So in Win7 I use the d3dWindower program to launch the game. There is no stuttery mouse or corrupted screens, and the game runs very well.

Thanks! I've never needed Glide3 before, so didn't have the appropriate dll. I can set Glide mode in Linux now.
It's strange that some of the menu screens are fine in Linux, but others show exactly the same corruption as in Win7.

No doubt I'll have to use Win10 eventually, so will try again then.

Are you able to run the d3dwindower?

I get an error message: can't find TextMap1.str!-1 on ver 1.60. My 1.28E ran fine. Thoughts ????

Happy to help, but I need to know what you have installed, and what you selected that gave this CTD

Win 10 Home
Dell 8400 2.80 Ghz
12 MB RAM
Intel 630 graphics
TM T-FlightStick-X

1.60 install over full installation of 1.28e full version download, the 1.28e was run initially and worked prior to 1.60 install
anything selected on PlaneSetExe and other give me the same error messag

I don't think you need to install it over 1.28e
Just download Jelly's part i and extract it and run part 2 in side that folder and test again..first post in this thread gives great instructions..

Hmmm... trying that now

160 is a stand-alone installation. From the top of this thread:

I re-installed standalone. Part 1 works fine but the default graphic was Glide which would not work. Changed to D3D and it flew. The installed part 2 over that but same error message cropped up. No joy.

The first two pictures in this thread show you how your folders should look after installing part 1 and part 2
If they do not look like that you have done something wrong.
Note that the part 2 7-zip exe has to be run inside the "UAW160" folder created by the part 17-zip exe

The third picture shows you the use of the file-manager that you need to select a planeset, a version of the UAW160 exe, and a theatre.
Did you follow those instructions? If so what did you select before you got the CTD?

Got it ! works . Some minor bugs but totally up and running. Thanks !

Had gone to bed and have woken up to see you've succeeded. Hope you enjoy this vast and varied programme.

I purchased AOE, PAW and EAW practically the day they were all originally released. I beta tested Suncom controllers. EAW was always my favorite but getting all the miscellaneous aircraft into the sim with all the terrain mods is that much more fun.Thanks to all!!!!

You are welcome

Very welcome. Have fun!

Ok, downloaded part 1, extracted to the desktop and run EAW.exe, instantly CTD with the game not even starting. I'm on Win7.

The "eaw.ini" included is set to Glide, and with some PCs this is a problem.
Either replace the "eaw.ini" with one of your own from another installation, or delete it to force the exe to build a new one.

Erased the eaw.ini, same CTD. I'm using two joysticks, can this be?

Try one. What is your graphics card?

A Radeon Vega 5600, tried with just 1 joy, same problem.

This is a bit baffling

Here is a link to an old thread with links to old EAW installs

https://www.mediafire.com/#jdj422smscdgr

Try downloading and installing one or two of these, and let us see what happens

Can't see any links there Jelly just a sign up page

That is quite odd. I run 1.6 from my PlaneSetTheatreSwitchV4.0, via a shortcut to it from my desktop. I also am on Win 7 and have had no difficulties. Ensure you start with the stock planeset and theatre to begin with. Put 1920x1080 resolution in the eawini if you have a widescreen monitor. Maybe even try a reinstall.

Just another thought.

If your force remade eaw.ini has the line:

DisplayDevice=1

try editing it to

DisplayDevice=2

Russ the link should take you to the page where you can download and install 1.29, 1.26, 1.28eFAW etc

I just tested the part 1 download in Win10 and it was fine.
I am about to switch to my small Win7 drive and do the same.

sorry Jelly for me it's just a basic sign up to create an account

This is a link to the thread in this forum

https://SimHQ.com/forum/ubbthreads.php/topics/4453472/older-installations-at-mediafire#Post4453472

Maybe that will work better
Let me know because it works for me

Working well on my Win7 small drive

That's got it for me Jelly..Now i can figure out what versions do or don't run on my machine

The link that did not work for you was the same as the one in the post. That is strange

The first link sent me here https://www.mediafire.com/#myfiles

The second here https://www.mediafire.com/folder/jdj422smscdgr/EAW_129
Looks like the first sent me to my mediafire account..

Nothing, it doesn't work.

What doesnt work? the link or UAW160?

I'm sure it will evetualy work. I can try to help if you want, I been through most of the situtations regarding eaw.

Is the game CTD when clicking on the exe or when setting up a configuration from the external frontend, then launching?

Is there anything else you can point out?

Another possibility: try with no joystick and no "eaw.ini".

try what Jel said above, thats a last ditch effort. But run the eaw.exe directly from the games main folder to avoid any other issues. Then try to run from external frontend next time with no joystick / controls.

Then there is this to consider if you had two joysticks previously



The preferred device is critical if there is more than one controller.
When I have my rudder pedals I must set the J/S as the preferred device.

Don't confuse him Jel with stick issue, until he trys it without his stick first.
To much info

But yeah that prefered stick issue is the result of the way eaw uses them, and autodects them. Alot different then most games, expecialy this day and age.

He was using two and even if one is disconnected the two may remain as selectable in the "advanced" setting. I am not sure, but I suspect that the two J/S thing is the cause of the problem, because it is not the video card.

Oh they ramain selectable even though he unplugged them and restarted his system?

Then maybe goto the device manager window and select detect hardware / changes by right clicking the computer name ant the top. Windows should then realize then that there un plugged. If not unistall the controllers.

Its weird there still showing though.


The video card issue in the last 10 or more years shouldn't be an issue, even the the recent integrated chips should display the menu. (if not use d3dwindower or other wrapper).

Ok, only one stick (is a Saitek X52 HOTAS), no EAW.ini. Same CTD at trying to start EAW.ini.

I will PM you

Why PM him?

I want to see too what the problems maybe and the solution.

This thread was meant to be a tutorial, but these posts are "diluting" the intentions. I will certainly let you know what happens. He has read my PM but not replied.
It suggested that he should try to install the 1.28eFAW download (link provided) to see if that caused the same problems.

I have had a reply from Stratos and he could not launch the 1.28eFAW set-up, so it looks as though he cannot run any version of EAW at the moment.
He will try with no joysticks.

I just used one of my Win 7 drives to fly with Lolo at GameRanger.
The in-game screenshots were fine, but the others were corrupted like this:



I will do some more work, using my other Win7 drive, and wrappers to see if I can find a solution.
It is not critical but sometimes it is nice to be able to record the set-up.

Geez looks like mine before applying Marks fix