Thursday, December 06, 2007
Do not install EVE trinity premium client patch!
Thoms alerted me to the following news from Massively: The EVE trinity premium client patch deletes the Windows XP boot.ini file, making it impossible to reboot your computer afterwards. Massively has detailed instructions on how to fix the problem, but if you already restarted your machine you'll need to enter command line commands into the recovery console you can only start with a Windows XP CD. So right now I can only advise you to not patch EVE before you are certain that all the problems are resolved.
As Massively says: "CCP is on the verge of earning the title of having the worst expansion launch in the history of the genre."
Comments:
<< Home
Newer› ‹Older
Wow. This could be pretty bad for those of us with little technical knowledge of how Windows XP works.
Thanks for the heads up.
Thanks for the heads up.
CCP has fixed the patch as of this morning, so this will only apply to people who already patched (probably a sizable number), or who downloaded the patch before this morning but haven't patched yet.
Link to CCP's news item about the problem here
Link to CCP's news item about the problem here
Haha. Must say that the rest of the patching was flawless, but this boot.ini thing is one hilarious screw-up. I feel sorry for CCP.
This is an absolute horrible thing, very very very bad.
But as a programmer, I can understand how it happened. I hear that Eve has a boot.ini file too, and so they deleted the wrong one.
As for how it escaped QA, the problem doesn't show itself until you try and reboot after patching, so I could easily see how QA has an XP machine, installed the patch, tested a lot of stuff in game, then marked it good.
Even if they did reboot later and find the computer did not boot, I'd imagine they would think something else happened, because what are the odds that their game patch causes a computer to not boot :)
But as a programmer, I can understand how it happened. I hear that Eve has a boot.ini file too, and so they deleted the wrong one.
As for how it escaped QA, the problem doesn't show itself until you try and reboot after patching, so I could easily see how QA has an XP machine, installed the patch, tested a lot of stuff in game, then marked it good.
Even if they did reboot later and find the computer did not boot, I'd imagine they would think something else happened, because what are the odds that their game patch causes a computer to not boot :)
Even though it's an easier thing to miss due to most likely QA using Virtual Machines and thus not even rebooting them but rather restarting them from a known saved state, it still is a MAJOR F.Up...
i have mixed emotions about this. on one hand, yeah, i'm a little mad that this got through. am i so mad that i want to contact my lawyer though? not really because i didn't reboot.
it would've freaked me out though if i didn't find out about the bug and rebooted and all of a sudden my computer didn't boot up.
i also feel bad this happened to these guys. they of course didn't do it on purpose and they are hard workers.
i'm still waiting for the posts in the forums from people that couldn't reboot and had to take it in to get fixed. of course we haven't heard from them yet because it is in the shop today and probably tomorrow before they can get back online and read the eve-online.com homepage.
it would've freaked me out though if i didn't find out about the bug and rebooted and all of a sudden my computer didn't boot up.
i also feel bad this happened to these guys. they of course didn't do it on purpose and they are hard workers.
i'm still waiting for the posts in the forums from people that couldn't reboot and had to take it in to get fixed. of course we haven't heard from them yet because it is in the shop today and probably tomorrow before they can get back online and read the eve-online.com homepage.
Holy cow! Sounds like a monumental cock-up. Just when Eve was getting a lot of good vibe on the blogosphere too.
I don't see any reason this should have happened, this ensures I'll be avoiding their products in the future.
Post a Comment
<< Home