>"Why don’t you help Wine? Wine implements Win32Api only, while ExectOS is a featureful Operating System, that implements a compatibility layer with NT™. This

>"Why don’t you help Wine? Wine implements Win32Api only, while ExectOS is a featureful Operating System, that implements a compatibility layer with NT™. This means, ExectOS will be able to run NT™ drivers as well, not only Windows® software. However, thanks to its modular design, it will be possible to implement Win32 subsystem as well at some point, based on Wine. Why don’t you help ReactOS? ExectOS goals are very different from ReactOS, and contrast the project’s core philosophy as being quite on different paths. While ReactOS aims to replicate Windows® NT™, ExectOS is a completely new Operating System implementing the XT architecture which derives from NT™. Although both projects share the goal of being NT™ compatible, they intend to achieve it in different ways. What ReactOS tries to replicate, ExectOS only implements as a compatibility layer. Thanks to that, ExectOS does not need to strictly follow NT™ architecture and is capable of providing modern features." ExectOS seems highly interesting -- basically it can be thought about as an open-source OS that can run Windows binary closed-source drivers... If ExectOS is going to do this (and apparently it is!) -- then let me propose the following use-case and corresponding suggestion... First, the use-case: I think it would be great to run a headless (non-GUI) OS infrastructure capable of hosting Windows binary closed-source drivers on a different networked piece of computer hardware. For example, let's say I have an old PC. An old PC with some expansion card or piece of hardware that is not produced anymore, where the vendor went out of business years ago, where there are no open source drivers -- where the only thing that remains is the ancient hardware and the ancient proprietary closed-source driver... OK, now let's suppose that I can run the ExectOS OS infrastructure headless on that old PC along with the ancient proprietary closed-source driver (I use a second attached modern networked PC with GUI, remote shell, debugger, etc., etc. to connect with and control the old PC...). Well, that would be awesome, because then ExectOS could be used to isolate, debug, and potentially understand (better) old Windows binary closed-source drivers for old (ancient?) attached hardware devices that are no longer produced, where open-source drivers are not available... So the suggestion: Via IFDEFs, compilation flags, conditional compilation, etc., create a headless (but still with built-in networking and/or the ability to run a network driver) version of ExectOS -- for the purpose described above. All I know is that if that version was created, then the old/vintage hardware restoration/documentation community -- would be forever in ExectOS's debt... Anyway, ExectOS sounds great! (Could it be made to work on old 386's?)