Originally posted by rshandlon

Ok, the story keeps getting better and better.  I have found where CCP was notified that the update DID indeed delete the boot.ini several days before they even patched.  The proof is the 8th post down, dated 12-3-07.

 

myeve.eve-online.com/ingameboard.asp

 

This clearly shows a clearly negligent act on their part and will cost them dearly.

Heh this post got quoted before as 'Proof' and once again ill say this......

- on the wrong forum.

- Wansant Bug reported by the poster.

- Was posted barly more than a day before the forums went offline for the 24hour patching.

- Before patch day the devs are very buisy getting everything ready for patch time so would hardly have time to troll the 1,000's of post on the forums.

- The moderators dont do bug reporting they do moderator stuff.

Originally posted by Bobarian

 So i turn my comp on yesterday and get this " (windows root)\system32\hal.dll" missing or corrupt. Now that its been traced to EVE. I have a dell xps in which you have to request your OS CD's (which i did today). Am i screwed until i get my OS CD's and reinstall XP?

Er, if you can find drivers...

This is the worst thread I have ever seen...Literally, really, truly, I mean that...

Eve borked your windows install. Well, let's go through the things that have borked my windows, and non-windows systems in the past year.

Macbook Pro: Superdrive update 2.1 (matshita 857D). Made the drive work perhaps 1/6th of the time, eventually failed. Mac's cost for the repair, nothing. It was out of warrenty and now just jingles when I start up the machine. This was an automatic update.

Bios update flash for Lenovo 3000 c200...Downloaded..."Installed Successfully" and then windows reported missing pci dll's at boot. Lenovo's cost for repair, nothing. I had to reinstall windows xp (legit copy) in a repair install, then had to re-register update server so I could pull windows updates. Time lost? To me, about 4 hours. Whoop.

Macbook Pro: USB update rendered my usb/firewire/keyboard and trackpad useless. The system boot just great, but all I/O devices were borked. External DVD would not accept my repair disks, and the superdrive was already screwed by a mac update. So, I had to make a bootable usb install of leopard to reinstall (my system disks were 10.4.7). Time lost, about 6 hours (not straight), money lost? About 80 bucks. USB drives are not free.

Should I even begin with how many games have sent Windows to blue with HAL borktedness?

So, should I sue each and every one? I mean really? Either I have a case, and should be a millionaire because of it all, or perhaps, you should just suck it up, back up regularly, and realize that computers crash. It happens, and it not the end of the world, much less worth my tax dollars to support the staff listening to your mindless litigation.

  I too seriously doubt that this will ever see a court room.  I do think it will cost CCP in the end though.  Not cash out of pocket but cash that could have been in the pocket.

   Players that haven't been arround long and players that were thinking of joining will now take pause before playing EVE because of this blunder.  Players playing that have lost hours fixing this problem and players that had to pay money to fix this problem might well say goodbye to EVE.  Potential players will look at this as possibe example of future problems that CCP's development team will deliver, instead of a sound update you get a broke PC.

    I had the error and was lucky enough to catch it before I restarted my PC.   I could be pissed that this file was removed in the first place but overall I am pleased with the update they put out from all their hard work and time invested, this one oversight is not going to ruin it for me.

  $h!t happens. If you haven't learned that yet, you will soon enough .  Hell they made a bumper sticker for it....

Well when they say extract info from your cpu, that don't mean take out your damn boot.ini file. They mean system specs crap like that the eula does not, protect ccp at all, I guess noone remembers the huge everquest class action lawsuit the eula does not give ANY!!  gaming company power to harm your computer in any way, and yea a simple reload can fix the problem but thats not the point this should not happen period. Just thought of this when you have major surgery you sign the little paper saying if something goes wrong you can't sue the doctor or hospital but funny how doctors still get sued left and right eula does not make computer gaming companies invul to everything.

wow.. yet another post reguarding this mistake... let it go. I swear people just love to tear down any company they can. CCP is a fantastic company and EVE is a good game, atleast i can play EVE without memory leaks causing my computer to start crawling 2 hours later, atleast my expansions are free, atleast it runs great on my machine, and atleast i can get customer service withen 24 hours after a petition... I have 4 accounts on EVE, and atleast another 4 spread over other games, EVE will continue to recieve my money.

Originally posted by Nisstyre

Well when they say extract info from your cpu, that don't mean take out your damn boot.ini file. They mean system specs crap like that the eula does not, protect ccp at all, I guess noone remembers the huge everquest class action lawsuit the eula does not give ANY!!  gaming company power to harm your computer in any way, and yea a simple reload can fix the problem but thats not the point this should not happen period.

