Linked by Howard Fosdick on Mon 31st Dec 2012 20:26 UTC
Hardware, Embedded Systems Last month, I explained why I use generic desktops and laptops running open source software. They're reliable and inexpensive. But this presumes you can fix them. I believe that even those with no hardware training (like me), can identify and fix most hardware problems. To prove it, here's a quick guide. Feel free to add whatever I've missed.
Permalink for comment 546812
To read all comments associated with this story, please click here.
RE[4]: Best trick
by umccullough on Wed 2nd Jan 2013 04:46 UTC in reply to "RE[3]: Best trick"
Member since:

Hmm, that's odd. Ideally you could run it when the case is off and identify exactly which component is causing the problem. But with laptops this could be a challenge.

Yeah, I tried to narrow down the location of the short while I had much of the machine apart, but with a laptop, it definitely gets tricky as you start pulling stuff apart to actually use it.

It's an old pentium 4 laptop anyway, so it's no huge loss, although it has a 1600x1200 screen which is what made it so compelling to utilize.

Reply Parent Score: 2