Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

×
Hardware

+ - Lessons in Hardware/OS Troubleshooting->

Submitted by
Esther Schindler
Esther Schindler writes "We like to imagine that every OS installation will work just as well as the vendor or open source community promises. When things don’t work out, identifying and remedying the case of failure can be time consuming and frustrating. This lesson in how to determine why Windows 7 didn’t install may help you troubleshoot a problem of your own — and save you from a Lost Weekend.

Maybe you'll find this useful all on its own. But the real key here is that the author is Ed Tittel — who's written over 100 books. If this hardware geek spends days solving a CPU-meets-Windows 7 problem, what chances do mere mortals have?"

Link to Original Source
This discussion was created for logged-in users only, but now has been archived. No new comments can be posted.

Lessons in Hardware/OS Troubleshooting

Comments Filter:

Money will say more in one moment than the most eloquent lover can in years.

Working...