Got windows 10 installed on my lap top,,Got a 1.26 version copied over and getting the 7217 error..I would appreciate any help to get it up and running on Win 10..I've looked around and really would welcome current information..Thanks for any replies

Try to right click the eaw.exe , goto compatibility settings and select ANY window os, hit apply and okay.

Wait a second,

then go back to right click and uncheck compatibility settings and apply then okay.



Win10 is suppose to automatically set an internal setting on, but for some reason it doesn't always. Its in my help docs.

Thanks Mark..I'll give it a go in the morning,,Totally overlooked it at your site,,win 10 is strange territory for me..I've rode them all out since DOS 3.0 and each new version of windows takes a bit of getting used to

I failed in casual efforts with EAW 1.2 and 1.6 to run on my Win 10 machine. When I get back from vacation I am going to really get serious about getting them working.

Yeah OG that's my dilemma Got 1.60,,a working 1.29 and Aces over Europe working in win 7 but Win 10 right now is foreign to me ,,But I know the community will get me straight ..Getting too old for this stuff LOL

NP Russ. The hint is on my troubleshoot help doc, under the 'problems running the game'

The workaround was a quick addition to the help doc, and I tried to place it in a good location.
Anyway theres two ways to add that compat layer that win10 uses.

They I described it up there or you can manualy enter it into the reg.

Again Win10 use to add it on its own, but after a few os updates I think they removed the automation.

Following up on the this issue you have or had with Win10?

Do you need better details from me on how to get Win10 to set the intial compatiblity layer?

Just remember its not an OS Comp Layer, its really just a 8/16 bit working reg fix.

This is of potential interest to me as well, so tagging along.

Okay, then

goto link:
https://eaw.neocities.org/troubleshoot.html#winreg

Scroll down to the bold underline topic: Windows 8.1/10 Compatibility Layer

There is a brief description and manual registry values to enter, or the quick method outlined at the end of that topic.

Unfortunately I can't help you troubleshoot that much - EAW worked with my windows10 system without a hitch in D3D right off the bat.
I can add though, and this may be useful to some, having very recently attempted the glide route (which does look better vs D3D, tbh) is that DgVoodoo did not work with my system at all - it just wouldn't do glide with it at all, no matter what settings I used or played around with. However, I was able to get it working just fine when I used NGlide instead, for what it is worth.

I have yet to install NGlide on my win 10 system, and that's my next thing to do in order to get EAW running properly. Have tried most of the suggestions offered above. Concur that the sim "looks" better with NGlide vice without.

nGlide i belive now supports AA settings in the video control panel, and some other settings get passed. Its probably best to use nGlide over 'semi'- native DX support from win10.

There are other APIs you can use too. I use GL as a means to play the game, cleans up the old terrain shimmer nausing effect. I use a old dll and config fille from 2004 I think it was, that works well.

I havn't found a option/setting yet with any of the other Wrappers or API's to clean the shimmer up unfornatly, and no one reported any find either.

I've mentioned somewhere that the terrain shimmer can be removed, at least in Windows 7 and in Direct X, using 4xMultisampling combined with 4xSparseGridSupersampling. There is also an old farm terrain tile that shimmers which can be fixed using an alternative farm.

Oh yeah, I remember now SkyHigh.
(Your old thread)
https://SimHQ.com/forum/ubbthreads.php/topics/4451547/1


If I recalled it took some reg tweaking via a nvidia tweak tool or something with similar name.
I'm not sure thats practical for everyone as I used that tool before, but didn't have much a clue what i was doing. There-ore I couldn't suggest it for everyday use or begin writing how to use it on my help site

Is there a way to adjust those two settings via the Nvidia Video Control Panel? If so then i'd like to know more.

EDIT:

I tried several MSAA and AA Transparency override settings in the Video Control Panel, but Couldn't get anything but smoother edges on planes. (jagged edge lines). 2x Override AA 4x Supersample Trans AA and MFAA ON. All this didn't produce the smoothed down terrain shimmer and it only slowed things down considerably.

I guess that super sample your talking about is I guess only in that tool.



EDIT2:

I given NVIDIA Inspector another shot, but I can't find either setting under the EAW Profile in that program. Could you fill me in here?

(I'm using the latest tool and video driver.) - If I have to roll back the vid driver its not worth it to me.


EDIT3:

Using the NVIDIA Inspector and after finding the settings, I was unable to reproduce the effect. I had terrain shimmering at all times.

A Side note I tried to break the 30fps in DX mode but could not.

Yes, one needs NVIDIA Inspector. As far as I can remember, I had to create my own profile in it, not sure if it comes already installed in the programme. I don't know anything about your driver, I'm using a fairly old one (maybe 2017). Works well for me, but I also do not get greater than 30 fps in DX. However, it is a very steady rate and seems perfectly smooth to me.

Can you provide a download of a EAW profile from the Nvidia Inspector program with the correct settings?

I have no idea how to go about that.

Haven't used nvidia inspector yet but will give it a shot later today

Well, I'm a #%&*$# fool, and finding that getting the ancient Crimson Skies having ALL its' internal Graphics features unlocked just might require Gfx cards far above the usual ones required for EAW use. For example can play Crimson Skies with internal Gfx features enabled (finally)--But only with a modern computer, and very modern Gfx card, to wit: Nvidia 2060 OC PRO. NOT cutting edge, but not to far from the edge, either.

All my EAW installs on my win 7 machine, using Nvidia 730 Gfx card work OK. That's pretty ancient computer, but probably not to different from what many legacy computers are using, Using SSDs.

Now, on my very modern Win 10 computer, I have a complete copy of my entire Win 7 drive, selected as a "Slave" drive. When I go to that drive, and select a particular game, I can play it through the very modern Gfx card. Playing some games directly through Win 10 is problematic, and so this thread.

IOW, I can play all versions of EAW on Win 7 computer. Unsure that same versions will play "through" Win 10. Can't play same versions of EAW on Win 10 computer directly.

Granted, my situation is a 'different' one, and ought to take a back-seat to newbies trying to get EAW running in any Opsys. Just mentioning it for future reference.

Call me confused.

I'm confused.

It almost sounds as if your launching EAW in win10 off a win7 drive. This does not equal a win7 launch since Win10 is loaded, Win7 OS on your 2nd drive is just a casualty,.

But maybe I'm misunderstanding you and all your posts about this. IDK.