Jump to content
Sign in to follow this  

ARMA 2: Operation Arrowhead - Linux Server beta 1.60.88775

Recommended Posts



mirror: http://ftp.tier1ops.eu/files/a2oa-server-1.60.88775.tar.bz2

CRC32: C866B9EE

MD5: F4F0B0AD340483701677134F3DA5A125

SHA-1: 19F09E8D49D19FE5A2F9D91BAC9C4E7B8AF015A5

Recent fix: resolved issue with "Failed to load TextureHeaderManager" , no need use -noTexHeaders commandline parameter!

Warning: This is 1.60 branch release, not MP compatible backward with 1.59 branch (1.59 client can't join)

Note that it requires Arma 2: Operation Arrowhead data to be updated to version 1.60 first in order to run properly.

Please provide us with feedback to this topic.

* this version brings linux in sync with actual windows server improvements and ai/mp fixes ...

Arma 2: Operation Arrowhead - Linux Standalone Server 1.60


Copyrigt © 2010 Bohemia Interactive Studio. All rights reserved.

For more information please visit


Installation instructions:


1. Following programs must have been installed on your Linux-box:

tar, gcc. Optional: md5sum (for setup integrity check)

1a. On some verions of Linux (this was reported for RedHat 9

and Gentoo linux 2.4.20) the NSCD deamon must be installed to

run ArmA 2 server successfully. Caching of DNS would be sufficient.

2. Copy the whole "ArmA 2 Operation Arrowhead" directory from Windows

to some Linux-directory (arma2arrowhead). DON'T DO ANY DATA CONVERSIONS

(even "dos2unix" translation of text files is not necessary).

Example: you can use PKZIP (WinZip, PowerArchiver, etc.) on

Windows and "unzip" on Linux.

Don't use upper case letters in the ArmA2 directory name

(/home/bob/arma2arrowhead will be good, /home/bob/ArmA2ArrowHead

may cause some troubles).

ArmA2 directory should contain subdirectories "Addons", "Bin",

"Campaigns", etc.

3. Copy the "server-x.xx.tar.gz" (x.xx is version number) file into

the arma2arrowhead directory. Unpack and install it with commands:

arma2arrowhead$ tar -xjf server-x.xx.tar.bz2

arma2arrowhead$ ./install

Watch the messages - they will inform you whether your installation

is successful.

4. Dedicated server can be started in foreground:

arma2arrowhead$ ./server

Or in background:

o$ nohup ./server > out.txt 2> err.txt &

[1] <pid>

5. Running server can be stopped by executing:

$ kill -s SIGINT <pid>

Where <pid> is process-id of mother server thread (printed out in

"nohup" command).

6. ArmA2 ArrowHead server has a feature: command-line parameter

"-pid=<pid_file>". It causes creation of <pid_file> with

PID of root ArmA2 process. If IP port specified in "-port=<nn>"

parameter is busy (in usage), ArmA2 will terminate immediately

and <pid_file> won't be written..

7. The "arma2server" script is provided for automatic server

start/restart/status query/etc. Please be sure to edit


After this is done, install (hard-link?) the script into

"/etc/rc.d/init.d/arma2server" file. After that it can be managed

by "chkconfig" (see info/man).

previous thread about 1.60.87589 beta linux :

Share this post

Link to post
Share on other sites

Just downloaded the server for my Linux system (64-bit Archlinux updated yesterday to be specific) and before even starting it up the following issues came up:

1) installer says version 1.57

2) .tar.bz2 package contains the directory "expansion/battleye" with the battleye.so. This confused the tolower program to not convert Expansion to lowercase until I moved the .so into /Expansion/Battleye and ran tolower again

3) installer removes .dll etc files only from root directory and not from battleye, expansion and expansion/battleye directories

3) readme says 1.58 BETA

4) readme still talks about "Campaigns" and "Bin" directories which do not exist since OFP / Arma1

5) readme first says "server-x.xx.tar.gz" then "server-x.xx.tar.bz2"

6) many typos and distro specific information in the readme

In short it is almost easier to do things manually than use the installer and the readme is full of errors, old and distro specific information. I have edited the install script to check battleye, expansion and expansion/battleye directories for *.dll and created a suggestion for a new readme.txt file with more update information and more general instructions. Of course the .dll's will not be removed before tolower is fixed not to skip "Expansion" directory if "expansion" directory exists (easy quick workaround would be to use "Expansion/Battleye" in the .tar.bz2 instead of "expansion/battleye"). The files I edited can be viewed and downloaded from http://codemartyrs.info/linux-dedi. Feel free to use them with the next release.

I know a lot of my observations are nitpicking and obvious for anyone with any experience with ArmA and/or half a brain but for someone who might be new to the game and the series it doesn't help to provide erroneous and conflicting information in practically every step in the process and readme.

Edited by Sekra

Share this post

Link to post
Share on other sites

thanks, we will look over your changes ;)

Share this post

Link to post
Share on other sites

We are running =Olut= Arma2 OA (ace) linux server and it has veeeery long startup time (around 9 minutes).

For previous patch 1.60.87589 I made loader which decreased time to 24sec.

Developers, can you give a look for this please.

The address which I did patch was 0x08FC0E61 and what I did change was

69 C3 E8 03 00 00 to 69 C3 D0 07 00 00

*(_DWORD *)(param2 + 4) = 1000 * variable2 % 0xF4240;


*(_DWORD *)(param2 + 4) = 2000 * variable2 % 0xF4240;

This is just dirty workaround but makes server to load 8 and half minutes faster.

When server is started, it will revert back to original value (1000).

Server is CentOs 5.7 64bit with 2.6.18-274.7.1.el5 kernel on i7 2600K CPU.

I'm sure most of servers start fine (fast), but I have also seen topic in here where peps were struggling with this same problem..

Its maybe kernel/distro related but we have to keep stock kernel (with updates) in system.

Is it some kind of loop in code which is checking system time and gets stuck or something?


Edited by Soppa

Share this post

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in

Sign In Now
Sign in to follow this