21–30 of 53 posts
With Microsoft's changes in Licensing, it seems there's a demand for an OS as straightforward as Windows, obviously with some degree of compatibility, but without all of the telemetry garbage. Could ReactOS (or a distribution derived from it) plug this gap?
What is needed for Xen or KVM to be "recommended" for ReactOS, https://reactos.org/wiki/Virtualization_software ?
I am really impressed with what ReactOS is doing, but what is the practical reason for it? I believe (correct me if I'm wrong) they're cloning Windows XP, which happens to be my favorite Windows operating system.
What is needed for Xen or KVM to be "recommended" for ReactOS, https://reactos.org/wiki/Virtualization_software ?
KVM is QEMU. QEMU is already listed there.
I wonder how practical ReactOS could be as a small business server? With Microsoft's changes in Licensing, it seems there's a demand for an OS as straightforward as Windows, obviously with some degree of compatibility, but without all of the telemetry garbage. Could ReactOS (or a distribution derived from it) plug this gap?
First off, I'd like to thank all the developers who have put their time and effort into building this amazing piece of software. I have been curious: if ReactOS aims to be binary compatible with windows, does this mean it succeptible to windows malware infections? I understand that despite having a similar API, the ReactOS implementation different from microsoft's implementation, so a vulnerability on Windows won't n…
If you open a virus embedded in an email attachment on ReactOS then, yes, it'll probably work. Viruses are Windows applications like any other.
The difference here is documented/support APIs vs other code paths.
This is true so long as the 'application' is using the normal APIs, as soon as an application depends on out-of-contract 'implementation details', which the bugs that are utilized by worms definitely are..., all bets are off.
In short ReactOS is more and more likely to implement the API needed by an app, but that doesn't mean it implements the out-of-API defects that malware depends on. Like anyway software, it probably as its own defects.
Earlier quoted context omitted.
If you open a virus embedded in an email attachment on ReactOS then, yes, it'll probably work. Viruses are Windows applications like any other.
>yes, it'll probably work. Viruses are Windows applications like any other. The difference here is documented/support APIs vs other code paths. This is true so long as the 'application' is using the normal APIs, as soon as an application depends on out-of-contract 'implementation details', which the bugs that are utilized by worms definitely are..., all bets are off. In short ReactOS is more and more likely to implem…
Which is why I said an email attachment. The average virus relying on user interaction doesn't need bugs.
Didn't Microsoft release the .NET API and also Wine can be used? https://www.winehq.org/ I am really impressed with what ReactOS is doing, but what is the practical reason for it? I believe (correct me if I'm wrong) they're cloning Windows XP, which happens to be my favorite Windows operating system.
Earlier quoted context omitted.
>yes, it'll probably work. Viruses are Windows applications like any other. The difference here is documented/support APIs vs other code paths. This is true so long as the 'application' is using the normal APIs, as soon as an application depends on out-of-contract 'implementation details', which the bugs that are utilized by worms definitely are..., all bets are off. In short ReactOS is more and more likely to implem…
> the bugs that are utilized by worms Which is why I said an email attachment. The average virus relying on user interaction doesn't need bugs.
I tried installing this on the latest VirtualBox release. It installed cleanly, but the VM would not fully boot. It just hangs on the startup splash screen, with the progress bar about three-quarters of the way across. I found a wiki page advising VirtualBox users to disable "I/O APIC", and to change the virtual network adapter to "PCnet-FAST III". But this made no difference. Just to be thorough, I re-installed comp…