DLL hell wrote on 2026-03-27, 17:48:

Out of the box dx8 Lite won't work with dx8 Game, any advice

My win nt 4.0 sp6a roll up setup is Intel 865g, Pentium 4 northwood and 512 ram, graphics card is the Intel integrated extreme graphics 2

Need to get PAE 64gb working on all NT versions including 3.1 and 2k

Then get Supermium browser up and running on all NT versions

wierd_w wrote on 2026-03-24, 21:02:

I figured it would work. […]
Show full quote

shadowmage wrote on 2026-01-24, 23:38:

Here it is: https://youtu.be/3FYarwJOp9k […]
Show full quote

the3dfxdude wrote on 2025-04-06, 14:31:

When D3D on top of OpenGL work was beginning, the devs were using the best Nvidia cards at the time. I think the minimum version of OpenGL ended up being 2.0, and I remember that version 1.5 was kind of dodgy. What is the best you can do with NT4.0? OpenGL 1.1? Maybe there are newer vendor provided drivers that come close. Sorry, I don't think I've ever done OpenGL with NT 4. I doubt anyone thought about testing and make working Wined3d on NT 4.0 for what limited set is available. It will be interesting to see.

Here it is:
https://youtu.be/3FYarwJOp9k

WineD3D works on Windows NT 4.0. 3DMark 2000 score - 21422. Unfortunately I couldn't make it work on Windows NT 3.51.

I figured it would work.

What was the ogl igp version?

It may be 'plausible' to use mesa for windows as a shim, hook the graphics card's IGP for everything that *can* be run on hardware, then using mesagl to supply missing features to reach OGL 2.0 feature level.

It’s the QEMU OpenGL passthrough, which directly exposes the host’s NVIDIA RTX 4060 Ti driver to the Windows NT 4.0 guest, providing full OpenGL 4.6 support.

Direct3D 9 benchmark 3DMark 2003 also works on Windows NT 4.0. Here is the video:
https://www.youtube.com/watch?v=gtvmWzg15I8

You can use Mesa9x (JHRobotics) with WineD3D to run 3DMark 2000 on Windows NT 4.0, but since it's CPU-based, it’s much slower.

shadowmage wrote on 2026-03-27, 23:11:

It’s the QEMU OpenGL passthrough, which directly exposes the host’s NVIDIA RTX 4060 Ti driver to the Windows NT 4.0 guest, provi […]
Show full quote

wierd_w wrote on 2026-03-24, 21:02:

I figured it would work. […]
Show full quote

shadowmage wrote on 2026-01-24, 23:38:

Here it is:
https://youtu.be/3FYarwJOp9k

WineD3D works on Windows NT 4.0. 3DMark 2000 score - 21422. Unfortunately I couldn't make it work on Windows NT 3.51.

I figured it would work.

What was the ogl igp version?

It may be 'plausible' to use mesa for windows as a shim, hook the graphics card's IGP for everything that *can* be run on hardware, then using mesagl to supply missing features to reach OGL 2.0 feature level.

It’s the QEMU OpenGL passthrough, which directly exposes the host’s NVIDIA RTX 4060 Ti driver to the Windows NT 4.0 guest, providing full OpenGL 4.6 support.

Direct3D 9 benchmark 3DMark 2003 also works on Windows NT 4.0. Here is the video:
https://www.youtube.com/watch?v=gtvmWzg15I8

You can use Mesa9x (JHRobotics) with WineD3D to run 3DMark 2000 on Windows NT 4.0, but since it's CPU-based, it’s much slower.

At least on linux*, Mesa3d can pass hardware supported functions through, and only process hardware unsupported functions as software.

I was considering 'older ICD' + MESA, where the OpenGL 1.5ish drivers of yore provide a big chunk of the pipeline, with lighting and shadows done as renders to textures by mesa.

Would still be slow, but not as slow as mesa doing all the lifting.

wierd_w wrote on 2026-03-28, 14:06:

At least on linux*, Mesa3d can pass hardware supported functions through, and only process hardware unsupported functions as sof […]
Show full quote

shadowmage wrote on 2026-03-27, 23:11:

It’s the QEMU OpenGL passthrough, which directly exposes the host’s NVIDIA RTX 4060 Ti driver to the Windows NT 4.0 guest, provi […]
Show full quote

wierd_w wrote on 2026-03-24, 21:02:

I figured it would work.

What was the ogl igp version?

It may be 'plausible' to use mesa for windows as a shim, hook the graphics card's IGP for everything that *can* be run on hardware, then using mesagl to supply missing features to reach OGL 2.0 feature level.

It’s the QEMU OpenGL passthrough, which directly exposes the host’s NVIDIA RTX 4060 Ti driver to the Windows NT 4.0 guest, providing full OpenGL 4.6 support.

Direct3D 9 benchmark 3DMark 2003 also works on Windows NT 4.0. Here is the video:
https://www.youtube.com/watch?v=gtvmWzg15I8

You can use Mesa9x (JHRobotics) with WineD3D to run 3DMark 2000 on Windows NT 4.0, but since it's CPU-based, it’s much slower.

At least on linux*, Mesa3d can pass hardware supported functions through, and only process hardware unsupported functions as software.

I was considering 'older ICD' + MESA, where the OpenGL 1.5ish drivers of yore provide a big chunk of the pipeline, with lighting and shadows done as renders to textures by mesa.

Would still be slow, but not as slow as mesa doing all the lifting.

OpenGL passthrough via QEMU also works on Windows 10, not just on Linux.

Here are some examples:
- Half-Life 2 running on a Windows 98 VM (host OS: Windows 10 1809):
https://youtu.be/R59aYcJxrGc
- Doom 3 running on a Windows 98 VM (host OS: Windows 10 1809):
https://youtu.be/R_ZtCmAYSUw

WineD3D is a wrapper, so it's possible it could also work on older GPUs. Someone already tried using WineD3D on Windows 98 with a Quadro FX 4500 GPU:
SoftGPU: OpenGL + DirectX + Glide driver for Windows 95/98/Me

Seeing 3dMark 2003 run with DX9 hardware acceleration and high frame rates in NT4 is really impressive. That would have been unthinkable back in the day.

I applaud everyone who worked on getting it working so well!