Slashdot Mirror

← Back to Stories (view on slashdot.org)

Lessons In Hardware / OS Troubleshooting

Posted by kdawson on from the feels-so-good-when-i-stop dept.

Esther Schindler writes "We like to imagine that every Microsoft OS installation will work just as well as the company 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 account 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 chance do mere mortals have?"

2 of 236 comments (clear)

  1. Hardly worthy of slashdot by zorog · · Score: 0, Troll

    Ultimately this is in Microsofts best interestes to ensure people can install Windows SHINYNEW(tm). There scattered offerings are the cause of this problem, they should offer one OS install disk with maybe a few kernels. Disclaimer I've never installed windows 7, its on mums cheap laptop and works fine for her much improved on previous offerings and for once MS makes XP look like the dated and cumbersome giant it is.

  2. In all fairness by tpstigers · · Score: 1, Troll

    Not all Windows 7 installs are painless. When I installed mine, I found out the hard way just how dependent a Win7 installation is on a network connection. My network connection wasn't supported so the install failed miserably (seriously - I haven't seen a desktop like that since Windows 95). I eventually worked my way around it by installing a wireless card and connecting through it. Great fun.