News: 0181070590

  ARM Give a man a fire and he's warm for a day, but set fire to him and he's warm for the rest of his life (Terry Pratchett, Jingo)

Intel, NVIDIA, AMD GPU Drivers Finally Play Nice With ReactOS (x.com)

(Saturday March 21, 2026 @06:38PM (EditorDavid) from the interface-time dept.)


ReactOS aims to be compatible with programs and drivers developed for Windows Server 2003 and later versions of Microsoft Windows. And Slashdot reader [1]jeditobe reports that the project has now " [2]announced significant progress in achieving compatibility with proprietary graphics drivers."

> ReactOS now supports roughly 90% of GPU drivers for Windows XP and Windows Server 2003, thanks to a [3]series of fixes and the [4]implementation of the KMDF (Kernel-Mode Driver Framework) and WDDM (Windows Display Driver Model) subsystems. Prior to these changes, many proprietary drivers either failed to launch or exhibited unstable behavior. In the latest [5]nightly builds of the 0.4.16 branch, drivers from a variety of manufacturers — including Intel, NVIDIA, and AMD — are running reliably.

>

> The [6]project demonstrated ReactOS running on real hardware, including booting with installed drivers for graphics cards such as Intel GMA 945, NVIDIA GeForce 8800 GTS and GTX 750 Ti, and AMD Radeon HD 7530G. They also highlighted successful operation on mobile GPUs like the NVIDIA Quadro 1000M, with 2D/3D acceleration, audio, and network connectivity all functioning correctly. Further tests confirmed support on less common or older configurations, including a laptop with a Radeon Xpress 1100, as well as high-performance cards like the NVIDIA GTX Titan X.

>

> A key contribution came from a [7]patch merged into the main branch for the memory management subsystem, which improved driver stability and reduced crashes during graphics adapter initialization.



[1] https://slashdot.org/~jeditobe

[2] https://x.com/reactos/status/2031439000708202743

[3] https://github.com/reactos/reactos/issues?q=is%3Apr%20author%3ADarkFire01%20label%3Adrivers%20sort%3Acreated-desc%20closed%3A%3E2025-06-01

[4] https://reactos.org/blogs/investigating-wddm/

[5] https://reactos.org/getbuilds/

[6] https://x.com/reactos/status/2029284725051806137

[7] https://github.com/reactos/reactos/pull/8613



What I wanted was Windows 95b (Score:3, Interesting)

by HiThere ( 15173 )

When I switched off MSWindows, what I wanted was Windows 95b compatibility. It never showed up. It still hasn't. I've intentionally avoided later versions because of terms in the licensing.

These days the only things that haven't showed up on Linux, or had better replacements are a few music programs (more my wife's field than mine) and a few games...that I may have lost the CDs for.

Re: (Score:3)

by evanh ( 627108 )

I find dotNet based programs tends to end in tears on Wine. They either crash easy or never run at all. I use a number of industrial controller programming tools and none work because of dotNet shenanigans.

Re: (Score:3)

by Z80a ( 971949 )

Much of the Win95 compatibility depends on 16bit code, which is not available on the 64bit mode regardless of windows or linux.At this point, your best bet is using 86box

Re:What I wanted was Windows 95b (Score:4, Informative)

by Samantha Wright ( 1324923 )

Good news! [1]Someone hacked it into existence [github.com].

It's done wonders for my addiction to Win 3.x games.

[1] https://github.com/otya128/winevdm

Re: (Score:2)

by Z80a ( 971949 )

Looking here, it do emulate a 16bit CPU, but i imagine, even via emulation, you're getting a CPU that is a hundred times faster than an actual 386 of that era.

Re: (Score:2)

by unixisc ( 2429386 )

Does ReactOS even have any 64-bit mode? They were targeting Windows 2000 or XP, neither of which had much of a 64-bit mode

Now just as insecure as real Windows (Score:3)

by OrangAsm ( 678078 )

Good job!

At this point.... (Score:3)

by unixisc ( 2429386 )

I just wish a team would come together, fork ReactOS and work on a fixed target of creating an FOSS version of Windows 7 ! Not XP, not 8, not 2000.... In fact, make it two projects:

1. A 32-bit version of NT, which seeks to support the entire win32 API, and maintain compatibility w/ everything from Windows 95 to 10. That one can be x86-only, and would top off its RAM support at 4GB

2. A 64-bit version of NT, which would support the win64API, but do nothing in terms of backwards 32-bit support. For this OS, make its upper memory limit 2^48, or 64TB of RAM (Microsoft only supports up to 6TB on Windows 10/11). This OS should be done w/ no x86 assembly underpinnings, and should be ported to RISC-V and Arm. If possible, also try to test it on legacy Alphastations and MIPS workstations that previously ran NT

In that project, have full support of NTFS: Microsoft's patent on that filesystem should be dead, given that it's way beyond 10 years since NTFS was first devised. If they like, they can have an extension of NTFS that is fully backwards compatible w/ Microsoft's implementation of it.

Re: (Score:2)

by unixisc ( 2429386 )

Sorry, I meant 256TB of RAM, not 64TB

Re: (Score:2)

by CAIMLAS ( 41445 )

Yeah, I don't really get it's trajectory. I'd have thought that by 2005/2010 or so they'd have pivoted to W7 workalike compatibility, due to it being vastly superior in literally every way.

At that point, you could conceivably implement W10+ compatibility at a much lower effort, making it a realistic bridge for people to stand on for modern hardware.

A focus on supporting newer hardware, with a newer architecture, would go a long way to bridging the "I can do windows things not on Windows".

At this point we're

Re: (Score:2)

by unixisc ( 2429386 )

Yeah, that's why I suggested 2 versions - a compatible 32-bit version, that aims to preserve such compatibility, and a brand new 64-bit version, which like AMD64 did back 20 years ago, just take the win64 API, but have all the code written around it portable, but w/ no 32-bit backward compatibility baggage. Unlike Microsoft, strive to make it compatible, so that even if it's not one's first choice on an x86-based workstation, it could be on an Arm or a RISC-V box

From what I understand, that project, like

For what purpose? (Score:2)

by CAIMLAS ( 41445 )

Years ago, when Windows 9x was in the field and ReactOS was starting out, the concept made sense: a compatible, open source Windows work-alike.

Today, Windows can't even run Windows apps, and ReactOS doesn't have a meaningful footprint beyond what WINE can provide. Hardware has far eclipsed Windows 2003/XP/7 compatibility (which is again, each of which are further beyond what ReactOS can provide); most of this same hardware works on Linux.

What value does ReactOS have, beyond providing a(n insecure by defaul

Lunatic Asylum, n.:
The place where optimism most flourishes.