Something to be said about good timing… it’s saved me a whole lotta time and panic on this fine Thursday.
About a week ago a new machine landed in my lap at work. I was surprised and sorta thankful. I mean, I’d had the same 3.2GHz P4 for over a year and it was still doing well, so I didn’t really plan on replacing it. In fact, it usually takes me a few days to get a new machine “just right” and, well, after installed XP at least over 100 times since it’s beta cycle, I would say that I’m “tired of it”.
But it was shiny and double-wide in bit size… in spite of the additional work, I was still excited, and how could I say no? So, under the occasional glare from co-workers [that didn’t get new machines] I started to configure it last week. Then moved my dev environment from my 1.8GHz to my 3.2GHz. And turned my 1.8 machine into a quasi-lab box, so that I could have a clean machine for particular tests… those are hard to come by, without taking a lab box offline.
The good timing part of it? The CPU fan has crapped out in the 3.2GHz box. Ever wonder what a P4 HyperThreading CPU will do if it’s uncooled? Hah! Every Geek in the reading audience just cringed and went “oooOOOooooo”. Well props to Dell for having a fail safe: it just shuts down the box, instantly. Then reports a Thermal Failure. Which is an error that sounds like your mom forgot to twist a cap tightly and you’ve got soup in your sandwich don’t it? Or maybe that trick where you put your friend’s sleeping hand in warm water and he pisses himself?
Anyway, it’s good timing. The dev box is now waiting for a new fan, and life will continue, since it’s not my primary box… which would have been offline now… in the middle of a ship cycle… erm.
Good timing, indeed.