Thanks again to boot.dev for sponsoring! Head over to sponsr.is/bootdev_MichaelMJD and use my code MICHAELMJD to get 25% off your first payment. That’s 25% off your first month or your first year, depending on the subscription you choose.
Hi Michael! 0.4.15 has been branched for release candidate and is receiving fixes to prepare for release. Since your last video we started holding meetings more regularly and were able to resolve several disagreements.
That was awesome and I’d do it again in a heartbeat. I’m hoping to slowly address the AMD side issues as it’s becoming increasingly clear they’re going to work first. Thanks for the awesome retest :) -The_DarkFire_
Hey Michael! I made a ReactOS driver for your exact Broadcom 57XX gigabit ethernet card, so internet should work out of the box for you. Life is busy though and I haven't gotten around to making the suggested changes required to merge it into master build
Very courteous of you to provide the seizure warning. I personally do not have seizure issues where I would need to skip the segment, but it's very respectable and shows your empathy and respect as a creator towards your audience. I'm new here, this is the very first video that I've seen of yours, and that little detail has encouraged me to subscribe to your channel.
Last I heard there were internal problems with the part of the ReactOS team that manages the release versions and led to such a stark contrast between Nightly and Release. It's a really understandable source of confusion for anyone that doesn't stalk every new bit of ReactOS information.
I keep telling people that Windows 2k, and by extension, Server 2k3, is the peak pure windows experience. Granted, 2k3 is a sort of cross between 2k and XP when it comes to the UI, but I find it counts towards peak Windows. It's a shame that the higher ups on the windows development have forgotten what makes Windows good...
The CD thing is about the deprecated Win95-era optical API used in those games that doesn't work either on modern Windows versions nor ReactOS. Regarding the debugger detection it works like this: at the very start of the code it replaces a JMP (jump to place in code) instruction with all zeros (NOP, no operation) and right after that the JMP in question and the code that displays the error. Most CPUs will cache everything to run it in advance and changing the code mid execution would do nothing, but sometimes (including when a debugger is there), the cache will be discarded therefore the JMP won't work (it has just been replaced) causing the error code to run. This is often considered bad practice.
@@ApertureSciencePsycho actually, the instruction 00 decodes to, is not a nop because it has side-effects. Suppose that eax contains the address of a valid memory area. Then, `add [eax], al` would add the low byte (al) of the value of that address, to the contents of whatever is stored at that address, thus, modifying what's there. In particular, if eax == 0, there would be a NULL access being done, and your program would crash. So, this is NOT a no-operation.
ive been following ReactOS for YEARS i mean like 12 - 15 this is by far my favorite in development OS out there, I hope it continues on to get bigger and better
15 minutes into the video and I have to say this is the best commercial for nightly builds being spectacularly awesome that I have ever witnessed! Ha ha! I believe your take on nightly builds was spot on. Thanks for gaslighting us, Devs, that’s great.
You can hear the Lovecraft-protagonist-grade madness in Michael's voice when he talked about everything he went through after booting into safe mode resulted in nothing but a black screen. Not to mention the giggle around the 25-minute mark.
Hey I noticed that your D531 is using BIOS revision A06, while Dell's website has newer revisions for that model (A10 and A12). Not sure how much or even if that would help with anything when it comes to running ReactOS on it, and I can't even find changelogs to check what they do exactly, but I guess since they bothered making those updates back then, they probably fixed some things. Obviously, if you want to try updating it, I'd use a stable version of Windows from back then. Also, a warning : revision A12 on the website is suspiciously recent and some people reported it being corrupt… may be something with them re-generating the latest updates in bulk with a newer certificate and not checking that the updated files actually work, so you might want to avoid that one, or perhaps try finding an earlier file on the web archive instead.
The dev I spoke with said the BIOS revision was fine, so I just left it on A06. I was also confused about the pretty recent date for the latest version on Dell's site.
A reskinned versión version reporting version 4.10. 1998 (Windows 98 first release) or 4.90.3000 (Windows Me) is in order! (although some early Memphis version would be more bugginess accurate).
@@AureliusR My opinion can be seen as optimism, realism or pessimism. Depending on the perception of the observing individual. When i first read about ReactOS in an IT magazine, i was a juvenile. Now i have a wife, a house and achieved my major life goals. ReactOS still hasn't made much progress. If HL3 will ever be a thing, it's gonna be within the next 10 years, i assume. So it isn't wrong to expect it to be released before ReactOS becomes useful.
we can talk about how amazing it is that you can copy system files from Server 2003 and they WILL work with ReactOS! amazing that React is computable to the point it one CAN copy files from Server 2003!
Michael, this is a great video! You made the wanted follow up, you installed it on real hardware, you came a long way further than I ever did. Thank you for sharing these experiences!
Yup, this is a living 21st century example of what the PC hobby was like back in the early 90s. If I could reclaim all the hours I spent reloading and rebooting I'd be about 38 instead of 66.
I totally agree with the Release vs Nightly confusion. I've inly used the Release because I didn't want to be bothered with a Nightly test version and its problems. I guess I'll be downloading a Nightly tonight.
The thing I've learned with most nightly builds for any software is that generally, most show-stopping regressions since a latest "stable" have been corrected. The only thing I've ever seen contradict this is with Debian, where stable actually means willfully putting effort into tanking your install.
Maybe its my Linux brain but when I think stable release I think the release that works the best to the level that the project is at, while "nightly" or "unstable" is for the cutting edge releases that have additions and changes that are tests and make the release less robust as a result, then when that testing is done and its as stable as possible they move that to stable?
Unfortunately "stable" is a bit of a loaded term It both means a) doesn't crash (what most people think of) and b) doesn't change radically (what Debian stable is most about) The idea of stable is that if you have a workflow and you keep staying on that stable version, it won't change, you'll be guaranteed your workflow will keep working and you won't have to change anything (or worse, realize that your very weird, wacky, way of doing something doesn't work anymore)
My experience with it is that it fixes things from the stable release, and breaks other things that might have regressions. Just the nature of the beast, I suppose.
An OS that has been in development for like 25 years doesn't even have working drivers for the official hardware that it has been developed on, and nothing works on it. Seems like a good OS.
It is not a easy task to reimplement an operating system that was originally made by probably hundreds or maybe even by more than a thousand of developers in a reasonable time. They still made a lot of progress lately, mostly in terms of stability of ReactOS from what I've heard. I believe that if the project was founded well, the progress would accelerate very quickly and we could get an actual beta in like few years.
@@Winnetou17 Difficult and tedious and MS keeps moving the goalposts. But whilst the developers enjoying working on it is surely reason enough to do it, one has to question the value of a project in such a state after a quarter of a century.
@@chaos.corner Well, they collaborated with and contributed to WINE, so I wouldn't say it was a waste, even if ReactOS doesn't ever reach an usable status.
I just want to say thank you for your videos. :) For some reason I really like exploring older tech/software., but also like to see things outside my usually bubble (Linux/Android/MacOS). It also help me to fall a sleep, but I try to re-watch them when I'm awake again. Keep up the good work!
I have an old 42" LG TV that I've moved to a guest bedroom and replaced it with a 48" TV. The 48" TV is smaller than the old TV because of how big the bezels are. It was also like 2/3 the weight. Stuff is getting crazy small.
40:06 Massive Credit is due to Bungie/Microsoft for making a game so robust that it can still run SOMEHOW on barely functional and barely compatible environments like ReactOS kernels from far in the future. I'm utterly shocked that the game even renders over 15 frames a second let alone has smooth gameplay. Well done Halo Devs!
I don’t think that joke works very well. Like, anything will react in some way, right? Saying that “because it reacts by crashing, we call it reactOS” just, doesn’t seem to make sense?
For a more mature project I think your reasoning about release vs nightly makes perfect sense. In this case I think the difference is simply that every release is also pretty experimental, and with the latest release years out of date it may well be that the current status is better no matter whether there is a new release or not. Completely agree that it's a communication problem having the project web site directing people to use said old release in that situation, though.
Been keeping an eye on ReactOS since 2011. Its too bad they haven't been able to make more progress. I'm sure its difficult, but I hope this video brings it more support and speeds up progress.
At first I was wondering what you doing with expectations so high of ReactOS, but later in the video I see you put in all sorts of work trying to get things working and I was very impressed. Good effort and great video!
reactOS is gonna be a godsend for retro computing when it starts to mature. imagine a WinXP machine where you don't have to worry about security constantly and with the ability to get modern QoL improvements to it.
it's a bit hard for me to understand the point of this whole endeavor. I use XP machines almost every day, and the problems with QOL features do not stem from operating system, but the hardware. No OS will ever make a single core machine fully usable again, and more powerful machines don't lack much in terms of QOL, even modern Internet is fully usable under XP with Supermium. I admire the developers' skills and passion, but it just seems they're working really hard to achieve something that would've been worth pursuing 20 years ago.
@@inferi312 well for starters it’s a nightmare to actually update XP these days. If you’re like me and have an RTM release you either have to slip stream service packs into the installer and then install Legacy Update and then run that a couple of times before you’re actually up to date The main goal of this is just a FOSS windows which will I think many years in the future be extremely useful like how free dos is.
@@inferi312 I seriously hope your XP machines are air gapped and are required for core services like embedded systems for a business with no suitable replacements, else you are a fool to keep using it in this day and age.
About the nightly and stable builds, nightly builds are fixed and updated often, sometimes every night (hence the name). After many people and machines have tried the fixes and patches with no problems, then they release a stable version. They don't want to release a stable version until they know it will work for everyone. So, if you want a version that will work for nearly any device and is tried and tested, get stable. If you want to get the latest and greatest, with experimental patches and updates being tested and put in, then get nightly.
Fun thing is, if you put the CD codes into Steam, the games will be added to your library. In fact, my HL code got me HL, Blue Shift, Opposing Force and maybe some others too.
It’s actually because this model shipped with two LCD sizes, and instead of redesigning the entire housing for the cheaper panel, dell just put it on the same chassis and thickened up the bezels lol
Gotta love the devs (or at least the person in charge of the Twitter account) making fun of you because "everyone knows the stable release sucks!" but... the daily doesn't seem that much better. Sure it doesn't crash, but it still doesn't actually work either. (Oops, I spoke too soon about crashing! Then, that poorly-written shibe meme is just being sore.)
Stable does not mean less crashes. Stable means the public methods don't change in subsequent sub-releases. It is a very important difference and one that may prohibit a new release because some APIs are still work in progress and freezing them now may make something way harder to implement later because now it has to remain stable otherwise other components need further reworking.
Thank you! I wish more people would get this. Same with Debian stable, many people don't get that stables doesn't just mean that it doesn't crash. Maybe we should invent a new term for this, like "steady".
I think you might be missing a bit of the bigger picture here. I could be wrong, but doesn’t "stable" usually imply reliability for most people? It suggests fewer crashes and a more dependable experience. The idea of a stable API might be better captured by terms like LTS (Long-Term Support), which emphasize consistency over time. To agree with previous comment, If most people misunderstand the term, it might indicate that "stable" isn’t the best choice for conveying this specific meaning.
@@tehaiks I think you might be missing the fact we're talking about ReactOS, are you seriously considering calling anything LTS about it, that's just crazy to even think about that. And no, LTS means your programs and dependencies stay functionally the same for a long time and only get bug and security fixes and nothing else.
I'm not gonna lie, even after being mortified by how much of a nightmare getting it that far was, seeing Halo launch in an open source OS and it actually working relatively fine for the hardware it was running on semi-natively still had my jaw drop.
@@SidcupRC It's native in this case. ReactOS does use some Wine code, but it's not being implemented on top of anything. It's an actual Win32 implementation down to the OS level.
32:53 is the serial port disabled in the BIOS? maybe enabling it would've allowed it to boot up? error says serial port isn't found, I'm assuming it's going to try to send debug output over serial and bombs out bc it's not there.
Thank you for this video. I had downloaded it and was going to install it on an old pc, but, now I've seen it (NOT) working, I'm going to give it a miss. Whilst I'm happy to fault find and spend hours getting things working, this does not apply to my gaming time, I've done all that already, now it's a must for me to just turn the system on and be gaming two minutes later.
i remember being excited about things after i heard about this project taking on where freewin left off or whatever. I even got some of the early releases and got nothing so i left it alone. here we are 2 decades later and based on your video, it's still barely off the ground. What's happening here though is very reminiscent of getting new software or hardware to work in that there's nowhere to turn, no place to really get an answer, then running out of options and trying random shit. ...kinda brings back some warm and fuzzy memories..
Just like Wine in the old days (circa 2003/6) When I use to put so many windows dlls, dcom, etc it to make games and even internet explorer 6 to work. 😂. Fun times. I wish I had the time to mess around nowadays...
I think the point of not just making another release is, they'd have to make a full release every night for it to not be irrelevant. As soon as a nightly build comes out after that release its probably better, and it gets better every night.
Unless I'm missing something, you'd think the official testing notebook for ReactOS would at the very least have the bare minimum working on it with how long it's been in development. Still, reverse-engineering the NT kernel is quite the feat, so it's understandable that it'll take a good while for everything to get up and running properly. Wonder how many of these bugs in this video alone got fixed after it was posted. At least the test-bed will be more usable for testing-out games and GPU-related stuff. All that's missing now is the audio.
The debugger message is probably coming from the CD copy protection that Call of Duty 1 has (only on the Singleplayer exe), and you could have bypassed it with a NoCD patch. It probably wouldn't have worked anyway because this game uses OpenGL exclusively, with the "DirectX 9.0b" requirement likely being only for the sound backend.
It's like Windows XP - and XP (NT 5.1/5.2 kernel) was mostly used with 32 bit software. While there was a x64 version, who cares, except for big databases.
Totally. I first learned of it in the late 90s. The fact that they are still tinkering with it without it being any further along than it is just makes me shake my head. I would think by now the OS would either be essentially completed or they would've given up.
Yeah, even AROS (open-source AmigaOS clone) and especially Haiku (open-source BeOS clone) are much, MUCH further along than ReactOS and don't crash every two seconds. I understand that Windows is a much more complex OS than AmigaOS or BeOS, so it's more difficult to get right, but it's been over 20 years.
@@pikachuchujelly7628 but amazingly, they have not given up. They're making incredibly slow progress, but still going after all these years. That's why it seems like zombie project to me.
Nice, reminds me of those WinXP destruction vids, but it comes predestroyed ... kinda ironic considering I was legit excited about this 20 years ago. Guess some things never were meant to be.
Glad to see the developers seeing the positives in your video and implementing changes. Its a shame its not in a more solid position but hopefully this will change.... And not too far in the future 😅
I'm absolutely blown away by how far some people can push the limits. To think that someone managed to replicate the entire Windows system from scratch with an open-source approach is mind-boggling. I have no idea how they pulled this off, but I can only assume there's an insane amount of reverse engineering involved, especially since it’s not based on Linux. Even if many things don't run properly it's a truly impressive work!
40:54 looks like your mouse input is in a very low Hz mode... like 10 Hz or something like this, and sometimes not updating, as the video itself looks smooth, just your motion looking around does not.
Great vid, and man... does that take me back to some bad days watching the system hang after mup.sys and having to go dig for "what was it doing after that..." :D Anyway, might want to throw Quake (the original) into the "test toolbox". It was one of the few things that ran in NT4 (and thus one of the reasons i became near competition level at it). It's a pretty "neutral" game as far as tech goes, and you have bucket loads of different ports, supporting OpenGL, DX, you name it. Also very small and no install, +2 bonus.
Thanks again to boot.dev for sponsoring! Head over to sponsr.is/bootdev_MichaelMJD and use my code MICHAELMJD to get 25% off your first payment. That’s 25% off your first month or your first year, depending on the subscription you choose.
sigma
Who asked for sponsor
Thank God you haven't joined to the dark raid shadow mjends side😅
@@IunahYTno one asked for it, but without sponsorship, he wouldn't be able to make videos, apparently.
hey Michael pls pin me plsssss man I'm a fan
Hi Michael! 0.4.15 has been branched for release candidate and is receiving fixes to prepare for release. Since your last video we started holding meetings more regularly and were able to resolve several disagreements.
I love that for you guys! Good luck and godspeed
I love the project! Keep going!
HOORAAAAY! good luck everyone!!!
Good news for people who love good news
YAY! ReactOS has so much potential! Glad to hear that things are improving!
michael mjd's commentary will singlehandedly save the ReactOS project
"..Hey it's michael from the future here"
you know something went wrong when michael from the future comes to interrupt the video
You know something goes wrong when Michael releases a video, but everything goes wrong.
You know something goes wrong when he uploads in general lol
Why don't they just use the server 2003 dlls anyway? Why do they implement WineD3D?
Yes
That was awesome and I’d do it again in a heartbeat.
I’m hoping to slowly address the AMD side issues as it’s becoming increasingly clear they’re going to work first.
Thanks for the awesome retest :)
-The_DarkFire_
Amazing!
Dude, you're awesome. Improving ReactOS on the fly like this is great.
hi john
You are the real MVP man, keep up the good work!
Hey Michael! I made a ReactOS driver for your exact Broadcom 57XX gigabit ethernet card, so internet should work out of the box for you. Life is busy though and I haven't gotten around to making the suggested changes required to merge it into master build
Very, very cool
Very courteous of you to provide the seizure warning. I personally do not have seizure issues where I would need to skip the segment, but it's very respectable and shows your empathy and respect as a creator towards your audience. I'm new here, this is the very first video that I've seen of yours, and that little detail has encouraged me to subscribe to your channel.
I really appreciate the kind words! I feel it’s very important to put those in so I always make sure to. Thanks for subscribing!
Last I heard there were internal problems with the part of the ReactOS team that manages the release versions and led to such a stark contrast between Nightly and Release. It's a really understandable source of confusion for anyone that doesn't stalk every new bit of ReactOS information.
I mean look at it, it can't even open any webpage
It's fun seeing ReactOS use the same UI elements as Windows Server 2003
everything in windows is still using those ui elements lmao
it's mainly based off server 2003 so that's why
anything from other Windows versions is purely for compatibility reasons
@@generallyunimportant Ech, maybe design wise. I think only the Explorer program has been left mostly untouched.
@@generallyunimportant I don't think that warranted a LMAO.
I keep telling people that Windows 2k, and by extension, Server 2k3, is the peak pure windows experience. Granted, 2k3 is a sort of cross between 2k and XP when it comes to the UI, but I find it counts towards peak Windows. It's a shame that the higher ups on the windows development have forgotten what makes Windows good...
The CD thing is about the deprecated Win95-era optical API used in those games that doesn't work either on modern Windows versions nor ReactOS.
Regarding the debugger detection it works like this: at the very start of the code it replaces a JMP (jump to place in code) instruction with all zeros (NOP, no operation) and right after that the JMP in question and the code that displays the error. Most CPUs will cache everything to run it in advance and changing the code mid execution would do nothing, but sometimes (including when a debugger is there), the cache will be discarded therefore the JMP won't work (it has just been replaced) causing the error code to run. This is often considered bad practice.
NOP is opcode 0x90 on x86 and x64 CPUs, not "all zeroes".
@hbm293 , a quick search lead me to an old forum that says that 0x0000 decodes to "add [eax], al" but has no effect which means it's a NoP
@@ApertureSciencePsycho actually, the instruction 00 decodes to, is not a nop because it has side-effects.
Suppose that eax contains the address of a valid memory area.
Then, `add [eax], al` would add the low byte (al) of the value of that address, to the contents of whatever is stored at that address, thus, modifying what's there.
In particular, if eax == 0, there would be a NULL access being done, and your program would crash.
So, this is NOT a no-operation.
@hbm293 idk that old forum guy knows better
ive been following ReactOS for YEARS i mean like 12 - 15 this is by far my favorite in development OS out there, I hope it continues on to get bigger and better
15 minutes into the video and I have to say this is the best commercial for nightly builds being spectacularly awesome that I have ever witnessed! Ha ha! I believe your take on nightly builds was spot on. Thanks for gaslighting us, Devs, that’s great.
You can hear the Lovecraft-protagonist-grade madness in Michael's voice when he talked about everything he went through after booting into safe mode resulted in nothing but a black screen. Not to mention the giggle around the 25-minute mark.
Now do the Everything Goes Wrong version
man i wish there is a "everything goes right" video where it works 1st attempt with no flaws
This is the everything goes wrong version 😅
@@MichaelMJD fair hahaha, next time a everything goes right version?
@Emayeah yeah We NEED THAT😂😂
We need a Everything Went Better than Expected version
Hey I noticed that your D531 is using BIOS revision A06, while Dell's website has newer revisions for that model (A10 and A12). Not sure how much or even if that would help with anything when it comes to running ReactOS on it, and I can't even find changelogs to check what they do exactly, but I guess since they bothered making those updates back then, they probably fixed some things. Obviously, if you want to try updating it, I'd use a stable version of Windows from back then.
Also, a warning : revision A12 on the website is suspiciously recent and some people reported it being corrupt… may be something with them re-generating the latest updates in bulk with a newer certificate and not checking that the updated files actually work, so you might want to avoid that one, or perhaps try finding an earlier file on the web archive instead.
The dev I spoke with said the BIOS revision was fine, so I just left it on A06. I was also confused about the pretty recent date for the latest version on Dell's site.
they’ve succeeded in recreating the nightmare of using a really old version of windows, what an achievement!!
A reskinned versión version reporting version 4.10. 1998 (Windows 98 first release) or 4.90.3000 (Windows Me) is in order! (although some early Memphis version would be more bugginess accurate).
"Imagine Windows 2000 except nothing works."
@@MistahMatzah So just Windows ME
I love how sometimes the camera gets the OS/2 box at the background, as if it's smirking to all Michaels' attempts to bring ReactOS to life.
I always look at that OS/2 box too. I have one at home too :)
Reverse engineering windows seems like a weird masochistic thing to devote your life to
yes
It's kinda sad as theres no need for it considering the adancements of wine and kernel
@@SameriddAndCave nah it definitely has a reason to exist still as a fun hobby project
fr
Based, to be honest.
I played with reactos years ago. It's cool to see that they're still working on it.
GTA VI will release before ReactOS has a stable. We may even get Half-Life 3 before we see any sort of half-decently working ReactOS build.
We'll see about that.
@@michalthekindInstall ReactOS on the AI to escape it
>
Why be so negative? What does that get you in life? Other than everyone noticing how negative and pessimistic you are.
@@AureliusR My opinion can be seen as optimism, realism or pessimism. Depending on the perception of the observing individual.
When i first read about ReactOS in an IT magazine, i was a juvenile. Now i have a wife, a house and achieved my major life goals. ReactOS still hasn't made much progress.
If HL3 will ever be a thing, it's gonna be within the next 10 years, i assume. So it isn't wrong to expect it to be released before ReactOS becomes useful.
we can talk about how amazing it is that you can copy system files from Server 2003 and they WILL work with ReactOS!
amazing that React is computable to the point it one CAN copy files from Server 2003!
Just keep copying more files from Server 2003 until everything works
Better yet, just install Microsoft Server 2003...
@@mchenrynick that was the best operating system ever, eventually ReactOS gets there
It’s the Ship of Theseus all over again, if you keep replacing files is it still ReactOS?
Michael, this is a great video! You made the wanted follow up, you installed it on real hardware, you came a long way further than I ever did. Thank you for sharing these experiences!
Yup, this is a living 21st century example of what the PC hobby was like back in the early 90s. If I could reclaim all the hours I spent reloading and rebooting I'd be about 38 instead of 66.
Fun fact: Mizu is japanese for water, so the Mizu theme is probably supposed to look kinda like a water theme.
I totally agree with the Release vs Nightly confusion. I've inly used the Release because I didn't want to be bothered with a Nightly test version and its problems. I guess I'll be downloading a Nightly tonight.
The thing I've learned with most nightly builds for any software is that generally, most show-stopping regressions since a latest "stable" have been corrected. The only thing I've ever seen contradict this is with Debian, where stable actually means willfully putting effort into tanking your install.
Maybe its my Linux brain but when I think stable release I think the release that works the best to the level that the project is at, while "nightly" or "unstable" is for the cutting edge releases that have additions and changes that are tests and make the release less robust as a result, then when that testing is done and its as stable as possible they move that to stable?
Unfortunately "stable" is a bit of a loaded term
It both means a) doesn't crash (what most people think of) and b) doesn't change radically (what Debian stable is most about)
The idea of stable is that if you have a workflow and you keep staying on that stable version, it won't change, you'll be guaranteed your workflow will keep working and you won't have to change anything (or worse, realize that your very weird, wacky, way of doing something doesn't work anymore)
My experience with it is that it fixes things from the stable release, and breaks other things that might have regressions. Just the nature of the beast, I suppose.
An OS that has been in development for like 25 years doesn't even have working drivers for the official hardware that it has been developed on, and nothing works on it.
Seems like a good OS.
To be fair the version ReactOS devs use has an nvidia GPU and not an AMD one
It is not a easy task to reimplement an operating system that was originally made by probably hundreds or maybe even by more than a thousand of developers in a reasonable time. They still made a lot of progress lately, mostly in terms of stability of ReactOS from what I've heard. I believe that if the project was founded well, the progress would accelerate very quickly and we could get an actual beta in like few years.
@@MarcinKralka Not only reimplement, but reverse engineer it, and make it so it's compatible. It's a lot of very difficult and tedious work
@@Winnetou17 Difficult and tedious and MS keeps moving the goalposts. But whilst the developers enjoying working on it is surely reason enough to do it, one has to question the value of a project in such a state after a quarter of a century.
@@chaos.corner Well, they collaborated with and contributed to WINE, so I wouldn't say it was a waste, even if ReactOS doesn't ever reach an usable status.
I just want to say thank you for your videos. :)
For some reason I really like exploring older tech/software., but also like to see things outside my usually bubble (Linux/Android/MacOS).
It also help me to fall a sleep, but I try to re-watch them when I'm awake again. Keep up the good work!
ReactOS Team: **Takes 20 years to make a Windows 2000 clone that can't even install drivers properly**
Thanos MJD: "Fine. I'll do it myself...."
Wow. ReactOS has really captured the experience of dealing with Windows driver installs from the 90s/00s perfectly.
ReactOS is Back
we’re so back
And it needs to leave again 😂
It never left lol
just need druaga1 to return
Why?
and as expected, everything goes wrong EVEN ON OFFICIAL HARDWARE. wow.
I know right! LMAO
ReactOS, go home you’re drunk 😂
a shame the stuff that isn't supported yet doesn't work! wow!
@@danielktdoranieit's Alpha testing...
It's not surprising that securom, safedisc and other copy protections don't run on ReactOS.
@@shadowopsairman1583yeah but was in alpha for 2 decades
I have been eagerly waiting for this video
I had totally forgot how absolutely *huge* the bezels are on those 2005-08 Dell Latitudes.
I have an old 42" LG TV that I've moved to a guest bedroom and replaced it with a 48" TV. The 48" TV is smaller than the old TV because of how big the bezels are. It was also like 2/3 the weight. Stuff is getting crazy small.
Why is having small bezels considered a feature? It feels kinda like wireless keyboards to me, some kind of stupid gimmick.
@@Eddies_Bra-att-ha-grejer bezels take up space. Smaller bezels mean a larger screen or a smaller monitor for the same screen size.
40:06 Massive Credit is due to Bungie/Microsoft for making a game so robust that it can still run SOMEHOW on barely functional and barely compatible environments like ReactOS kernels from far in the future. I'm utterly shocked that the game even renders over 15 frames a second let alone has smooth gameplay. Well done Halo Devs!
Thanks to you yesterday I came to know of this OS I didn't know anything about. I'm currently compiling it under linux and everything went fine so far
I'm honestly pretty impressed this works at all
It's called ReactOS because it reacts by crashing
reactOS' official reaction when you try to do literally anything on it: 😱😱😱
Rename suggestion: CrashOS.
I don’t think that joke works very well. Like, anything will react in some way, right? Saying that “because it reacts by crashing, we call it reactOS” just, doesn’t seem to make sense?
I get something to watch while eating
Bro ain't no way I'm 1 second Earlier than you 😂 what a coincidence
im eating rn lol
@@vista6009nah i beat you by approx: 10.871 milliseconds
I was eating 1 min ago
Finished my dinner while watching lmao@@Mahanagha
For a more mature project I think your reasoning about release vs nightly makes perfect sense. In this case I think the difference is simply that every release is also pretty experimental, and with the latest release years out of date it may well be that the current status is better no matter whether there is a new release or not. Completely agree that it's a communication problem having the project web site directing people to use said old release in that situation, though.
Been keeping an eye on ReactOS since 2011. Its too bad they haven't been able to make more progress. I'm sure its difficult, but I hope this video brings it more support and speeds up progress.
At first I was wondering what you doing with expectations so high of ReactOS, but later in the video I see you put in all sorts of work trying to get things working and I was very impressed. Good effort and great video!
I think all hardware that can still run XP / Server 2003 will cease to work before ReactOS ever becomes a viable XP alternative.
ReactOS will become a viable XP alternative finally after Microsoft moves on from the NT kernel.
reactOS is gonna be a godsend for retro computing when it starts to mature. imagine a WinXP machine where you don't have to worry about security constantly and with the ability to get modern QoL improvements to it.
that's a really good idea wtf
I've been telling myself this for at least a decade or more now
I'm still huffing that copium that we might have a stable release in my lifetime....
it's a bit hard for me to understand the point of this whole endeavor. I use XP machines almost every day, and the problems with QOL features do not stem from operating system, but the hardware. No OS will ever make a single core machine fully usable again, and more powerful machines don't lack much in terms of QOL, even modern Internet is fully usable under XP with Supermium. I admire the developers' skills and passion, but it just seems they're working really hard to achieve something that would've been worth pursuing 20 years ago.
@@inferi312 well for starters it’s a nightmare to actually update XP these days. If you’re like me and have an RTM release you either have to slip stream service packs into the installer and then install Legacy Update and then run that a couple of times before you’re actually up to date
The main goal of this is just a FOSS windows which will I think many years in the future be extremely useful like how free dos is.
@@inferi312 I seriously hope your XP machines are air gapped and are required for core services like embedded systems for a business with no suitable replacements, else you are a fool to keep using it in this day and age.
maybe in 2050 they'll be able to be compatible and run like win 2000! yay!
in 3100 right as GTA VI releases they will release the one that's up to date
@@petermmm42 hate to break it to you but that joke doesn't work anymore gta 6 got a release date LOL
@@sonicSnap who knows what if it gets delayed a whole bunch like ksp2 so in that hyoer specific situation my joke works
@@petermmm42 i mean it could but the release date took so long and is technically vague enough that i doubt it'll go that way
By the time Zefram Cochrane makes his first warp flight on April 2063, ReactOS will be fully equivalent/compatible with Windows Vista R1.
You make some of the best tech videos on youtube
About the nightly and stable builds, nightly builds are fixed and updated often, sometimes every night (hence the name). After many people and machines have tried the fixes and patches with no problems, then they release a stable version. They don't want to release a stable version until they know it will work for everyone. So, if you want a version that will work for nearly any device and is tried and tested, get stable. If you want to get the latest and greatest, with experimental patches and updates being tested and put in, then get nightly.
The AC'97 driver brings me back
Good to see nothing's changed in decades with ReactOS, still a dumpster fire just like its inspiration. Truly, one of the OSes of all time.
I wonder how much other hardware will work if you copy over drivers from a Win2K/XP/Server2K3 install.
I am pretty sure the ReactOS CD drivers don't work with DRM schemes used by Half-life Blueshift or PONG.
Fun thing is, if you put the CD codes into Steam, the games will be added to your library. In fact, my HL code got me HL, Blue Shift, Opposing Force and maybe some others too.
Honestly super cool that your videos are able to inspire more development and changes on ReactOS
It's funny how shocking the size of the bezel on that laptop was. We've come a long way
It’s actually because this model shipped with two LCD sizes, and instead of redesigning the entire housing for the cheaper panel, dell just put it on the same chassis and thickened up the bezels lol
If you look at something like the PowerBook G4 Titanium or the Latitude C840, their bezels are nice and thin
Yeah, new video! Let's goooooooo (I love to listen to these videos as podcast while I cook. For real. Sometimes I even go back to old videos to do so)
So, it is the Nightly MJD Frankenstein 2000 Version now.
Edit: Very nice that you got the Help :)
Thank you for making this video I was wondering if anything had changed I hadn't seen anything recently.
So much work! Thanks for the videos ultimately! 👍
Gotta love the devs (or at least the person in charge of the Twitter account) making fun of you because "everyone knows the stable release sucks!" but... the daily doesn't seem that much better. Sure it doesn't crash, but it still doesn't actually work either. (Oops, I spoke too soon about crashing! Then, that poorly-written shibe meme is just being sore.)
3:30 bro just spent two and a half minute yapping to the trollers lmao
Stable does not mean less crashes. Stable means the public methods don't change in subsequent sub-releases. It is a very important difference and one that may prohibit a new release because some APIs are still work in progress and freezing them now may make something way harder to implement later because now it has to remain stable otherwise other components need further reworking.
Thank you! I wish more people would get this. Same with Debian stable, many people don't get that stables doesn't just mean that it doesn't crash.
Maybe we should invent a new term for this, like "steady".
I think you might be missing a bit of the bigger picture here. I could be wrong, but doesn’t "stable" usually imply reliability for most people? It suggests fewer crashes and a more dependable experience. The idea of a stable API might be better captured by terms like LTS (Long-Term Support), which emphasize consistency over time. To agree with previous comment, If most people misunderstand the term, it might indicate that "stable" isn’t the best choice for conveying this specific meaning.
@@tehaiks I think you might be missing the fact we're talking about ReactOS, are you seriously considering calling anything LTS about it, that's just crazy to even think about that. And no, LTS means your programs and dependencies stay functionally the same for a long time and only get bug and security fixes and nothing else.
@@gentuxable fair enough, thanks for the knowledge drop. :)
If this was more stable and updates were more regular, I would love to use this as daily. Love the whole old Windows feel, brings back memories.
Your tech videos bring a smile to my day, tysm
I'm not gonna lie, even after being mortified by how much of a nightmare getting it that far was, seeing Halo launch in an open source OS and it actually working relatively fine for the hardware it was running on semi-natively still had my jaw drop.
But doesn't it use code from the WINE project? Is it even 'native'?
@@SidcupRC It's native in this case. ReactOS does use some Wine code, but it's not being implemented on top of anything. It's an actual Win32 implementation down to the OS level.
Micheal i say you should ask people who know how to code and test to join up with reactOS team and give them a helping hand
Fusion power plant and ReactOS are always 20 years away from viability...
I love projects like this. It warms my black, shriveled heart to see people put so much love and effort into them. Wishing you the best!
Congrats on doing this right! Good video
WOOOOOO FINALLY I WAS WAITING FOR THIS
where is the "but everything goes wrong" in the title?
it's always fun to see another react os video
I am currently watching this on a Dell Latitude!
32:53 is the serial port disabled in the BIOS? maybe enabling it would've allowed it to boot up? error says serial port isn't found, I'm assuming it's going to try to send debug output over serial and bombs out bc it's not there.
I feel blessed that Michael finally posted
They’re testing on the same laptop I used at work 15 years ago? Nothing else? That explains it.
Thank you for this video. I had downloaded it and was going to install it on an old pc, but, now I've seen it (NOT) working, I'm going to give it a miss. Whilst I'm happy to fault find and spend hours getting things working, this does not apply to my gaming time, I've done all that already, now it's a must for me to just turn the system on and be gaming two minutes later.
I love that there is a dedicated team of software developers who do their best to pack all of the worst aspects of the windows XP era into one package
i remember being excited about things after i heard about this project taking on where freewin left off or whatever. I even got some of the early releases and got nothing so i left it alone. here we are 2 decades later and based on your video, it's still barely off the ground. What's happening here though is very reminiscent of getting new software or hardware to work in that there's nowhere to turn, no place to really get an answer, then running out of options and trying random shit. ...kinda brings back some warm and fuzzy memories..
Dev - it works on my computer
Project maneger - we are NOT gonna send your computer to the client
“MJD guy entered the chat”
Sooo persistent. well done!
Just like Wine in the old days (circa 2003/6) When I use to put so many windows dlls, dcom, etc it to make games and even internet explorer 6 to work. 😂. Fun times. I wish I had the time to mess around nowadays...
I will never use this but for some reason it makes me so happy someone is doing this.
It's like I am listening to a young Jeff Goldblum, you have the same mannerisms and accent. It is uncanny!
I watch you struggling with all the drivers and system crashes, and I think to myself, this is so much like Windows 95. They nailed it.
I think the point of not just making another release is, they'd have to make a full release every night for it to not be irrelevant. As soon as a nightly build comes out after that release its probably better, and it gets better every night.
Unless I'm missing something, you'd think the official testing notebook for ReactOS would at the very least have the bare minimum working on it with how long it's been in development.
Still, reverse-engineering the NT kernel is quite the feat, so it's understandable that it'll take a good while for everything to get up and running properly. Wonder how many of these bugs in this video alone got fixed after it was posted. At least the test-bed will be more usable for testing-out games and GPU-related stuff. All that's missing now is the audio.
I'm glad this project exists and I'm glad people are working on it. But every time I've tried to touch it and run it, it's been a complete nightmare.
The debugger message is probably coming from the CD copy protection that Call of Duty 1 has (only on the Singleplayer exe), and you could have bypassed it with a NoCD patch. It probably wouldn't have worked anyway because this game uses OpenGL exclusively, with the "DirectX 9.0b" requirement likely being only for the sound backend.
fucking around with drivers and fucking up the system gives me warm nostalgic feelings.
It's like Windows XP - and XP (NT 5.1/5.2 kernel) was mostly used with 32 bit software. While there was a x64 version, who cares, except for big databases.
Is it fair to call ReactOS a zombie OS? It seems like their project has staggered on, not fully alive or dead for soooooooooooo many years.
Totally. I first learned of it in the late 90s. The fact that they are still tinkering with it without it being any further along than it is just makes me shake my head. I would think by now the OS would either be essentially completed or they would've given up.
Yeah, even AROS (open-source AmigaOS clone) and especially Haiku (open-source BeOS clone) are much, MUCH further along than ReactOS and don't crash every two seconds. I understand that Windows is a much more complex OS than AmigaOS or BeOS, so it's more difficult to get right, but it's been over 20 years.
@@pikachuchujelly7628 but amazingly, they have not given up. They're making incredibly slow progress, but still going after all these years. That's why it seems like zombie project to me.
This ReactOS reminds me of Windows NT 3.5 because it has a lot of promise, but very few device drivers.
It's based on 5.2, so 5.1 drivers don't work and 6.0 drivers don't work. There's not much that got released for Server 03.
Nice, reminds me of those WinXP destruction vids, but it comes predestroyed ... kinda ironic considering I was legit excited about this 20 years ago. Guess some things never were meant to be.
Glad to see the developers seeing the positives in your video and implementing changes.
Its a shame its not in a more solid position but hopefully this will change.... And not too far in the future 😅
6:58 Why did you select workgroup and not domain because you don't have a domain controller
Nice Video!Huge fan.
I'm absolutely blown away by how far some people can push the limits. To think that someone managed to replicate the entire Windows system from scratch with an open-source approach is mind-boggling. I have no idea how they pulled this off, but I can only assume there's an insane amount of reverse engineering involved, especially since it’s not based on Linux. Even if many things don't run properly it's a truly impressive work!
40:54 looks like your mouse input is in a very low Hz mode... like 10 Hz or something like this, and sometimes not updating, as the video itself looks smooth, just your motion looking around does not.
The ReactOS auditing drama on Wikipedia is a fun read
Great vid, and man... does that take me back to some bad days watching the system hang after mup.sys and having to go dig for "what was it doing after that..." :D
Anyway, might want to throw Quake (the original) into the "test toolbox". It was one of the few things that ran in NT4 (and thus one of the reasons i became near competition level at it). It's a pretty "neutral" game as far as tech goes, and you have bucket loads of different ports, supporting OpenGL, DX, you name it. Also very small and no install, +2 bonus.