Manually Install   1-21-2018

Written By: MarkEAW
Other Info by: Wudpecker, McGruff_GS, Sydbod, vonOben, VBH, Knegel, LLv34_Snefens, Adrian, Russ

Download Links:


About Custom EAW Modifications

 Is The Game Already Installed | Update Drivers | Manually Adding EAW
Clean Installed Folder For v1.0 

About v1.0 | About v1.1 | v1.1 Updater File List | About RUN ONCE

Safe Keeping | Game Shortcut | Compatibility Mode/Tab Settings Warning | Run The Game
v1.2 Updater File List | Clean Installed Folder For v1.2
Saving Some HD Space | Do Not Move Note

Difficulty - Flight | Difficulty - Combat | Display | HUD | IAS and TAS
Controller Setup | EAW.INI and Joystick | Force Feedback (FF) | Flight Sensitivity

Setting The Screen Resolution | Frames Per Second | Anti-Alias

A Quick Note About The EAW Demo
HexEdited Patches | FXEXE Patches | CodeGroup Patches

Some Of The Errors Listed
Wrapper Programs - Win2000 or WinXP | Wrapper Programs - WinVista/7/8.1 | Wrapper Programs - Win10
D3DWindower v1.88 Wrapper Program | Menu Colors Messed Up (DD Reg fix) | nGlide Wrapper Program
Conflicts With The Compatibility Tab | Sound Problems | \Program Files sub-folder
Game Crashes To Desktop CTD Solutions

Win2000 | WinXP

EAW Downloaded from EB Games | Other Known Video Problems | Win95/Win98/WinME | D3D.DLL Missing Error
About Registry Entries Produced by Windows | EXE File Names | Having Multiple Copy's of the Game
Faster Performance by Registry Tweaking



This document was written to get EAW manually added to your system. To supply technical support information on how to get the game to run properly on any version of Windows (For your Info: 32 bit or 64 bit systems will run EAW.) Depending on which Windows OS you have you may have some issues with the game. Those issue are covered in this help document.

About Custom EAW Modifications:
Before you get started, you need to know there is currently three types of custom modifications. There is the custom HexEdited enhanced replacement eaw.exe's , the FXEXE machine level manipulated special effects mod, and The CodeGroup source code modifications such as EAWv1.28x or higher versions. (Note: Install instructions for the CodeGroup archives is different than the other game types.) I have included near the end of this document some information regarding these modifications. If your eager to learn more about those three types of patches mentioned, before proceeding any further in this document, go ahead and jump down to the 'MODIFICATION PATCHES' section near the end of this document first. Then come back here after your done reading the appropriate subjects to guide to with installing the CD EAWv1.0 to v1.1 and/or v1.2.


This section will get you started first with some good advice then onto copying and pasting files from your EAW CD to your hard drive. It will also show a folder list of what v1.0 looks like. There is some talk about the different versions that you may want to keep on your hard drive (multiple, but different 'installs').

Is The Game Already Installed:
So if you have installed the game previously from the CD with SETUP.EXE or AutoInstall, uninstall EAW with the uninstaller, restart and come back to this document here and continue reading (This is to avoid problems on a modern Windows OS).

Update Drivers:
Before adding the game to your system, you'll want the latest drivers and updates for your Windows OS, Video Card, Sound Device, and Controller Device. (If available).
Small Note: In the past, some technical docs may have suggested you roll back or use older drivers for your hardware, this help document does not cover such situations as on modern Windows you need the latest drivers and OS updates for the game to work properly under compatibility layers and fixes etc....

Manually Adding EAW:
Manually 'installing' or as the case really is, adding (copy and paste) EAW solves all kinds of hassles and problems for different Windows Versions and different Game CD types. You do not need to have an automated installer, install the game for it to operate correctly. The game does not require any game registry entries to be present...other than those provided by the Windows OS itself, and those are created once the game is added to your system...

To manually add EAW withOUT running the automated installer (AUTORUN.EXE or SETUP.EXE) from the CD follow these directions:

  • Create your folders where you want the game on your HD. (Do NOT use the \Program Files sub-folder to place your game folder, this will cause Crashes to Desktop on modern computers and other problems on WinXP. Put it on the root of C:\ or on a second hard drive or partition if you have one.) Note: The default game path and folder names are shown in the table further below.
  • Then highlight and copy over only the files listed in the table below to your new game folder. (The rest of the files on the CD are just for use by the automated installer.) Copy these files for a full 'installation'; "eaw.exe" , The "\Music" folder, "d3d.dll", "SMACKW32.DLL" , "Dsetup.dll", "chatline.txt" , ALL "***.CDF" files.
  • Once your done Copying and Pasting, make sure none of the files are marked as read-only since copying them directly from the CD usually results in this. (There is a file that the game will want to write too and change. The other files need the read-only lifted from them for future updates.)
  • Do NOT run your game yet, See instructions below this table for updating from the CD v1.0 to a newer version.


Clean Installed Folder For v1.0 (for reference)

\MicroProse Software\European Air War\
3d.cdf		4,896,269	10/17/1998 03:50
chatline.txt	438		10/8/1998 23:03
COCKPITS.CDF	20,899,837	10/16/1998 00:28
d3d.dll		130,560		10/14/1998 20:44
DATA.CDF	1,433,420	10/18/1998 18:10
Dsetup.dll	127,488		7/29/1998 18:00
eaw.exe		1,367,040	10/18/1998 19:32
FLT.CDF		39,540		10/18/1998 18:10
FONTS.CDF	960,576		10/15/1998 02:28
GRBRIEF.CDF	9,438,292	10/15/1998 02:30
Menu_eng.cdf	37,760		10/16/1998 17:57
Movies.cdf	298,809,288	10/15/1998 02:49
Music.cdf	1,452,428	10/15/1998 02:28
PIC.CDF		26,334,148	10/15/1998 02:31
readme.rtf	27,987       	10/18/1998 19:10
SMACKW32.DLL	96,256		6/9/1998 09:21
SOUND.CDF	1,203,659	10/15/1998 02:28
SOUND16.CDF	2,501,836	10/15/1998 02:33
SPEECH1.CDF	10,431,783	10/15/1998 02:51
SPEECH2.CDF	11,943,211	10/15/1998 02:33
SPEECH3.CDF	12,407,240	10/15/1998 02:29
Sprites.cdf	250,040      	10/16/1998 00:25
TERRAIN.CDF	7,942,132	10/15/1998 02:30
Text_eng.cdf	168,543		10/18/1998 05:02
UKBRIEF.CDF	10,101,180	10/15/1998 02:33
USBRIEF.CDF	11,970,136	10/15/1998 02:32
WSOUND.CDF	9,310,061	10/15/1998 02:50
Wsprites.cdf	25,140,369	10/15/1998 02:50
AmerProm.bgm	5,523,468	8/26/1998 21:59
BritProm.bgm	6,513,556	8/29/1998 15:10
Captured.bgm	9,071,660	8/31/1998 15:30
Drum1.bgm	1,459,968	9/30/1998 09:58
GermProm.bgm	6,513,796	8/31/1998 11:02
HallOFam.bgm	7,056,968	9/1/1998 16:47
MenuMus.bgm	7,836,020	8/14/1998 12:00
Rescued.bgm	5,082,520	9/30/1998 10:02
ViewObs.bgm	9,408,380	9/16/1998 14:05
YouDead.bgm	11,813,424	9/21/1998 15:45





