Today and yesterday, I have been having problems connecting to the official website; it simply spends a long time loading, only to return "Unable to connect". I know it is not a lack of Internet connection, as every other website works perfectly fine. Is anyone else having this issue?

Software context:

Firefox 115.19.0 ESR (64-bit) on Windows 7 build 7601

UPDATE: After further investigation, I have determined that my router or ISP is either intentionally or unintentionally preventing connections to reactos.org, but not iso.reactos.org . I find that suspicious.

In fact it's worse than that Darwin code was used by Apple to further develop the current Mac OS. None of that was wasted time. React OS devs are just wasting their time spinning their wheels creating a project with unachievable end goals, with no point what so ever as there never was an end goal for the project.

Perhaps at least the React OS team should hire a project manager?

The entire team are still stuck in the instalation phase of defining whatever the hell the project goal is in a nutshell as opposed to some pie in the sky lofty goal of "Windows NT parity."

Hello, 
My name is Vojin Vidanovic, I am PhD in social work from Serbia.
I would like to start sending small donations to ReactOS team every few months via PayPal

Website user rasvoja, just registered

On side notes- Congrats on x64 naughty build, will test soon
- Congrats of SMP in progress!- It's great to have XP level free Windows, not Wine
- It uses XP driver model x32? x64 in nightly build
- What are the prospects of going to Vista level that would enable use of e.h.
https://github.com/Eclipse-Community/r3dfox/releases andOffice 2010 as well as overal better sw- Can you bundle this browser https://win32subsystem.live/supermium/, plus latest working LibreOffice in agreement with authors- I see NT4 and Win2000 sources laked long time ago,
- Some claims are from Win10 sources leaked tooI know you have to reverse engineer but could we expect
by early 2026 that you reach Vista levels and Vista driver model?

I am sorry to hustle you, but this is only email adress listed.
Please forward to the right address.

Also you should actively promote and ask for donations inhttps://www.reddit.com/r/reactos/
2 000 plus people there!

I have seen on Torrentz and Elsewhere that WInNT4, Win2000 and even some Vista code
https://github.com/Apress/win-vista
Seems even more code leaked
https://www.reddit.com/r/DataHoarder/comments/tk35bm/hackers_leak_37gb_of_microsofts_source_code_bing/
Is leaked? Can this help reverse engeenering and avdancement of ReactOS?
On other news this browser could fit ReactOS

Vista level would enable

https://github.com/Eclipse-Community/r3dfox/releases

As far I understand by NT kernel compatibility and driver model ReactOS is
about XP 32/64 level, early Windows Server 2003 at best.
I would like to know is some transition to Vista x64 models planned, since that would enable a lot more modern software to run

There are some builds in the nightly build section that classify themselves as ReactOS 0.4.16, is this branched from the main because 0.4.15 is headed for release, or am I missing something? Also, should I keep using 0.4.15 builds or use the 0.4.16 builds?

0.4.16 builds

Edit:I wanted to mention I've had more success with the 0.4.15 builds, most success I've had was a liveCD 0.4.14 build I got somewhere, should I just try more 0.4.16 builds?

Edit 2:Buildbot is uploading to the site again after months and the first build of 0.4.16 I use works wonders on 2 7-era laptops (+1)

Why are last a few nightlys non-existent? did building bot fail?a

Error opening source

Something went wrong while opening
(the path to the ISO image).

Error: (0 , h.requestMetadata) is not a function.

I tried rufus, but it said “The image you have selected is an ISOHybrid, but its creators have not made it compatible with ISO/File copy mode. As a result, DD image writing mode will be enforced.”

I have a few old laptops at my disposal (a Dell Inspiron 5100, a Dell Inspiron 5160 somewhere, and a Lenovo Thinkpad X201, a Gateway NE56R31u, and a Windows 8.1 era Toshiba Satellite (also location unknown); not going to list the others because they're not in the scope of what I'm hoping to do, but they're all dinosaurs by now) and I was considering installing ReactOS onto one of them. Not as a daily driver, obviously, but something to just have a functioning copy of the OS on. What I'm thinking about doing is upgrading the RAM (if I can) and putting a fresh SSD in one to use ReactOS on. I saw the video by MichaelMJD last night about "official hardware", and I've also been thinking about looking for a cheap-but-useable Dell Latitude D630 on eBay to use for this. It wouldn't be for anything major, mostly just to have something to pull out and experiment with from time to time. I probably won't be using the nightly builds unless I can get all of the drivers to work. Any suggestions or ideas?

i tried this OS lpong time ago to test virus like memz, they work very well, but for real hardware i tried to install it but it wont boot the installer and the question surged, do i need to have a Legacy boot, because the computer only allowed UEFI OS Or there is a way to boot it even having UEFI laptop

I have a toshiba laptop from the early 2000's w/o. a hard drive.

1. I made a live usb of reactos. Booting from plopbt, i select a boot option, and hangs on usbd.sys when booting on any mode. Any fixes?
2. I have some drivers for the laptop (Toshiba Satellite A15 S127, 2003). Is it okay to install them without bricking a system?

I'm all behind the idea of a Windows alternative, so I'd love to do a recurring donation to this project if I knew that it would actually help, but I know very little about this dev team and it seems like work on this project has progressed very slowly.

Does anyone here donate to the project and/or would you recommend doing so?

I have a Win 7 era laptop (g6-2000 series notebook), what can I do for drivers?

I used Rufus to create a bootable usb to install reactos, when I boot this usb I see a loading bar for a second and then I’m stuck at a blank screen. By help would be appreciated

Can it run 16-bit dos applications