Installing ReactOS in 2024 but Everything Goes Wrong...
Support the channel on Patreon to get early access to these videos!
/ michaelmjd
It's about time we take another look at ReactOS - the open source OS designed to be binary compatible with Windows programs. Let's see what I got myself into this time...
Chapters:
00:00 - Intro
01:55 - Installation
06:24 - Setting up drivers
10:23 - A sign of what's to come
11:06 - Driver Drama
21:50 - Themes & Visual Styles
24:22 - More driver nonsense
29:03 - One last resort
39:35 - The Applications Manager
41:37 - Tux Racer
42:28 - FrontPage 2003
47:08 - Revenge of Arcade
49:00 - SimCity 2000
50:23 - Half-Life
53:30 - Outro
● Gear I use to make these videos: www.kit.co/mjd
Camera: amzn.to/3ipyKc5
Tripod: amzn.to/3pqxycn
Microphone: amzn.to/35UbkXb
Editing Software (Premiere): amzn.to/39kawfS
Thumbnail Editor (Photoshop): amzn.to/3lVqVN6
● Affiliate Links:
Get a FREE 30-DAY TRIAL of Amazon Prime: amzn.to/2xVmMB3
Get a FREE TRIAL of Audible: amzn.to/44CX7tN
Amazon: www.amazon.com/?tag=teammjd-20
● Music/Credits:
$5 Windows 98 PC illustration created by Kurtis Black
Background Music:
"Ersatz Bossa" from the KZhead Audio Library
"Acid Jazz" and "Airport Lounge" by Kevin MacLeod of www.incompetech.com
Outro Music: Silent Partner - Bet On It
Amazon Affiliate Notice: I am a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. All Amazon links that I provide will use my affiliate code with Amazon.
Some materials in this video are used under Section 107 of the Copyright Act of 1976, which allows "fair use" for purposes such as criticism, commenting, news reporting, teaching, and research.
#MichaelMJD #ReactOS #Windows
Just wanted to quickly reiterate that the selection of the latest “stable” build (that yes, is from 2021) for this video was intentional. Yes, there are more recent nightly builds of ReactOS - but I wanted to use the most recent “stable” release, as it’s the one most prominently featured on the ReactOS website, and is what most people are going to end up downloading should they choose to test this out. Nightly builds are even more experimental, and as stated on the site “you're more likely to encounter regressions at the cost of new features.” Because of that, I thought they were better saved for a future video should people be interested. And if you’d like to see that, let me know!
I'd love to see that. Not just for the utter catastrophes that may ensue, but also to see how they stack up compared to the latest stable release here.
I would like to see a comparison of the current state of the nightlies versus the current stable release.
I would be interested! The driver system needs to be worked on (it's non-functional in its current state), and so any kind of feedback in any form could be handy. Provided a ReactOS developer/contributer watches the videos you upload.
Definitely would be interested in seeing that
I am so invested in this OS, thinking I might get my modernized windows 7 someday but the lack of interest of devs and other partners makes me very sad....I think of it as my favourite windows replacement since i am addicted to the windows ecosystem and given the future windows update it is less of windows....
Wish you tried a nightly build, the release build is missing three years worth of updates. Unfortunately our release manager refuses to promote the nightly builds and also refuses to branch a new release so we're kinda stuck :(
Sounds just like with Emulator releases, the stable ones are often years behind.
Are the nightly builds stable though?
@@DarkestVampire92 I didn't get any crashes with the nightly build half a year ago, and I would suspect it's not too different now. And otherwise you have one build for each night that passes, so maybe the issue wasn't there a few days earlier or later.
@@DarkestVampire92 More stable than 0.4.14 thanks to some major registry fixes among other things.
I mentioned the nightly builds in this video but decided against using one as I wanted to get the latest stable build. Not opposed to trying the nightlys sometime though!
"Acknowledge that this is an alpha" reactOS will never exit out of the alpha stage.
Like Star Citizen? Wait I'm probably insulting ReactOS..
@@Soundwave142 I can't wait to run Star Citizen's release version on React OS's first Beta.
@@vogonp4287 LOL that is damn funny.. 🤣
@@Soundwave142 Star Citizen is actually a playable game unlike this complete disaster that fails to do even most basic things after DECADES of development.
@@LastofAvari well trying to reverse engineer windows fully is difficult, thats why wine depens on linux drivers
i love michael just completely ignoring the "WARNING INSTALLING A CUSTOM DEVICE MAY FREEZE YOUR COMPUTER OR RENDER IT UNBOOTABLE" lmao
Warnings? Where we’re going we don’t need warnings.
Only errors count
@@MichaelMJD real
I'm looking for a place to start And everything feels so different now Just grab a hold of my hand I will lead you through this wonderland Water up to my knees But sharks are swimmin' in the sea Just follow my yellow light And *ignore all those big warning signs* 🤣
@@MichaelMJD it might be useful if you install drivers one by one.
"but Everything Goes Wrong..." Of course, it wouldn't be a Michael MJD video otherwise, that's why we are here
I think the "everything goes wrong" part is pretty average for reactOS videos.
ReactOS and Michael MJD were made for each other.
We enjoy the pain.
Love Michaels vids for exactly this reason
@@sumabich721 This, unfortunately.
Snappy reporting "Windows XP 64 (32-bit)" is a result of ReactOS presenting itself as a version of Windows that never existed. See the banner on the desktop, reporting NT 5.2. Microsoft's 32-bit NT 5.2 only existed as Windows Server 2003; 64-bit NT 5.2 came in both Windows Server 2003 and Windows XP Professional x64 varieties. By selecting "Workstation" in ReactOS's setup, it sets the ProductType in the registry to WinNT (as opposed to ServerNT), and because ReactOS is targeting NT 5.2, that combination results in a SKU type that never existed in Windows itself. Snappy is probably seeing NT 5.2 and ProductType=WinNT, the only valid combination from Microsoft existed with Windows XP x64. But then, being a 32-bit operating system, it makes a non-sense sounding term appear in the installer.
Good Video but there are three things that are infinte - The Universe - The react os dev cycle - The WinRAR test version
That's more Sun Tzu's job than Einstein's.
@@ChaseMC215 Considering he wrote the art of RAR
You forgot The Star Citizen Dev cycle as well.
Whats with the Mario Kart Double Dash Rainbow Road clouds
The last one is false actually. I've witnessed how WinRAR falsely gave message about "corrupted" password-protected .rar file, but after activation it started working without a hitch.
If this is a build from 2021, you should also consider making a video on the latest 2024 nightly and see if there are any improvements.
there are !
Please! +1 for 2024 version
+1
an everything going wrong video about reactOS? well now this is just getting far too easy
yeah thats too easy. i had to go trough like 3 dvd drives in my laptop to even get it to install and dont even get me started on installing any driver. the only driver that *worked* was the wifi driver but that would hardlock the os any time i tried to connect to a network that wasn't password protected
or even password protected
What I really want him to find the simplest computing task like installing Word and finding a way to brick his pc while doing so
I assume that reverse-engineering Windows NT code is exceedingly difficult... Because that's the only explanation I can think of as to why it's still in Alpha after 26 years of development.
@@KaneLivesInDeathAccording to LTT and the Wikipedia page, yea it’s reverse-engineered. But I am not trying anything on my devices that is still in alpha. Already ruined enough machines (including two $2500+ gaming computers) thanks to the Windows 11 beta years ago itself 😅
Nothing gives me a heart attack more than the "Safe Mode" failing into a blue screen. Cool OS. lol
Reminds me of Windows 98 (Not SE) and Windows Millenium... :D
Hopefully you make a follow up video using the latest Nightly Build, it is infinitely more stable then the 2021 release
I’m planning on it, and thanks so much for the super chat!!
I hope it happens.
@@MichaelMJD can't wait bro
ReactOS would be a brilliant alternative to trying to find and install old versions of Windows on older systems, however even now nearly 30 YEARS after development began, it is just not in a state where it can be considered an alternative to those old versions of Windows.
Having known of reactos for a long while, ~decade, iv always wished it would actually be a fully functional direct replacement to modern windows. Like graphic drivers and all working for modern hardware. Obviously an extremely tall order, but would be cool to see.
Having known of reactos for a long while, ~decade, iv always wished it would actually be a fully functional direct replacement to modern windows. Like graphic drivers and all working for modern hardware. Obviously an extremely tall order, but would be cool to see.
@@brokeredneck We do have such an alternative. It's called Linux.
@@ericwood3709 Only Linux hates Nvidia drivers, is overly complicated and is uncompatible with tons of software
@@JustGausS well nvidia has now added open source support for linux and the proprietary drivers work perfect. Its quite easy to install those proprietary drivers.
I remember testing Reactos in the middle of 2006. It's amazing how everything, apart from the look, remains exactly the same as I remembered it. Kudos to the developers for still spending so much time on a system that is clearly far from usable.
This is an old build in this video
The issue is that we have not enough active developers, and our release management is kinda absolute crap (and ignoring that the website isnt promoting the nightlys, which are 3 years of updates infront)
@@TheCustomFHD Just out of interest. How far do you think we are from a version of ReactOS that it is possible to use as a daily driver? Do the nightlys fit that bill?
@@porcupinepunch6893 4.14 is 16 years newer than whatever release was available in 2006.
please do a video on the newest nightly build PLEASE I want to see what this looks like with 3 years of updates
ReactOS is so cool in concept and I have empathy for the devs that they're essentially trying to remake Windows from clean-room reverse engineering but DAMN did they bite off more than they can chew
Our dev team is like 7 active people.. and people are not interested in fixing this up, because all thats shown, is it being broken.. (the nightlys are way way newer and massively less broken (not not broken though.))
@@TheCustomFHD I love what you guys are doing. 7 people making an OS. That's incredible, especially with the breadth of needed compatibilities to make a windows NT compatible OS.
@@Alacrysta (ill have to note that "7" in this case was a rough guess, but there doesn't seem to be much more of actually active people that often and repediatly develop for ROS atm.. inactive devs we have some more obviously.) And while i say "our" or "we", all im really doing is keeping up with the community and developers, as im interested aswell in what they are doing, and because i wish to help some day aswell.. but yeah ill see to forward the positive feedback-
lol ReactOS has given me tons of issues in the past trying to get running on older hardware. Great video!
It would genuinely be cool to see a project like ReactOS take off one day, what with all the problems modern Windows has and the fact that Linux is not exactly a drop-in replacement. Sadly it probably won't ever happen. Oh well. We can dream I guess.
Not in this century :D
You know he's trying a 3 yr old version right?
Yeah, would be really cool to have a independent "Windows"
The only real benefit of ReactOS is native driver support. With how good Linux's driver support is these days and DXVK providing a fast replacement for DX, you might as well just use Wine. For gaming, Linux is almost a drop in replacement for Windows now. You can just launch steam and 90% of games just work out of the box. Modern competitive games with anti-cheat tend not to work though.
@@artvandelay1720Well, ReactOS's 'native driver support' is very flaky, to say the least, and will continue to be for awhile...
Hello from ReactOS team! Thank you for the very nice and thorough video! Your efforts are truly appreciated! However, could we kindly suggest a tweak to the title? It might unintentionally mislead viewers, especially those new to the project. While it may seem like you're testing the operating system in 2024, it's clear that 0.4.14 isn't cutting-edge for that year. In actuality, you're testing the system based on its 2020 codebase. Since then, the project has made significant strides in stability and compatibility. ReactOS version 0.4.15 is on the horizon with a massive list of changes, and it will be set to release relatively soon. Anyone eager to explore its improvements can check out the nightly builds.
It's not really fair to call this video misleading when the ReactOS website markets 0.4.14 as "our latest and greatest".
@@shockwave952 they mention the caption, not whole video. The caption could be misleading
@@SuperArt1st What's misleading about it though? It's 2024 and he downloaded the version that's recommended on the project's official website. I'm not trying to be mean about it or anything, but I do think that the team needs to resolve whatever internal issues are preventing them pushing more frequent stable builds. That way they can avoid situations like this where people are trying outdated versions.
@@shockwave952 you are right, but..... This is not a dispute about politics, where you can appeal to anything, including someone’s organizational problems. This is computer science. Version 0.4.14 is 99% based on code not from 2024, but from 2020. That's just a fact. Let's be careful with the facts and try to avoid slippery statements and understatements
@@SuperArt1stWhat? They're just talking about what is on the website. If something is marked as "nightly" it's implied to be a less stable, not recommended version. Why would (what is effectively) a demo video show off the versions of the OS that aren't recommended?
So we got a Michael, and he's attempting to install a jank not-Windows OS. Michaelsoft Binbows LIVES!
7-zip can unpack most self-extracting executables and installers.
That floppy wall is absolutely glorious
One thing I love about ReactOS is the people behind it do watch videos like these and give feedback. I made a video about ReactOS once and they gave some feedback.
00:00 Including WinRAR's free trial
And "Activate Windows" popup
And Visual Studio load time
8:45 "the application failed to initialize succesfully"
That does make sense when you think about it.
Average windows error:
no that does make sense
this gives off "Task failed succesfully" vibes lmao
@@michaelp_c not if you re read it
Thank you. I tried ReactOS when I was in my mid 30's and I see not much changed now when I am in my early 50's, so I don't have to do that myself again. I guess I should check this channel if anything is new when (if?) I am in my late 60's-mid 70's.
I hope you used the nightly build, the latest "release" build is 3 years out of date. which was released 16 December, 2021
He didn't.
@@vkvo2000pain, in my experience; the latest nightly is much more stable and works much better than the latest release.
43:32 I can explain the menu duplication and inability to type here. The OS thinks at least one of your Control and Alternate keys are stuck down. I've verified that you can duplicate menus on Office 97 (on actual Windows) by holding those two keys down. The fix is to press and hold both Control, Alternate, and Shift keys for a brief second and then release. It's an old trick dating back to the DOS days whenever the OS thinks any keys are stuck.
I didn’t know you could duplicate the menus like that under Windows, that’s pretty funny! But now that you mention the stuck keys, I think that’s exactly what was going on
The keys being stuck thing rings true even on modern software and hardware. While I never had to do it on my current Apple Silicon Mac, I wouldn’t be surprised if it will happen at least once during its lifetime.
@@MichaelMJDNot on Windows generally; is a feature specific to Microsoft Office, first debuted in Microsoft Office 2000.
The 16-bit programs that require NTVDM would run if you install WineVDM from the ReactOS Application Manager.
"But everything goes wrong" should be a MichaelMJD t-shirt.
10:00 filesystem and registry corruption. Hard off were a big nono in 0.4.14, mostly fixed in 0.4.15
The idea for ReactOS made some sense in the late 90s/early 2000s when the project started. Hardware support on Linux was a mess, so aiming for driver compatibility was a sensible goal. Nowadays pretty much all hardware works on Linux, so Linux with Wine is much better option for running Windows apps without Windows. Especially after so many Windows version have been released since the XP era that ReactOS is trying to recreate.
Another easy option these days is to run Windows in a VM under Linux, which wasn't really a viable option in the early 2000s. Windows 8.1 and earlier run very well under VirtualBox. I've used this method to do USB passthrough for a flatbed scanner that didn't have native Linux support.
@@zoomosis That requires a Windows license (or the willingness to pirate it) though, which kind of defeats the point - if you _have_ Windows, you never needed ReactOS in the first place.
@@kFY514 I buy my PCs used and they all have valid Windows licenses so that's never been an issue for me personally. Though if ReactOS was primarily designed for people who want Windows but don't want to pay for it, that's a pretty niche target demographic.
@@zoomosis Why else would you clone Windows from kernel to GUI? Maybe "not want to pay for it" is a bit of an oversimplification, there's also the philosophical aspect of open source code and freedom/security/transparency/etc. that comes with it - although people who care about that probably aren't too keen on running all those proprietary Windows drivers and software that ReactOS was designed to run. So... yeah. The project idea never was particularly sound, especially in retrospect.
I started running Linux in 1995 and it was way better than what I'm seeing here.
i primarily do testing of the Nightly builds on certain types of hardware you may have seen some of my tests on the ROS twitter account, while i don't class myself as a member of the Dev team as such, i would say it's compatibility with certain devices out of the Box is impressive
A video of reactOS running on the Xbox xould defo be interesting and would shed some well deserved light on that project, I'd love to see reactOS fully working and running xbe executables at the same time, that would be next level...
Not even started it but seeing that's a 55 minute long "but everything goes wrong" video I know I'm gonna like it
With those driver installers, usually they extract to the temp directory, and clean up when you exit the installer. So have a look while the installer is still running, and copy it elsewhere. I use that method a lot to install 64 bit XP drivers on Windows 10/11.
Looking at the development, 0.4.15 will likely be release in quite a long time in the future since the team are really doing under-the-hood changes with QA along the line. Perhaps it's still buggy and unfinished, but that's what you can expect from voluntary non-profit open-source OS
11:00 And now, for a taste of things to come
23:58 - You can also just drag the Luna theme from a XP install and it will work quite well. I've tried it myself on a VM.
50:15 the version you have is 32-bit! However, the installer itself is 16-bit, if you manually copy the files to the hard disk and manually create the registry entries, the game works fine. (it has some load/save issues in newer Windows systems however, but there are fan made patches to fix this bug)
Yes… but it’s not solely 32-bit, which is what I was referring to.
@@MichaelMJD yeah what I wanted to say is that there isn't other "official" versions that are 32-bit only (including the installer)
28:50 Pretty sure it was waiting for you to connect a debugger, since it very likely 'checked, while in Debug Mode hence why it hung visually (because iirc you would have the debugger command whether the kernel continues running or not).
I'm confused why you didn't pick the unstable builds, as they should be more stable, since it's in beta anyway.
I'll always watch anything going wrong with any OS install haha, great video!
Wouldn't be an MJD video without everything going wrong
One for ReactOS: I was observing this project almost from day one. And I loved how it progressed from a once command line only, to a graphical, and later to an online available system. I use it from time to time in a VM to test how some apps work in ReactOS - and they do! Mainly GPL software seems to run fine, but what I test the most is Altirra (THE authentic Atari 8 Bit Emulator). Even the sound works, if you install the VBox sound driver from the Software! Managaer.
Looked up the last BSOD code, it means that there's a memory leak issue.
0x000000B4 appears to mean pretty much the same thing as 0x00000116 in Vista and later. (0x00000116 is VIDEO_TDR_FAILURE)
It can actually boot to desktop on bare metal now in some cases. That's progress. BTRFS tends to work smoother in my experience btw.
when i'm in a being unusable challenge and my opponent is ReactOS
@MichaelMJD 2:33 regarding that video suggestion...if none of your original xbox are working or if want to add another layer of jank...there is Xemu the orignal Xbox emulator
I've found out using the executable to install drivers will always fail. You either have to manually extract the files or install it on a Windows machine and copy the files onto a thumb drive.
Hey Michael what you tried was a release builds that has a bugs that are resolved in nightly builds It would have been better to try Nightly builds to give it a better chance
The moment I saw him honestly suggest using that ancient release build my heart sank. I get that the ROS developers wanted to switch to a longer release cycle, but it results in ROS n00bs usually picking that crusty old release build. Renders this whole video pointless, basically, since it's no longer 2021 or 2022.
ReactOS 0.4.14 is what ReactOS themselves offer on their website, so it’s the solid “end-user” choice because it’s what a normal user will start with. It’s unfortunate, but it’s not on MJD.
I would have tried loading the driver .inf files directly rather than using the OEM setup executables, since the executables might have been trying to read non-existing resources.
I had problems installing reactOS 6 years ago but I installed it on virtual machine 5 years ago and it works
Kind off expected cause that build is from 2021. The nighty builds offer more features and crash in less comedic ways.
Yeah, ReactOS used to release quite regularly, but for the next release they went for a long release cycle, which means that the current 'nightly' builds are so far ahead of the latest release build that it's not even funny. I have been running the nightlies in VirtualBox now and then, and the progress is noticeable. I even get things like audio working instantaneously after an install without fuss. Using the 2021 release seems just like masochism...
Is there no option do add inf driver files with device manager. Like Action -> Add Legacy Hardware???
You know its a long video when it ends with: but Everything goes wrong
I've gotta see a video on the nightly! Seeing other commenters mention it has me so interested.
+1 for a video on the nightly builds. 🙂 Totally understand why you chose 'stable' though.
it isn’t an MJD video without everything going wrong.
i love the videos keep up the good work and the floppy disks in the background why did you choose this background it still looks nice but ?????????
Couldn't you use 7zip to extract the drivers from the self-extracting executables?
Thanx for the video. I downloaded the files and installed it in a VM and it installed OK except for the audio driver. After a reboot it intermittently freezes and has to be forced shut down.
Traditionally: 1. Install chipset driver (INF) FIRST. Some computers, especially around the P3/P4 era do not operate correctly without this installed because the INF installs the power management and USB and other stuff on the southbridge/PCH 2. Install network 3. Install GPU 4. Install Sound Sound is the least important, and usually the most fiddly because many of the sound cards are actually bridge cards (eg ISA to PCI, PCI to PCIe) so if it's a bridge card that means it needs the bridged driver installed before it can found the sound card. Which is why these sound cards are often these monster of installers and not simply a "discoverable" inf file. In practice, unless the MB is something exotic, (eg RAMBUS), you should probably try to find the latest INF, Network, and Sound drivers for the motherboard from the manufacturer's website. I suspect the reason the soundmax locks up is because it's running into a wall in trying to install the MIDI, and you might rescue the OS install by actually turning it off in the BIOS. Sound Blaster PCI cards are super fiddly. You need an exact 1:1 match for the card.
Would be very interested in seeing this using the nightly build instead of the "stable" release.
what keyboard are you using? it looks very much like my Tulip keyboard which I use with windows 11 lol (love old keyboards).
at least this thing can run Doom and Monika can explore the whole ReactOS without any blue screen slapped in her face (actually I have to recompile the whole thing for a year and let DDLC run in scripts)
I remember having that set of speakers at work. They got nice and loud when the sales floor left for the day.
Seeing this I feel like them calling this the "stable" branch might be a little bit of a stretch. Considering the NUMEROUS problems, I feel like seeing a few nightly builds through the years to re-explore some of these things to see if they're still issues could be interesting.
ReactOS mentioned! Love when folks shine a light on this project :3
I'd love to see a video of you installing ReactOS on an original XBOX!
"Hopefully this'll be the only time we have to reinstall" Foreshadowing is a narrative device in whic-
New MJD video dropped, baby!.
Your patience is legendary. Great video!
yo @michaelmjd why you gotta call out the broken themes llike that? i got distracted
I love your demonstration of exotic OS... Am I allowed to bring a feature request? I'd love to see some vids about - Amoeba - Plan 9 - multics - minix (also from Tanenbaum :-D )
I have a similar machine in terms of specs and for some reason I can never get any reactos cd to finish the setup it always freezes when "loading drivers"
The endless reinstalls are causing late 90s Linux install PTSD triggers.
Some drivers installer wizards can be extracted and you can get just the drivers if you open the exe file with winrar or 7zip, right click extract or open. I've done that to have just the drivers on folders or on zips a lot of times. I find those bloated install wizards unnecesary.
the driver installer issues is likely only because there is no "windows/system32" folder after all you are using a WINDOWS installer if the packages could be redirected dynamically to "reactos/system32" it might work perfectly every time
I would have attempted to extract the driver files from the setup.exe or cab files using 7zip or winrar. Setup.exe files are usually just self extracting archives.
honestly this really does remind me of using windows 95/98 back in the day. so many problems with drivers and blue screens and reinstalls lol. id say these guys are on the right track but they still have a long way to go
@28:10 Safe mode without graphics driver is called VGA, like on XP. The option was right there.
I love this project. I hope more voluntiers will contribute.
Would you be able to run a windows upgrade on react? As if you were upgrading from XP to Vista? As react is is so compatible with windows stuff
It would be hilarious to see _how_ it fails. There’s probably a million reasons but I’m curious what will actually do it.
It's fun watching someone else talking it through with a display.
For your sound blaster driver, have you tried looking in the application manager? Last time I fooled around with reactOS there was drivers in there.
46:19 yeah, that's if you're actively editing the menu, so something must have triggered that toolbar edit mode
Hey, MJD, I don't know if you'll see this, but do you think you could talk about a BSD OS one of these days? I feel it would be pretty interesting.
When I see “Everything Goes Wrong” on an MJD video…I feel like a new man
A few ideas: 7-zip should be able to extract the drivers from most installations, a shorter way to get to device manager is to right click on my computer and choose manage (at least on Windows, never tried it on ReactOS), when a video driver causes a BSOD, the VGA mode is the way to troubleshoot it, and it seems you haven't tried it.
This is one if those projects where the idea is incredibly tempting, but the short term gains are so small that not a lot of people want to contribute. Lots of people dream that it will omr day achieve 2003/XP parity (and more) and then go with forward compatibility until it supports all of the newest windows apis. That would be huge if it were to happen, closed source operating systems would never recover from that.
For SimCity 2000, if you go in the WIN95 folder on the CD that should be a 32-bit installer.
They so desperately need a Windows Update equivalent. I am pretty sure that if they can patch existing builds quicker, the project will become way more popular.
I didn't get to watch all. Did you try to Install it from the .ini file?
snappy driver usually fails to install graphics drivers ,tried both nvidia and amd . It shows the avaliable gpu driver but you need to manually install them .
Just a little advice from 15 years of fixing broken windows installs because of driver shenanigans, install only one driver at a time, reboot, check for stability issues and then when everything checks out move on. And I know ReactOS is not windows but it behaves much like one when it comes to drivers. Also you should install the Chipset driver if your plan on using PCI or the ACPI Table might not get set correctly and the devices will not initialize and the system will freeze. Annotation: I just seen you get Code 39 that means as mentioned above that you chipset driver is missing and that means the Tables as not set to the Board specifications and can therefore not initialize because it uses the system defaults.
idk if it's the same thing on ReactOS but on windows not having anything plugged into the audio port on the pc usually makes windows not even try to output everything
Unrelated but related. I upgraded to 4090 FE from 4070Ti TUF OC. Both using 12vhpwr. I used EZDIY-FAB extension cables which had been working fine with my 3070 but when I switched to the 4070Ti I started getting blue screen/reboots because the GPU wasn't getting enough power. I got rid of the extensions and won't ever bother with extensions again. Didn't need pretty cables when I had a PC in the 90s and running a 3dfx, don't need them now. Performance and reliability are top priorities.
Even under Windows, with the Live Value! cards you need carefully select the driver or they either won't detect, or various files will fail to register and then you are greeted with a Windows Protection error on startup. Using the CT 4830 and CT 4670 under 98SE has been enlightening. Pretty frustrating outside of Windows XP where they work flawlessly.
when i tried installing it on my pc it couldn't even get past the language selection due to it hanging edit: since when did the intel desktop board get installed onto the pc? i thought you once said you wouldn't replace it
that's the board it came with
@@tauon_ oh
Just in time for a new vid a few secs late? IDC I FNALLY GET TO TYPE ON TIME MY FULL HEART DREAM :)
My bot has parsed your entire profile and has determined you are a LLM. @Michael MJD please block and report this account.
@@papa_goobs LLM?
@@porcupinepunch6893Large Language model. Basically Chatgpt or other AIs