-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 |If people are receiving errors... |How is it that people thing that a distribution is ready for hte desktop?
~ These sorts of issues are common. We had a fair number of customers with Windows XP who would complain of a blue screen, stating "UNMOUNTABLE BOOT VOLUME". It turned out to be a bug in XP's IDE cache routines, one that rarely occured but came without a warning or pattern. Windows would refuse to mount that partition on a reboot; since most people only had one partition, they couldn't boot to XP at all. ~ The blue screen hinted at using the recovery console to repair it, if I recall correctly, but gave no other details. If you thought to look in Microsoft's news servers, or searched the Knowledge base, you could have run across the full repair procedure; I doubt many desktops users know about either of them, and they couldn't have done the legwork from the dead computer. The method involved a simple command in XP's text-based recovery console, pretty easy to do if you have it. But I've never seen a "Product Recovery" CD that contains the recovery console, and many if not most XP users only have a recovery disk. ~ Microsoft released a patch for this in February, so it's no longer a problem. Still, the bug was probably present at XP's release over three months earlier. ~ The point is that odd hardware issues are a bad way to judge whether or not an OS is desktop ready. I believe the best way is to see if it works as your desktop. If the install goes sour, or some critical hardware isn't recognised, then that OS is not ready to be your desktop. ~ HJ Hornbeck (Microsoft's writeup:) http://support.microsoft.com/default.aspx?scid=kb;[LN];Q315403 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE96wrobYQU8p5saQIRArgLAKCCVE1kjGo5ag0Ln4b90tWf6TtzuwCfe5bE eJ59eSiV4aCXUrSo87rRyWk= =Oqkr -----END PGP SIGNATURE-----
