Official Soldat Forums
Soldat Talk => Need Help? Report Bugs! => Topic started by: -Tri-Edge- on August 28, 2007, 04:58:27 am
-
this morning i've decided to make my soldat look more fun and downloaded this interface http://forums.soldat.pl/index.php?topic=3881.0.
And ofcourse got some bugs, why not...
This time it is Battleye, im getting this message:
(http://img441.imageshack.us/img441/6233/screenshot07082801zc9.th.png) (http://img441.imageshack.us/my.php?image=screenshot07082801zc9.png)
I've been uninstalling and installing clean version about 5 times, also tried this:
Kicked by BattlEye for not responding on clean installs
Quote from: $able
Can you enter the following in the Windows Explorer address bar: %appdata%
Then delete the Soldat folder over there.
Do a fresh reinstall of Soldat 1.4.2 and DONT apply the 1.4.1 BE update package.
Help me please, im getting desperated, i've just solved the problem with acces violation, and now this...
-
Fuck >< I have similliar problem. Something about 5 minutes after joining some server I am kicked. This has something to do with BattleEye cus if I want to join the server again, I can see "unable to load battleye86.dll" or something like that.
I don't think it's caused by battleye upgrade cus every time there is upgrade Soldat displays it in a new window just after running Soldat.exe
Any suggestions? I CAN'T FU*kIN PLAY! :(
-
Just give it a little bit...sable will get online and help soon most likely lol calm down. Youll be able to play soon.
-
Same problem here. I've tried to apply the BE from other friends, whose soldat runs smoothly, but without any progeress. The problem occurs only on server with BE turned on.
I've reinstalled soldat a few times, still nothing.
I didn't have the problem earlier, it just appeared yesterday without any reason.
-
i have the same problem >:( >:(
unable to load BEClient_x86.dll
-
(http://img337.imageshack.us/img337/485/bekf0.png)
Not letting me to climb or anything :F
-
I have the same problem. I spend a few minutes in a server and the BattleEye says it couldn't load BEClient_x86.dll.
-
Guys, $able posted this solution before... probably more than twice:
"This is a known bug.
Go to your BattlEye directory, delete the BEClient_x86.dll file and manually rename the BEClient_x86.dll.new file to BEClient_x86.dll."
But if I'm not mistaken, this was in 1.4.1... try it anyways.
-
hmmm
there isn't a "BEClient_x86.dll.new" file
-
hmmm
there isn't a "BEClient_x86.dll.new" file
Yup Yup.
There isn't file such as that.
-
Guys, $able posted this solution before... probably more than twice:
"This is a known bug.
Go to your BattlEye directory, delete the BEClient_x86.dll file and manually rename the BEClient_x86.dll.new file to BEClient_x86.dll."
But if I'm not mistaken, this was in 1.4.1... try it anyways.
This didn't work at first. I then copied the file and had one with the .new bit added and one without. It worked fine for a while but then I got kicked for having an unresponding client.
-
Go to the following dir in Windows Explorer: %appdata%\Soldat\BattlEye and make sure your BEClient_x86.dll is not write-protected.
-
Its not.
And soldat still ain't working correctly
Guys, $able posted this solution before... probably more than twice:
"This is a known bug.
Go to your BattlEye directory, delete the BEClient_x86.dll file and manually rename the BEClient_x86.dll.new file to BEClient_x86.dll."
But if I'm not mistaken, this was in 1.4.1... try it anyways.
This didn't work at first. I then copied the file and had one with the .new bit added and one without. It worked fine for a while but then I got kicked for having an unresponding client.
That worked fine! <33333
-
If you do this in appdata it will work.
However, I would still like to know what is wrong there... It's MM's code, I guess he fucked it again. :x
-
Hey,
I'm not sure whether I understood you all correctly. I copied "BattleEye_x86.dll" and renamed it to "BattleEye_x86.dll.new". Still doesn't work...
-
Re-read again.
-
Delete the original "BattleEye_x86.dll"
Then Rename the "BattleEye_x86.dll.new"
to be BattleEye_x86.dll and it should work
-
Once I done that, soldat asks me to reinstall or create it manually.
-
You mustnt do that in the BattlEye folder in the Soldat install dir. Only in appdata!
-
This is ridiculous, it was working just fine and now suddenly I get these errors too, none of the above fixes it.
-
I have a question: Do you guys all run the game in Windows 98/ME compatibility mode to fix the access violations?
-
I do (otherwise the game doenst run at all)
-
I dont talk about the comp. mode in Soldat options btw.
I guess you are on Windows XP?
-
Yes, on XP, I right clicked the EXE, and in the compat tab, ran the program under 98/Me compatibility.
And on another note, the Video Compatibility is ALSO checked in the Soldat setup.
-
Yes, this is the problem here, I am investigating it atm.
Date Posted: 28-08-2007, 20:51:16
Ok, the compatibility mode on WinXP ****s up things here. Do the following: Go to %appdata%\Soldat\BattlEye in Windows Explorer address bar and rename the .new file to BEClient_x86.dll (delete the old one before).
DONT do anything in your Soldat install folder!
-
if it helps, the .new file is not named like it is in the error message we get:
BECLIE~1.DLL.new is the name of the file. Let me try renaming it and see if I still crash.
-
Yep, this is the problem in comp. mode.
Date Posted: 28-08-2007, 21:22:17
Btw, access violations of course are not related to BE.
-
$able, if you want a cheap workaround, if it can't find the BEClient_x86.dll.new file, search for BECLIE~1.NEW, and then it will find it. It pays to have been around since the days of 8.3 filenames >.> lol.
-
They're still around in my FS/OS AFAIK :)
C:\WINDOWS\Escritorio>dir
El volumen de la unidad C no tiene etiqueta
El número de serie del volumen es 3041-110E
Directorio de C:\WINDOWS\Escritorio
. <DIR> 14/09/04 10:09a .
.. <DIR> 14/09/04 10:09a ..
NOD32 LNK 359 27/02/07 6:05a NOD32.lnk
ACDSEE~1 LNK 1,350 21/08/07 9:54a ACDSee 4.0.lnk
ARES LNK 385 21/05/07 7:50p Ares.lnk
JUAMPI LNK 377 25/08/07 2:53a JUAMPI.lnk
WINAMP LNK 403 31/01/07 7:54a Winamp.lnk
MENSAJ~1 URL 134 25/05/06 5:53p Mensajes de Texto.url
INTERN~1 LNK 402 25/05/06 6:41p Internet Explorer.lnk
REINIC~1 LNK 275 17/02/06 9:12p Reiniciar conexion.lnk
MENSAJ~2 URL 147 11/07/05 12:35p Mensajes de Texto Personal.url
PROPUE~1 DOC 32,768 26/02/07 7:40a PROPUESTADEMODIFICACIONES07[1].doc
10 archivos 36,600 bytes
2 directorios 394,86 MB libres
C:\WINDOWS\Escritorio>
-
$able, if you want a cheap workaround, if it can't find the BEClient_x86.dll.new file, search for BECLIE~1.NEW, and then it will find it. It pays to have been around since the days of 8.3 filenames >.> lol.
http://msdn2.microsoft.com/en-us/library/ms683197.aspx - this is the function I use.
The string returned will use the same format that was specified when the module was loaded.
So obviously its not my fault, but M$ fucking up things in compatibility mode.
-
$able, if you want a cheap workaround, if it can't find the BEClient_x86.dll.new file, search for BECLIE~1.NEW, and then it will find it. It pays to have been around since the days of 8.3 filenames >.> lol.
http://msdn2.microsoft.com/en-us/library/ms683197.aspx - this is the function I use.
The string returned will use the same format that was specified when the module was loaded.
So obviously its not my fault, but M$ ****ing up things in compatibility mode.
When running in Compatability mode, the following applies:
Windows Me/98/95: This function retrieves long file names when an application version number is greater than or equal to 4.00 and the long file name is available. Otherwise, it returns only 8.3 format file names.
-
How come it works on a Win98 system then?
-
Who knows, compatability mode might reduce it to only short filenames for whatever reason.
My original point still stands; all you are doing is getting the filename, and then appending .new to it, correct? All you need to do, is if finding a file by that name fails, remove the .DLL from the original returned string and replace it with .NEW and try again. It's a quick workaround.
-
That wouldnt really work.
Anyway, I added GetLongPathName() and it works fine.
-
yes i also have that prob , i have to run soldat with win98 mode on ... well im trying to do that , but in the battleeye folder just appears me the file BEClient_x86.dll and BEserver_x86.dll ;<
-
Open my computer
Put in %appdata%\Soldat\BattlEye
Then Delete BEClient_x86.dll
Next step: RenameBattleEye_x86.dll.new into BEClient_x86.dll
Worked for me.
-
@k001: You have not read my post properly. I am not talking about the BattlEye folder inside your Soldat install folder, I am talking about the one in your appdata.
-
yes sry , my fault , now it is working fine , thks for the help $able ;)
-
I used that fix that Ride gave successfully. I also run it in ME compat mode.
-
I had the same problem yesterday, so I did what $able said, and it worked, but now i get it again...Anyone got any ideas? =[
-
There is another update, so re-do what I posted. This new update fixes the problem.
-
Ummm... when i delete my BEClient_x86.dll it says "Cannot delete BEClient_x86 : Access is denied. Make sure the disk is not full or write-protected and that the file is not currently in use."
-
There is another update, so re-do what I posted. This new update fixes the problem.
Where do I get it? :e
-
ericaisadude, you need to close Soldat before. If it still doesnt work, restart your system.
STRIPE, do the same as yesterday...
-
ericaisadude, you need to close Soldat before. If it still doesnt work, restart your system.
Or unmarking write-protection in file properities?
-
I feel sorry for Sable :(
People just don't listen
-
:/
ViN, with write-protection you can still delete the file in explorer.
-
ericaisadude, you need to close Soldat before. If it still doesnt work, restart your system.
STRIPE, do the same as yesterday...
How am I supposed to do that when there is no BEClient_x86.dll.new? Now there's only BECLIE~1.DLL.new and BEServer_x86.dll
-
Re-read my post on page 2. I said you are supposed to rename the ".new" file, nothing else.
...
-
:/
ViN, with write-protection you can still delete the file in explorer.
Oh sorry, I though not.I feel sorry for Sable :(
People just don't listen
I agree with you.
I just carefully read and I don't have problems. Others should try that too.
-
Looks like it worked. I had this problem too.