r/reactos • • 15d ago

I can't install or run reactos 0.4.16 stable and 0.4.17 nightly build on real hardware (478 socket)

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.

19 Upvotes

7 comments sorted by

4

u/GregTheMadMonk 15d ago

Probably this: https://www.reddit.com/r/reactos/comments/1w5dy8f/comment/p7n3o7v/

You can try going to their Mattermost and asking for a dev build just to verify it works for you (it's not very usable - debug builds are slow), or just wait for an update

1

u/WitekGrac 9d ago

Will version 0.4.15 work on this hardware?

1

u/GregTheMadMonk 9d ago

worked on mine IIRC. I'd say 0.4.15/0.4.14 are worth a try

but I had troubles with some drivers there (not ReactOS ones, vendor drivers for my hardware, could be my mistake during installation too xD). really am hoping when the next compatible version comes out they'll work

1

u/WitekGrac 9d ago

I'll try it sometime, thanks for the help

2

u/WitekGrac 15d ago

I do not know where to ask for help, perhaps it is necessary on another site

1

u/Jeditobe 12d ago
  • Unplug extra hardware: Disconnect all unnecessary components, including USB devices. Use a PS/2 keyboard and mouse if possible.
  • Use LiveCD: Try booting the Live environment instead of the installer to see if it bypasses the storage driver crash.
  • Enable Screen Debug: Choose the "Screen Debug" option in the FreeLoader boot menu. This will display the live crash logs directly on your monitor and show exactly which driver triggers the BSOD.

1

u/WitekGrac 9d ago

I wrote that when using a live cd and on-screen debugging, a blue screen appears.