I found a fix for the "memory .dll error" for vista 32 & 64 bit user's.

[R.J.Travis]

I found this in the PR forums under a name that did not tell the people what it fixed.

I tested it and it work's!!!! PB dose not kick you or anything I have not had 1 crash since I tested on my 4 computers with 32 bit & 64 bit.

you should re wright this and make it a sticky please.


I found a fix for the "memory .dll error" that kicks some of us out to desktop every 2 or 3 map loads on certain servers, some more than others but from what I have been reading this is a problem for a lot of people running Vista, myself included.

The problem is that the BF2.exe is trying to use more memory than it is allowed to, this fix enables the BF2.exe to use more than it's current limit of 2gb (physical and PF together) for the second or two it needs it during certain map loads.

Here you go

(You'll need to be an Administrator)
First, you'll need to grab and install Visual Studio C++ Express from Microsoft.
It's free so don't worry.
Once installed, you'll need to update it, also make sure u have latest game
patch installed.

Backup the bf2.exe file, just in case.

Now, click
Start ->Visual C++ 2005 Express Edition ->Visual Studio Tools ->Visual Studio 2005 Command Prompt
(dont left click on VS 2005 command prompt though, right click on it and then click "Run as Administrator"
**If you dont run it as Administrator the fix will not work**

Then, once the black Command Prompt box is open, navigate to your battlefield 2 directory.
If you don't know how to navigate in DOS, follow this:

In Vista 32: cd c:\Program Files\ ENTER **or** In Vista 64: cd c:\Program Files (x86)\ ENTER

then usually it's "cd EA GAMES" ENTER

then "cd Battlefield 2" ENTER

NOW WRITE THIS

editbin.exe /LARGEADDRESSAWARE BF2.exe hit ENTER

It should then come up with a "Microsoft copyright or trademark" type thingy, this means it was successful.
Type "exit" and hit ENTER, and it's fixed!

64 bit Vista users can now restart and play, 32 bit Vista users follow the next step...

In a command prompt and once again **Run your command prompt "As Administrator"**

Type this command:
BCDEDIT /set increaseuserva 2900 ENTER
Now exit out of that box, restart and you're done!

[creepinshadow24/7]

i have this problem very seldom, (like 2 a year), and when you edit the binarys, doesn't PB kick you?

[R.J.Travis]

No PB will not kick you if you follow what it says i tested it on 4 computers & 20 public servers.

[creepinshadow24/7]

ok, still. too much of a hassle for me, i can live without this fix, since the error appears too seldom to do this.
(yeah, i'm lazy)

[R.J.Travis]

It truly took me only 5m to do it was really easy.

[Sutaki]

I'm doing it with the 2008 version (9.0) and i can do everything up until that editbin.exe thing it tells me "'editbin.exe' is not recognized as an internal or external command, operable program or batch file." Help please!

[R.J.Travis]

Originally Posted by Sutaki

I'm doing it with the 2008 version (9.0) and i can do everything up until that editbin.exe thing it tells me "'editbin.exe' is not recognized as an internal or external command, operable program or batch file." Help please!

editbin.exe /LARGEADDRESSAWARE BF2.exe

type it just like that should work

[Mora]

Can you not just upload the edited exe? it would be allot easier.

[Hetzer]

Originally Posted by R.J.Travis

I found this in the PR forums under a name that did not tell the people what it fixed.

I tested it and it work's!!!! PB dose not kick you or anything I have not had 1 crash since I tested on my 4 computers with 32 bit & 64 bit.

you should re wright this and make it a sticky please.


I found a fix for the "memory .dll error" that kicks some of us out to desktop every 2 or 3 map loads on certain servers, some more than others but from what I have been reading this is a problem for a lot of people running Vista, myself included.

The problem is that the BF2.exe is trying to use more memory than it is allowed to, this fix enables the BF2.exe to use more than it's current limit of 2gb (physical and PF together) for the second or two it needs it during certain map loads.

Here you go

(You'll need to be an Administrator)
First, you'll need to grab and install Visual Studio C++ Express from Microsoft.
It's free so don't worry.
Once installed, you'll need to update it, also make sure u have latest game
patch installed.

Backup the bf2.exe file, just in case.

Now, click
Start ->Visual C++ 2005 Express Edition ->Visual Studio Tools ->Visual Studio 2005 Command Prompt
(dont left click on VS 2005 command prompt though, right click on it and then click "Run as Administrator"
**If you dont run it as Administrator the fix will not work**

Then, once the black Command Prompt box is open, navigate to your battlefield 2 directory.
If you don't know how to navigate in DOS, follow this:

In Vista 32: cd c:\Program Files\ ENTER **or** In Vista 64: cd c:\Program Files (x86)\ ENTER

then usually it's "cd EA GAMES" ENTER

then "cd Battlefield 2" ENTER

NOW WRITE THIS

editbin.exe /LARGEADDRESSAWARE BF2.exe hit ENTER

It should then come up with a "Microsoft copyright or trademark" type thingy, this means it was successful.
Type "exit" and hit ENTER, and it's fixed!

64 bit Vista users can now restart and play, 32 bit Vista users follow the next step...

In a command prompt and once again **Run your command prompt "As Administrator"**

Type this command:
BCDEDIT /set increaseuserva 2900 ENTER
Now exit out of that box, restart and you're done!

Ok, I've executed this fix (went without any of the problems mentioned above) and will report back with my findings once I've run the game. I'm hoping it'll stop the broken net connection problem I'm having, if that is memory related as I suspect.

If it works I'll post the exe for others to try.

[Hetzer]

I made it through two maps without a hitch (no loss of conn), but CTD on the loading-bar for Sunset City.

The conn might be a coincidence or it might haved fixed that, I won't know until further testing (playing actually, who am I kidding ).

The CTD I can live with, I'm always able to get back in before everyone has deployed. It's the loss of conn that drives me up the wall, so fingers crossed this has at least had a positive influence on that (not holding my breath of course, it's a bit of a long shot).