2 ms·
Why is kernel32.dll running in user mode and not kernel mode
- maldev 3y agoWhen I read the title, I thought this was going to be a REALLY stupid post. But this post is amazing and explains a pretty tricky concept, and history, of "subsystems" in a pretty easy way. Effectively, Kernel32(Now KernelBase) has the logic for usermode stuff, and goes into ntdll solely for syscall stubs. It then gently eases the idea of User32 having a similar purpose, as well as GDI. These are the 3 "subsystems" that interact with the Kernel, and it's a pretty core concept, but alot of newbies struggle to understand.
- yukkuri 3y agoI love when TONT gets into, well, old things.
- jiofj 3y agoBack in the day of course. Now he's clearly run out of stuff to post. Which I guess makes sense, it couldn't last forever.
- karmakaze 3y agoWhat complicates this further is with GDI (from Wikipedia/Architecture_of_Windows_NT) > The Graphics Device Interface is responsible for tasks such as drawing lines and curves, rendering fonts and handling palettes. The Windows NT 3.x series of releases had placed the GDI component in the user-mode Client/Server Runtime Subsystem, but this was moved into kernel mode with Windows NT 4.0 to improve graphics performance. I remember how rock solid NT 3.51 was, then NT 4.0 and early Win 2000 was a period of less stability especially on laptops until it finally got stable again.
- fomine3 3y agoI understand why, but still it's a bit weird that System32 is 64bit and SysWOW64 is 32bit
- mirages 3y agohttps://learn.microsoft.com/en-us/windows/win32/winprog64/file-system-redirector https://learn.microsoft.com/en-us/windows/win32/winprog64/fi...