Author Topic: Battleye issues (Read 7491 times)

$able · « **Reply #20 on:** August 28, 2007, 01:22:06 pm »

I have a question: Do you guys all run the game in Windows 98/ME compatibility mode to fix the access violations?

Flamiex · « **Reply #21 on:** August 28, 2007, 01:23:08 pm »

I do (otherwise the game doenst run at all)

$able · « **Reply #22 on:** August 28, 2007, 01:34:42 pm »

I dont talk about the comp. mode in Soldat options btw.

I guess you are on Windows XP?

Flamiex · « **Reply #23 on:** August 28, 2007, 01:36:26 pm »

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.

$able · « **Reply #24 on:** August 28, 2007, 02:17:06 pm »

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!

Flamiex · « **Reply #25 on:** August 28, 2007, 02:20:25 pm »

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.

$able · « **Reply #26 on:** August 28, 2007, 02:28:37 pm »

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.

chrisgbk · « **Reply #27 on:** August 28, 2007, 03:03:22 pm »

$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.

mar77a · « **Reply #28 on:** August 28, 2007, 03:21:58 pm »

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 · « **Reply #29 on:** August 28, 2007, 03:28:13 pm »

Quote from: chrisgbk on August 28, 2007, 03:03:22 pm

$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.

Quote

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.

chrisgbk · « **Reply #30 on:** August 28, 2007, 03:35:23 pm »

Quote from: $able on August 28, 2007, 03:28:13 pm

Quote from: chrisgbk on August 28, 2007, 03:03:22 pm
$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.

Quote
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:

Quote

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.

$able · « **Reply #31 on:** August 28, 2007, 04:12:43 pm »

How come it works on a Win98 system then?

chrisgbk · « **Reply #32 on:** August 28, 2007, 09:39:50 pm »

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.

$able · « **Reply #33 on:** August 28, 2007, 11:08:27 pm »

That wouldnt really work.

Anyway, I added GetLongPathName() and it works fine.

k001 · « **Reply #34 on:** August 29, 2007, 09:54:00 am »

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 ;<

ViN · « **Reply #35 on:** August 29, 2007, 10:06:14 am »

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.

$able · « **Reply #36 on:** August 29, 2007, 10:07:43 am »

@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.

k001 · « **Reply #37 on:** August 29, 2007, 10:11:35 am »

yes sry , my fault , now it is working fine , thks for the help $able

Geoffrey · « **Reply #38 on:** August 29, 2007, 05:29:32 pm »

I used that fix that Ride gave successfully. I also run it in ME compat mode.

STRIPE · « **Reply #39 on:** August 30, 2007, 12:31:42 pm »

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? =[

News:

Author Topic: Battleye issues (Read 7491 times)