EVE Online Patch Kills Windows XP.

What happens when you name the main configuration file of your application "boot.ini", and then gimp your installer? A system with a very confused bootloader! The latest update for EVE Online, Trinity, was scheduled to add all sorts of wonderful features such as upgraded models, textures and the additional of HDR. Tragically, along with the addition of these new beautifications comes a slightly less than perfect installer which can potentially clobber NT Loader's configuration settings, leaving the machine unbootable.
Obviously, this resulted in some rather angry response from the general public. This just goes to show what user level file permissions are good for, and why you should not run applications in administrator mode. This is a moot point of course, since installers run as an administrator anyway. It's a nice thought though.
More information of Trinity: EVE Insider
Disgruntled users forum posts: Thread 1 Thread 2
EVE-Online Patch Makes XP Unbootable [Slashdot.org]








good heavens, I upgraded to vista a month ago and the eve update went smoothly. :)
btw, the game looks really really pretty now.
Eve is very pritty now. I have XP and I personally didn't have issues with the upgrade but I figured that naming a file called boot.ini would definitely be problematic at somepoint.
Microsoft should follow Apple's idea and for the next version of windows switch to a *nix core.
They fixed it two hours after deployment, after they pulled it out of distribution when they found out. Like everyone said, it looks radically amazing.
~Sol~