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 546811
To read all comments associated with this story, please click here.
RE[3]: Best trick
by Alfman on Wed 2nd Jan 2013 04:28 UTC in reply to "RE[2]: 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.

I've soldered a new power connector into a laptop where it had been damaged, but I'm not sure I'd ever feel compelled to stick one in the oven. ;)

Reply Parent Score: 2