WINS: Runtime Re-hoster and PE/Mach-O Binary Loader in Zig for Linux

Hi! :slight_smile:

I’ve been working for the last few days on a project called WINS, written mostly in Zig. The basic idea is to run/re-host Windows binaries on Linux without relying on Wine or Proton.

This is still experimental, so I’m not claiming 1:1 compatibility or anything close to that yet. I’m mostly trying to implement the Windows behavior that real programs expect, test it against actual software, and keep expanding the runtime from there.

So far I’ve managed to get several kinds of software running, including Electron-based applications and actual Windows games.

Some of the games I’ve used as real-world test cases are:

  • Fallout: New Vegas

  • Cuphead

  • Dark Souls III — currently in progress

For the Steam games, one of my goals has been to preserve the normal Steam ownership/launch flow instead of bypassing it. Steam still verifies the game normally; WINS is focused on the compatibility/runtime side.

Current technical scope

At the moment WINS is mainly being developed and tested on:

  • Linux x86_64

  • Zig 0.16

  • Native Linux execution

  • Windows PE/Win64 binaries

  • Steam integration

  • D3D11 translation/runtime work

  • Windows input, threading, memory, exceptions and API compatibility

  • Audio through the Linux host stack

Dark Souls III has been particularly useful because it exercises a much larger part of the runtime than the previous games: Steam, D3D11, input, audio, shaders, resource handling and a lot of Windows-specific behavior.

I’m not interested only in video games, but games are probably the most visually obvious way to demonstrate whether the system is actually doing something useful. :stuck_out_tongue:

I could use some testers

If anyone here has a Linux x86_64 machine and owns one of the tested games on Steam, I’d love to get results from hardware/configurations other than my own.

I’m especially interested in things like:

  • GPU / driver differences

  • distro differences

  • crashes or first points of divergence

  • rendering differences

  • input/audio problems

  • anything that works on my machine but fails elsewhere

Even a simple “I tried this and it died here” report is useful.

Contributions are welcome too

If you’d rather look at the code, review the architecture, point out something stupid I’m doing, improve documentation, add tests, or actually contribute code, all of that is welcome.

The repository is on GitHub: DannyBaanks/WINS.

I’m still learning a lot while building this, so constructive criticism is genuinely useful.

And just to be transparent: yes, I use AI agents heavily while programming this project. I use them for implementation, debugging, reverse engineering assistance, testing and review, while I handle the direction, architecture, experiments and verification of the results.

If anyone wants to test WINS, inspect it, break it, or just tell me why something I’m doing is terrible, feel free. :slight_smile:

1 Like