Linked by Thom Holwerda on Fri 30th May 2008 14:49 UTC
Windows We have learnt quite a lot about Windows 7 this week, and one of the things was that Windows 7 would not get a new kernel. The call for a new kernel has been made a few times on the internet, but anyone with a bit more insight into Windows' kernel knows that there is absolutely no need to write a new kernel for Windows - the problems with Windows lie in userland, not kernelland. While the authenticity of the Shipping Seven blog is not undisputed, the blogger makes some very excellent points regarding the kernel matter.
Permalink for comment 316664
To read all comments associated with this story, please click here.
RE[6]: Comment by FunkyELF
by Ophidian on Mon 2nd Jun 2008 15:32 UTC in reply to "RE[5]: Comment by FunkyELF"
Member since:

This is good information to have, going to have to save this to a notes file somewhere.

I wonder if Process Explorer is doing something similar when it is able to kill tasks that Task Manager can't.

taskkill /f /im

The only way an executable can stay running after you terminate it like this is if it is stuck processing I/Os in a driver. If that's happening and you really want to learn why, obtain a copy of windbg, start a livekd session, run ".symfix" and ".reload" to get symbols, find your target process and thread using "!process 0 7 " and if you see any IRPs mentioned in the thread description, run "!irp " on them to find out which driver is holding you hostage.

Reply Parent Score: 1