Can we have a universal wtf please? CCP recently launched their spiffy new update to EVE Online, called Trinity, packing all kinds of goodies such as a new DX9 renderer, new ships, missions... oh, and a shotgun to the head of your Windows XP installation it would seem. Yes, that's right: install Trinity and you could end up making your PC unbootable.

Spotted at SlashDot but confirmed here, the reports state that CCP used a bizarre name (and coding booboo) for the configuration file to Trinity. Instead of naming it, say, config.ini, it's labelled as boot.ini and, unfortunately, the installer will copy the file to the root location of your Windows installation in certain cases... neatly overriding the original and thus making one's PC unbootable!

Luckily for some people, the problem only occurs under specific circumstances, and the devs state that the following scenarios will not experience the issue:

• Running Windows Vista
• Running Linux or OSX(Mac)
• Running Classic Client
• Install from the Premium Full Installer

However, if you're upgrading from the Classic client to Premium and you have Windows XP, then you're pretty much guaranteed to kneecap your PC. So, only a handful of people then? Absolutely not! You would have thought that CCP would have at least tested the most common OS+client configuration for EVE Online players during testing.

Mr Q&A Manager? Boom! Headshot! Naturally, CCP are pretty apologetic about this and I'm sure they feel gutted that such a major problem is going to tarnish the launch of Trinity, especially amongst the fans, but I dare say there's not a lot of CCP-love on their forums right now.

Edit: CCP have removed the faulty installer.

Comments

	Neeyik 2007-12-06 #1 Okay, so they've removed the fault installer so how does one upgrade then? Full client install only, I guess.
	WiZZyWiGG 2007-12-06 #2 Quote: Originally Posted by Neeyik Okay, so they've removed the fault installer so how does one upgrade then? Full client install only, I guess. Nope the update on the site works as it should now. Tested it this afternoon on my work XP machine. Boot.ini is intact.