BF2 1.5 Alt-Tab Fix Through RendDX9.dll

[]TAR[ Rebiv4]

This hotfix is causing MD5 kicks. I deleted PB and reinstalled, still happened.

[Snares]

This hotfix is causing MD5 kicks. I deleted PB and reinstalled, still happened.

Keep using your bat files, as they will prevent the kick. The reason for the kicks is that Evenbalance probably haven't updated their checklists yet. Make sure you delete your cache as well.

[DDS]

EA games are the most incompetent developers I have ever seen.. release a "fix" that causes problems.. seen this from 1.0 forward.. unbelievable

[Snares]

EA games are the most incompetent developers I have ever seen.. release a "fix" that causes problems.. seen this from 1.0 forward.. unbelievable

Well fortunately, this isn't a Evenbalance problem now. PR has to update their own check lists so that they will accept the md5 from this new hotfix. If you go play on a vanilla BF2 server, you shouldn't have any problems.

[DesmoLocke]

EA games are the most incompetent developers I have ever seen..

Too bad EA is a publisher and DICE (EA Digital Illusions CE) is the developer.

Since applying the hotfix, I have had no issues with vBF2 servers. However, some of the MD5 checks when in PR servers is still causing a PB kick for some reason.
I suspect EvenBalance to correct it in due time.

[Snares]

Too bad EA is a publisher and DICE (EA Digital Illusions CE) is the developer.

Since applying the hotfix, I have had no issues with vBF2 servers. However, some of the MD5 checks when in PR servers is still causing a PB kick for some reason.
I suspect EvenBalance to correct it in due time.

https://www.realitymod.com/forum/f27-pr ... 9-dll.html Please carefully read the first post in this thread to fix the PB kick.

[DDS]

Well fortunately, this isn't a Evenbalance problem now. PR has to update their own check lists so that they will accept the md5 from this new hotfix. If you go play on a vanilla BF2 server, you shouldn't have any problems.

\

THe "fix" came from EA Games, not PR. PR must then adapt to said "fix". So yeah this is an EA "problem".

[Snares]

\

THe "fix" came from EA Games, not PR. PR must then adapt to said "fix". So yeah this is an EA "problem".

I suppose it is kind of a "problem" in the sense PR must adapt to said "fix," but I'm not really too mad at EA right now. The original alt-tab problem was EA's, but the hotfix, in itself, is not. EA is not responsible for PR's specific MD5 check lists. I'm just really grateful that DICE was kind enough to do anything about it at all.

[LMLM111]

Edit: Ignore this post. I made a mistake. Snare's post is correct. I'll leave what I put below but please ignore it.



The original post suggests using a rename method for the .dll files. This is not a good idea because if you accidentally click the wrong .bat file for whatever reason your .dll files could get mixed up.

Instead, use a copy over method from source files which are never changed:

dxbfstart.bat

Code: Select all

c:

cd "Program Files\Battlefield 2"

copy RendDX9_hotfix.dll RendDX9.dll /y

DxBFMainMenu.bat

Code: Select all

c:

cd "Program Files\Battlefield 2"

copy RendDX9_15.dll RendDX9.dll /y

This way, you can be sure that the right .dll is in place and that the wrong rendx9.dll was not renamed to the wrong source because no renaming is used.

[Snares]

The original post suggests using a rename method for the .dll files. This is not a good idea because if you accidentally click the wrong .bat file for whatever reason your .dll files could get mixed up.

Instead, use a copy over method from source files which are never changed:

dxbfstart.bat

Code: Select all

c:

cd "Program Files\Battlefield 2"

copy RendDX9_hotfix.dll RendDX9.dll /y

DxBFMainMenu.bat

Code: Select all

c:

cd "Program Files\Battlefield 2"

copy RendDX9_15.dll RendDX9.dll /y

This way, you can be sure that the right .dll is in place and that the wrong rendx9.dll was not renamed to the wrong source because no renaming is used.

That's incorrect. If you keep RendDX9.dll in its original form, and RendDX9_fix.dll in it's original form, you can never accidentally rename the bat files. Copying takes much longer and creates fragments. Go ahead, try it. Run the bats in the reverse order, do anything you want. It will never mess up. Carefully look at the bat files and you will see why. In the start, you rename one bat file to *_15, and then rename *_fix to *. In mainmenu, the only possibly option is to rename * to _fix. The last line of mainmenu will not work, because the bat file will not rename another file to the same filename. You get

