When good hardware goes bad

"Goes bad" meaning "breaks". My beloved 22" monitor has died on me. I've gone from 1920x1200 pixels of widescreen goodness to an old 1024x768 CRT that they were going to throw in the trash at work.

The good thing is that now I can see for sure whether all of my web sites look OK in 1024x768 resolution. The bad thing is EVERYTHING ELSE. Oh god it burns. I can feel a headache coming on from squinting. Already I miss having 3 terminal windows right beside my Gvim. My conky display runs 2 feet off the bottom of my screen. Short of my HD exploding and losing all my files, this is my worst nightmare.

I'm debating whether I should format my laptop and dual-boot some Linux distro on there or something. Vista is such a dog. The only time I touch Vista is when I have to do something for work or when I want to play a game, which is very seldom, and I feel so unclean afterwards.

(Read the entire Westinghouse saga, if you dare: The beginning, Update 1, Update 2, Update 3, Update 4, Update 5, Update 6, Update 7, Update 8, Update 9, VICTORY, aftermath.)

2 Responses to “When good hardware goes bad”

  1. Quoth ph0enix:

    You're talking about your Apple monitor? That's really sad. Did it die infront of you or sometime in between usage? Perhaps you can get it fixed.

    This would be a good time to look into DELL 30″ monitors.

  2. Quoth Brian:

    Not my Apple. I bought a 24″ Westinghouse monitor from newegg a while back. (link)

    I turned it off, had a bath, came back, and it was dead. I'm going to have to send it back to Westinghouse and hope it can be repaired or replaced. It's probably going to be gone for a month. I've read very bad things about their customer service.

Leave a Reply

You can use these tags in comments (Note: HTML is automatically escaped inside <pre> tags, nowhere else, so if you post source code, put it in <pre>):

<pre lang="some_programming_language"> 
<em>
<strong>
<a href="url">

NOTE: Comments are automatically spam-filtered. If your comment fails to appear, it was likely munched by the filter. Try not to link-spam or post anything that looks like it was typed by a robot.