Right click the installer, select ‘troubleshoot compatibility’, follow the wizard.
I won’t argue with that; it’s just that XP integrates DirectX much better than Windows 2000. Windows 2000 was MS’s first attempt at unifying everything, and they polished it with XP.
If you turn off the eye candy in XP it has a performance level that is on par with 2000’s. You can also switch to “classic” menus so that you don’t have to jump through hoops to find everything.
Of course, if you do that then XP pretty much looks and feels exactly like 2000 anyway, so I don’t know if there’s that much point to it.
Yeah, ok… Try setting up a WiFi connection in 2000 and get back to me. Noone should be using 2000. Just properly nLite XP and you’ll have everything you’re looking for plus be running a modern, patched OS.
EDIT: And by ‘modern’ I mean, well, you know… Sigh.
Sigh, sigh sigh
Why not? You should explain why no one should do this if you are going to make the assertion.
If you have a system that requires neither Wifi nor DirectX, why shouldn’t you use 2000? Are there un-patched security vulnerabilities?
I once had to set one up on 98 (not SE, plain 98) and it was a pain in the butt.
The point is: from a sane software developer’s point of view, you can’t. That’s what sane version number are for. If you write some piece of software against a library version X.Y you can generally assume it will work against library version X.(Y+Z). The only reason to change X to X+1 is when old versions actually won’t work anymore. Of course, marketing is different, which is why although you CALL it Windows 7 ™ which sounds nice and new to users, it’s actually 6.1 (or, Vista, revision 1) from the point of view of the software, meaning you generally guarantee compatibility with Vista.