reactos VS Proton

https://reactos.org/ implement some of the windows API

You can use Rufus: https://rufus.ie/en/

To modify the ISO to turn off hardware check and TPM support for Windows 11 to install it on an unsupported PC.

https://github.com/pbatard/rufus/wiki/FAQ#user-content-Help_...

Besides Linux and BSD Unix there is: https://reactos.org/ https://aros.sourceforge.io/ https://www.haiku-os.org/ and https://www.arcanoae.com/arcaos/

I know some third-world nations still use DOS and the BORLAND DOS compilers because people donate old computers to their nations.

With the right OS, old computers are still usable. Please don't throw them away, e-cycle them so they get used by poor nations that cannot afford new PCs.

ReactOS is sometimes very disappointing. Take the issue with toolbar icons, for example. Toolbar icons in at least Office 97, Office 2000 and Visual Basic 6 were affected, as was some game [0]. Microsoft Office is a complex Win32 application, making it a good guinea pig for testing compatibility. And yet, this was fixed a few months ago, and the Office bug was reported in 2016 [1]. The bug with no text wrapping for tray balloons is also an embarrassing thing to have lingering for years (I assume it was like this since the balloons were first implemented in ReactOS).

Does the world really need a buggy Windows Server 2003 reimplementation? I think the efforts of the development team could be better spent elsewhere.

[0]: https://github.com/reactos/reactos/pull/5227

[1]: https://jira.reactos.org/browse/CORE-12377

Anyone tried ReactOS recently? Supposed to be a clean-room FOSS Windows NT compatible OS.

https://reactos.org/

It's still on my TODO. Mostly cause my parents want XP back.

> It's whitespace. There's wayyyy too much god damn whitespace in modern UIs, and it's awful.

I wanted to see how LibreOffice would compare on my netbook, and frankly it's better than the new Word, but still "worse" than the old version: https://i.imgur.com/cWGYh3M.png

That said, at least LibreOffice lets you have your custom themes and actually offers a variety of different interface layouts, which I think is a nice touch: https://wiki.documentfoundation.org/Videos/User_interface

> Windows 7 with the Classic theme (which really was just a slight evolution over Win2K) was peak UI/UX, and you'll never change my mind. It's been downhill ever since, getting worse and worse with each generation.

To be honest, I'm inclined to agree with this. That's also why I rather enjoyed the Redmond theme even in *nix distros. There's just something so very usable about the old Windows look and more modern attempts, such as SerenityOS https://serenityos.org/ and even ReactOS https://reactos.org/

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.

This has been reported to the proton team here : https://github.com/ValveSoftware/Proton/issues/7317