https://www.trinitydesktop.org/newsentry.php?entry=2014.12.16
The Trinity Desktop Environment (TDE) development team is pleased to announce the immediate availability of the new TDE R14.0.0 release. The Trinity Desktop Environment is a complete software desktop environment designed for Unix-like operating systems, intended for computer users preferring a traditional desktop model, and is free/libre software.
Unlike previous releases TDE R14.0.0 has been in development for over two years. This extended development period has allowed us to create a better, more stable and more feature-rich product than previous TDE releases. R14 is brimming with new features, such as a new hardware manager based on udev (HAL is no longer required), full network-manager 0.9 support, a brand new compositor (compton), built-in threading support, and much more!
(Score: 2) by HiThere on Wednesday December 17 2014, @08:00PM
I waited a VERY long time for a MSWind95 compatible OS. It never showed up. It still hasn't showed up. About a decade ago I talked to a ReactOS developer, and he told me that if wine didn't support it, ReactOS wasn't likely to. I didn't go into details about why, but the impression I got was that either they used the same code, or the used wine as a template for development.
Wine *STILL* don't run MSWind95 applications...except some of them (i.e., not the ones I was interested in).
Javascript is what you use to allow unknown third parties to run software you have no idea about on your computer.
(Score: 1, Informative) by Anonymous Coward on Wednesday December 17 2014, @09:38PM
either [ReactOS] used the same code, or [they] used wine as a template
Neither of those was or is completely accurate.
There has been a significant amount of cross-pollination between the 2 for many years.
Some years back, ReactOS had a major refactoring and they threw away a lot of code in favor of what WINE had done.
If neither of those runs your must-have Windoze-only app, ISTM the next choice is one of the Tiny* things you can get via BitTorrent.
(The less M$ code you run, the fewer bugs and exploitable holes you will encounter, so the cut-down stuff seems like an obvious decision if all-FOSS code isn't getting you there.)
Run that in a virtual machine, of course.
Replacing a snapshot of a M$ OS in a VM is about as simple as a recovery from an M$ failure gets.
.
...and the suggestion in the first place by Marand of ReactOS (whose devs have to grope around in the dark because the source code for MSFT stuff isn't available freely) is about as far away from the statement by ticho as anything could be re: forking existing FREE code.
-- gewg_