Code: Select all

A duplicate file name exists, or the file cannot be found.

and the bat crashes, thereby removing any chance of messing up.

[DesmoLocke]

No need for the .bat files now with the server side hotfix for the PR servers has been released. Snares, you might want to make a note of it in the first post.

[Snares]

No need for the .bat files now with the server side hotfix for the PR servers has been released. Snares, you might want to make a note of it in the first post.

There is still a need, since many servers will not install the hotfix for at least a few days. I will make note of it in the original post though.

[LMLM111]

That's incorrect. If you keep RendDX9.dll in its original form, and RendDX9_fix.dll in it's original form, you can never accidentally rename the bat files. Copying takes much longer and creates fragments. Go ahead, try it. Run the bats in the reverse order, do anything you want. It will never mess up. Carefully look at the bat files and you will see why. In the start, you rename one bat file to *_15, and then rename *_fix to *. In mainmenu, the only possibly option is to rename * to _fix. The last line of mainmenu will not work, because the bat file will not rename another file to the same filename. You get

Code: Select all

A duplicate file name exists, or the file cannot be found.

and the bat crashes, thereby removing any chance of messing up.

Yes the duplicate filename error stops a rename replace condition.

Btw, thanks Snares for the quick fix.

[Snares]

Yes the duplicate filename error stops a rename replace condition. Copying doesn't take much longer. We're talking hundredths of a second here due to hdd caching in Windows and the hdd cache (2.5MB is less than almost all HDD's caches made today). As long as the file already exists and is in the same place, I don't think it will fragment, but just replace the existing sectors. I'm not positive about that. NTFS might indeed fragment the target but generally NTFS does minimize some/much fragmentation by itself (but not all).

For reference, the hotfix RenDX9.dll file I hvae is dated 9/7/2009 at 2:12pm and is 2,498 kb.
The alt-tab bugged RenDX9.dll file on my machine is dated 9/26/2006 at 5:51pm and is 2,489 kb. I give this information for those who need it when they see a file and aren't sure which one it is, due to renaming.

I still think the copy over method is better but to each his own. Your hard drive crash from fragmenting. Not.. just kidding.

Btw, thanks Snares for the quick fix.

I'm not sure why your bugged RendDX9.dll is 2,489 KB...mine is 2,496 KB. If you get any MD5 errors download this one: RendDX9.dll

By the way: I tried your bat method, and it fails. You will get "The process cannot access the file because it is being used by another process. 0 file(s) copied" upon trying to run mainmenu.

[LMLM111]

I'm not sure why your bugged RendDX9.dll is 2,489 KB...mine is 2,496 KB. If you get any MD5 errors download this one: RendDX9.dll

Thanks! Yes I did get some MD5 errors recently. THANK YOU for being so helpful.

[LMLM111]

By the way: I tried your bat method, and it fails. You will get "The process cannot access the file because it is being used by another process. 0 file(s) copied" upon trying to run mainmenu.

Edit: you are correct. That error occurs. I will edit my original post to avoid confusion. Sorry.

[LMLM111]

By the way: I tried your bat method, and it fails. You will get "The process cannot access the file because it is being used by another process. 0 file(s) copied" upon trying to run mainmenu.

Yes you are correct.

[Soppa]

Actually I found this renaming method for avoid being kicked because using largeaddressaware patched bf2.exe here: https://www.realitymod.com/forum/f370-pr-tech-archives/56529-solution-vista-64bit-2gb-memory-crash-desktop-issue.html

I cant see any reason why this wouldnt work for other files too. You wont get kicked or banned by PB. Method is ugly but its workaround for sure.

Reason why you can get error message of locked files is because you are trying to overwrite them. You should rename files .old before "replacing" with original files, that way you cant get error messages of locked files.

NOTE: There could be little risk if PB is updated to check files MD5 sum's and keep some kind of history of em. This could be good update tho because this copying method makes whole PB quite useless

[FIN] SOPPA

[coroneln]

a link to the Hotfix w/o the annoying need to register in a forum:
The Order of Doom PRl

in the main page the last downlad link the one that says ALT_TAB Hotfix

[LMLM111]

I'm not sure why your bugged RendDX9.dll is 2,489 KB...mine is 2,496 KB. If you get any MD5 errors download this one: RendDX9.dll

Yes I think that file fixes my disconnects. Will try for longer time now.