Bytten by the computer snake
Oct. 16th, 2008 03:18 pmAs I look back on it now, it started last night. My main vista machine was coming back after the update required reboot when the RAID Drive failed AGAIN! This was the last and final Western Digital drive I will ever install. The Seagate replacement has been ordered.
After a reboot of my work machine, I noticed one application wasn't working but there had been connection issues reported all day by others so I just figured it needed a night's sleep.
Wrong. The .net framework update failed but also fucked up my installation. Who the hell knew .net framework was the foundation of so many of my apps. ARGH. Nothing I needed worked. I killed a couple of hours trying to fix it myself - rolling back, trying some tricks found in forums, etc. Nothing.
And... of course... I have work piling up. Oh yes, when the computer works fine, I'm dead idle. When the computer fails, bugs r us. Fuck.
Finally, I called the corporate help desk and got a really nice guy who fixed everything. The fix took 3.5 hours. But, he really was nice and respectful and pleasant and competent - most of the 3.5 hours was spent waiting for the network and/or the computer.
I did the top few emergency things and then, as I was starving, I broke for lunch. One delicious cheeseburger later, I'm going back to work.
After a reboot of my work machine, I noticed one application wasn't working but there had been connection issues reported all day by others so I just figured it needed a night's sleep.
Wrong. The .net framework update failed but also fucked up my installation. Who the hell knew .net framework was the foundation of so many of my apps. ARGH. Nothing I needed worked. I killed a couple of hours trying to fix it myself - rolling back, trying some tricks found in forums, etc. Nothing.
And... of course... I have work piling up. Oh yes, when the computer works fine, I'm dead idle. When the computer fails, bugs r us. Fuck.
Finally, I called the corporate help desk and got a really nice guy who fixed everything. The fix took 3.5 hours. But, he really was nice and respectful and pleasant and competent - most of the 3.5 hours was spent waiting for the network and/or the computer.
I did the top few emergency things and then, as I was starving, I broke for lunch. One delicious cheeseburger later, I'm going back to work.