NtDoom running inside the Windows kernel.
The tenacity of Doom players to make the game run on everything is amazing
this post was submitted on 08 Jul 2023
140 points (100.0% liked)
Technology
37712 readers
166 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
It's not just about being DOOM players. It's a long running joke in the programming and engineering world. Wether it's a fridge, a toaster, a decommissioned 1970s super computer... can it run DOOM?
It's the computing world's version of a shitpost.
But can it run Crysis?
The main reasons why it's Doom specifically are also because:
-
The game is open-source: https://github.com/id-Software/DOOM/pulls?q=is%3Aopen+is%3Apr This makes it much more doable to port it to other platforms (and to strip out anything not absolutely required to get the first level to run when you run into technological limitations) than when you have to rely on unofficial modding tools.
-
It's nearly 30 years old and designed for computers with only a few megabytes of memory and for processors of well under 100MHz, which are specs which the majority of modern systems have, even embedded systems. It also renders fully on the CPU and doesn't require specific hardware like a GPU or a specific graphics chip.
-
Being a first person shooter with 3D-ish visuals it looks a lot more impressive than if you show off a simple game like Pong orTetris or something like that. It has the right balance between performance requirements and impressiveness, and it's also a game that was very popular in its time and it's instantly recognisable to a lot of people.
This is so stupid. I love it!
lol this reminds me of psDoom
https://psdoom.sourceforge.net/
video of it in action:
https://farside.link/invidious/watch?v=Pf7rpde49NU
I want a version of psDoom - but for browser tabs!
I want a version of psDoom - but for browser tabs!
Didn't they also get it to run on a pregnancy test?
No. A pregnancy test that had a screen was used as a display for doom gifs when hooked up to a much larger computer.
IIRC, the screen wasn't even from the pregnancy test, just a small OLED one stuck inside the case.
The pregnancy test merely provided the case. Looked cool though.
Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.
Can we run Doom on printers?
I'm ignorant, but what does this means? I mean, what's the difference running it "in the kernel" and running it normally on windows?
Windows (and most other operating systems) have a "user land" and a "kernel space".
"user land" is where all your applications run. A "user land" application can only see other applications and files owned by the same user. Eventually, a user land app will want to do "something". This can be something like read a file from disk, make a network connection, draw a picture on the screen. To accomplish this, the user space app need to "talk" to the kernel.
If user space apps were instruments being played in an orchestra, the kernel would be the conductor. The kernel is responsible for making sure the user land apps can only see their respective users files/apps/etc.
The kernel "can see and do everything", it reports to no one. It has complete access to all the applications and every file. Your device drivers for your printer, video card, ect all run in "kernel space".
Basically, the OPs link: they've ported Doom to run effectively like a device driver. This means that if doom crashes, your PC will blue screen.
This has no practical purpose, other than saying "yeah, we did it" :)
Thank you both for your reply! Now I got it!
It means that all the code is running in privileged kernel mode instead of user mode. Kernel mode is usually reserved for the operating system and device drivers only. If code running in kernel mode has an unhandled exception or error, the entire system will crash. This creates the BSOD or “blue screen of death” on Windows.
User mode is less privileged and where all your typical applications run. If something crashes in user mode, it only crashes that process, not the whole system.
It’s a crazy thing that they did. Very impressive technically, but not really useful.
Very impressive technically, but not really useful.
Those are my favourite kinds of shitposts. I find them legitimately beautiful
load more comments
(2 replies)
view more: next ›