And in case people haven't noticed yet, CCP doesn't need to be protected. They will feel the bite of this blunder in forms of some players maybe quitting, some others not joining and maybe they even will have to compensate some people.

No lawsuit will reach courts. If anyone sues them, they will make amends out of court and anyone in their right mind will accept those simply because it's easier and better for everyone involved.

Quit waving around "CLASS ACTION LAWSUIT!!!!" like we're in frikkin Law and Order. <.<

Originally posted by singsofdeath

 

Originally posted by Nisstyre

Well when they say extract info from your cpu, that don't mean take out your damn boot.ini file. They mean system specs crap like that the eula does not, protect ccp at all, I guess noone remembers the huge everquest class action lawsuit the eula does not give ANY!!  gaming company power to harm your computer in any way, and yea a simple reload can fix the problem but thats not the point this should not happen period.

I honestly did not quite understand what you are trying to say. <.<

 

And in case people haven't noticed yet, CCP doesn't need to be protected. They will feel the bite of this blunder in forms of some players maybe quitting, some others not joining and maybe they even will have to compensate some people.

No lawsuit will reach courts. If anyone sues them, they will make amends out of court and anyone in their right mind will accept those simply because it's easier and better for everyone involved.

Quit waving around "CLASS ACTION LAWSUIT!!!!" like we're in frikkin Law and Order. <.<

Well all i am saying is that they are not protected from something like this is all i mean, i wouldn't bother i was in the everquest class action and it was long draw out and what we got wasn't worth the time. They should atleast offer a free month or 6 for ppl that felt the bite. I wasn't effect myself so i am not to worried tho i will be leaving the game not just because of this i been playing 4 years ,and just tired of playing this is as good of a reason as any to head on out :P.

Most of you are morons and don't know a thing because it didn't happen to them.

Firstly to the person saying "XP sp2 users are not affected" is talking out of his ass, because it does.

"it takes 5 minutes, you must be a retard if you can't fix it".

I'm sorry, but once CCP released any kind of warning it was 6 hours after the fact, during which many xp users shut down for the night. Once you reboot the next day and find out you cannot even get windows to start, what are you going to think. Read Eve-Online news? What If they don't have a second computer to read it with, even if they think of that? Getting more to the point, some of you 'experts' who think it is a 5 minute fix because you can just 'boot into windows and copy-paste fix it'...  ROFL that is the best line i've seen in a while. Yes the 'boot.ini' is deleted, lets just BOOT into windows and quickly fix it; you must be a computer genius. Once its taken effect you can't do shit without the windows disk, and even that did not help me, I had to use a 2nd computer to copy a new custom made boot.ini into dos because bootcfg would not generate a new boot.ini . If I had no second computer, I could either reinstall windows, or take it for repairs for $100.

'They offered sufficient help to fix it'

I tend to disagree. If you opened a petition asking for help, they direct you to a thread 80 pages long. In this thread, if you can find the developer posts, they tell you to copy and paste their new boot.ini into a new file. How do you do this if you rebooted before their warning was issued. They provide no recovery instructions once you have rebooted your computer. I had to search Microsoft's technical support site for the solution.

 Oh yeah and for e-lawyer time: I would go for negligence and not gross negligence. They made a mistake, but a very STUPID and CRITICAL one. I would say you could sue for the amount it cost to repair, such as $100 for the geek squad to fix it, but not $1 million for losing work time (as you should have expected something like this to occur and back up your work, etc). Although their intent was not to harm the computer, they should have taken more care and quality control to insure that critical errors did not destroy your operating system, and not NEGLIGENTLY releasing a bad patch. Overall it would not be worth suing for the $100 because of the additional legal and court fees. Perhaps a class-action lawsuit would be better.

You don't think this affected many people?

The Eve-O forum thread is 80 pages.  'nuff said.

I downloaded it within the time frame and I got hit with it, and I restarted, but it took me a whole like minute and a half to use the recovery console and build a new boot.ini....not to mention, if you didn't restart it would take even less time.

End the end, you can place the blame anywhere you want, but why in the world, is a text file vital to booting a windows OS, sitting in an unprotected folder?

Originally posted by CHAOS100

Most of you are morons and don't know a thing because it didn't happen to them.

Firstly to the person saying "XP sp2 users are not affected" is talking out of his ass, because it does.

"it takes 5 minutes, you must be a retard if you can't fix it".

