Prank blue screen of death (SO REALISTIC!!!)
You were playing your favorite video game (which your mom and dad told you specifically not to), when all of a sudden, oh noooes! A BSoD (blue screen of death) appears, you panic, not knowing big boi words. It restarts, then says get fooled! You've been gnomed!
Funny BSOD prank. I tried it out with my dad, he totally got fooled XD. Kinda hard to prank people since it's on a webpage (for the people who know nothing about computers, it may be easy), but nevertheless fun. Looks sooo authentic, I even put real errors in there (yes, DRIVER_IRQL_NOT_GREATER_THAN_OR_EQUAL_TO is an error)! Hope you like it (hint: works best in full screen) :)
So, I had seen your Repls, forked this Repl in particular, and had put in a bit of time to heavily rewrite the code (it was pretty gross, not to be mean), and had completely rewritten it, much more readable all around now.
And it just so happened to be... that you had posted that very Repl, leading me here.
Also, I had updated it to use an image that one of the posters had uploaded (a deleted user).
And, lastly, I failed to get the authentic Windows 7 Lucida Console font family that BSODs used, so I settled for Lucida Sans Typewriter, which is what Lucida Console is a derivative of.
https://repl.it/@xxpertHacker/Fake-BSoD
Much more authentic.
Also, I see that you're a Node.js user, if you ever use Deno, which Repl supports at https://repl.it/l/deno, they make heavy use of promises, but they also have top-level await enabled by default, making it effortless to use. (V8 has had it since 2019, I have it enabled in my own browser)
It made the multiple levels of nesting into just one level.
Besides that, I made a greater separation between HTML, ES, and CSS, a large portion of it was tightly coupled together, which isn't good practice.
But really, the biggest change was the removal of the switch case, replacing it with one line:
switch(iterator){ case 1: document.getElementById('booting').textContent = 'Booting up... |'; iterator++; break; case 2: document.getElementById('booting').textContent = 'Booting up... /'; iterator++; break; case 3: document.getElementById('booting').textContent = 'Booting up... -'; iterator++; break; case 4: document.getElementById('booting').textContent = 'Booting up... \\'; iterator = 1; break; } iterator2++;
vs
{ const limit = 90 + Math.floor( Math.random( ) * 50 ); for ( let iterator = 0; iterator !== limit; ++iterator ) { await delay( 0.1 ); textNode.textContent = "|/-\\"[ iterator & 3 ]; } }
Imho, that's way cleaner now.
But, I just realized, your code was already statically typed, maybe you'd like TypeScript?
But what did you mean about the timeouts? They're mildly accurate, for short durations. As long as you don't set a timeout for over an hour, it should be fine.
Promise.all
on a promise and a delay that rejected to create HTTP timeouts, maybe the wrong person? But still, cool nonetheless.
Timeouts are a very niche feature.
you can try making it fullscreen so it looks more real
@Baconman321I don't know how realistic this is because this type of screen has never appeared on my laptop as long as I remember
My computer stopped working and every time I opened it, it said, “You PC needs to be restored please insert a disc or mini SD”
I thought it actually happened so i brought my computer to the technicans.
wait nooo!
I've heard of Black screen of death but not blue!
what about the GSOD (Green Screen Of Death) that exists in windows insider editions?
@Leroy01010The green screen of death only appears when you're running an Insider Preview version of Windows 10. It's the same as the blue screen of death, and it will show the same error messages. ... If you see a green screen of death (GSOD) on your PC, that's a sign you're using an Insider Preview build of Windows 10.
@Lethdev2019that is literally what i said.
@Leroy01010also - have you seen my earlier comment?
@Leroy01010how do i know that? it is because i can't sit down for 5 mins without someone needing help during school with the computers.
@Leroy01010DRIVER_IRQL_NOT_GREATER_THAN_OR_EQUAL_TO means that there is an issue in your driver software - this can be fixed by reinstalling, updating or uninstalling drivers. Usually this happens because the driver software requests a used memory address so the OS (windows) denies access to the driver which the hardware needs which causes a kernel panic (BSOD)
IRQL_NOT_GREATER_THAN_OR_EQUAL_TO is the generic error code.
you can find more info here: https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa--irql-not-less-or-equal
you don't really get those types of bsods UNLESS windows is modifed via regedit.exe. usually you get something like this:
It has actually happend to me with the code MEMORY_MANAGEMENT which is to do with the Random Access Memory.
But still, pretty good job :)
yeah it is to do with the camera drivers. it is a type of nmi. (non maskable interrupt). Drivers tells Windows on how to use a device.
@DungeonMaster00this is so cool. it will probalby give hardcore geeks some 'nam flashbacks
Add this javascript:
onclick=()=>{document.body.requestFullscreen()}
It will go fullscreen when you click :D
cool
Use fullscreen and it actually will be realistic :-)
Uh that’s not an error. This is a real error:
So https://duckduckgo.com?q=!w%20magic%20sysrq%20key will show the sysrq Wikipedia page.
yes lol
insted of saying restarting: 100% say dumping pysical memory: 100%
yea dumping pysical memeory is win7, but i though this was simmilar to win7.
Isn't dumping memory to disk just saving the contents of RAM to an ssd/hard drive/other "permanent" storage device?
Yup.