Why does system32 crash the system? I mean the kernel and shell

File: thread.jpg (27KB, 375x281px) Image search: [Google]

27KB, 375x281px

>>59173626
Chances are some of the .dll files are loaded at runtime to support plugins and whatnot.

>>59173626
You're right.

Deleting system32 would not cause the system to crash, despite what many would tell you. This logic is why when you rm -rf /* a UNIX system, it can still run.

RM is still in use even when it is deleted, as it is loaded in memory.

It's also how some background updates work, the binary gets placed where it needs to go, next time you execute it, you execute the new version.

>>59173626
>kernel and shell are already loaded in to memory

Not entirely, many essential dlls and executables arent needed all the time, which is why deleting it could do nothing for about 10-15 minutes.

>>59173675
>Not entirely, many essential dlls and executables arent needed all the time
So parts of the OS aren't loaded in to memory?

Patch guard would crash your system, it validates files off disk.

>>59173714
Files as in integrity of the kernel in memory, it loads the same file off disk, and checks that version vs the version in memory

Next Question:

How does the Kernel interact with new hardware?
Doesn't it have to be written specifically to accommodate that new hardware?

>>59173707
If the entire OS were to be loaded in memory you'd need about 18GB of RAM just for the OS alone.

>>59173626
The real question is, how much of all of that stuff can you delete before you cause a problem, and how much of it is just wasted space?