Slash comment HERE
KB-Here

Microsoft does some incredibly stupid things, for no good reason...
The most major and glaring idiocy in Windows is hard disk controller drivers. For this reason alone, I wouldn't ever suggest using Windows as a server (or on ANY type of system that is remotely important in any way).

If you take the hard drive out of one machine (perhaps after it has become a smoldering pile of metal and circuit boards) and install it in different system, there's an extremely good chance Windows NT3.1/NT3.5/NT4.0/2000/XP/2003/Vista/etc. will BSOD. It will crash and burn before you can even boot into safe mode.

You see, for some reason, Windows has a different, incompatible driver for every different brand of controller. For IDE/SATA-based systems, there are basically 4 (VIA, Intel, etc.). Microsoft's only official solution to this problem is for you to buy exactly the same hardware again.

To their credit, they now have an unofficial and unsupported fix... and it only took them a little more than a decade from the onset... Now that's a speedy response!

The solution [microsoft.com] is to basically extract all the drivers from a .CAB file on the hard drive, and add a load of registry entries that basically enables all 4 of them.

There are a few surprising things about this. First is how screwed you are if you don't know about this BEFORE your machine turns to mud, as you can't boot-up your system in order to add the necessary registry entries to begin with. Thanks to unofficial options like Bart'sPE and it's remote registry editor, you can spend a couple hours sorting out the mess, locating keys, copying, editing, and finally modifying the reg files so they can be added to the non-running system. EVENTUALLY, if you know enough about what you're doing, you can get it to work, and finally be able to boot-up your system.

The second surprising thing about this is that the problem is extremely serious, fixing it after-the-fact is extremely difficult even now, (it was borderline impossible before BartPE), yet the fix is minor and has no negative effects, and still, in the past decade of NT systems with this problem, Microsoft has NEVER made this behavior the default. The files and information are all already on the hard drive of every Windows system installed, the OS simply just won't consider using them.

For some reason Microsoft WANTS Windows to crash when you change the hard disk controller. ALL other hardware changes will be detected by the system, and proper drivers automatically installed by (recent versions of) Windows.

The number of registry fixes I add to any fresh Windows system to avoid bugs, stupid behaviors, bad defaults, and show-stoppers like this on, is absolutely staggering

Unfortunately for my particular generation there may be a reason why songs like "Freebird" & "Fly Like An Eagle" stay with us.
Now if only someone can create a way to counter-act this phenomenon so one may actually enjoy hearing them again!

Link to Research.

Link to Graph.

Link to the article below:
The songs we listen to as teenagers become our all-time favourites because they are hardwired into our brains, a new study has revealed.
The 'reminiscence bump' can be partly explained by what's called differential encoding, or an ability to store events better during early adulthood.
Janssen said: "You recall more memories from the period of 10 to 25 (than previous or subsequent periods) and the bump has a peak between 16 and 20.
"The brain works at its optimum in that period. It's a sponge and it soaks up everything." He also says that how often the songs are played is equally important.
During our teenage years we form personal connections with songs by playing them over and over again.
While music preferences were strongly linked to childhood hits, favourite books and movies were more likely to be those read or viewed recently.
He said: "All distributions showed a reminiscence bump so there's evidence that people store events better in their teens.
"However, I also found a larger recency effect for books and a larger reminiscence bump for records - so I suggest a kind of interaction between those two mechanisms.
"The results suggest that differential encoding initially causes the reminiscence bump, but resampling strengthens the bump." Janssen is a University of Amsterdam PhD student.