wasn't XP supposed to be both more robust and EASIER???

  • Thread starter Thread starter Patric
  • Start date Start date
P

Patric

This halt error I received should never have happened in
this particular upgrade. This particular error shouldn't
ever happen when swapping system boards with identical
IDE controllers. When the Athlon XP motherboard generated
this error, it was understandable, though not necessarily
forgiveable. Microsoft really needs to clean up the
Windows XP boot process. After all, Windows XP is
supposed to be more robust than Windows 9x, but I almost
never encountered these issue in 9x, and when I did, the
fixes were relatively straightforward, and didn't even
require re-entering the CD key. These days, Microsoft is
under the microscope, and every little incident like this
only serves to make users trust the company a little bit
less. And given the declining perceptions of the Redmond
giant among influential technology users, Microsoft
really can't afford to lose even a bit of trust. To me,
reactivation seemed like a minor hassle. But when Windows
XP actually prevented me from logging on after a simple
refresh install, I'm certainly reconsidering my opinion.
Microsoft should seriously consider building in an easy
refresh install process. After all, wasn't XP supposed to
be both more robust and easier?
 
It is provided it has the correct drivers, which includes the one in the
seat ;-)
 
When you swap motherboards, you need to do a repair install. It's not
the IDE controller, but there is lots of other hardware on the mobo that
XP assumes is present when you boot. It likely works this way because
Microsoft speeded up the boot process.
 
Back
Top