4 ms·
> You have no idea what you're talking about. Care to elaborate why, instead of just accusing? FYI, MinWin is completely a user-mode library change; it has no
by wfunction 13y ago
> You have no idea what you're talking about.
Care to elaborate why, instead of just accusing?
FYI, MinWin is completely a user-mode library change; it has nothing to do with the kernel. Even Wikipedia explains the misconception: https://en.wikipedia.org/wiki/MinWin#cite_ref-14 https://en.wikipedia.org/wiki/MinWin#cite_ref-14
On the other hand, there is such a think called "MinKernel", which is related to the kernel itself: http://cdn-static.zdnet.com/i/r/story/70/00/013290/minwinminkernel-620x428.png http://cdn-static.zdnet.com/i/r/story/70/00/013290/minwinmin...
- quotemstr 13y agoI've already said too much. I just want to emphasize that the whole thing is quite subtle, and it's hard to make sense of it given only public information. What you should focus on is the documented ABI available on each OS and platform since that's the real place where what we do affects what you do.
- wfunction 13y ago> I just want to emphasize that the whole thing is quite subtle, and it's hard to make sense of it given only public information. Well, I made sense of it using only public information, and yet you claimed "You have no idea what you're talking about". Obviously that means you must know better than me, so care to share where I made a mistake?
- meanguy 13y agoFor starters, it's ntoskrnl.exe. Dig out the original Windows NT stuff from the early 90s and you can infer Dave Cutler and team's original vision. The fact that Microsoft made hundreds of billions of dollars off it, layering all sorts of legacy chaos atop it, obscures the jewel at the core.