So I raced this weekend. There are pictures. There is a story to be told. Why am I not telling it, you ask? Why are there no pictures? Well it is because of some freakish glitch in the video drivers on my desktop computer. The computer that has the nice monitor I use to view and choose the photos I post on this blog.
Somehow I've managed to corrupt the video drivers each time I've rebuilt the system from scratch and each time, I completely lose video output and wind up staring at a blank screen. So you might be asking yourself why is this on my blog? And you might also wonder why it matters and what it would have to do with my working out? So what if there are no pictures, you say. And indeed a good argument could be made that pictures on a blog devoted to training and triathlon aren't necessary.
But I have a reason to be at least somewhat concerned by this. Not only was this the computer that I kept my video and my blog pictures on. This was also the computer that I attach to my Tacx bike trainer. Not to mention it is the only Microsoft Windows system I have (everything else, including the homebrew PVR attached to the TV downstairs is some flavor of Linux or BSD). This means it also has all my iTunes music as well. Blah, blah, blah.... You get the picture. I sort of need to have this thing running.
Of course all the files are backed up and I do have access to the pictures, but that isn't the point. The point is I don't like it when something I built isn't working. Everything sort of stops for me until I get it working again. So today, instead of going to the gym and working out, what was I doing? I was trying to rebuild the desktop. Nothing worked. At least nothing that provided me with video output. So I'm stuck with having to work some major MS-fu to put Humpty Dumpty back together again.
Got all that? So anyway that's why I raced this weekend. And there are no pictures. And I haven't blogged.