As I can only test things on a Vista laptop and a nvidia card, and a Win 7 desktop with a Radeon card I am requesting feedback from people who have installed the EAW 140RV1 public release version.
If it is working please let me know, with details of you operating system and graphics card.
If it is not, then tell us what goes wrong and when, again with details of you operating system and graphics card.

If people post, then others reading this thread can see if their set-up is similar to one already listed.

Working fine on my HP laptop and a GeForce 8400M GS card.
Working fine on my acer desktop with Windows 7 and a AMD Radeon HD 6450

Installed all here and running sweet...Amd quad core,,AMD hd4200 on board video,,win7 64 pro. Small problem on my part if i try to unzip eto etc to my install i get error53 file not found if i unzip the individual set and copy them in all works well but that's my error not the programs.
Loose nut on the keyboard is the technical term

Hello,

it was easy to install and it seems to work without problems. Though, i made just three missiony for now.

The fps on my dual core PC is rather low but stable between 20 and 30 fps.

Good work!

Tank you Tony.


Greetings,

Knegel

Danke Ralf
What operating system are you running?

I have re-installed Win8 on a drive and upgraded it to Win 8.1 which has enabled me to check some curious observations that ShoGun mentioned.
First of all I get a CTD "pic not found" with RV1. I do not know if this is driver related or not (do the 64 bit drivers still support 16 bit?).
The CDF version works better, but there is no mouse for making selections in the more recent versions.
The mouse is visible in some earlier CDF versions, so maybe something got lost that does not bother Vista or Windows 7. A lot of back tracking will need to be done to find out.

Hi tony, as i told you in a pm, in my desktop running a Win7 64b and a GTX 560 vcard I get those problems too. With the D3D Windower I can select options but i get the "pic not found" trying to launch a mission. Without the D3D is simply impossible to do anything in the menus (no mouse, and a flashing screen). More strange is that I've got the same problem on my oldest installations which were working fine till now on my PC. Did a quick test with just RV1 on a laptop (win7 64b + ATI card) and seems to work with no problems.
So must be a problem with a recent update in my Nvidia card. I'll do further tests on my girlfriend's PC.

Hi Trindade
If the only change is to an updated driver then logically it must be a driver problem.
I suspect that the new drivers may have dropped support for 16 bit graphics. Maybe you can roll back the driver?

Hi Tony,

the 110´s and the Ju88´s (similar cockpit??) stopped to work on my end. The loadingscreen move normal to the right side, but when the cockpit should show up, the game ctd just with a message that it stopped to work.

Other twins like P38, do17 and Blenheim work normal, so i guess its somehow cockpit related.

Greetings,

Knegel

Tony The newest game to work in windows 8.1, with all screens working and game runs
great. 1.40 Test Install EAW140V09[8Plane,EAW140V09[16Plane],EAW140V09[30Plane]
No mouse lag Works Great


marv

Thanks!
I will try to use the V09 30plane version as a new base.

Tony, your not starting up in software mode in Win8?

That used to cause the pic not found error I think.

i just install 1.40basicrv1 but my mouse unable to move..can anyone help me? im using windows 8.1

Thanks

Hi woki,

I had that same problem, not sure if it was that version, but was related to my new video card drivers.

The change of the "eaw.rc" file several versions ago is the source of the problem.
Why and how this file affects the mouse movement, and why the problem did not occur in earlier versions of Windows is a complete mystery. Shogun first noticed it.
The upshot is that I made four new versions with the previous "eaw.rc" file in them. They work in Windows 10, 8.1 and earlier versions of the operating system.
I have just re-uploaded them.

In the "140BasicRV1" folder at OneDrive there is a "Win8.1NoCDF" 7-zip which will generate the "140BN.exe" (new map version) and the "140BO.exe" (old map version).
These two files need to be put in your "EAW Versions" folder.

Similarly in the "140RV2CDFVersion" folder at OneDrive there is a "Win8.1CDF" 7-zip which will generate the equivalent exes for the CDF version.

Hello MrJelly
i try using your new 140BO and 140BN for win8.1 but still no success and i just got an idea using .exe from 1.28E or 1.29 and it works but i dunno if it's work propperly

This is confusing.
According to what you wrote you have installed "1.40basicrv1".
This installation has no CDF files in the folder as the exe does not use them.

A 1.28e or 1.29 exe needs all of the CDF files and will crash if even one is missing, so it can not work.
If it does work for you then you do not have the correct set up.
So tell me more about your set-up, what the problem with the new exe was, and exactly what you did to get the problem. Pictures would be helpful




I have really stopped work on the 1.40 no CDF version. The 140 users are using the 140RV2CDF version.

Jel

Just as a check I switched to my Windows 8.1 hard drive and tested the "140BN.exe"

For windows 8,8.1 and 10 you need to install DirectPlay for EAW to work