Windows XP (and I believe 2000 and NT too) terminates if you kill some important system processes such as lsass.exe. It is probably safer to shutdown the system after one of these procs has been compromised instead of going on and hope everything is ok. Same motivation for going to "blue screen" after a kernel error.
My guess is that you will find info about kernel improvements in Longhorn over at http://www.sysinternals.com. Mark Russinovich and David Solomon wrote a summary article of the kernel improvements in Windows XP (http://msdn.microsoft.com/msdnmag/issues/01/12/XPKernel/default.aspx) earlier. And of course they have written the definitive guide to the Windows Kernel: "Inside Windows 2000"(http://www.sysinternals.com/insidew2k.shtml).
But it seems that Charles have got something more about the future of the Windows kernel. Looking forward to that
Apr 06, 2005 at 4:51 PMstaceyw wrote:Great. Always good to hear Anders. Looking forward to the c# Data concepts. Will that be talked about at TechEd?
TechEd uses to be more about the present then the future. PDC is more about the future, so my guess is that some plans for C# v3 will be discussed at PDC'05.
rhm: Try this link http://msdn2.microsoft.com/library/80h6baz2.aspx (or more readable http://msdn2.microsoft.com/library/system.reflection.emit.dynamicmethod.aspx)
Gotta love the new MSDN Library
Small excerpt from it:
"You can use the DynamicMethod class to generate and execute a method at run time, without having to generate a dynamic assembly and a dynamic type to contain the method. Dynamic methods are the most efficient way to generate and execute small amounts of code.
A dynamic method is associated with a module, and is effectively global to that module. With sufficient permissions, a dynamic method can access the private data of types declared in that module. You can associate a dynamic method with any module, whether or not you created the module."
rhm wrote:"I'd like to see a video of kernel debugging in action using that windbg that was mentioned. You know, just to see how hairy it really is in there."
There has been a bit of that in earlier videos. Check out the video when Jason Zander gives a tour of the CLR team. Somewhere they stop with some guy who is debugging a GC error with WinDBG. Also check out Jason Zander's blog where he earlier wrote about using SOS(Son of Strike) in WinDBG to debug .NET applications there.
Chris Sells(www.sellsbrothers.com) got a grant from MSR to study about doing refcounting in .NET, using SSCLI/Rotor. Read his/their findings here: http://www.sellsbrothers.com/tools/RotorRefCounting.doc
More interesting is their conclusions, which can be found here: http://www.sellsbrothers.com/writing/refcount_rotor.doc.
Seems like performance is the major problem refcounting introduces.
Here is a cool use of Tablet PC: http://jrhull.typepad.com/seward_street/2004/11/why_every_anima.html (nice drawings!)
Nov 05, 2004 at 7:59 PMBeer28 wrote:I just can't believe that Bill freaked out about 60k and now he innondates developers with a 20 meg virtual machine to replace the appx 5 meg java vm or msvbvm6 with when it wasn't even distributed with service packs, and wants everybody to develop on it and act like that's the normal way to develop instead of using C++ and long lasting binary code libraries.
It's not that bad The 20mb you need to download contains various compilers etc. He could freak out because of the quite huge working set of a .NET app, but since they're working on reducing that, maybe he's freaked out already .
For comparison, my Java Runtime folder (%PROGRAMFILES%\Java\j2re1.4.2_05) takes up 34MB. Can't remember how big the download file was...