EA download manager & W7

Glaucus · 22 Apr 2010 at 09:43

Has anyone found a work around for EA download manager or know when EA are like to release a new version.

n111ck · 22 Apr 2010 at 10:20

Whats the problem? Works fine on W7 64bit for me.

Glaucus · 22 Apr 2010 at 10:25

n111ck said:
Whats the problem? Works fine on W7 64bit for me.

"in order to launch this game, please log into EA download manager. To verify game ownership"

It's a known problem with some games, or even versions.

EA just say W7 is not supported.

Kenai · 22 Apr 2010 at 10:30

Works just fine here too (HP 64) and did so on RC as well.

Frapple · 22 Apr 2010 at 10:36

Works perfect for me, download, install, play.

Is that error through EADM itself?

Glaucus · 22 Apr 2010 at 10:54

Frapple said:
Is that error through EADM itself?

yep

well pops up when you click play game.

Kenai · 22 Apr 2010 at 11:05

What game are you having issues with? I've noticed a few posts around the net that seem to have this same issue in XP with BF2142.

I'm wondering if its not a totally different issue and EA support just can't be bothered to try and help so they're fobbing you off with 'W7 not supported' rather than address a different issue in the software.

KNiVES · 22 Apr 2010 at 11:06

Never worked with Vista x64 and it certainly doesn't work with my fresh install of Windows 7 x64 either. Half the time I get verify game ownership, and the other half I get bf2pace.exe errors on both Battlefield 2/2142 games. Steer well clear until EA actually says Windows 7 is going to be properly supported.

It's really ****ing sad that you have to use XP, an OS that came out nearly ten years ago and two generations ago to use the program.

Glaucus · 22 Apr 2010 at 11:08

it's 2142 v1.50
MOH airborne, not sure which version

I know several people have this problem on W7.

KNiVES · 22 Apr 2010 at 11:10

Did you ever get bf2pace.exe errors too? Once you actually log in once in a blue moon, you'll be faced with that. The bc2pace.exe relies on the XP folder system, and the Vista/7 ones make it crash instead. You've got a mountain to climb....

Kenai · 22 Apr 2010 at 11:11

hmmm, BF2/2142 seems to be cropping up a lot in reference to this issue, it wouldn't surprise me if it's an issue with BF2/2142 and EADM rather than W7 and EADM as I have about half a dozen EADM games and they all work without issue on W7-64 HP and did so on W7-64 RC1 (well, Airborne has PhysX issues but that's not EADMs fault) but I don't have any BF games on there.

Glaucus · 22 Apr 2010 at 11:15

Kenai said:
hmmm, BF2/2142 seems to be cropping up a lot in reference to this issue, it wouldn't surprise me if it's an issue with BF2/2142 and EADM rather than W7 and EADM as I have about half a dozen EADM games and they all work without issue on W7-64 HP and did so on W7-64 RC1 (well, Airborne has PhysX issues but that's not EADMs fault) but I don't have any BF games on there.

Yep it is only a problem with certain games, but it is to do with the way EA Manager verifie, in W7. I expect different file structure or something.

There website just says they are working on it and a new version oe EA Manager will be released soon. Been saying that for ages.

Frapple · 22 Apr 2010 at 11:36

Assuming you've tried the obvious running as administrator/turning compatibility mode on?

Could try this if it's installed the game:

Locate your CDKey in the registry, google for it.

Copy the installs files from EADM's download location, should find a folder with your email address as it's name.

Install it from those files (e.g. setup.exe) using CDKey found in registry

Secret_Window · 22 Apr 2010 at 19:28

I had the same problem but with Vista 64bit a few years back - I contacted their support and just ignored pretty much everything I said and kept firing their troubleshoot guide at me - which had no helpful info on the issue at all. They are totally useless.