The Steam Machine helped grow the popularity of Linux gaming, including installations of Bazzite and other gaming-oriented Linux distributions. Valve seemingly doesn't want to stop its open-source development efforts anytime soon, and is now working on a port of the Mesa Radeon Vulkan driver (RADV) to Windows; It's already running Counter-Strike 2, according to developers at Collabora.

As cross-platform development is rather tricky, Valve opted to get a port of RADV to Windows going by way of sponsoring contractors at Collabora. In its blog post, Collabora explained the several hoops it had to jump through to accomplish this task.

With Windows 10 and WDDM 2.0, Microsoft improved the split between graphics drivers' userspace code (the vast majority of the driver itself) and the kernel-level portion that actually talks to the graphics card. This presented the opportunity to hook RADV to the AMD kernel card driver. That's easier said than done, however, as communication between those parts often carries non-standardized data that RADV needs to understand. And to understand the "conversation," it needs to be recorded and analyzed.

An earlier 2024 effort by Faith Ekstrand yielded a basic-but-valuable utility for logging WDDM 2.0 calls and reverse-engineering them to produce a basic RADV implementation. Out of both debugging necessity and as a development tool, Collabora built and expanded upon Ekstrand's work, improving the logger to the point where it can now fully analyze any Vulkan application that runs with AMD's official driver and dump all the data passing to the kernel.

After a lot of work getting to grips with how the AMD driver interacts with the kernel driver, including but not limited to reverse-engineering obscure data structures, the team made progress, and Windows RADV is now able to run some games, including Counter-Strike 2.

Despite the ongoing effort, Collabora explains that since user- and kernel-space driver are a matched pair, changes to those aren't guaranteed to be backwards-compatible, meaning that even a fully functional RADV could break at any point. For that reason, Collobora is requesting that AMD, Microsoft, or both provide a documented interface to the kernel driver or an intermediary compatibility layer.

AMD graphics driver development on Linux has coalesced around the Mesa Vulkan stack, with both company and community devs contributing to the RADV project. Over in the Windows world, the only option is AMD's proprietary driver, which can cause a lot of headaches when developing cross-platform games and applications.

AMD's Vulkan driver for Windows has developed a reputation for instability. Meanwhile, Linux RADV is generally praised for its stability and performance, sometimes running faster than the AMD Windows driver, especially on older cards. With a rapid development schedule, it also generally sees fixes and speed upticks often.

If at some point using RADV on Windows becomes viable, you'd be getting an arguably more stable, mature driver with active development. Games' graphical issues could become far easier to debug and patch thanks to the open nature of RADV, and studios developing with Linux in mind can target the one platform instead of two with different behaviors. Any developer or company can contribute to the project, too.

Furthermore, this lets Valve improve Windows compatibility layers, and any optimizations can be carried over to both operating systems. All told, this is likely one of the several moving parts to improve Linux — thus the Steam Deck, Steam Machine, and upcoming hardware — as a viable gaming platform. Even a future notion of gamers installing RADV on Windows to get a performance or stability boost isn't too far-fetched.

Additionally, RADV on Windows would also help keep discontinued cards usable, and given pricing right now, that certainly would be a good thing.

Microsoft released Windows NT 4.0 to manufacturing partners on July 31, 1996. Codename Cairo marked an important milestone in the history of Microsoft’s original server OS and would far outlive Microsoft’s original plans as enthusiasts and administrators clung to it, as older readers will be aware. Headlining features of NT 4.0, which made it a winner, include the melding of the intuitive new Windows 95 UI into the fully 32-bit enterprise OS. It was also notable for being the last version of NT to support Alpha, MIPS, or PowerPC CPU architectures.

Historical Windows NT timeline:

• Windows NT Server 3.1 – in 1993, the first version of Windows NT also introduced NTFS
• Windows NT Server 3.5 – in 1994, this update provided integrated support for Winsock and TCP/IP
• Windows NT Server 3.51 - client/server support added in 1995
• Windows NT 4.0 – in 1996, NT got the Windows 95 UI and the familiar My Computer, My Documents, and so on
• Windows 2000 Server – the 5^th NT release started a new naming scheme, introduced Active Directory, plus NTFS 3.0 with file system encryption
• Followed by the more modern Server releases…

