The Graveyard

The Lair Of Gary James

Windows BSOD Strikes Again

Posted by BigWords on July 11, 2009

Problem signature:
Problem Event Name:    BlueScreen
OS Version:    6.0.6000.
Locale ID:    2057

Additional information about the problem:
BCCode:    9f
BCP1:    00000003
BCP2:    83812BF0
BCP3:    838503D0
BCP4:    8389E9C8
OS Version:    6_0_6000
Service Pack:    0_0
Product:    768_1

Files that help describe the problem:
C:\Users\This Little Piggy\AppData\Local\Temp\WER-117999-0.sysdata.xml
C:\Users\This Little Piggy\AppData\Local\Temp\WERF517.tmp.version.txt

Read our privacy statement:

Just when I thought that the billionth update to ‘fix’ Vista was unnecessary, the computer shuts down. Upon restart I get hit with the above message.

I’ll bite. What the hell is going on with Windows? Is it so hard to get an OS running properly? The alternatives are no use for me at the moment: Linux is on the main rig (and there is no way I’m carrying that sonuvabitch around with me) and the Mac is so old that I’m constantly worried that it’s going to explode with the work I make it do. I’m on the laptop at the moment, and I need the OS to work. There’s a fourth choice, of course, but I’m going to get to that later in the post, first I want to think about this…

Who decides a program is ready to roll?

In the old days, when I could squeeze an entire game onto one side of a cassette, I created a bunch of fun little platform games that NEVER ONCE crashed my Amstrad. They were as pointless as most ‘celebrities’ and as shallow as a boy band, but I liked making dumb time-wasting games. The sense of achievement in getting blocky groups of pixels moving in a way that simulated some form of ‘reality’ was cool, and I always considered the problems which may have occured with the coding. Not so at The House Bill Made, where the roof is leaking and the Windows are cracked.

I remember the first time I was in a crunch, and every little glitch had to be fixed ASAP. It wasn’t fun, but it was important. These days, with downloads and patches, you can get away with releasing  (or unleashing) something that is completely unsuited to the job and get away with it. Part of the problem – in my opinion – is the lack of focus in large companies. The more employees on the payroll, the more ways in which a company begins to stretch. People bring baggage to their code, it doesn’t matter what the project is, so the opportunity for problems is increased. A big company like Microsoft is asking for problems.

Ah, but there is the fourth choice…

If you have enough time, a rebel streak running through your bones (and a mind that can cope with complex systems) you can bypass relying on other people’s operating systems completely. I am, of course, talking about a custom OS. The architecture might not turn out as labyrinthine as you would get with a ‘name’ system, and the ergonomics could be crafted for each user’s needs individually. Who’s with me? Who wants to get the bastards at Microsoft where it hurts – in their fucking pocket? We’ll all switch over completely to Linux or a custom OS on a set date. We won’t tell Billy’s boys… We’ll just carry on as normal, and ignore anything they have to say.

How does the first of April, 2010 sound? It’ll be the best prank in history…


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: