DXGL

I just managed to make a Windows NT 4.0 compatible build, but as I have yet to get my retro PC to work correctly, I will have to consider it experimental.

I did everything I can with the Visual C++ 2005 compiler, but it appears that the runtime has a hard dependency on Windows 98 or 2000, or later.
Now I'm going to make a Visual C++ 2003 project file, see if that works.

I just modified my code to support psapi.dll however a dependency called MinHook still depends on the Toolhelp32 API.
I might have to modify the code to work with the Windows NT Native API (ntdll.dll) directly in this situation.

I have created a new fork of MinHook to ikmplement the changes needed ...

In this case virtualization is better than emulation because my CPU can better brute force software Mesa virtualized than emulated.

Voodoo3 will not be supported because as you admit it is only OpenGL 1.x and the architecture is far more limited and doesn't support GLSL.

I'm having trouble getting my retro PC working correctly; my 6200 is the wrong kind for the 77.72 drivers. I'm going to resort to virtualization and Mesa drivers to test.

I have opened Issue #52 to track this:
https://github.com/dxgldotorg/dxgl/issues/52

These fixes will be applied to the 0.5.x branch to allow for a quick release based on functional code, but will trickle down to the master and 0.6-dev branches to incorporate these fixes into future planned versions ...

OpenGL 2.0 to 1.x downgrade would require a complete rewrite; DXGL is written with a strict dependency on GLSL and multiple render targets.

Looking at what it takes, I found I could use an alternate code path involving GetModuleHandle and GetModuleInformation which is unsupported on Win9x but ...

I do not plan on supporting any graphics cards below OpenGL 2.0 because the architecture of those legacy cards is so much different than modern GPUs. Presumably MCD drivers will be OpenGL 1.x and thus unsupported. There is a runtime check for the OpenGL version when DXGL's ddraw.dll starts up.

As ...

There is no usage of .NET at this point. Also, DXGL only depends on OpenGL.

If I ever decide to support NT4 I will not depend on any OS-level hacks.

So far I have not attempted to test Windows NT 4, but I have managed to get it down to Windows 2000 so far with the VS2005 and VS2008 builds.
The DXGL Config app will launch on Windows 98, but as of the 0.5.x series the DXGL wrapper crashes upon initialization.

It seems that Visual Studio 2005 ...