BF2S Forums Now I know how to get BF2 and BF2:SF to work together...

The reason it wasn't so clear was because 1.12 came out like the day SF did, for people who didn't have the expansion (and those who did). It was a last minute thing and people are too stupid to care or read or search for anything these days.

Ryan_Mercury wrote:

The reason it wasn't so clear was because 1.12 came out like the day SF did, for people who didn't have the expansion (and those who did). It was a last minute thing and people are too stupid to care or read or search for anything these days.

I think 'stupid' might be putting it a bit strong. Perhaps people already had the patch but were still experiencing problems. I know I had the patch and I didn't do any searching, after all, I've heard from several sources, those that follwed instructions after searching for information were still doing it wrong, this despite following EA procedure.
EA UK admitted themselves that there was a problem with 1.03 and that it shouldn't be used in conjuction with 1.12 if you have SF (which I did)... but nowhere on their site (EA) did it mention anything about it... probably not up until now.

So I don't think it's a case of people being 'stupid' (well not in that majority of cases ). I just think it was a patch in progress and that the information wasn't readily available until they'd realised there was indeed a problem with patching 1.03 and 1.12(SF) together.

This of course doesn't mean everyone had problems, indeed most didn't, but some did and it wasn't even if it was a case of system configuration, we all had different ones. It was just a case of some worked and some didn't. It's in EA's interests to solve all of the problems, after all, it is a business and it's in business to make money. The fact that they're making games that we enjoy is just a bi-product.
I don't think anyone has flamed EA (on this thread), but you have to admit yourself, when something doesn't work or breaks down without reason, who do you blame

..hmmm...I removed my nerve system and put it into icebowl. Then I

- removed SF
- re-installed SF and patch

...NO PROBLEM

Both, BF2 and SF, are working fine.---> nerve system cooled down too...

P.S. I tried to run BF thru debugger before I uninstalled SF but didn't manage to get any decent log...well, next time
Oh...about PB. The uninstallation did absolutely nothing to PB folder. Neither did the new installation...weird thing.

Last edited by BudRell (2005-12-12 00:17:27)

..and now I know why I didn't get any good debugger output.

The game is "protected" with "quick'n'dirty" style (IMO). AE has used protection which tells OS that the game is already debugged --> the game will not "open" in normal way. It must be done in another way and I will debug this one (god damn).
Why ? Because I WANT TO KNOW WHY the code makes weird things that makes me angry.

Hmm...no matter which CD (or DVD..) you have in player. I bought BF2 and SF in DVD-format and I can join both versions with both DVD.

There's one thing that I realized only a week ago.
If you start the game from "play BF2"-icon (NOT the instant play !) but you want to play SF instead, you don't have to quit BF2 to switch to SF !
Just go to Community menu (or what it was..), the same menu you can download those demos from servers, and select game mod there. BF2 then says that "you have to quit bla bla...". Press OK and the SF will load.
So...you can play SF with original CD atleast that way.

Works also if you started the game in SF. Do the same thing I wrote above but choose BF2 as the game-mod and  the game will unload SF and start in BF2 mod.

Last edited by BudRell (2005-12-20 01:05:20)

Thanks,  I finally got a reply from EA and they said that the patch failed.  I had BF2 with 1.12 and then put SF on and had to reaply the patch.  It all runs fine except the switching versions.  They said that there is a code missing in a file and that I had to redo the patch and get a cod out of it and then paste that code in a particular file and that would fix it.  Below is what they sent:

The issue you are having can be  due to a corrupt download of the patch.  Try downloading the patch from one of the other download locations listed for the update on http://www.eagames.com/official/battlef … ate_112205

Please check your game version.  This can be found at the lower left hand corner of the Main screen under the Quit button. Un-patched version of the game is 1.0.2442.0
Patched version 1.1   is 1.1.2475.0
Patched version 1.02  is 1.1.2484.0
Patched version 1.03 is 1.1.2551.0
Patch version  1.12 is 1.1.2554.356
Run the 1.12 patch installer again and select the language.
Click Next, and then stop on the 'Welcome to the Install Shield Wizard for Battlefield 2 Patch v1.12' screen.
Click on Start and then Run.
Type %temp% in the Run box and hit Enter.
Click on View at the top of the window and choose Arrange Icons By and then Modified. Scroll to the end of the list. The last folder icon should have an alpha-numeric code for the name such as {3D3B4B03-9974-4B03-B7B2-FAB1919C8E3D\}.

This code name is randomly generated per system, but should be the last folder listed. Open this folder. There should be another alpha-numeric named folder inside. Open this folder.
Click on Edit at the top of the window and choose Select All.
Click on Edit again and choose Copy.
Close all open windows except for the installer.
Open My Computer and navigate to the game folder.
By default this is C:\\Program Files\\EA GAMES\\Battlefield 2.
Once in the Battlefield 2 folder, right-click on an empty space in the window and choose Paste. This should copy the patch files to the game folder. Double-click on the Patch.exe file (the icon for this file looks like a window). This should be one of the files copied over. This will prompt the files to update. When it completes patching, you may close the installer window. You should now be patched to version 1.12.The patching process uses and needs at least 3 GB of working space on your C:\\Windows\\temp area as it edits and re-patches the files on whatever drive you have installed the game. Please try to free more space on your systems drive ( Drive C for the patch to work.

I'll post again once I have tried the fix.  I had a bunch of time to just play at the moment so I am taking advantage of it and then I will give the fix a try.  I'll let everyone know how it goes.

Andy