This file should be replaced with licence file when built

Just met this "jewel" when installing some chipset drivers. I clicked yes, most certainly it should be replaced :) Talking about weird license agreement ...

Design issues

I don't consider myself one of those I-am-always-smart-and-right people that can be regularly seen commenting on the daily wtf when someone posts a message regarding poorly designed and implemented piece of code. People are different, they have different knowledge, experience, they handle pressure differently, etc...

Almost always there is an explanation as to why some of the poor "craftsmanship" sees the light of production environment. I wonder what was the reason behind the next COM component that one can observe on computer with Media player 11 installed.

The device, \Device\Harddisk1\DR1, has a bad block.

Grrr... I haven't been reviewing Event log entries for quite a while (around a month or so). Today I've been surprised by the copious amounts of errors linked to the message above. Almost brand new Acer laptop, It isn't four months old since I've bought it. Former laptop (also Acer product) managed to survive without a scratch on a disk for around three years or so. And after such entries began to appear, it worked flawlessly until retirement (well that would be a matter of debate, I agree. Maybe I was only lucky enough for that long).

Even at the highest peak of disk utilization for prolonged periods event log entries were no higher than two or three per week. In my case there is 1.529 events during paging operation and other various I/O operations. Looks like to me that disk is slowly saying it's goodbye... grrr...

PS of a little comfort is the fact that SMART returned good status. Yeah, right....