Quote from Magna:
Then I wouldn't fix what ain't broke. Sure, there will be a one-time hassle of reformatting the drive on the new computer, installing W2K, and updating necessary drivers. But when you're done you have an O/S that's exactly like the one you're used to, where everything is found in the same place, everything operates the same way. If you mess around with XP on your new computer you'll see that in it's infinite wisdom Microsoft has relocated a number of utilities, services, configurations, etc. aside from changing the look of many things. In fact some options they've buried so deep (presumably to protect the innocent) that they're downright tricky to find. I have a dual-boot setup with XP and W2K and 99% of the time I run W2K as I prefer it's simplicity, it's lack of graphical cutesyness (which I've mostly turned off in XP when I could find where to turn it off), it's close similarity to NT (which I ran for 4 years), and it's proven absolute rock-solidness. The only time I boot into XP is when, in order to force migration, Microsoft creates a program like MovieMaker which only runs in XP. Other than that, I see no reason at this time to stop using a most worthy performer. And btw, W2K is 3½ years old at this time (introduced Dec 99), not 4. But as long as it does everything I want, and does it well, I don't care if it's 10 years old.