Updating the game with the official MPS patches can be done with either v1.1 or v1.2. Some players will want to keep different versions 'installed' on their hard drives in order to compare game play experience or basic comparison among the available versions. This would naturally allow you to see the changes MicroProse (or others) have made to the game, thus making the changes more prominent and notable. This is strictly an optional course of action. Read my v1.1 and v1.2 Help Document along with the MicroProse Patches Help Document for more specifics on those versions.

About v1.0:
(*If you intend to keep a copy of stock (out of the box) EAWv1.0 around, then for safe keeping so you don't need to install v1.0 again, optionally copy your game folder you copied/"installed" from the CD some place else, and rename it to a NEW folder name, or Burn it to a CD. This will be your backup full install of v1.0.)

About v1.1:
(*If you intend to keep a copy of v1.0 and update it to v1.1, and keep that version around, I suggest you read the section below titled 'UPDATE TO v1.2' and substitute where the text reads v1.2 with v1.1 patch program, those instructions will teach you how to patch to v1.1. Then for safe keeping so you don't need to install v1.1 again, optionally copy your newly patched game folder some place else and rename it to a NEW folder name, or Burn it to a CD. This will be your backup full install of v1.1.)

eawv1-1 Patch Files (These are the files patched by the Official v1.1 Updater):

3D.CDF 		4,895,593 	12/15/1998 14:27
d3d.dll 130,560 12/17/1998 14:30
DATA.CDF 1,433,420 12/21/1998 11:29
eaw.exe 1,411,072 1/11/1999 18:43
FLT.CDF 39,540 12/31/1998 15:59
FONTS.CDF 1,067,664 12/16/1998 13:01
grb_031.snd 105,644 12/15/1998 11:36
Menu_eng.cdf 37,876 12/22/1998 19:55
readme.rtf 35,003 1/8/1999 00:18
TEXT_ENG.CDF 168,738 1/11/1999 09:58
V1.1 Details.rtf 16,801 1/10/1999 21:35

Before updating to v1.1 or v1.2 it has been said in the past that you need to run v1.0 of EAW once so it creates the eaw.ini file in the games root folder so when you use the official patch updater program it can find it and use it to patch the game.
I have not had any problems installing the v1.2 patch over a v1.0 clean fresh installation by following the steps outlined in this document, which does NOT instruct you to 'run once'.
I've found that the official v1.1 and the v1.2 updaters just need the eaw.exe to be present for the patch installers to extract their files.
See my MicroProse Patches Help Document for information on what the v1.1 and v1.2 patches change or fix within the game.




Now that you have V1.0 manually installed/added, you may proceed to update to v1.2 with the official MPS patcher. This is an upgrade to the out-of-the-box game which you should install since v1.2 includes the most recent official multiplayer fixes and is generally a good idea to use that version. (However at this point you may want to update only to v1.1 for your own reasons, such as testing or examining the older versions game play. Just substitute the v1.2 text with v1.1 below.)

Note: If you have the 2001 re-release by Infogrames CD (their logo is on the CD), the v1.2 patch is located on your CD in the \Patch folder, other players will have to download it. (The Infogrames v1.2 patch is identical to the MicroProse patch and includes everything that the older v1.1 has. The v1.1 patcher is not on the Infogrames CD, you will have to download it, if you want it).

  • Copy the official MPS v1.2 patch exe into your EAW game folder and run it. (On WinVista/Win7/Win8 You may need to run the patch program as an Administrator to get it to work correctly. Windows 10 seems to apply an automatic compatibility fix to the file upon its first run. There is a long delay after running it so wait about 10 to 20 secs for the patch updater program to show that something is happening.)
  • The patch will look for the closest eaw.exe file and it should find your v1.0 too patch (This will happen almost instantly once it appears to be working, this is because you ran it in the game's root folder directly.)
  • Once patched, delete the v1.2 patch exe (eawv1-2.exe) file from your game folder. (You no longer need it and its just in the way.)

Safe Keeping:
For safe keeping so you don't need to install v1.2 again, optionally copy your \European Air War\ game folder some place else and rename it to a NEW folder name or Burn it to a CD. This will be your backup full install of v1.2. (Also its always nice to have a stock version of 1.2 running someplace else along side a newer or older version, for game play comparison!)

Game Shortcut:
Go back to your original 'install' (the one you will be playing from for now) and you can create a desktop shortcut to eaw.exe by right-clicking the mouse on the eaw.exe file and choosing Create Shortcut. Put this on your desktop.

Compatibility Mode/Tab Settings Warning:
Do NOT run the game using a Compatibility Mode that is found In the Games Shortcut Tab settings for any reason. See the section of this document titled 'PROBLEMS RUNNING THE GAME' under that title find and read 'Conflicts With The Compatibility Tab' area for further troubleshooting information about Tab settings and why they should not be used. (other than in Win2000).

Run The Game:
Now that you followed and read all the above instructions, run the game for the first time to the Main Menu (do NOT enter the Flight Screen), this will create a new file called eaw.ini in your games folder that contains most of the games configuration settings. Exit the game and read on in this help document. If the game won't run right now, then read the section titled 'PROBLEMS RUNNING THE GAME', then come back here and read on.



eawv1-2 Patch Files (These are the files patched by the Official v1.2 Updater):

3D.CDF 		4,895,593 	12/15/1998 14:27
d3d.dll 130,560 12/17/1998 14:30
DATA.CDF 1,433,420 12/21/1998 11:29
eaw.exe 1,430,016 7/29/1999 15:24* EXTRA.SPT 3,924 4/13/1999 17:54*
FLT.CDF 39,540 12/31/1998 15:59
FONTS.CDF 1,067,664 12/16/1998 13:01
grb_031.snd 105,644 12/15/1998 11:36
Menu_eng.cdf 37,876 12/22/1998 19:55
readme.rtf 44,954 7/26/1999 10:38*
TEXT_ENG.CDF 168,743 1/8/1999 11:13*
V1.1 Details.rtf 16,801 1/10/1999 21:35
*Files that v1.2 patch update. Other files are the same as v1.1


Clean Installed Folder For v1.2 (for reference)

\MicroProse Software\European Air War\
3D.CDF		4,895,593	12/15/1998 14:27
chatline.txt	438		10/8/1998 19:03
COCKPITS.CDF	20,899,837	10/15/1998 20:28
d3d.dll		130,560		12/17/1998 14:30
DATA.CDF	1,433,420	12/21/1998 11:29
Dsetup.dll	127,488		7/29/1998 14:00
eaw.exe		1,430,016	7/29/1999 15:24
EXTRA.SPT	3,924		4/13/1999 17:54
FLT.CDF		39,540		12/31/1998 15:59
FONTS.CDF	1,067,664	12/16/1998 13:01
grb_031.snd	105,644		12/15/1998 11:36
GRBRIEF.CDF	9,438,292	10/14/1998 22:30
Menu_eng.cdf	37,876		12/22/1998 19:55
Movies.cdf	298,809,288	10/14/1998 22:49
Music.cdf	1,452,428	10/14/1998 22:28
PIC.CDF		26,334,148	10/14/1998 22:31
readme.rtf	44,954		7/26/1999 10:38
SMACKW32.DLL	96,256		6/9/1998 05:21
SOUND.CDF	1,203,659	10/14/1998 22:28
SOUND16.CDF	2,501,836	10/14/1998 22:33
SPEECH1.CDF	10,431,783	10/14/1998 22:51
SPEECH2.CDF	11,943,211	10/14/1998 22:33
SPEECH3.CDF	12,407,240	10/14/1998 22:29
Sprites.cdf	250,040		10/15/1998 20:25
TERRAIN.CDF	7,942,132	10/14/1998 22:30
TEXT_ENG.CDF	168,743		1/8/1999 11:13
UKBRIEF.CDF	10,101,180	10/14/1998 22:33
USBRIEF.CDF	11,970,136	10/14/1998 22:32
V1.1 Details.rtf16,801		1/10/1999 21:35
WSOUND.CDF	9,310,061	10/14/1998 22:50
Wsprites.cdf	25,140,369	10/14/1998 22:50
AmerProm.bgm	5,523,468	8/26/1998 17:59
BritProm.bgm	6,513,556	8/29/1998 11:10
Captured.bgm	9,071,660	8/31/1998 11:30
Drum1.bgm	1,459,968	9/30/1998 05:58
GermProm.bgm	6,513,796	8/31/1998 07:02
HallOFam.bgm	7,056,968	9/1/1998 12:47
MenuMus.bgm	7,836,020	8/14/1998 08:00
Rescued.bgm	5,082,520	9/30/1998 06:02
ViewObs.bgm	9,408,380	9/16/1998 10:05
YouDead.bgm	11,813,424	9/21/1998 11:45



Saving Some HD Space: (Optional)

  • To save some hard drive space and remove clutter you can move or delete the files: readme.rtf , V1.1 Details.rtf and SOUND.CDF (This last file contains  8-bit sounds for slow computers, you won't need them on modern computers as you should be using the 16 bit sounds).
  • You also can download what is called an 'empty' Movies.CDF file that replaces the in game movies to save 284mb of space. (most likely the videos will not play correctly or at all anyhow on NT Windows.)
  • And finally there is the newer and smaller Dsetup.dll file that can be replaced to save a bit of pre game memory. (not at all necessary).


Do Not Move Note:
Now since you have run the game once, you will NOT want to move your game folder, for compatibility reasons with the Windows OS and it's Registry. This is important and more details about this can be read under other sections of this document; specifically go to the section titled SOME FINAL WORDS and read the 'About Registry Entries Produced by Windows' topic if you wish to learn more, and then come back here to continue on.


Now go onto the next section that's titled; 'GAME CONFIGURATION', There are a few things you should do with-in the game before playing (before seeing the flight screen), I'll go over them briefly in that section below.




This section of this help guide will quickly show you some of the more important settings in the game. Start EAW and open the configuration option screen. (For more details please read the official EAW User Manual).

Difficulty - Flight
Fly full realism! When you first start it's tempting to choose all the easy settings: ie stalls off, blackouts off etc. Bite the bullet, turn all the hard settings on (everything on the right should be selected) this will allow you to learn to fly properly. You will have problems at first with stalling and spinning, with a little practice, You will get the hang of things. Almost all games online are played "full real" so you need to get used to it.

Difficulty - Combat
Same again: all the hard settings, ie everything on the right.

Don't leave the units on default: choose metric or English - whichever you prefer. If you don't, during online play you'll get distances displayed sometimes in meters, sometimes in feet - depending on the host's settings. That will be a bit confusing for you. Select the one you prefer now.

Turn HUD on. Yes it's not very historically accurate to use it but absolutely crucial information. This shows your airspeed and altitude (bottom left in green) as well as your target's speed and altitude (bottom right in red).

IAS and TAS:
Choose IAS (indicated airspeed) rather than TAS (true airspeed). (A long technical explanation for this is the airspeed gauge actually measures air pressure and then works out your speed from this. At high altitude, where the air is much thinner and pressure lower, you are actually going much faster than at an equivalent indicated airspeed at low altitude.

As a combat pilot, your main concern is the air pressure over your wings. This gives you lift. If you use TAS (true airspeed) you'll notice that, at high altitude, your plane stalls much earlier than it does lower down. If you use IAS, the (indicated) stall speed stays pretty much the same so you don't need to bother about compensating for alt.)

Controller Setup
Select these settings (top left): joystick, rudder, throttle, mouse. Your joystick might not work otherwise. However your flight controls may require special configurations...But if you don't have rudder controls of some type, you will want to get them, whether its rudder pedals or a twist handle Joystick...(see my Joystick and Remappable Help Document for in depth advanced controller trouble shooting and configuring.)

EAW.INI and Joystick:
There is a line in the [CONTROLS] section of the eaw.ini file: "Windows Joystick= ". The options are 0 or 1. If your joystick doesn't work with the game you could try changing this setting. Eaw.ini is in the folder where you installed the game (..\MicroProse Software\European Air War\). You open it with Notepad, You could put a shortcut to this file on your desktop since you'll need to edit this file again at a later time and probably often for other things.

Force Feedback (FF):
If you've have a force feedback stick, you can set the FF gain in controller setup. You should most likely set your FF effects in your stick software to default while you set them from within the game - and come back to them to fine tune afterwards. Fiddle about and test offline until you've got settings you like.

Flight Sensitivity:
Set Flight Sensitivity to around two thirds for now. This controls how sensitive your stick will be with the Flight Model. (You may also have stick software which allows you to adjust stick sensitivity, this is different than Flight Model Sensitivity.)

Later on, once you've tried the game out a bit, you can take the time to do some flight testing to get the sensitivity just right. You must have sensitivity high enough to give you full control deflection: if it's too low you won't be able to turn as fast as you should (a very bad thing in a dogfight). However, if it's set too high the plane will be very "jerky" and it'll be hard to line up a shot - especially in 'pilot full zoom mode'.

Also, to be on the safe side, you will also want a back up of your eaw.ini file so you can pluck out of it your control settings and remapped keys if anything goes wrong.




This section will briefly direct you to some graphical options you have regarding the game and video card settings.

Setting The Screen Resolution:
EAW looks pretty good straight out the box, but can look incredible if you fiddle a bit. By default, EAW plays in 640x480 screen res. In EAWv1.1, Higher Resolutions where introduced. They produce much smoother looking flight window graphics, so donít get stuck using the default....

You set the custom resolution in a file called eaw.ini in the games root folder. You open it with notepad and manually enter the Width and Height (There is no in-game slider or setting). See my Inside The EAW.INI Help Document in the 'Graphics' section for more information on the possible resolutions, drawbacks and the advantages of changing the resolution.

Frames Per Second:
The size of the screen will effect the Frames Per Second. You want the frame rates ideally at 30FPS or more but above 15FPS the game will operate correctly, although a bit slow. If the game is running smoothly when you enter dense bomber formations your doing well. (Although there is no FPS display in v1.2, in source modifications v1.28 and above CTRL-G gives the FPS in the top right hand corner.)

Most modern graphics cards have an anti-alias setting in their control panel which improves things even further, usually setting the Anti-Alias of x2 will be enough to loose the jagged edges on planes. (you may need to do this in the "Override Mode") Don't expect many of the more advanced video card settings to work in EAW, the DirectX version of the game is too old (DX5/6) to take advantage of them on Modern Video Cards and there newer drivers. There is no fix for this in any version or code modified EAW game. To Learn more, see my Known Bugs And Feature Ideas Help Document for the details.




This section is to explain the different types of modified and available EAW games.


Quick Note About The EAW Demo:
The official EAW Demo is really a software only rendered game and allows you to play for 5 mins at a time, sometimes longer depending on how well you do in combat. It's available as an English or German download. See my Community Addons and Files Help Document for some extra words about the EAW 5min Demo.


HexEdited Patches:
There are several HexEdited replacement eaw.exe's available, including the so called unofficial 1.2a enhancement version and the unofficial v1.26e patch updater with fixes and some game data updates, the later is considered to be a 1.2 executable regarding compatibility. Also most if not all HexEdited exe's included a NoCD option built in. Those you apply over a previous official patch or newly added full clean "installation" of the EAW game. See my HexEdited Patches Help Document for further details and install instructions for each of these custom "upgrades" and special NoCD Instructions.


FXEXE Patches:
The FXEXE/AFB/The Final Cut special effects update in concern with Windows compatibility is considered to be a v1.2 executable, and the archive contains its own readme with install instructions. The FXEXE does not require your game CD to play other than for you to first copy the files for a full 'installation', patch to v1.2, then you overwrite some of the files with the new ones in the FXEXE archive. Please read this Manually Install Help Document to get EAW v1.2 up and running first. See my FXEXE Patches Help Document for additional information, including some install directions.


CodeGroup Patches:
There are several unofficial Coded 'patches' that have new bug fixes, features added, and a lot of community game data in them. These full blown game data mods usually come with very large individual add-ons and theaters of operations. Most of these 'patch archives' are even considered 'Standalone' where you don't need the game CD to install nor run the game; they will not require you to add the CD files to your computer before hand. To install any of the CodeGroup source code modifications, please refer to their readmes if available, along with some of the information you read in this help document for usage directions to insure proper operation. See my CodeGroup Patches Help Document for more information on the changes and details of those versions.




This section is very helpful to troubleshoot a Modified EAW version as well as running the stock EAW.


Some of the Errors Listed:
(These are typically related to graphic problems)
Here are some of the errors messages and conditions you could receive when trying to run the game:
"not a valid win32 application".
"Sorry, EAW will not run under WinNT".
Crash to Desktop(CTD).
Your menu screen colors are messed up.
Your menu screen is garbled or tearing.

The following information will help you get around them.


Wrapper Programs - Win2000 or WinXP
If using fully updated versions of Win2000 or XP and the game won't run normally even after you properly have configured your Windows version. (Win2k requires some extensive but effective manual OS configuring to use the built in Compatibility module to get EAW to run. WinXP only needs some guidance (see the section at the end of this document titled 'WIN2K AND WINXP OPTIONS' for further help with Win2k or WinXP without the need for wrappers)), otherwise try using special programs called Wrappers to run the game for an overall workaround of any errors.

The Wrapper programs that other EAW pilots have used are: D3DWindower, DDWrapper, DXWnd and nGlide. Use only one of them at a time. For the most part these programs run EAW in a window, although some can be set to run full screen. Further below I mention settings you should use for the D3DWindower Wrapper Program to run EAW properly. I also provide information on the nGlide Wrapper program.

Wrapper Programs - WinVista/7/8.1:
If using WinVista/7/8.1 and the OS is fully updated, the game can run "natively" in full screen withOUT wrappers and with out problems, usually faster than on Win10. However, Some of you may just have one or both of these following small issues; Your games menu screen colors maybe messed up or you may have garbled (tearing) menu screens.

For the garbled screens; try using special programs called Wrappers to run the game to correct this type of error. The Wrapper programs that other EAW pilots have used are: D3DWindower, DDWrapper, DXWnd and nGlide. Use only one of them at a time. For the most part these programs run EAW in a window, although some can be set to run full screen. Further below I mention settings you should use for the D3DWindower Wrapper Program to run EAW properly. I also provide information on the nGlide Wrapper program.

If the game is running properly with out using a Wrapper program and the only problem is colors of the menu screens are messed up, I highly suggest you to use only a special registry fix designed for those Windows versions, see the topic below titled "Menu Colors Messed Up (DD Reg Fix)" for more information on how this is beneficial to you.

Wrapper Programs - Win10:
The Custom external D3D wrapper Programs at this time of writing will not work in Win10 with EAW properly...(under Win8.1/10 I prefer the use of the OS built-in compatibility fixes and forgo using the D3DWindower or other program).

All tests show that Win10 applies its own Compatibility Fix or Mode to the eaw.exe when the game is first launched. This will run the game with a Windows OS Compatibility Mode (DWM8And16BitMitigation) and it will run properly, (The fix offers mitigation for applications that work in 8/16-bit display combo color mode because these legacy color modes are not natively supported in Windows 8.1/10).

If you ever needed to remove the OS set Fixes to strictly use a DirectDraw / Direct3D Wrapper to run in Windows 10 the entries to remove are listed below. (You do not want to run a wrapper plus an OS set Fix together, they will conflict with each other and most likely give you the 7217 error, The OS set Mode Fix are known to conflict with the DXWnd wrapper and may do so with other D3D wrapper programs).

These are the Win8.1 and Win10 Registry Additional Compatibility Mode/Fix Entries:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

These are the Values (Note that the folder path to your game will be different):
Value Name: D:\MicroProse Software\EAW12\eaw.exe
Value Data: DWM8And16BitMitigation

and/or (setting for All Users):
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

These are the Values (Note that the folder path to your game will be different):
Value Name: D:\MicroProse Software\EAW12\eaw.exe
Value Data: $ DWM8And16BitMitigation

(See Microsoft's reference: Application Compatibility Toolkit (ACT) Technical Reference (Windows 10) for many more fixes you can enter to tweak out EAW. There is a list for Win7 Win8 and WinVista as well). I have tried many of these, see the section titled ' SOME FINAL WORDS' and the topic 'Faster Performance by Registry Tweaking' for my findings to improve the game performance.


D3DWindower v1.88 Wrapper Program:
If you need to use the D3DWindower wrapper program With Win2000/XP/Vista/7 to correct the colors or get rid of garbled menus or run in a Window with Borders these are the minimum settings needed for EAW to run properly (settings tested with WinVista/Win7). If your going to use this Wrapper, make sure you first set the Direct3D setting under the DisplayDevice setting in your eaw.ini file. For Direct3D use a value of 1 or 2.

D3DWindower Settings:
  Under Options Common - Width and Height set to 0. (This will load the games menu screens in there natural size (640x480 or 1024x768 depending on the EAW game version your using) and the flight screen of the game will go with the eaw.ini resolution setting you entered.)
  Under Use windows mode - Checked. Then go over too Window mode options - DirectX1-7 checked, DDraw Color Emulation checked, DDraw Color Convert checked (if you don't check this one you'll get the 7217 error), Everything else is unchecked.
  Then over to foreground control - Nothing checked.
  Then over to Direct Input - Nothing Checked.
To launch EAW just double click on the icon you made within the D3DWindower program.


Menu Colors Messed Up (DD Reg Fix):
On Windows Vista/7/8.1 the game can run "natively" in full screen withOUT wrappers, however in Vista and Win7 you might just have menu screens colors messed up. For this you can use a DirectDraw Windows Compatibility Registry Fix Patcher. (Windows 8/10 users don't need to use these DirectDraw Registry Patching Programs as Color and Menus display properly, so no fix was developed for them.)

The registry program patchers worth mentioning are the "DirectDraw Compatibility Tool" by Galogen and "w7ddpatcher" by Mudlord,  read the readmes that come with them to understand how to use them. These create automated registry patches for the menu screen color fix without a Wrapper program needed. Its considered a 'light' alternative, and works well with minimal overall overhead as this Registry Fix will only run the DD 8-bit menu screens under a compatibility profile and not the actual D3D 16-bit in-flight action screens. Note: Once the Reg Fix patcher program writes the information to the registry for a specific eaw.exe, you should not move that particular game folder or exe.

How it Works; Those entries are understood by Windows Vista and Win7 as they are determined by the exact eaw.exe used. (The 'patching' programs gather the games filename, the process ID, and sets the registry keys accordingly. This variable, along with the needed flags makes a compatibility profile in the Registry for Windows Vista and Win7 to use with that application, only. It won't affect other parts of your registry or other programs...For instances a EAW v1.0 exe and a EAW v1.2 exe are determined by the patching programs to be different specifically by various attributes of the exe, and Windows reads those differences when launching the EAW Game.) This could be an issue with single game folders having swappable eaw.exe's like the CodeGroup's versions...

Important; Do NOT double up on the DirectDraw color/garbled menus problem workarounds. Meaning don't set one of these Registry fixes and then run a Wrapper program with DirectDraw(DD) color correction setting as well, this will cause problems. You only need one or the other. If you made a mistake and need to delete these entries in the registry file, here are there locations written by each Reg Fix program:

The DirectDraw Compatibility Tool writes here:

The win7ddpatcher Tool writes here:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\DirectDraw\Compatibility\European Air War
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectDraw\Compatibility\European Air War


nGlide Wrapper Program:
This is an another wrapper, but this one is for the 3Dfx Glide mode in EAW (translates Glide to D3D, for modern gamers who do not have an old Voodoo video card), some EAW users may find that the game runs faster in Glide mode then in D3D mode, so there may be a use for Glide Mode for many users who are having low Frames Per Sec in D3D mode alone. nGlide works for many WindowOS versions, including modern versions. If your going to use this Wrapper, make sure you first set the Glide value under the DisplayDevice setting in your eaw.ini file. For Glide use a value of 0.

Another reason to use nGlide with EAWv1.0/v1.1/v1.2 or any other version when using an Nvidia video card is that nGlide will produce the missing Direct3D mode Horizon Fog graphics (Fog Tables are incompatible with Nvidia's modern drivers). Then I would suggest to use nGlide to restore the Horizon fog. (see side note next few paragraphs down).

You can have nGlide installed along side a D3D wrapper program, so you can switch back and forth between D3D and Glide anytime you want, before game launch of course. (I wouldn't recommend having another Glide wrapper installed at the same time as nGlide though, this will cause problems. At the time of this writing, nGlide is the most compatible and up to date Glide wrapper for EAW use. If you have an unsupported WindowsOS, you may need to find another Glide Wrapper program to use...)

A side note:
Using nGlide and EAWv1.0/v1.1/v1.2 or any other version of the game that has not been Coded to use the more advanced 'Glide API v3.0' will be seen in reduced available colors, since those un-updated exes use the older 'Glide API v2.43'; These are typically game versions under EAWv1.28e(Feburary 2016 build), and only display a fixed 8-bit 256 colors in its flight screens, rather than the many more selectable colors available in Direct3D.
More recent Code modified versions of EAW (starting with Feb 2016 for EAW v1.28e, 1.29 and 1.40) will be using the improved Glide API version, this will display the game in 256 colors with a selectable 24 bit color palette.

nGlide v1.05 supports window mode by pressing Alt+Enter to create the window border while in game.


Conflicts With The Compatibility Tab:
Do not run the game 'As An Administrator' or in Compatibility Mode in the games shortcuts Compatibility Tab in any version of Windows (except Win2k), its not required for the game to work properly and will cause problems if they are enabled.
Problems that will arise include conflicts with a D3D Wrapper program that will result in a 7217 error and can cause a few other issues with your Controllers, Your Joystick may not be detected by the game properly resulting in the axis for movement not working, only the buttons will function, your Keyboard can possibly become unusable during the game as well. It has also been found that the custom frontend launchers on the CodeGroups source code modifications would give an error when you click the final button: "FLY!" ... So make sure you don't use the shortcut Compatibility Tab (uncheck all of the items) before running the game, this only needs to be done once.


Sound Problems:
It's quite common for people with Win9x and WinXP that have better sound cards to actually have sound problems where some or all game sounds don't work. You can fix this by turning sound hardware acceleration down a bit, or off altogether. (see my Sound Help Guide Document for more advanced and detailed sound troubleshooting.)


\Program Files sub-folder:
If you followed my manual install directions up above, you placed your game in a folder other than \Program Files. If you did not you maybe wondering why the game is Crashing to the Desktop (CTD) as soon as you load the game with errors like "European Air War Has Stopped Working" and "A Problem Has Caused The Program To Stop Working".

This is because by installing in the \Program Files folder, Windows Vista/7/8/10 expects to have any file that a program writes too, like the eaw.ini file, to be in the \AppData system folder, however EAW expects to find the file it writes too, the eaw.ini file, to be in the games root folder. Windows will cause a CTD under these circumstances. You may also notice if you happen to get pass the initial load of the game that none of your game settings are staying where you set them, including your controls key assignments. This is for the same reasons. You may not even have an eaw.ini in the games root folder as a result. Windows often stops EAW from writing and updating the correct copy of the "eaw.ini" file.

The above reasons are why NOT to place the game in the \Program Files sub-folders as these problems will always happen. So move your game elsewhere as mentioned previously in this help document, such as "C:\EAW" or on a separate partition or hard drive.

(Note: This could be tied to the "User Account Control" or UAC built into windows; UAC can stop EAW.exe from writing too your disk as a precaution. In other words if EAW.exe tries to modify it's own eaw.ini file without your intervention, it is prevented from doing so. However I highly recommend you do NOT turn off your UAC. It's better to just move the game out of the \Program Files sub folders.)


Game Crashes To Desktop CTD Solutions:
These are hopefully all the known CTDs for EAW, besides those error messages mentioned in the previous areas of this help document which you would need to have read.

  • Blank Screen or CTD When Loading Game.
    If you still have the full MOVIES.CDF file and not the blank movies.cdf file in your game folder. You may get a Blank screen when the game first loads. Hitting the ESC key should get you passed it. You may also get a CTD. This is because the SmackVideos are for playback with the 8-bit code in the games exe.
    Solution: open your eaw.ini file (this file is in your game folder and opens with Notepad) and change the line PlayIntro=1 to a value of 0.
  • Game CTD When Loading Game.
    Your using a in-game resolution that isn't supported by your monitor or graphic card.
    Solution: Change the eaw.ini Width and Height settings to something your system supports natively.
  • Game CTD When Entering Flight.
    You have set the Display Device to "software" mode and your system doesn't support it (bad 8 bit support).
    Solution: Goto "Configure game->Graphics" set "3d renderer" set to "3d mode". You can also change your display device in the eaw.ini. To change which card/vid mode EAW uses, follow the steps below;
    1. In your European Air War folder, open the file called "eaw.ini" with notepad.
    2. Scroll down until you find the section "[Graphics]", then under that the line that reads "DisplayDevice=".
    3. Changing this number will alter the display mode based on the numbers above.
    4. The next time you run the game, these settings will be in effect.
    -2 for OLD SOFTWAREMODE (CPU Powered, no D3D)
    -1 for D3D SOFTWAREMODE (CPU Powered)
    0 for 3Dfx GLIDE API
    1 for PRIMARY D3D CARD
    Note: I do not know the differences of values 1 and 2, but the game on occasion seems to do a new detection and picks the value of 2 more often.
  • Game CTD Just Before Entering Flight.
    You don't have a Joystick plugged in, but the setting for "Force Feedback=1" in the file.
    Solution: Open the eaw.ini and set "Force Feedback=0" You can find this entry under the headline [CONTROLS]
  • Game CTD Just Before Entering Flight.
    This could be the result of not having your Joystick plugged in or detected by EAW correctly, when previously it was plugged in when you launched the game last time. Note: If you launch the game without your Joystick plugged in or it's not detected properly, you will loose all assigned buttons.
    Solution: Plug in your Joystick and configure it correctly, then try running the game in flight again.
  • Game CTD When Launching To Fly.
    There is a common problem with the savedata due to a changed scenario; For an example: If you fly a default game mission in a Spit IX (Slot 11) offline the settings are saved in a file named "Default11.msn" which is placed in the "Savedata" folder, with details of the mission in it (targets, bases, support aircraft, enemy aircraft etc). The next time you fly a Spit IX the eaw.exe reads that file and uses it for the default mission settings. However, if afterwards you fly a custom add-on that uses the same slot, then the eaw.exe tries to use the settings in the "Default11.msn" file, this is when the problem occurs. Since you switch scenarios, and the values in the "Default11.msn" file no longer make sense as they do not apply to the new add-on, this will crash the game. Note: Also some of the "last game" settings are also stored in the "eaw.ini" file
    These may also cause a problem when a change of scenario is made.
    Solution: Delete all of the "DefaultXY.msn" files from "Savedata" folder...
  • Game CTD After A Duration In Flight.
    It could be the "Extrasquads = " setting in the eaw.ini is set too high for your computer system, as the extrasquad setting requires a lot of memory usage.
    Solution: Use a smaller value when setting it like 1 or 2, if that doesn't work try 0.
  • Campaign Crashes Game After A Mission.
    You may get a CTD in Career Mode after a mission has ended. This is because the SmackVideos are for playback with the 8-bit code in the games exe. If you still have the full original MOVIES.CDF file and not the blank movies.cdf file in your game folder.
    Solution: To avoid this change the Video Playback=1 setting in your eaw.ini file (this file is in your game folder and opens with Notepad), change the value to 0.
  • Game CTD When Loading Game.
    You install/patched a newer version of EAW over an older incompatible installation.
    Solution: Delete your eaw.ini file, then let a new one get created when you run the eaw.exe again.
  • Game CTD When Loading Game / It will never run
    If you ran into a big problem (this doesn't happen for normal use, nor often, so don't worry) because something went wrong and the game won't run anymore (after it was working for a duration at one point). You may be experiencing odd errors or a quick flash and the game CTD. Meaning the game no longer runs and will not ever run again.
    To correct this you may need to go through the entire Windows OS Registry searching for entries of "eaw.exe" and/or "EAW" and/or "European Air War" etc... and remove them so you can start over.
    I had to do this once before myself and I'm no expert, and resulted in the game running again. This is because when ever you delete/rename a EAW game folder or the game has been effected by other compatibility problems, the old Registry Entries that where left over can be detrimental to new 'installations' of the game where it won't run/launch. For more information about how Windows adds registry entries go to the section below titled SOME FINAL WORDS and read 'About Registry Entries Produced by Windows'.


*For more advanced technical information, please read the end of this document, under the section further down, titled 'SOME FINAL WORDS'. Perhaps that area of this help document will guide you if the above info has failed in helping you properly.




This section is to explain how to run EAW on Win2000 or WinXP without Wrapper programs by using the provided Microsoft built in compatibility options. You may find you have better performance than using a Wrapper Program. (Note: Most of the following information has been researched but untested by me, if you have easier steps to take, please fill me in by contacting me).


Windows 2000:
Follow the directions in this install guide document, plus read the following; Win2000 and EAW will work with at least SP2 (or above) installed with some separate manual setup and configuration. W2K is the only version of Windows that requires the use of the Compatibility Tab Mode setting and then a special manually set setting of the built-in compatibility parameters are needed to use the Joystick in game. Note: Multi-player will not work on Win2k, there is no fix.

More Notes About Win2000 and ACT.

Since older application may have problems running properly on Windows 2000, like EAW does initially, backward compatibility needs to be adjusted to help address the problem of it running on a foreign version of Windows. So Microsoft created the Windows Application Compatibility Toolkit that allows one to learn how to run or code an old application on a newer Windows version, like EAW going from Win95 to Win2k. You'll need the Microsoft ACTv3.0 program package; (act30pkg.exe 23,882KB which was published by Microsoft for download on 4/02/2003) (the newer versions don't run in Win2K, so only use the older v3.0 Toolkit package).

The compatibility fixes (shims, as they are called) for programs are contained in a file database named sysmain.sdb, which in is located in the C:\winnt\apppatch\ directory (note you need to install the Application Compatibility Toolkit to find this file in your Win2k directory). This will have EAW fixes and a Win95 compatibility layer built in to it. However, as an optional course of action you may want to obtain a better compatibility layer, the Win98 layer from the database on a WinXP machine. This may run EAW better. You just copy over the database file from the WinXP machine sysmain.sdb to your Win2k machine. (don't forget to first rename the smaller Win2k database sysmain.sdb file to something else).

Note. It's unclear if these application fixes listed in the systems database are active, or if they need to be moved to a custom database, and then installed to become active... You might need to try this if you want to enable the automatic preset modes found in the sysmain.sdb file. It is fairly simply to make a new database, just cut and paste modes and fixes from the original system database. I found that you cannot modify the existing system database fixes/modes (but you can only disable them), although you can modify custom databases.


To enable the standard Compatibility Mode that's available using EAW's program shortcut:

  • Log on as Administrator
  • Right-click the EAW game shortcut, and then click Properties
  • Click the Compatibility tab.
    (This tab appears only if the Compatibility-mode interface has been properly enabled on the computer)
  • Click to select the Run in Compatibility Mode check box to enable Compatibility-mode support for the program.
  • Click Windows 95 (or Win98, if you have added the WinXP database) compatibility mode in the drop-down box.
  • Click OK to save the changes.
  • Double-click the shortcut to run the game.

To apply the Joystick Fix correction to the Win95 Compatibility Mode (or the Win98 Mode, if you selected it). Use the program QFixApp.exe or Microsoft Application Verifier v2.50 (appverif.exe) that is included with the Microsoft Application Compatibility Toolkit v3.0. The following isteps below will show you how to use a custom application fix, rather than the preset fix, which is necessary, as this will allow you to select the newer Win98 Mode (if you have added the WinXP database) rather than Win95, it will also show you how to fix the Joystick input along the way.

Compatibility Administrator;

  • Click "New" button,
  • Select new custom database,
  • click on database menu, mouse over "create new", click application fix.
    A Wizard opens up;
    -Give your fix a name (such as EAW Fix)
    -Vendor "Microprose Software"
    -Select program file location ( eaw.exe for eaw)

Compatibility Modes Wizard;

  • Select Win95 (or Win98, if you have added the WinXP database) Compatibility fixes.
  • Find the "emulate windows joystick" fix
    -Then UNCHECK this box to disable the emulate joystick fix.
    -Click next
    -Click finish
    (you have now created a new custom database, containing two application fixes).
  • Press the Save button to save database
  • Right click on the name of your database.
  • Select Install.
    (The database should now be found under installed databases, and should be active.)
    (EAW should now work in Win2k, and your Joystick should now get recognized by EAW as well.)
    (Multiplayer still will not work on Win2k however, there is no fix for that.)


History Brief of Past Fixes for EAW in Win2k.
(Some of these where too difficult or didn't work properly)

The following information is presented here just to show what methods have already been tried in the past, it does not provide steps on how to use them. These methods never solved all the problems and therefore where abandoned.
-One older method to fix EAW was to patch the v1.2 eaw.exe so that the built in OS check would think it was running on a Win9x system. For some this would let you, sometimes, run the game.
-Also there was the APCOMPAT.EXE program used to run EAW. This was a program located on the Win2k CD in the Support subfolder. The program allows you to 'emulate' the settings found in Windows 98. Doing so it would use more overhead. This method was abandoned for the better method, as the steps outlined in this document guide you.
-Finally there is another custom set up to allow EAW to run under Win2k, this consisted of a 'SetWin95.cmd' program (and other files) to run before launching eaw.exe and it would use more overhead. This method was abandoned for the better method, as the steps outlined in this document guide you.
-A major problem in the last two methods resulted in the games EAW.INI file being written to the C:\winnt\ system folder (instead of being in the correct location, inside the games folder). This prevented any in game settings to be retained, including control key assignments. One way to correct this was to place or install the game to the \My Documents folder instead of the \Program Files folder.


Windows XP:
Follow the directions in this Manually Install Help Document, plus read the following; WinXP and EAW works best with at least SP1 installed as it comes with a pre-configured compatibility module and Win95 and Win98 profile parameters for EAW (The module is called Application Compatibility Update). Insure your game executable is indeed filename EAW.EXE for the module to effectively work with the game, WinXP expects that filename for this game. As this help guide has instructed elsewhere: Do NOT use the Compatibility Tab to run the game (other than in Win2000).




This section is to explain some more of the problems running the game properly. To provide some technical know how, such as how EAW behaves with the Windows OS and it's Registry.

EAW Downloaded from EB Games:
If you purchased the 183MB download setup install file program from EB Games back in 2006/2007, this installer program will not run under any operating system other than one of the Win 9x operating systems, even when setting the compatibility tab for the installer program. You will need to be able to install EAW (using the Full Install option) on a Win 9x system, then burn the resulting EAW folder to CD or DVD. Take the disc to your system running Windows 2000 or Windows XP and copy the EAW folder to your hard drive.


Other Known Video Problems:
There are a a whole bunch of other problems with the graphics portion of the game, especially from the 8-bit built in frontend/The menu screens and corrupt/tearing of the briefing map screens etc. These problems will be less likely on a Win10 system. To Learn more, see my Known Bugs And Feature Ideas Help Document for the details.


The stock game is designed for Win95. Installs and runs.


D3D.DLL Missing Error:
For some reason the Windows OS likes to remove the d3d.dll file from your game folder on an occasion... This prevents the game from loading up. Simply replace the dll again with a copy of the same one, the version of the dll that your using. It should remain once you replace it...


About Registry Entries Produced by Windows:
The EAW game itself does not put any entries into the registry. EAW does not use any information that is stored within the registry for its own purpose. The only entries in the registry are those produced by the Windows operating system. The operating system produce changes in the registry whenever you run, move or duplicate the EAW.EXE file on the hard disk. These entries are used by Windows for tracking, compatibility and running the game itself.

There is an entry produced by the operating system that shows the path to every EAW.EXE and this value will be updated automatically. As far as I can tell any entries in the Registry for EAW are based on the full file/folder path to a eaw.exe. (The cache location used on the HD is different for each file/folder path name.
Meaning that a file called "C:\MicroProse Software\EAW12\eaw.exe" is a totally different file than the one called "C:\MicroProse Software\EAW10\eaw.exe") It's unclear if Windows itself checks the eaw.exe file for any specific attributes similar to when someone uses a custom DirectDraw registry color fix.

Moving a game folder that you have already run a game in, is considered moving a game that the Windows OS has set Registry entries for already. Once you have moved the game folder contents to a new location, or renamed the folder the game is in, you should clean out the Registry of the old location. A build up of Compatibility Registry entries for the game, may at some point cause the game not to load and run, no matter where it is on your system. See 'Game Crashes To Desktop Troubleshooting' topics under the section PROBLEMS RUNNING THE GAME , and read the topic titled 'Game CTD When Loading Game / It will never run' for more details on this rare occurrence.

If you have to, to remove a Compatibility Layering issue do the following:

From the taskbar, click on the Start button

In the Search or Run field type REGEDIT or REGEDT32, Press the Enter key on the keyboard
Click Yes in the User Account Control dialog (if necessary)
Navigate to:
HKEY_CURRENT_USER and then Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Click Layers to select it
You may find multiple EAW entries listed. If multiple eaw.exe are listed, make sure you select perhaps the entry that is disallowing launch.
Press Delete on the keyboard
Click Yes in the Confirm Key Delete


EXE File Names:
Remember to get the best performance, stability and compatibility out of the game and Windows, any of the specially modified or even unmodified EAW "exe's" available from the EAW community will have to be renamed to just "eaw.exe" before you run them. (Note: Most available modified exe's are the US English types.) WindowsXP (and perhaps Win2000 too) are very sensitive to the EAW naming as they have built in compatibility fixes/shims (not the same as compatibility mode you find in a shortcut Tab) and they look for eaw.exe.

Other Windows versions like Vista/7/8 may require the same thing, but are not as sensitive, However, unless you really know what your doing, it is just a good rule to follow through all Window versions. Otherwise you'll have problems running the game properly. Not to mention many registry entries will have to be rewritten by the Windows OS for every name of a exe you have run, which will eventually cause problems.


Having Multiple Copy's of the Game:
You can have as many copy's of EAW on your HD as you want, especially when you manually install the game. You can have two separate folders of each official patched versions of the game on your hard drive, a 'dual installation' (or triple, or even more). Just make sure you patch one game folder to v1.1 and the other to v1.2. Then you can have even more, separate game folders of any version.

Some of the Windows compatibility fixes will set them self based on the location (or folder path) to the eaw.exe. The DirectDraw registry fixes are based on the exact exe used. So it's best once you RUN or Apply a FIX any particular EAW game folder, that you leave it in that location. Otherwise you may need to reapply a Windows fix...

Also if you want to save HD space, you only need one FULL EAW installation. For the other game folders use a small installation (remove the CDF files) and then link the small installations to your full installation in the eaw.ini. (see the next paragraph) The small installations are only a few MB in size without add-ons since they do not need the duplicate cdf files. This is the preferred way for some pilots for installing many EAW game folders and gives a very clean main folder because you never need to add any add-ons to your full installation.

To set the folder path to your full installation, open your eaw.ini file in the SMALL installation of EAW and find the Debug Path= line. Add in the full path to your FULL installation of EAW, such as; Debug Path=C:\Microprose Software\European Air War\Full\ That will allow the small game folders to source from the full.


Faster Performance by Registry Tweaking:
The Application Compatibility Toolkit; ACT is a tool that allows a person to test different compatibility settings of a application on the fly. In this case it will be used to research remedies for EAW. ACT was used by Microsoft to find adequate Compatibility Fixes to run EAW on Modern WindowsOS (As far back as Win2k, with the older 3.0 version of ACT. The current ACT v6.0 will only support back to WinVista and comes with the Assessment and Deployment Kit (ADK) package as an option to install). Usage instructions will have to be read at the Microsoft web site as I do not guide you here.

The ACT database that comes with Win10 has included a Microsoft pre set Fixes which I have listed below for reference. These are automatically applied upon running any eaw.exe. (Note: These pre set fixes are stored in the database, WINDOWS\AppPatch\sysmain.sdb.)

These are the Fixes that Microsoft has set to run the eaw.exe application on modern WinOS in the database.(FILE_DESCRIPTION="European Air War" , COMPANY_NAME= "Microprose Software").
They are:

  • 8And16BitCopyOnFlip - I think this setting is defunct, left over from previous database. I couldn't find this setting anywhere on its own in the ACTv6.0 toolkit.
  • EuropeanAirWar - Not sure why they included this, defunct, left over from previous database?
  • IgnoreAltTab - Apparently the game doesn't work well with Alt Tab switching so they disabled it.
  • Win95VersionLie - This will get around the "Sorry, EAW will not run under WinNT" error. I changed mine to Win98, in hopes that it would run better.

Plus Windows (at least Win10 does) automatically adds a Mode when EAW is first run. This is in addition to what's in the database mentioned above. The additional Modes/Fixes are found in the Windows Registry, under the Value Data entries:

  • DWM8And16BitMitigation - This Additional Compatibility Mode Layer allows the game to run with correct colored menus and hopefully no corrupt menu displays. I can't seem to permanently remove this entry in the registry as its created once eaw.exe is run, every time for every eaw.exe location. You'll find this Mode on Win10 does slow the games flight screen down a little bit (slower than say on a native OS). However, I have found a few ways to squeeze a few more Frames Per Second out of the EAW in spite of this Additional Compatibility Mode, read on.


In light of Microsoft improving ACT and adding in more Compatibility Fixes and Additional Compatibility Modes, I decided to test EAW with the new ACT to find more settings to see if I can improve performance and add speed increases. I tried to find Fixes rather than Modes as the Mode settings seem to demand more to run the game. These are the Fixes/Modes I found to improve the game. I have found you can apply the new Modes or Fixes directly to the registry, which seems a lot easier for me to understand than making my own custom database. (Note: Custom databases need to be 'installed' for your windows os to use them, at this point I have not gone that route, so I use the registry Value Data to apply my fixes I choose, once I tested them in the ACT Tool).

This is the Win8.1 and Win10 Registry Additional Compatibility Mode/Fix Entry Location:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers

These are the Value Data you enter as a single line:

Value Data:  DWM8And16BitMitigation 8And16BitAggregateBlts 8And16BitTimedPriSync

The line above gained 5 Frames per second (from 38 to 43 on my machine): (Currently the best bet for fast gaming)
1) Game Menus display correctly; remedies menu color corruption and tearing , Additional Compatibility Mode.
2) Increase speed a bit under 8/16 mitigation from #1 setting / HUD stops flashing (but removes pointer)
3) Fix mouse pointer so it shows up. (but slows down setting #2, still more FPS than without #2)

And this one:

Value Data:  DWM8And16BitMitigation Disable8And16BitD3D

The line above gained 26 Frames per second (from 38 to 64 on my machine): (However you loose DirectDraw Acceleration and it moves and squishes the HUD and Radio Subtitle text. Primarily useful for testing by a programmer only at this point).
1) Game Menus display correctly; remedies menu color corruption and tearing , Additional Compatibility Mode.
2) Increases speed a lot (but distorts text in flight screen) (there maybe a Mode or Fix that can retain some of the speed, while fixing the text. However I don't think there is one from my incomplete research, you can try to find one and please let me know if you do solve this issue).


Since the game seems to have a few quirks left, I'll continue my experiments when possible and write in the help doc the information I discover.

The remaining issues with stock EAW that may be possible to cure with ACT:

-Menu/Map and Briefing Screen Corruption: ?Some win7 users still get menu tearing? with just DWM8And16BitMitigation applied?
-Standard Menu Screen highlighted/hover colored fonts that get distorted when they switch, especially with AA set for the graphic card. Check the FXEXE Main Menu, since it uses HQ its more noticeable there.
-Menu selection speed is too fast in Mission Selection Screens, I suspect this is due to hardware acceleration for DirectDraw: ?Maybe NoGDIHWAcceleration will fix it?