1247 réponses à ce sujet

[Delafoi]

Can't even get this piece of **** refunded, thanks Bioware.

Edit: Yes, I'm still having the admin problem.

Modifié par Delafoi, 19 mars 2011 - 11:03 .

[N0blewarri0r]

ive got the same problem

[Kyanzes]

Still looking for solution to the admin problem (I don't wish to use super admin, first game that ever required) and to the "you must be connected to the internet" problems.

[Petardillo]

And here's still having the "Dragon Age 2 has encountered a problem..." issue.
Is it really so difficult to make a decent patch when pirates found the solution first day?

[Lacan82]

Petardillo wrote...

And here's still having the "Dragon Age 2 has encountered a problem..." issue.
Is it really so difficult to make a decent patch when pirates found the solution first day?

Programming isn't easy. especially when you have to program the program to operate with enomouse amount of hardware component combination and not to mention different OS and configurations.

They can't just wave a wand and have the patch in one day. They have to hunt down the line of code that is causing the issue for x system then figure out how to fix it so that it doesn't break everything else and allow it to run still.

[Diangelos]

Lacan82 you do realize the problem is the software they use to block piracy that the pirates cracked the day of launch and have been playing since and all we ask is for them to just disable the crap since it is only penalizing the PAYING customer at this point...

[Lacan82]

Diangelos wrote...

Lacan82 you do realize the problem is the software they use to block piracy that the pirates cracked the day of launch and have been playing since and all we ask is for them to just disable the crap since it is only penalizing the PAYING customer at this point...

And I said programming take time. Even if they remove it they have to remove it and make sure it doesn't break how something else works.

They have to go through all the same programming lifecycle phases they do even when altering the program.

Planning, Designing, Coding, Testing, and listening. Anytime they wish to make change or alterations to the program they must do all these phases over again.  Why? because they have to keep in mind how it will effect the overall program.

It doesn't matter what the issue is the fact is it will take time to fix.

[loringr]

Lacan82 wrote...
Programming isn't easy. especially when you have to program the program to operate with enomouse amount of hardware component combination and not to mention different OS and configurations.

They can't just wave a wand and have the patch in one day. They have to hunt down the line of code that is causing the issue for x system then figure out how to fix it so that it doesn't break everything else and allow it to run still.

I'm pretty sure this (the admin privileges thing) is an error with the "activation.exe" program called by the launcher before the actual game starts.  I would think it would be possible for EA to at least provide a workaround, if they wanted to.

[Lacan82]

loringr wrote...

Lacan82 wrote...
Programming isn't easy. especially when you have to program the program to operate with enomouse amount of hardware component combination and not to mention different OS and configurations.

They can't just wave a wand and have the patch in one day. They have to hunt down the line of code that is causing the issue for x system then figure out how to fix it so that it doesn't break everything else and allow it to run still.

I'm pretty sure this (the admin privileges thing) is an error with the "activation.exe" program called by the launcher before the actual game starts.  I would think it would be possible for EA to at least provide a workaround, if they wanted to.

Disable UAC


If disabling UAC outright doesn't work PM me. I'll give you a few more work arounds to try.

Modifié par Lacan82, 19 mars 2011 - 04:39 .

[Roen106]

Lacan82 wrote...

loringr wrote...

Lacan82 wrote...
Programming isn't easy. especially when you have to program the program to operate with enomouse amount of hardware component combination and not to mention different OS and configurations.

They can't just wave a wand and have the patch in one day. They have to hunt down the line of code that is causing the issue for x system then figure out how to fix it so that it doesn't break everything else and allow it to run still.

I'm pretty sure this (the admin privileges thing) is an error with the "activation.exe" program called by the launcher before the actual game starts.  I would think it would be possible for EA to at least provide a workaround, if they wanted to.

Disable UAC

Thats not exactly a helpful solution when you don't follow through on explaining how to do that or what it is.

[Lacan82]

Roen106 wrote...

Lacan82 wrote...

loringr wrote...

Lacan82 wrote...
Programming isn't easy. especially when you have to program the program to operate with enomouse amount of hardware component combination and not to mention different OS and configurations.

They can't just wave a wand and have the patch in one day. They have to hunt down the line of code that is causing the issue for x system then figure out how to fix it so that it doesn't break everything else and allow it to run still.

I'm pretty sure this (the admin privileges thing) is an error with the "activation.exe" program called by the launcher before the actual game starts.  I would think it would be possible for EA to at least provide a workaround, if they wanted to.

Disable UAC

Thats not exactly a helpful solution when you don't follow through on explaining how to do that or what it is.

To turn off UAC

• 
  Click Start, and then click Control Panel.
• 
  In Control Panel, click User Accounts.
• 
  In the User Accounts window, click User Accounts.
• 
  In the User Accounts tasks window, click Turn User Account Control on or off.
• 
  If UAC is currently configured in Admin Approval Mode, the User Account Control message appears. Click Continue.
• 
  Clear the Use User Account Control (UAC) to help protect your computer check box, and then click OK.
• 
  Click Restart Now to apply the change right away, or click Restart Later and close the User Accounts tasks window.
  
  
  
  
  UAC is User account controls. It is a secuirty feature in vista/win 7 that even tho you login as administrator it actually only gives you a standard login, and will prompt you to run as elevated mode.  By turning it off it should by pass the elevation requirements for administrator

[Seifz]

Lacan82 wrote...

Diangelos wrote...

Lacan82 you do realize the problem is the software they use to block piracy that the pirates cracked the day of launch and have been playing since and all we ask is for them to just disable the crap since it is only penalizing the PAYING customer at this point...

And I said programming take time. Even if they remove it they have to remove it and make sure it doesn't break how something else works.

They have to go through all the same programming lifecycle phases they do even when altering the program.

Planning, Designing, Coding, Testing, and listening. Anytime they wish to make change or alterations to the program they must do all these phases over again.  Why? because they have to keep in mind how it will effect the overall program.

It doesn't matter what the issue is the fact is it will take time to fix.

Yeah.  Pirates did it in a day, though, and they didn't even have access to the source code.  They had a much harder challenge than EA does.

Also, I program a lot.  I know how much work it takes to call an external program and check its return code.  I'm sure that this is what's happening.

rc = execute(DRM_Utility);
switch(rc) {
case 1: GuestError(); Exit();
case 2: UnregisteredError(); Exit();
...
}
PlayGame();

Now obviously that's just pseudo-code and obviously it's a bit more complicated than that, but that doesn't change the fact that commenting out the call to the activation.exe program and commenting out the checks for the return code takes about... oh, two minutes?  Trivial.

I understand that corporate policy probably requires that even such trivial changes go through a number of other steps such as testing, QA, etc.  However, they haven't even bothered to tell us that they've found a way to fix it.  I don't think they've made it that far!

I also understand that while it's happening, I'm unable to play the game that I purchsed while my rommate has been able to play his "free" copy for more than a week, now.  Also, I'm pretty sure that they could have had this fix in v1.01 if that's what they were going for, but I'm willing to bet that they're trying to fix the DRM instead of disabling it like they should.

Please, stop making excuses for EA.  And disabling UAC doesn't work, anyway.

Modifié par Seifz, 19 mars 2011 - 05:39 .

[harrison1988]

I utilized the "alternate" access method, and logged in. After 2 weeks of constantly receiving that "Dragon Age 2 has encountered a problem..." error, I can now launch the game and it looks like I have access to ALL the DLC's I'm entitled to. Thank you EA and Bioware, for being so unbelievably useless.

[Lacan82]

Seifz wrote...



Please, stop making excuses for EA.  And disabling UAC doesn't work, anyway.

Disabling UAC will get rid of the admin privilage message. Don't tell me it won't work for that because I know better. It will also allow the user to pinpoint the underline cause of the issue and possibly generate a crash log to send to EA to get the program fixed faster.

[triatom]

Ok, so I've "upgraded" to patch 1.01 and my game has now stopped working.

I've had problems with the game crashing at the "press any key screen", where I would press a key, whether keyboard or mouse, and it would crash. However, sometimes I would somehow get it to work and be able to play and whenever it did crash I could always kill dragon age 2 and try to relaunch.

After the installation, I can't get it to work and my whole computer freezes up causing me to have to restart. If anyone has run into this problem and has resolved it on this thread sorry I tried to read through as many pages as I could.

Using Windows XP 64-bit, and all my specs check out.

Modifié par triatom, 19 mars 2011 - 06:03 .

[Seifz]

Lacan82 wrote...

Seifz wrote...



Please, stop making excuses for EA.  And disabling UAC doesn't work, anyway.

Disabling UAC will get rid of the admin privilage message. Don't tell me it won't work for that because I know better. It will also allow the user to pinpoint the underline cause of the issue and possibly generate a crash log to send to EA to get the program fixed faster.

No, it won't.  Really.  In fact, you can log into Windows with the administrator account, disable UAC (even though you don't need to because you're administrator), set every executable in bin_ship to "run as administrator", and launch the game as administrator, and you'll still get the "cannot run with guest account" nonsense.  I know this because I've tried it multiple times.  Really.

The problem is obviously in the DRM itself.

[Lacan82]

Seifz wrote...

Lacan82 wrote...

Seifz wrote...



Please, stop making excuses for EA.  And disabling UAC doesn't work, anyway.

Disabling UAC will get rid of the admin privilage message. Don't tell me it won't work for that because I know better. It will also allow the user to pinpoint the underline cause of the issue and possibly generate a crash log to send to EA to get the program fixed faster.

No, it won't.  Really.  In fact, you can log into Windows with the administrator account, disable UAC (even though you don't need to because you're administrator), set every executable in bin_ship to "run as administrator", and launch the game as administrator, and you'll still get the "cannot run with guest account" nonsense.  I know this because I've tried it multiple times.  Really.

The problem is obviously in the DRM itself.

Have you tried turning off the guest account login on your system?

[Seifz]

Lacan82 wrote...

Seifz wrote...

Lacan82 wrote...

Seifz wrote...



Please, stop making excuses for EA.  And disabling UAC doesn't work, anyway.

Disabling UAC will get rid of the admin privilage message. Don't tell me it won't work for that because I know better. It will also allow the user to pinpoint the underline cause of the issue and possibly generate a crash log to send to EA to get the program fixed faster.

No, it won't.  Really.  In fact, you can log into Windows with the administrator account, disable UAC (even though you don't need to because you're administrator), set every executable in bin_ship to "run as administrator", and launch the game as administrator, and you'll still get the "cannot run with guest account" nonsense.  I know this because I've tried it multiple times.  Really.

The problem is obviously in the DRM itself.

Have you tried turning off the guest account login on your system?

I've never had the guest account enabled.  Also, that wouldn't matter if I was logged in as administrator.

Look, I've tried all the easy remedies and even a few more advanced remedies.  Nothing works.  The problem appears to be in the activation.exe executable in the bin_ship\\Core folder.  It's the EA DRM executable.  I know for certain that this executable is being called when I start the game and it's easy to see this for yourself.

As a regular user, set the activation.exe executable to "run as administrator".  You'll want UAC on for this, so you'll need to enter your password here.  Now, start the game from the launcher as normal.  Before you can play, you'll be prompted to enter the administrator password when the activation.exe executable is called.  Immediately after this point, I get the unsifficient privilages error.

Disabling the DRM with an "unofficial" solution solves the problem entirely, but it doesn't let me use my own EA account to play the game.  So, I don't like that solution.

[harrison1988]

Disabling the DRM with an "unofficial" solution solves the problem entirely, but it doesn't let me use my own EA account to play the game.  So, I don't like that solution.

I logged in just fine with the "unofficial" solution. According to the extras menu, I have all the DLC's I purchased as well.

[Seifz]

Hm, fair enough. The one that I found just had all DLC unlocked and I didn't want to use anything I hadn't paid for. I'll keep looking.

[Tymmicus]

Still struggling with insufficient rights issue. Disabling UAC doesn't work. Creating/using different accounts doesn't work. I even went so far this morning as to flash my BIOS (took a few hours of research, several aborted attempts with useless ASUS Updater utility, a couple of large cups of coffee and much nail biting); so that is not the solution, either. I have to say I agree with Seifz. Maybe EA can bring him in as a consultant!

[dayalu]

Gawd, I bought the game hoping to play it during my week off and nothing, sigh. This could be the last game i buy from this company, since i don't even get to play it

[Ragnarokpc]

Yeah I called tech support and they walked me through disabling UAC etc., which didn't help. I still think my problem is that my computer can't seem to display its own specs, so the game can't tell what I'm running. Shouldn't we be able to manually enter what we have, or maybe EA could make it's own program to report my computer's capabilities? I seem to remember that from older games . . . and yes, I've tried the "repository" solutions and had no luck.

[Seifz]

Ragnarokpc wrote...

Yeah I called tech support and they walked me through disabling UAC etc., which didn't help. I still think my problem is that my computer can't seem to display its own specs, so the game can't tell what I'm running. Shouldn't we be able to manually enter what we have, or maybe EA could make it's own program to report my computer's capabilities? I seem to remember that from older games . . . and yes, I've tried the "repository" solutions and had no luck.

EA already has its own program to determine your PC specs.  The DA2 Configuration program does exactly that!  The problem is in the EA Core DRM, though.  They want your specs so that they can prevent the game from working if you change your hardware unless you re-authenticate it.  Microsoft uses a similar system for Windows, but at least Microsoft's works and they disclose precisely what types of hardware changes will require a re-authentication.  EA's clearly doesn't work and they definitely don't disclose that information.

What's really annoying is that my WMI information is perfectly fine and displays properly in the control panel, in the DA2 configuration utility, and in numerous other applications that have requested the same information.  I'm thinking that the bug is in the program that checks the WMI information (bin_ship\\Core\\activation.exe).  Either this program is reading the WMI information incorrectly (which explains why updating the BIOS has worked for a few people) it's incorrectly requesting access to something it shouldn't, or it's not reading a return code properly somewhere.

Regardless, all that really matters is that EA's DRM is preventing me, you, and thousands of others from playing our games.  Instead of removing the DRM entirely so that we can play, they're working to fix the DRM itself.  In the meantime, the ineffective DRM has already been cracked for more than a week and the pirates have been playing without any trouble at all.  That's poor.  Shame on you, EA.

[X2Zjtk44]

I guess I'm having the same problem as everyone else - insufficient privileges... The worst thing is that it ran fine for a week before giving me any problems. UAC has been off always and there's been no hardware changes other than plugging my ipod in to charge (unplugging it didn't make any difference).

This is pretty poor - if your giving the customer something that they don't really want to buy (DRM) it has to be 100% dependable.

Regrets buying Dragon Age 2...