OK, I'll look for the patch to V1.2, since I have the original disk.

Suggestion in the section concerning configuring DXWnd;

You have written:

Aero Handling, Aero compatible mode and Optimize for Aero mode, checked

This was a bit confusing; suggest it be re-written so:

Aero Handling section: "Aero compatible mode" and "Optimize for Aero mode", checked.

Defining the section being configured helps locate the user, and breaking up the separate entities being configured/checked helps the user to see that there is more than one, if that is the case.

Might also want to give better directions on how to access Main Menu at any stage, particularly once the game is configured. For example, I double click the DXWnd shortcut, and game icon(s) pop up. Getting to Main Menu for configuration at that point is something of a trial and error, for me, at least.

main menu of what, the game or DXWND?

Thanks for the other ideas. I know i was lacking in pointing out what your suppose to check when i written it, never got back to it i guess.


EDIT:
You only need the disk then place EAWPRO over it. overwriting as necessary You o NOT need to update to 1.2 first, that is no longer necessary., but it won't hurt things if you have already.

Getting to Main Menu screen of DXWnd is what I was referring to; sorry about confusion.

I think I will try to use my disk, strip it of unnecessary stuff, as per your instructions on help site, apply v1.2 patch, available on your web site, overly EAWPRO, and then try to get DXWnd going. As I say, the v1.28E with EAWPRO applied seems to be OK in D3D Windower. FWIW, my particular disc does not have any patches included. ETA: has V1.2 patch included on disk.

I will let you know the different frame rates when things are up and running.

Getting to the main window of DXWND, is you run the dxwnd exe correct?

IIRC, I had to fiddle with things to get to DXWnd configuration screens. A better description of how to get to config screens when one is in DXWnd main screed (that one is easy to get to) would be useful, I think. Most users will not be configuring often, so will not have memorized required step(s) to get to config screen(s).

okay, I'll come up with some perhaps.


Thanks.

I should have added text with in a few days if I still have it 'installed'

Let's put it this way: Original author of DXWnd did not provide good instructions on how to go to config screens from Main screen. You are simply correcting his mistake.

Yes, unlike probably a good many people, I DID read his 'ReadMe", but getting to config screens from main screen was not at all intuitive.

Sorry to be so picky, but many people will click on DXWnd main screen, see a blank window, and go "WTF?"


On a side note, have you gravitated to a better windower/wrapper for EAW than DXWnd? You used to be very high on it,

I am currently using D3D windower, and it seems to work well enough for many versions/combinations of EAW. In fact, it works for versions for which some have said it should not work at all.

That said, I am always interested in lightweight windower programs that work well in conjunction with NGlide, which I always use in conjunction with EAW. My graphics card is an ancient nVidea card, as you may recall, so I find I must run both a wrapper and nGlide for best visual experience.

nothing wrong with running a d3d/Dx wrapper and nglide. (The DXWND wrapper said by the author works with nGlide)
I haven't experimented too much with using two wrappers, I use one or the other, or none.

If I could, I'd use dgvoodoo since it has a DX wrapper built in with a glide wrapper. But the DirectX portion needs calls to files names hacked into the eaw.exe, actually name changes for the ddraw.dll I think.
In other words its a pain to set up, so its been rejected by me for now.
Same with DXWND wrapper , alone its a bit demanding and it jitters the planes at medium distance, but I understand with nglide it works good. But thats two wrappers, and I'm not interested in myself using two at the moment.


As far as my limited help doc info on the DXWND, I had the text in there for how to get to the main tab settings from the dxwnd start window. its a right click and then select modify on the eaw.exe icon. I expanded the text a little bit now, hope it helps.

The D3DWindower, its small and light weight, and I honestly only used it for like a month or two when i had windows 7. It runs in compatibility mode cause its an old exe. But if it works for you thats great. I should expand on my help doc notes about it, if I ever run with it again I will.

EDIT:
I remember I dropped using the D3DWrapperV1.88 cause I found a registry fix for windows 7 directdraw colors. The eaw menu screens where toasted so the fix was part of the Window OS , just undocumented, but works.
Now that I'm on win10 I can just run nGlide with opengl or vulkan api's (I think thats what it supports). Thats another not well documented wrapper I used in the help doc as well.
Right now I'm just using Win10 for some EAW games and DXWND for testing with other EAW Games.
DXWND is such a resource hog, I need to find a bunch of tab settings to help remove that plane jitter, and this might take useing the expert tab settings. Thats if the author of the Wrapper doesn't tweak/optimize it better for DirectDraw-D3D combo displays as EAW uses both in the flight screen as far as I can tell.

EDIT2:
There is a OpenGLide wrapper made in 2004 for glide 2.xx games (that restricts the use to EAWv1.2 and EAWPRO, as the other un-offical updates are v1.xx use glide3.xx), its light weight, and you only need the dll and configure file I believe. You need OpenGL to use it, and it cleans up Terrain Shimmering just like the olden days. I used it and may go back to it. I just wish a newer version existed for win10 (but it does work on that os).
https://eaw.neocities.org/troubleshoot.html#wrap


I just found this site trying to relocate openglide....the last openglide is listed.
http://www.sierrahelp.com/Utilities/DisplayUtilities/GlideWrappers.html

In the above, you said: "The D3DWindower, its small and light weight, and I honestly only used it for like a month or two when i had windows 7. It runs in compatibility mode cause its an old exe. But if it works for you thats great. I should expand on my help doc notes about it, if I ever run with it again I will."

May I suggest that you add such comments as soon as conveniently possible? Some people are currently using D3D, and so your additional comments, while still relatively fresh in you mind, might be of assistance to some people now.

Thank you again for your efforts!

Just seen this post , well again, brought to my attention.

I do have it noted that it was designed for Windows XP but runs on later WindowsOS Versions like vista and 7.
Not sure what you want me to enter or add for text on the Troubleshoot Help Doc?

And thanks for the input.

Merely to add your thoughts to the Doc before you become engaged in something more urgent. As I now see, you have such comments down in your notes, so there is no apparent danger of them being lost or forgotten. However, such thoughts being added to the Doc might be of immediate use to others.

You do so much that I am hesitant to make some trivial suggestions. But sometimes, even trivial things can be important to others, hence this post.