I for one would like some information about that error I get it when trying to Install any thing from scratch except Jell's 1.40

OK a history lesson
When EAW was being written hard drives were tiny and space was at a premium.
So Microprose came up with ways to save space, including using selection screens such as "Main2.pic" being their own form of compressed 8-bit PCX files.
Routines in the exe decompress and display them.
However, the exe also has a routine that checks that the user's graphics card and driver can handle 8-bit graphics. If it cannot the exe CTDs with the 7217 error message.

This became a real problem for EAW users back in 2000 because when they updated their systems the many of the newer cards only supported 16-bit graphics.

Will Gee helped us with a work-around that kicked in and tricked the exe into thinking that the card supported 8-bit, and displayed the screens, even though a slight downside was stuttery mouse movements. His code was added to the original 1.28 release, and has been included in all subsequent versions.

The d3d windower also circumvents 7217 somehow.
Windows 10 appears to have some routines of the same ilk.

What I suspect is happening now is that some of the newer cards only support 64 bit graphics and Will's work-around was for cards that supported 16-bit and not 8-bit.

Thanks Tony now I at least understand what it means and how to try to get her running if it shows up again.

@Tulaig

Don't use a wrapper program in Win10 for Direct Draw screens,
Run the eaw.exe directly by clicking on it. Win10 should create a compatibility fix for it. Try running it twice that way.

Well guys, now I am back to my original problem which is I don't get the right side of the screen again and my mouse cursor as soon as I move the mouse disappears....if I click the left mouse button CTD and this happens when I use Mr. Jelly's or the original EAW.exe options.

I haven't updated my install to the newest yet, so I don't know if its an install issue or not.
I never had the problem your having, never read anything about it either.

Can you get a screenshot of the problem, maybe that would give some clue. Try to use windows print-screen key (this is suppose to copy to the clipboard, then you paste it somewhere) or the Windows snipping tool (the later is under windows accessories).

Beyond that I'm out of ideas. Anyone?

I'll see what screen snaps I can get so you can see my frustration. I am stymied! Like I said, the only thing I am running different from any of you guys is I am using the displayport port from my graphics card to my monitor and corresponding cable.

That's so weird.

The clipping of the screen, anyone, would that be a refresh problem?


Are you using a multiple desktop?, or is the desktop size in your video card settings something other than 'no scaling'?

Now of course it would be full screen without the bottom tray showing, but you get the idea...and the mouse disappears. single desktop, single monitor and my desktop is set to 3840X2160

I want to thank all of you that have participated in chasing this down, I have figured it out. in Win 10 I had my size of text at 175% otherwise at 4K I would have needed a magnifying glass to read anything...as soon as I dropped it to normal, logged out and back in voila I was able to log in and take care of business, now I just have to figure out the joystick controls.

Wow, I was going to say the font size could be effecting it, next. Glad you figured it out.

The fonts used in EAW are not scalable, and this is possibly the cause

Glad to see you get her working Tulaig.Lot of work but worth it.

You guys have convinced me to stay clear of Win10!

XP RULES!!

Given the problems that you have had with XP that is far from the case LOL.
With the security flaws I would not touch it with a bargepole, unless I had no other choice.
If you analyse Tulaig's problem it is straightforward. he has a 3840x2160 pixel monitor, twice the size of the one I use at home. So he did something to make his text more readable. We do not know why, at this stage, but it affected the running of EAW. Undoing it fixed the problem, and it may not be a problem specific to Win 10.
My desktop PC is running EAW in Win10 very well indeed.

Tried Win 10 and somehow EAW stutters with or without windower and i couldn't correct itFrame rates and smoothness are great in Win 7.Also everything I got runs in 7.Eventually I'll have to get a new machine so Win 10 is inevitable

I know crazy that something that minuscule can create such havoc...but thanks to you guys and a bit of perseverance we figured it out and anyone else that comes after me that is experiencing these types of issues we know to point them in that direction for a look!

Again, thanks everybody for the help and hanging in there to get this baby running!

Tulaig

I'm pleased to know that