How to setup a win32 ofp server under linux...

[sicilian 0]

This paper describes how to use win32 “OperationFlashpoint†server executables on a penguin machine.

The method to use win32 OFP servers on Linux announced hereby was successfully tested on SuSE Linux 8.2 / 9.1 and requires the following packets “XFREE86â€, “VNC†and finally “Wineâ€!

Those who are familiar with compiling sources may do so, anybody else is recommend to install rpms' which are already compiled and much more easy to handle - for beginners.

<span style='color:darkblue'>NOTICE:

ONCE YOU HAVE SETUP THE VNCSERVER (STEP 3) SUCCESSFULLY, PERFORM THE FOLLOWING STEPS WITH THE VNC CLIENT FROM A REMOTE MACHINE!

(Steps one to three on the Linux server! Steps four to six from the VNC client)

REMEMBER THE USEFUL AND MIGHTY “MAN†PAGES, WHICH COULD PROVIDE MORE DETAILED HELP ON SPECIFIC PROBLEMS OR VISIT THE WEBPAGES OF “WINE, VNC AND XFREE86â€!</span>

This paper is free to be distributed and copied all over the world and in any way! Alteration, however, requires a written and signed permission from the authors! Thanks to Anywhere [1stG.U.N.S]!Done by the storiedveterans.de 08/2005

<span style='color:red'>SteP onE:</span>

::installing packets::

A X-Server is a core service to run windowmanager like KDE, GNOME etc. These windowmanagers are needed to start the win32 ofpserver executable, since it creates window(s) like on the Microsoft windows desktop!

Because of the fact that you maybe want to remote control the server, a pipe from the Linux machine to your machine at home is needed. This requires another client server architecture, provided by VNC. Once the VNCserver is started, its client will be able to obtain the whole colored desktop from the remote controlled machine. It's like the terminal service on Microsoft Windows!

To run win32 executables on penguin powered machines WINE is needed!

How to:

Use YAST (SuSE) or an other RPM packetinstaller and setup the following packets:

xfree86 (X-Server)

xfree86-xvnc (remote desktop / terminal service)

wine (windows “emulatorâ€)

It should be known that you do not need to reinstall any packet if it is already installed and up2date

<span style='color:red'>SteP twO:</span>

::configuring the X-Server::

sax2 (configure the X-Server)Useful commands:

sax2 -a

sax2 -p

lspci

Configure xf86config (should be located in /etc/x11/) by hand to fit your needs.

If you are running SuSE Linux, you need to configure susexf86config!

It was mentioned from the root of the storied veterans [stoV] (SuSE Linux 9.1), that he didn't need to configure the X-Server due to SuSEs' preconfiguration of its Linux distribution.

SAFETY FIRST:

Run xauth list to verify access authorization to the X-Server.

Copy .Xauthority to the home directory of the user who will run the win32 ofpserver on Linux.

(It's a bit dirty but the user who will run the ofpserver needs to connect to the X-Server from a remote machine.)

<span style='color:red'>SteP threE:</span>

::configuring/starting VNCserver::

This is the VNCserver part. This server is needed to send the desktop data to a

client, which on the other hand will print the received data to your monitor.

How to:

Just start the VNCserver by typing "vncserver" if it is already available on

your system. The “xnvc†service should be started up now, loaded with all the needed parameters.

Anywhere from the 1stG.U.N.S provides us with the following command to start the VNCserver without using the command vncserver:

Xvnc :1 -desktop X -httpd /usr/share/vnc/classes -auth /home/user/.Xauthority -geometry 1024x768 -......

However, our own root noticed, that he simply started the VNCserver and it went fine as well as with using parameters.

VNC opens two networkports -> 5801 & 5901 which are needed for the comm between VNCserver, VNCviewer and a browserviewer.

We strongly recommend to use a ssh-tunnel for connections to the VNCserver and to deny connections from other hosts than local e.g. by using iptables filter rules.

(e.g. iptables -I INPUT -p TCP --dport 5901 -s ! 127.0.0.1 -j DROP)

<span style='color:red'>SteP fouR:</span>

::starting VNCviewer on a windows machine::

Use VNCviewer (e.g. MS Windows version) to control the desktop on your Linux machine. Just connect to the ip where the X-Server is located and the VNCserver is running. (e.g. 23.23.23.23:1)

The standard windowmanager is quite ugly and known as TWM, but however, this ugly thing is for administrative purposes only and do not need any support of transparent and shiny windows Of course, you can run KDE or some other desktop with VNC but TWM just needs one process what makes it a lightweight.

<span style='color:red'>SteP fivE:</span>

::preparing WINE::

Login as the user that will run ofp by typing "su username".

Create a directory for WINE -> mkdir .wine and change to it cd .wine

Create a directory for windows -> mkdir windows and change to it cd windows

Create a directory for system -> mkdir system

Create a directory for profiles -> mkdir profiles and change to it cd profiles

Create a directory for administrator -> mkdir administrator

Run wine or winecfg now. During the first start WINE will configure itself and create a directory called “dosdevicesâ€. Therein, WINE links/maps to the virtual drives.

Whilst the [stoV] root did nothing more on this step 5 and it runs fine, too, Anywhere said he trimmed the paths in

/home/user/.wine/user.reg

/home/user/.wine/dosdevices

by creating a “path†in “user.reg†to the ofp directory. However, all roads lead to Rome.

<span style='color:red'>SteP siX:</span>

::run win32 styled OFPServers::

Just hop to your ofp directory and start the server by typing

wine OFPR_server.exe -config=server.cfg -port=2304 .....

Attention: wine caches fonts when it's started first, so don't be panic.

FINALLY, YOU HAVE SETUP A RUNNING WIN32 FLASHPOINT SERVER ON LINUX!

This tutorial is available as pdf hosted on the ALSR, too.

<span style='color:blue'>Download as PDF</span>

Thx to StoV and 1st GUNS

[kegetys 2]

Doesn't the server work anymore using the TTY output driver in wine? It should be much more efficient to use that instead of running X.

[hoot 0]

however, this is just one way to setup the win32 server and to control it from a remote machine. if you are able to set it up by using tty then you may do so, we didn't have test it that way, yet.

the paper was meant to be a handy package for average linux'ers with dedicated servers, not for the real nerds gaming q3 with tty output

anyhow, test it with tty *pls* and post you suggestions here...

Quote[/b] ]It should be much more efficient to use that instead of running X.

we are running lots of services and are fighting with a least 28 players every evening on the battlefields...there is no lag present with the current config...it's just linux

edit:

the average setup it this: ofpserver on a linux dedicated/root server and a windoze client at home...