From: "Frank Haber" 

I remember zombie processes in UNIX. I'm astonished that that page you
referred us to seems to think that a kill can be defined as "the
message to go die was sent and probably received."  Sounds like
typical programmer optimism to me, filtered through a rosy haze of object
orientation.  You may now throw things.

Modern hung stuff seems more driver- or hardware-based, usually (gut feeling).

Microsoft is now talking about "new cancel standards" in Vista,
with file-based stuff to back up the thread-based cancels.  Apparently the
snoop or monitor processes can't be trusted to know the score.  Concurrency
is truly a bitch, and I'm gradually learning why the definition of
"race condition" has expanded so much.  It apparently can even
now include a cancel that happens just as the target has successfully
completed.  What a nightmare.  A lock is not a lock, and a block is not a
block. OMG.

--- BBBS/NT v4.01 Flag-5