• Registered: 2009-11-27
  • Posts: 14

Topic: Strange new error

Hi, I am new (Mildly obvious) and love FirstStrike.
It has so far worked fine, but today I experienced a strange new error that takes place when choosing "launch" from the .exe launcher.
http://img686.imageshack.us/img686/8852/firststrikeerror.jpg

Like I said, this is very recent, I used the launcher all the time and never had this problem.

The game loads fine, but you need to "x" out of the error about 15 times before the game loads.

Here is the exact problem, I load launcher, click launch. It shows the "looking for updates" or whatever screen, but then quickly closes both screens, and this appears. I tried manually updating from "file" in the launcher, but that didnt do anything (no new updates)

Can anyone help? I dont want to reinstall unless I really need to (1.16 GB is HUGE)

~IL

http://miniprofile.xfire.com/bg/sf/type/0/omegaclassa.png
Catch me on Xfire! My most common BF2142 name is "IronFixation"
  • Gwynzer
  • Gwynzer
  • Emperor Incarnate
  • Offline
  • From: Aberdeen, Scotland
  • Registered: 2008-06-24
  • Posts: 1,926

Re: Strange new error

I get this problem too.  I actually found out from someone that it apparently has something to do with XFire.  I've no idea why it causes it, but other than being a minor nuisance, I've ignored the problem.  It happens to me with another few games too.

I actually went online and downloaded the WSOCK32.dll  and placed it in my windows .dll folder, but then I got another .dll error.  I then placed THAT file in the right folder, and got a new error asking for ANOTHER file.  When I then replaced that file it came up with a seperate error message saying that some values in that new file hadn't been "allocated" properly, I then gave up tongue

BlackIntel Game Leader
DUKE815: Teamwork's complicated.  I've found that ramming a Lambda with a Y-wing at full boost is most effective.

Gwynzer's Website

3 Reply by Benu_Kenobi (edited by Benu_Kenobi 2009-11-30 19:02:11)

  • From: Finland
  • Registered: 2007-01-01
  • Posts: 350

Re: Strange new error

Apparently this error is caused Xfire trying to find .dlls from a wrong place in an x64 system. It's not limited to 2142, other games such as Mass Effect seem to suffer from it, too.

This thread might be of help.

-edit-
Possible solution:

Here it is, as discovered by Selth:

Go to the start menu.

Right click on 'Computer' on the menubar on the right.

Go to properties.

Click on 'Advanced system settings' under tasks.

Click on 'Environment Variables', in the 'Advanced' tab.

Under System Variables, look for the variable Path.

Double click the value.

In the Edit System Variable window that appears, add this line at the END of the text in the variable value dialogue box:

;c:\windows\sysWOW64.

Click OK.


Your set! No more Wsock32.dll error messages.

alternatively:

you need to find those files:
wsock32.dll
winmm.dll
oleacc.dll
msimg32.dll
they should be somewhere in the system folder (if not just download them somewhere)

once you have them just copy them into the root folder of the game that is having the wsock32 error (maybe its not the root folder but the folder with the .exe in it not sure)

~The Farce is strong with this one
  • Registered: 2009-11-27
  • Posts: 14

Re: Strange new error

Actually, I had an early version of .net 1.1 (I think) on my computer, as well as all the other versions up to 3.5, I just recieved an update for the 1.1 and now it is gone.....which is weird.
Anyhow...This was solved 2 days ago, but I did not post it until I was sure it was resolved.

A final comment,
Thanks for all the help guys, I am sure that everything you told me to do contributed in solving the problem.
At least I hope so.
If a new error appears, I know who to ask big_smile

~IL

http://miniprofile.xfire.com/bg/sf/type/0/omegaclassa.png
Catch me on Xfire! My most common BF2142 name is "IronFixation"