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.

Hi. I got a question about the reliability of ReactOS regarding to the security. I think I heard somewhere that ReactOS uses some of reverse engineered code from legacy Windows (like XP?). If this is the case, do the devs regularly patch all the vulnerabilities arisen by those codes manually as those Windows are no longer updated? I also heard that the the development of ReactOS is very slow. How much does it usually take to patch a vulnerability once it is found? I'm very intrigued by the concept and the feel of the OS, but those are the concerns that impede me from trying the actual thing. I'd definitely like to try it out if it is proven to be secure. Thanks in advance!!

[CLASSIFIED] Transmission received.

STATUS: WARNING
MESSAGE:
Not everyone can see what is coming.
But you should...
Prepare for unforeseen consequences.

DATE: [REDACTED]

I tried Virtual Box but it's UI completely ignores DPI and worse yet, it insists on the settings dialog being so large it actually cuts off the bottom because it goes off screen. I did try reducing my DPI temporarily but the experience was horrendous so I gave it up as an affront to UX.

Getting ReactOS to install on boxes was a breeze, just click create, search for "Windows XP", select the ISO and you're off. Unless you also configure the RAM, VHD and CPU cores like I did, then you're delayed by the few seconds it takes to do that 😅

Anyways I booted in no prob, went through the usual setup process from the ISO itself and had my desktop up and running in maybe 3min tops. Plugged in the vbox guest additions iso, found out it was not allowing the 3d accel option to be selected (though that may be a problem with reactos itself judging by how pretty much no option I tried in the file manager allowed me to change it's state) so I dug a little deeper into the config file for the VM and found it was disabled there.

Turned it on, found yet ANOTHER 3d accel setting in ~/.config/gnome-boxes/QEMU Session set to false so turned that on. Had long since lowered the initial desktop settings I chose to improve performance so dunno if that helped at all but anyways, after that I finally went looking for my shared folder and no show.

I'm now at an impasse, anyone got any ideas on what I should do next?

Edit: Tried asking gemini for suggestions, long story short it seems impossible for now. Here's the final summary from the chat that mentions the important points:

While you can grab vioserial from an older Fedora VirtIO ISO (0.1.185) and spice-webdavd-x86.msi from the SPICE site, spice-webdavd will not function in current builds of ReactOS

Edit 2: For now gone with making an ISO as I can live with not being able to pull out my Last Scenario saves for the time being as I was mainly trying to see if I could get it's MIDI output through the VM instead. This is the command I added to thunar to generate the ISO:

ARCHIVE=$(zenity --entry --title="Create ISO Archive" --text="Confirm archive name:" --entry-text=%n) && [ ! -z "$ARCHIVE" ] && genisoimage -J -R -V %n -o "$ARCHIVE.iso" %f

Edit 3: And that was also a bust, game copied over fine but it couldn't boot the audio at all and just noped right out of trying. If the devs are looking at this thread then the game in question is Last Scenario, an RPG Maker XP game that can be downloaded for free here:https://site.scfworks.com/?page_id=8

i LOVE the catppuccin color palette

I don't have any expertise in OS programming or programming in general. I have often wondered if you could create an OS that could run a wayland desktop while also being able to natevly run windows applications like reacOS.

Version 0.4.15 should be ok, or should I try with a nightly build, for driver stability and games?

Be among the first to try it. It's almost release, final preparations are underway.

Software and hardware used:

CPU is Core 2 Duo
4GB DDR2 RAM
ReactOS nightly 0.4.17-443
-Nvidia GeForce GTX 960 with 368.81 drivers

-SoundBlaster Audigy with Audio Support Pack drivers:
Install from Audigy_SupportPack_7_0\Audio\Drivers\Setup.exe
-WineVDM from Application Manager for 16-bit installers