Where’s the peanut butter?!

I suspect this is related to some corporate syncing policy gone awry but I have an annoying behavior every now and then on my phone. The backlight timeout (time before the light goes dim and you need to click something for it to turn on again) is customizable from 10 seconds to something really long. But sometimes I find it setting itself to 10 seconds and if I change it back to what I want (1 minute), the setting won’t stick and it’s back to 10 seconds the next time I turn it on. The solution seems to be to change the following registry key “HKCU\ControlPanel\BackLight\LockLevel\LockLevel” from 1 to 0. Then if you change the backlight timeout, it won’t reset on you.

One of the goals I’m aiming for now that I’ve quit my job is to run a marathon. Today I did my first competitive run in a while - the Beat the Bridge 8k and am pleased with how it went. I was reminded about this by a friend at work last week and registered late and ran by myself. I put myself in the 7-8 minute mile group which is faster than I’ve been running but apparently not faster than I can run when I have people to compete with and a little D4 rockin. I was upset when I crossed the finish line, though. I looked at the clock and it read something like 43 minutes. How did that happen?? I’d timed myself with my watch and been keeping track throughout the run. I knew it took me 30 seconds before my spot in the swarm of runners even crossed the start line after they blew the horn, but that couldn’t account for a pace like that…Then I realized that they must have started the clock for the first wave of runners and they took off 5 minutes before my group. So yay!

In related news, I’m starting a Google Calendar list of Seattle area runs. I’ve got the furry 5k, Fremont 5k, a fall city 10k, and a Seward to Madison park run. I’m looking for running buddies, especially for the long runs in the Hal Higdon training program since I’m pretty sure I’ll need some encouragement!