I have been tracking this reactos fork for months, and today while i am checking the starred list, this repository has rebranded into LiberNT, and what they did is absolutely incredible.

https://libernt.com/

Its on real hardware too.

I have a PC from about 2002 with some kind of celeron, a 478 socket geforce 2 and 655360 kilobytes of RAM. I tried to install reactos stable 0.4.16, I click install (screen debug), the dll and drivers start loading, and then just a blue screen with no text and nothing at all. I tried LIve boot and I got a normal bsod (see photo 1). Then I downloaded 0.4.17, the latest overnight release, launched it, pressed live boot, and I got a blue screen with strange letters (photo 2).

Please help me what is the problem, I tried to record usb using rufus/winsetupfromusb (I booted from usb and not cd). I would like to install the OS on this PC and not on a virtual machine.

:)

Neptune OS combines the seL4 microkernel and ReactOS by implementing the NT Native API in userspace of seL4. The latest 0.4 release contains initial Linux kernel driver compatibility, which makes it possible to draw framebuffer with unmodified Linux DRM driver code. Note that currently only part of ReactOS codebase has been ported on top of Neptune OS.

While it is not the ReactOS proper, ReactOS make this interesting project possible.

Is there a method to upgrade Windows to ReactOS without a re-install?
I have a system that has legacy software that I like to keep and am unable to re-install.
It would be lovely to have an upgrade path for this machine but I am unsure if this is possible to do this..

I kind of wish a project like reactOS had become the main FOSS windows competitor and not linux. a decently big FOSS os with a hybrid kernel would be nice.

windows diverges from unix in a few ways that are good, while linux inherits more unixy-ness. linux is built to run on a lot of different machines, windows is made for desktop computers. linux has a lot of features that make it incredibly powerful and versatile, but they can be kind of cumbersome. I often wonder if something that's built with the assumption that its being used on a desktop could be more streamlined.

In my ideal dream world we would have reactOS as the main FOSS competitor to windows, and linux as a super modular thing you can use for things like kiosks and weird DIY projects.

Running old laptop with old BIOS

Linux, BSD, and other OS run in live mode and install

Hello!

I have a motherboard which has a setting in it's BIOS called "Onboard IDE Operate Mode" which I set to "Compatible" since it's a multiboot setup with legacy OSes. It's configured to use "Primary P-ATA+S-AT" and all my drives (DVD drive and HDD) are primary devices on legacy P-ATA connections.

I was previously able to install an older version of ReactOS on it, but now when I try to run the boot CD, I get the BSOD with IO1_INITIALIZATION_FAILED error. That is, unless I run the live environment from RAMFS, in which case it loads successfully, but fails to see any discs to be installed onto.

The live environment loads successfully if I switch IDE mode to "Enhanced" instead of "Compatible" - but this breaks my setup.

Is this a regression or does ReactOS just not support older IDE modes anymore?\

P.S. Text setup crashes with the same BSOD

P.P.S. I've tried using a newer SATA drive in the same configuration and setting _it_ as a boot disk drive, but the result was the same - it stars loading then hits BSOD

P.P.P.S. Funnily, if I plug in a USB stick, _this one_ the live RAMFS environment does see as a possible install location :)

Hello,i have been thinking for a wile top switch too React OS but i fear that it night not be fitting for my Daily Tasks like Using Gimp,Playing Games from RPG maker,Stream,browse the web,using Applications that are supported by Windows 10/11 too,soo i wanted too ask you guys for an opinion,Thank you for your time

Using qemu

$ qemu-system-x86_64 -enable-kvm -cpu host -smp 6 -m 8G -hdd hdd.qcow2 -cdrom reactos-bootcd-0.4.17-dev-742-gf29960d-x64-msvc-win-dbg.iso

i also tried with -cpu qemu instead of host and -m pc but it's all the same

Spent today testing the new 0.4.16 x86 release across Hyper-V, VirtualBox and VMware Workstation.

Hyper-V gave a 0x7E during boot. VirtualBox installed successfully, although I managed to break the keyboard/mouse input after allowing the post-install hardware wizard to automatically install a device (it did warn me in all fairness) . VMware Workstation was the best experience: default virtual hardware, ACPI PC Uniprocessor, FAT32, and I just cancelled the hardware wizard after first boot.

From there ReactOS was surprisingly functional. DHCP/DNS worked immediately, Internet connectivity worked, Applications Manager worked, Firefox 48 worked substantially better than Chrome 49, and I was even able to authenticate successfully to Microsoft 365. Outlook Web eventually hit the wall with the old browser, but authentication succeeded.

I also successfully ran Chicken Invaders, so obviously enterprise application compatibility has been validated.

The biggest thing this left me wondering was, what is the current plan for getting a genuinely modern browser running on it?

For people considering ReactOS as a possible way to extend the life of older PCs, the OS itself already feels much more usable than I expected. But so much everyday computing happens in a browser that Firefox 48/Chrome 49 became the limiting factor almost immediately. A current browser would change how useful it feels, even while the OS remains alpha.

Very cool project. I started this expecting to play with it for 20 minutes and somehow lost most of a Monday to it.