I'm sorry, but once CCP released any kind of warning it was 6 hours after the fact, during which many xp users shut down for the night. Once you reboot the next day and find out you cannot even get windows to start, what are you going to think. Read Eve-Online news? What If they don't have a second computer to read it with, even if they think of that? Getting more to the point, some of you 'experts' who think it is a 5 minute fix because you can just 'boot into windows and copy-paste fix it'...  ROFL that is the best line i've seen in a while. Yes the 'boot.ini' is deleted, lets just BOOT into windows and quickly fix it; you must be a computer genius. Once its taken effect you can't do shit without the windows disk, and even that did not help me, I had to use a 2nd computer to copy a new custom made boot.ini into dos because bootcfg would not generate a new boot.ini . If I had no second computer, I could either reinstall windows, or take it for repairs for $100.

'They offered sufficient help to fix it'

I tend to disagree. If you opened a petition asking for help, they direct you to a thread 80 pages long. In this thread, if you can find the developer posts, they tell you to copy and paste their new boot.ini into a new file. How do you do this if you rebooted before their warning was issued. They provide no recovery instructions once you have rebooted your computer. I had to search Microsoft's technical support site for the solution.

 Oh yeah and for e-lawyer time: I would go for negligence and not gross negligence. They made a mistake, but a very STUPID and CRITICAL one. I would say you could sue for the amount it cost to repair, such as $100 for the geek squad to fix it, but not $1 million for losing work time (as you should have expected something like this to occur and back up your work, etc). Although their intent was not to harm the computer, they should have taken more care and quality control to insure that critical errors did not destroy your operating system, and not NEGLIGENTLY releasing a bad patch. Overall it would not be worth suing for the $100 because of the additional legal and court fees. Perhaps a class-action lawsuit would be better.

You don't think this affected many people?

The Eve-O forum thread is 80 pages.  'nuff said.

XP SP2 automatically makes a backup of boot.ini in case the original gets wiped out so in the case of this bug it would just restore from the backup. So unless the user fucked with restore settings on their system then the bug would have no effect. Not to mention the fact that windows had to be installed on a drive other than primary for the bug to take effect to begin with.

Hmm, well it affected my system... I have XP SP2... I downloaded the update on Wednesday night. It is a big deal, but from what I've seen CCP has been doing their best to fix it... I was lucky cuz i hibernate the computer usually over night so when i read about the problem it wasn't too hard to fix...

Originally posted by xenon2050

Hmm, well it affected my system... I have XP SP2... I downloaded the update on Wednesday night. It is a big deal, but from what I've seen CCP has been doing their best to fix it... I was lucky cuz i hibernate the computer usually over night so when i read about the problem it wasn't too hard to fix...

yes your boot.ini would get erased, but when you rebooted windows would have gone from the backup copy so you wouldn't have had any problem.

Originally posted by shane910

  I too seriously doubt that this will ever see a court room.  I do think it will cost CCP in the end though.  Not cash out of pocket but cash that could have been in the pocket.

   Players that haven't been arround long and players that were thinking of joining will now take pause before playing EVE because of this blunder.  Players playing that have lost hours fixing this problem and players that had to pay money to fix this problem might well say goodbye to EVE.  Potential players will look at this as possibe example of future problems that CCP's development team will deliver, instead of a sound update you get a broke PC.

 

    I had the error and was lucky enough to catch it before I restarted my PC.   I could be pissed that this file was removed in the first place but overall I am pleased with the update they put out from all their hard work and time invested, this one oversight is not going to ruin it for me.

  $h!t happens. If you haven't learned that yet, you will soon enough .  Hell they made a bumper sticker for it....

For any player that decided to trial up in the time of this update, I can assume this would prevent them from subbing up, which unfortunately for CCP will mean lost income. I can also assume because of that they will be more careful in the future.

Yet today hit a new record, 41690 players logged at the same time, being last record around 38k.

Really, the boot.ini issue, though very infortunate, has been managed very quickly by CCP and the minor player base who got hit could repair their systems with ease. Infortunate, yes, but not to be at the limit of wanting the game you like and play to be shutted down by lawsuits and crap like that.

I think th e most interesting thing is the poor coding practice of using a filename of boot.ini. That was just asking for trouble.

"One thing I noticed yesterday was that the content upgrade install blew away C:\boot.ini. I'm sure that the intention is to actually delete <EVE Install Folder>\boot.ini. Might need to fix that! "

Originally posted by woalCE

I think th e most interesting thing is the poor coding practice of using a filename of boot.ini. That was just asking for trouble.

 

"One thing I noticed yesterday was that the content upgrade install blew away C:\boot.ini. I'm sure that the intention is to actually delete <EVE Install Folder>\boot.ini. Might need to fix that! "

HAHA yea shame he didnt bug repot it tho.