Here is a screenshot of Process Explorer from my workstation.
From this photo, which is intentionally small, the one with the appropriate understanding should be able to derive that Process Explorer has a serious flaw, or so I think :-) That's why I call it "flaw" and not "bug".
The one who finds what I think is the flaw will get as prize my precious OSR Online WDK Bug Bash technical award t-shirt:
To make things just a bit interesting, I will accept a challenge from the first that claims that "This is not a flaw, it is intended by design". However the challenger must bet something that's of value equivalent to my t-shirt.
The contest is open to anyone who publicly declares his entry in the comments section of this post.
Hint: "I just clicked one menu item of PE" .
Hint: This is not an artificially generated situation. It is real usage.
Have Fun!
Dimitrios Staikos - Δημήτρης Στάικος - 史德衡
PS: I didn't check the Process Explorer forums about this. If I can't see why this is intended by design then most likely no one has noticed. If I am such a grand fool, then I deserve grand humiliation :-)
It is much much more than an online dictionary. It does both simplified and traditional (which is what I study by virtue of being in Taiwan). It also integrates with Google translate but then breaks down the Chinese word list in a very clever manner so that it is much easier to understand the Chinese phrase. Did I mention it can even play you animations on how to properly write each character?
Can't live without it!
Enjoy!
Dimitrios Staikos
When I bought my latest workstation I decided it would pay off to spare no expense, while trying to stay out of the "Game Machine" zone. One of the things that I decided I should have was hard disk redundancy. Backups and source control are must of course, but if my workstation crashes my problem is not losing the data. My problem is making an identically optimized workstation. I need about a week to do that.
Just think about it: Reinstall Windows with Service Packs and a gazillion updates, Office with its own updates, Visual Studios and service packs, SDKs, WDKs, .NET frameworks of several versions and SPs, tools, etc, the endless list makes me shiver only to think of it. I have better things to do than looking at progress bars that pretend to be progressing thanks to some nice visuals.
So when time came I did what I thought best. I got an Intel WX58P workstation motherboard with hardware RAID and installed 4 identical 1TB hard disks in RAID10 configuration. In fact I got some "Enterprise Class" hard disk from Western Digital, just to be on the safe side.
Today was pay-back day. Just 8 months after purchase and one of the disks in the RAID crashed. Here is how it looks like from the Intel Matrix Storage Console (click for details):
It took my hardware provider BARTEK (hail to them too) about 6 hours to come to my office with a replacement disk but it was the horroriest time (if there is such a word) that I've had in months!!! What if the currently not mirrored disk also crashed??? Oh my... I lose everything...
I tried to do some reasoning but it wouldn't be of much help. What is the possibility of two enterprise class hard disks crashing withing a 7 hour window? And especially the right two disks! But the one had already crashed, so it's history! Now I had 3 disks... What was the possibility of one crashing, especially the right one crashing? Especially given that another one of the same class and lot had already crashed! It's history of course but it can be indicative of problems in the whole lot... Probabilities were always confusing me...
And poor me, I had strong reasons not to shutdown the machine for 7 hours... Now that I think of it, it was not that wise, I should have shutdown to reduce the probability of an additional crash, but now it's history too...
Anyway the disk was replaced in time, the RAID was restored and now I am a happy blogger telling you how great it feels to have RAID save your ass(ets).
Enjoy!
Dimitrios Staikos
