A player with corrupted screens in Windows 7 found it difficult to get his PC to use the D3DWindower, (which fixes the problem for me in Win 7).
For him the game was unplayable.

I came up with an alternative, based on some past experience.
Years ago I had corrupted screens, but I could see enough to select multiplayer. When I did, the protocols screen was not corrupted.
What was even more interesting was that when I returned from multiplayer the previously corrupted screens were no longer corrupted.
We never found out why, but it worked and several people used it

In UAW160 we have a library of scripts for multiplayer games, and also a version of the exe that goes straight to the multiplayer section without the normal selection screens.
Loading this exe, and a script allows the user to fly a "host-only" mission which is not actually multiplayer, but the equivalent of a single mission game, with no corrupted screens

I noticed this also many years ago on my first EAW flights with a real old ATI video. I noted there is a difference in whether the mainscreen does the color rotation routine or not.
If there is a network connection then the color is not cycled, etc.
BY color cyle I mean the 'stunning 256 colors' rotation mainscreen menu effects.

For coders;
Its my theory that its the color cycle function which AFAIR is done by either the v refesh or hertz shifting that is the problem. Probably just commenting out that function (not sure the name - look it up in the code or the docs I have posted) or even a hex edit could stop the cycle.

When EAW starts the main menu shows and there are various ways to get into game menus
example from the EAW_13_04x Docs - this is by no means exclusive there is a lot of other stuff that goes on and many pics illustrate different paths that occur when triggered by the game menus, functions, etc
https://eawonlinux.neocities.org/images/_c_net_lib_8c_acd0047c984144a6e9c4b960dfddb7686_icgraph.png


Also you might note stuff occurs at the end of a flight or mission, campaigns etc. . This shows also some interesting stuff about the campaign end that checks for a movie etc. To solve that other error complained about by some Gog forum people, you could most likely change or fix those areas.

I always thought it had to do with directdraw and the refresh rates. Jumping about screens to come back to a previous screen, must be the result of some initialization of DD.
But i really don't know for sure.

Update:
The post I made about a language problem with the desktop was related to this thread.

We got everything working for host only missions without corrupted screens, but the later discovery had me wondering about the user's lack of success in installing the d3dwindower.
He went back and successfully installed it on his C drive and not the desktop. When he used the windower to launch UAW160 with a full version of the exe (not the special multiplayer only version) it ran with no corrupted screens, as it does for me in Win 7.

He is a happy camper