Yep, by fooling around and trying not to cause an infinite loop, I caused an infinite loop.
Didn’t think of CTRL + C, but holding the restart button on the case helped (I think). My PC went into “recovery mode” because it didn’t shut down properly (at least, I think it was recovery mode. Something like that).
and when it grows above 80% you kill your “program”
I think if a couple of times the OS fails to boot then automatically offer recovery mode
it is more likely that WIN will do a disk check or sim…due to unnatural shdwn.
but if it offers you the option to simply continue to win you choose that.
The shutdown process - Windows has several checks in place before programs are closed and users are logged out. It is only after ensuring that everything is properly closed that the OS begins to halt and shut itself down.
The first thing that happens is that Windows does a user check to find out whether other users are logged into the computer, or another account is used on the same PC. If it sees this, the operating system alerts you by asking and confirming whether you want to actually shut down.
After confirming that you really want to shut down your PC, Windows begins the process by shutting down any programs, windows, or processes that you are running. The OS compiles a list and sifts through that to send a shutdown signal to every program that is open. In case a program contains unsaved data, it usually prompts you to save the data to continue before it can exit. When a program cannot be stopped, Windows prompts you to end it by force.
After programs and processes that belong to you have been stopped, Windows now gets down to the business of ending your session. The operating system simply logs you out to end your session.
If things go according to plan, Windows now gets ready to halt itself. This part is where the operating system shuts down, bit by bit, as all active services are closed. Windows basically needs to make sure that all associated programs, services, and processes are all safely ended, and your next restart does not create issues or problems.
After Windows is done with itself, and safely halted operations, it then sends a signal to the power management hardware of your computer to turn off the power.
I thought you were trying in some CLI
so when the CPU rises above some limit
you press CTRL + C (abort the current task)
and the focus of course you have to leave on CLI
Sounds like the end of the world. I guess Windows is scarier than I thought.
Oh yeah, a few pics. I literally named my batch file “virus.exe”. Webroot didn’t consider the name or what it did. I guess it doesn’t really care after all!
I mean, it’s not a virus in that sense, but it is still harmful. Not to Webroot, thought. I guess spamming windows until my PC crashes isn’t considered “harmful”…
Yeah, most antivirus looks at the contents. It is funny that it didn’t see mine as a threat, though.
I scanned my computer with WD (I couldn’t scan the individual file, since webroot took care of that).
Nada
I told my mom and dad I would do coding instead of playing games, and I told my dad “Hey look, I ended up creating an infinite loop to open an infinite number of windows”. He just looked at me and said “is that what you do instead of doing something productive?”
Funny how when I wanted a computer, I told my mom “Well it will help me in the future. It is a lot easier to know programming when you go into computer science at college than to go in there with no knowledge at all”. She just said “well, many people go in without knowledge.”
Now, when I have a computer and my mom asks me to code, she says “well, it is better to start and learn now!”
You know, what I really want to understand is how people come up with methods of storage like .mp3 files. People make decoders for mp3 files and such all the time. How do they know what each individual byte means?
I have always tried to make my own data format using the binary file format that other file formats (like mp3 or exe) use. It is hard to understand the syntax behind it.