After the initial Windows NT 4.0 release, Microsoft followed up with a version for embedded systems and its Terminal Server edition.

The Windows NT line was critical to Microsoft as it led the charge against dominant Unix server software ecosystems. Its first public release was in 1993, with version 3.1, but NT 4.0 coupled the underlying data server and personal workstation tooling with Win95 UI elements such as the Start Menu, Taskbar, Task Manager, and so on. It would also support new components like the cryptography API, DCOM, TAPI 2.0, and some DirectX (v2) features.

Despite all the new technology under the hood and the frills of the latest UI, Microsoft’s Windows NT 4.0 launched with remarkably low minimum requirements. Would-be users were recommended to install it on a PC with a CPU that ran at 33 MHz or better, had 32MB of RAM, SVGA graphics, and a hard disk with 256 MB capacity. This was in the Pentium / Pentium Pro era. NT 4.0 would become “the server for the masses,” boasted Microsoft on the OS’s 20^th anniversary.

Another reason that NT 4.0 was so important is that it formed the foundation for the Windows XP release (2001), leaving the DOS-based 95, 98/SE, and Me versions of the consumer OS behind as archaic hybrids. In the half-decade between the release of NT 4.0 and XP, Microsoft had a lot of work to do, such as implementing Plug and Play, building out gaming tech, adding WDM drivers, and so on. Thankfully, PCs also grew in muscle, specs, and multimedia capabilities to make the larger and more demanding XP a big hit.

Windows XP landed with a core marketing line that it was “Built on NT technology,” which felt uncomfortable to read if you were from the camp that believed ‘NT’ was short for ‘New Technology.’

It is pretty easy to find an old Cairo release online for retro machine tinkering. Those interested in a more casual poke around in NT 4.0 out of interest, curiosity, or nostalgia will find there are some online installs you can play with via a web browser.

Legendary Windows developer Dave W. Plummer has shared details and screenshots of a version of Task Manager for Apple Mac computers. Apple computer users currently have Activity Monitor for peeking at CPU activity, memory usage, as well as closing apps and processes, by default. However, “Activity Monitor blows,” asserts Plummer, in response to people asking why he would port the classic Windows utility to the fruity computer.

Preempting questions from his social media followers, Plummer mused over the optics of releasing Task Manager for Mac, due to his Microsoft development history. In case you missed it, Plummer was the original dev behind Windows Task Manager when it debuted as a lean and mean 80KB accessory. He’s also recently reimagined this essential Windows system tool in a retro-futuristic Atari Tempest remix.

Back in the world of Macs, and looking to the side from the world of PCs, there is indeed a case for a better task manager or activity monitor for Apple computers. The Windows utility has more features under the hood, giving it a far greater scope and utility value (task priorities, startup management, services control, and more). We haven’t tried the new Mac version of Task Manager; it hasn’t been released at the time of writing, but if it can decant some of the Windows features over to the Apple computing platform, it may be an attractive addition.

Plummer says the utility is currently in beta, and he intends to “throw it up on the App Store… (for free in Beta, because the first taste is always free).” There’s also, admittedly, a chance he will get bored with tinkering with it and release the source for others to continue with.

We already mentioned the optics over a seasoned Windows dev coding / porting staple Microsoft OS code to Apple Macs, but Plummer has addressed queries about this in further posts today. In this Tweet, the dev asserts that “Microsoft very graciously sent me the source code to XP Task Manager along with permission to share/demo it.” Moreover, the project is written in Swift and uses no original code, and Plummer says he has no post-Windows XP code to tap into, either.

Meanwhile, development continues apace, with Plummer providing insight into some drive meter activity coding he’s currently working on. The dev is finessing drive activity for Task Manager for the Mac right now and pondering over the flickery visuals resulting from “drawing instantaneous drive activity at 60fps.”