Comment Re:The Solution is Obvious (Score 1) 829
They did it for Windows 2000. I read somewhere that MS charged a big company running windows 2000 at the time over $10000 for a single patch after windows 2000 expired.
The best option is to get rid of it. I dealt with this issue back when windows 2000 went EOL (primarily with scientific equipment that would lose certification if tampered with) and believe me you don't want to go there if you can avoid it. You can avoid it if the system is not network facing and you don't use media like USB drives on it. But any level of network from Internet to Sneakernet puts you at risk.
The only major problem I've run into compatibility when it comes to transitioning programs windows XP to 7 is 64Bit and UAC. Disabling UAC, enabling the Administrator account, and using the 32Bit version of 7 will 99/100 times get an old program to run in 7 using XP compatibility mode, and if it still doesn't work, then there's windows XP mode (although that can get infected, you can minimize the impact with NAT or Disabling Network support.)
Hardware is a different story. Many XP drivers will install in 32bit 7 but they can cause bluescreens and the like. I've honestly had better luck with Vista in this regard. Again with UAC Turned off.