Showing posts with label Fedora. Show all posts
Showing posts with label Fedora. Show all posts

Sunday, June 30, 2013

AIM Media Center Remote Control RC118 with Linux and XBMC

Bought myself a new remote control from Maplin yesterday for my media centre running XBMC on Linux (Debian Testing). It's an AIM Media Center Remote Control, model RC118 and only costs £20.


It's nicely made for the price, the only cons are that it's got a Windows logo on one button (uck!) and unlike my old remote (also from Maplin) not all the buttons work 'out of the box' on Linux & XBMC.

The 'pro' of this remote however is that it's a 'standard' MCE RC6 remote so the buttons can be translated and mapped with lirc. I couldn't do this with my old remote as it emulates a keyboard device.

For a relatively popular remote, surprisingly little information can be found on the web on how to set it up properly with lirc and XBMC, just the usual array of forum posts and incomplete or non-working advice. So some reading was required of the lirc & XBMC's Lircmap.xml documentation.

So here's the solution, if you discount creating the map files (as I've supplied them here) it's actually very simple. I've tested this on Debian (Testing) & Fedora 18 so I assume this would work just as well on derivatives such as Ubuntu/Mint and CentOS/RHEL respectively.
 

So first, install lirc...

Either use your preferred software installer GUI or save time by opening a terminal & using the command line;

On Debian & Ubuntu

 sudo apt-get install lirc  

On Fedora

 sudo yum install lirc  


Configure lirc

The lirc daemon is configured with the file /etc/lirc/lircd.conf.
 In the terminal, you can open this file for editing in gedit (or your preferred text editor);
 sudo gedit /etc/lirc/lircd.conf  
Append the following text your lircd.conf.
 begin remote  
  name rc118  
  bits      13  
  flags RC6|CONST_LENGTH  
  eps      30  
  aeps     100  
  header    2700  855  
  one      486  419  
  zero     486  419  
  pre_data_bits  24  
  pre_data    0x1BFF83  
  gap     107341  
  min_repeat   1  
  toggle_bit_mask 0x8000  
  rc6_mask  0x100000000  
    begin codes  
      Power          0x1BF3  
      Record          0x1BE8  
      Stop           0x1BE6  
      Pause          0x1BE7  
      Rewind          0x1BEA  
      Forward         0x1BEB  
      Previous         0x1BE4  
      Play           0x1BE9  
      Next           0x1BE5  
      Zoomout         0x1BD9  
      Zoomin          0x1BDA  
      Eject          0x1BB7  
      Select          0x1BDB  
      Menu           0x1BF2  
      Back           0x1BDC  
      Info           0x1BF0  
      Up            0x1BE1  
      Down           0x1BE0  
      Left           0x1BDF  
      Right          0x1BDE  
      OK            0x1BDD  
      Vol+           0x1BEF  
      Vol-           0x1BEE  
      Chan+          0x1BED  
      Chan-          0x1BEC  
      Mute           0x1BF1  
      PICTURES         0x1BB6  
      VIDEOS          0x1BB5  
      MUSIC          0x1BB8  
      1            0x1BFE  
      2            0x1BFD  
      3            0x1BFC  
      4            0x1BFB  
      5            0x1BFA  
      6            0x1BF9  
      7            0x1BF8  
      8            0x1BF7  
      9            0x1BF6  
      0            0x1BFF  
      Star           0x1BE2  
      Hash           0x1BE3  
      Clear          0x1BF5  
      Keyboard         0x1BA5  
      Edit           0x1BF4  
      Red           0x1BA4  
      Green          0x1BA3  
      Yellow          0x1BA2  
      Blue           0x1BA1  
    end codes  
 end remote  

On Debian...

The Debian package of lirc comes with a /etc/lirc/hardware.conf file, the Fedora install does not and just works without one. On Debian I had to also amend the hardware.conf file by amending the DRIVER & DEVICE variables to...
 DRIVER="default"  
 DEVICE="/dev/lirc0"  
This is likely to be the same for most installations but if in doubt of what your device is, look in /dev;
 ls -l /dev/lirc*  

Restart lirc

 sudo service lirc restart  

Configure XBMC

XBMC already comes with a set of key maps for remote controls via lirc in the file /usr/share/xbmc/system/Lircmap.xml. You can also have a user specific Lircmap.xml in your ~/.xbmc/userdata directory.
Here we'll put our mappings for our 'rc118' lirc remote (this name being defined in our /etc/lirc/lircd.conf file) to our user Lircmap.xml file.

In a terminal, open a new file in gedit (or your preferred text editor);
 gedit ~/.xbmc/userdata/Lircmap.xml  
Paste the following text into your new file;
 <lircmap>  
   <remote device="rc118">  
     <mypictures>PICTURES</mypictures>  
     <liveradio>RADIO</liveradio>  
     <myvideo>VIDEOS</myvideo>  
     <mymusic>MUSIC</mymusic>  
     <record>Record</record>  
     <pause>Pause</pause>  
     <stop>Stop</stop>  
     <skipminus>Previous</skipminus>  
     <play>Play</play>  
     <skipplus>Next</skipplus>  
     <reverse>Rewind</reverse>  
     <forward>Forward</forward>  
     <start>Menu</start>  
     <back>Back</back>  
     <info>Info</info>  
     <volumeplus>Vol+</volumeplus>  
     <volumeminus>Vol-</volumeminus>  
     <left>Left</left>  
     <right>Right</right>  
     <up>Up</up>  
     <down>Down</down>  
     <select>OK</select>  
     <channelplus>Chan+</channelplus>  
     <channelminus>Chan-</channelminus>  
     <mute>Mute</mute>  
     <recordedtv>Eject</recordedtv>  
     <guide>Zoomout</guide>  
     <livetv>Zoomin</livetv>  
     <menu>Select</menu>  
     <one>1</one>  
     <two>2</two>  
     <three>3</three>  
     <four>4</four>  
     <five>5</five>  
     <six>6</six>  
     <seven>7</seven>  
     <eight>8</eight>  
     <nine>9</nine>  
     <star>Star</star>  
     <zero>0</zero>  
     <hash>Hash</hash>  
     <clear>Clear</clear>  
     <teletext>Keyboard</teletext>  
     <enter>Edit</enter>  
     <red>Red</red>  
     <green>Green</green>  
     <yellow>Yellow</yellow>  
     <blue>Blue</blue>  
   </remote>  
 </lircmap>  
Save your new file.

Disable the remote's kernel driver

Now the RC118 remote is handled by lirc you have no need for the Linux kernel to handle it. To prevent XBMC from receiving input from both lirc and xinput (resulting in double key presses for those buttons that did work out of the box) you need to disable the relevant kernel module.

Unload the RC6 decoder driver with the following command;
 sudo modprobe -r ir_rc6_decoder  
To disable this driver so it's not loaded when the system is booted, blacklist it as follows;
 echo "blacklist ir_rc6_decoder" | sudo tee -a /etc/modprobe.d/ir_rc6_decoder.conf  


Now start or restart XBMC and your AIM RC118 remote works completely.

Sunday, March 24, 2013

Play Freespace 2 natively on Fedora

Was sitting here this snowy Sunday afternoon craving for a bit of good ole space sim action. After a brief flurry of searching the web for something free, recent enough to look cool and immersive and would run under Linux or Wine I was pretty disappointed to find.. not much. (Yes there's Vendetta Online but that's only free for so long). Unfortunately the epic space sim genre is not the vibrant part of the game industry it once was.

I decided to embrace the old school and dig out my copy of Freespace 2 which is meant to run perfectly under Wine according to the Wine AppDB and I remember it very fondly, well after a straight forward Wine install it didn't work on my Fedora 18 installation currently running Wine 1.5.24.
Rather than shuffling towards the drudgery of trying to get FS2 working under Wine or the even worse experience of having to exit what I had running in the background, rebooting into Windows 7 (ugh) and trying to get it working there, I noticed during my search-fest that there's a FreeSpace Source Code Project (FCSP) that is actively developing the open source, multi-platform version of the Freespace 2 binaries called FS2Open! Sometimes life just throws you a bone.

Now it should really end there, I installed the thing, used the old disks to grab the content, had a wail of a time, went and did something else. Erm... no.
As with some open-saucy type projects, the only set of end to end instructions that seems to exist for Linux is a mighty wall of links & text. Their guide is comprehensive but many links and pages are involved and so it becomes a bit of a slog.


Therefore if you're running Fedora and want to begin playing the latest open-source, upgraded FreeSpace 2 the straight forward way then I've documented my simplified, start to finish guide for Fedora 18 for you.

What's required?

To get FS2Open going you need;

The FS2Open engine

This is the open-source Freespace 2 core engine.
Project contributor 'niffiwan' has published some pre-compiled Linux binaries for a range of distros, these are available for download HERE.
You can go ahead and download the appropriate binary for you distro but if you want the latest version of FS2Open you're best just compiling from source as covered in this walkthrough.

A launcher

Launcher software is used to configure and run FS2Open.
The FCSP project's launcher download page gives the option of 3 launcher projects. The official launcher software is called wxLauncher and appears to be the most complete.
For Linux, compilation of wxLauncher from the source code is required. The source comes with build instructions but the Linux section only covers Ubuntu. This gives you little idea of what packages you need to install on Fedora to compile the sofware.

The original game media

Your 3 original Freespace 2 CDs or ISO images.

The FS2Open media enhancements

A lot of work has been done to enhance the original game's content to bring FS2 more up to date. The extra content comes in the form of game mods packaged up in additional VP files
The official download page for the latest MediaVPs is a forum post HERE.
Rather than manually download each file in the browser we'll make things a bit more straight forward later using the command-line.

Let's go..

Firstly open a new terminal.

Install the Fedora packages you'll need

 sudo yum install SDL SDL-devel python python-markdown wxGTK wxGTK-devel openal-soft openal-soft-devel cmake gcc gcc-c++ unshield subversion libvorbis-devel automake autoconf libtheora-devel readline-devel lua-devel libpng-devel libjpeg-devel  

Create game directories under your home directory

 mkdir -p ~/Games/freespace2/temp/mvp  
 mkdir ~/Games/freespace2/temp/src  
 mkdir ~/Games/freespace2/mediavps_3612  

Get the FS2Open source code

 cd ~/Games/freespace2/temp/src  
 svn checkout svn://svn.icculus.org/fs2open/trunk/fs2_open  

Compile & install the FS2Open binaries

Note: we're not doing any optimization here, just the quick and easy get-it-going approach. The full mega-guide is HERE.
 cd fs2_open  
 ./autogen.sh  
 make  
Assuming the compilation went OK copy the binary to your freespace2 directory;
 cp code/fs2_open_* ~/Games/freespace2  


Compile & install wxLauncher

Download

Download the latest source code tarball from the wxLauncher downloads page HERE. Save the file to your Downloads directory.

Unpack

 cd ~/Downloads  
 mkdir -p wxlauncher/build  
 tar -C wxlauncher -xzf wxLauncher-*.tar.gz  

Build

 cd wxlauncher/build  
 cmake -DUSE_OPENAL=1 -DCMAKE_INSTALL_PREFIX=/usr/local ../  

You should see messages confirming a successful build which looks like this;
-- Configuring done
-- Generating done
-- Build files have been written to: /home/yourname/Downloads/wxLauncher-0.9.1/build

Compile

 make  

Install

 sudo make install  


Get the game content.

The next step is to copy the original game content from the FreeSpace 2 CDs (or ISO images if you have them) to the freespace2 directory you created earlier.

Mount the game media

Clearly there are many ways to mount disk and iso images but here's the easy to describe, simple way of doing this. It assumes as you're running Fedora then you'll be running a Gnome 3 desktop, it is the best DE after all.

If you're using CDs, insert the first disk and open it in Gnome 3's file manager 'Files' when prompted.
Alternatively if you have ISO images of the CDs it is just as easy to mount them in Gnome 3, just double-click the ISO file in 'Files' and it will be automatically mounted and appear as a device. You could mount all 3 ISOs at once this way if you wish.

Whether you're using a CD or an ISO file, just hover your mouse cursor over the device to see it's path, this example shows the path of a mounted ISO file;

These paths will be the source of your data extractions.

Extract the data to your game directory

The tool 'unshield' you installed earlier is a tool for extracting files from Microsoft CAB files with InstallShield headers.
With the first disk/ISO mounted unpack data1.cab and put all '.vp' files in your game directory as follows (substituting /path/to/your/cdoriso for the actual mounted disk/ISO path);
 cd /path/to/your/cdoriso  
 unshield -j -d ~/Games/freespace2/temp x data1.cab  
 mv ~/Games/freespace2/temp/*vp ~/Games/freespace2  
For disk/ISO 2 the required vp files are just in the root of the disk, so mount disk/ISO 2 and copy them directly;
 cd /path/to/your/cdoriso  
 cp *vp ~/Games/freespace2  
... and lastly mount CD/ISO 3, like you did with disk 2 copy the vp files directly from it's path to the game directory;
 cd /path/to/your/cdoriso  
 cp *vp ~/Games/freespace2  


Implementing the game enhancements (MediaVPs)

Download the files

The available MediaVPs are packaged up in a number of separate ZIP files.
Download them to your ~/Games/freespace2/temp/mvp directory and unpack them. All together this is a 1.2GB download.
There are cleverer ways to process this list of downloads but the following list of commands requires less explanation here. You can just copy the list of commands and paste into your terminal to perform them in a batch.
 cd ~/Games/freespace2/temp/mvp  
 wget http://mvp.fsmods.net/3612/MediaVPs_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_Root_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_Root_Update.zip  
 wget http://mvp.fsmods.net/3612/MV_Music_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_Assets_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_Assets_Update.zip  
 wget http://mvp.fsmods.net/3612/MV_Effects_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_Effects_Update.zip  
 wget http://mvp.fsmods.net/3612/MV_Advanced_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_AnimGlows_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_RadarIcons_3612.zip  
 wget http://mvp.fsmods.net/3612/MV_CB_ANI_1.zip  
 wget http://mvp.fsmods.net/3612/MV_CB_ANI_2.zip  
A few of these file are optional but we're going full fat here.

Unzip the files

 unzip '*.zip'  

Place the VP files in their own subdirectory which you created earlier.

 mv *vp ~/Games/freespace2/mediavps_3612/  
 mv mediavps_3612/* ~/Games/freespace2/mediavps_3612  
 mv MediaVPS_3612/* ~/Games/freespace2/mediavps_3612  


Running and setting up FS2Open

Now, still in the terminal run wxlauncher;
 wxlauncher  
You'll be presented with something like this;

Nice!

Mods

Select the 'Mods' tab.
Select the MediaVps mod and select the [Activate] button.

Basic Settings

Select the 'Basic Settings' tab.
Select the browse button to set the Game Root Folder to /home/yourname/Games/freespace2.
Select the Refresh button and pick the available FS2 Open executable option.
Once you've picked the executable the video and audio settings should be picked up automatically.
If you have your joystick or gamepad plugged in, select it in the Joystick drop-down.

Advanced Settings

Select the 'Advanced Settings' tab, here's where you can experiment with the many settings available with FS2 Open.
As a starter set the Lighting Presets to 'Baseline Recommended' and the Flag Sets to 'High Memory usage features on'.

Then select/enable the following options;
Graphics section
  • Apply Lighting to Missiles
  • Enable 3D shockwaves
  • Enable Post-processing
  • Enable soft particles
  • Enable FXAA anti-aliasing
HUD section
  • Enable 3D radar
Gameplay section
  • Enable 3D warp
  • Enable flash upon warp
  • Enable 3D models for ship selection
  • Enable 3D models for weapons selection
Audio section
  • Preload mission game sounds






Finally...

There are many user-made mods available that continue the Freespace saga as well as introduce additional stories & universes including Babylon 5 and BSG. Check out the highlights panel on wxlauncher's Welcome tab, the Freespace Wiki and the project's list of user-made campaigns and total conversions list for more details on what's available.

Before you do, don't forget your joystick, hit the Play button and get stuck in...


This should at least see me through until the release of Star Citizen.

Sunday, August 09, 2009

Make Fedora 11 unlock your Gnome keyring automatically upon login.

I love Fedora 11, it's so clean and doesn't have the crushing Intel graphics driver bugs present in Ubuntu 9.04. However one bug/feature that is really annoying is that you are made to unlock the Gnome keyring manually whenever an application attempts to access your keyring for stored credentials.
For instance if your network connection is a wireless connection using WEP/WPA encryption, the Network Manager application cannot connect after you login until you've typed in your Gnome keyring password, most annoying.

It is possible to make your Gnome keyring unlock automagically after login using the tool pam-keyring-tool.

Firstly it's often recommended that you delete your current keyrings. I don't think this is necessary as such but if you find this solution doesn't work then delete the keyrings in a terminal as follows;
 rm -f ~/.gnome2/keyrings/*  

Then in your Gnome desktop browse to System > Preferences > Startup Applications.
Select the [Add] button.
Enter the name as something meaningful such as GNOME Keyring Unlock
Enter the following in the command field;
 cat ~/.keypass | /usr/libexec/pam-keyring-tool --unlock --keyring=default -s  

Then select the [Add] button.

Finally you'll need to put your account's password in a file in your home directory..

 echo "yourpassword" > ~/.keypass  

...and set some secure permissions on the file...
 chmod 400 ~/.keypass  

Finished.

Now logout and log back in, you'll no longer be nagged to unlock your keyring.
If you deleted your default keyring file earlier, you'll have to re-enter your previously stored passwords and keys (such as your WEP/WPA key) when prompted.

Monday, February 16, 2009

Creating a local Yum repository from a DVD ISO (Fedora 10)

Someone approached me in work today with a problem, he had installed Fedora 10 in a virtual machine on our VMWare ESX server as he wanted to experiment with an Apache web server on a Linux host, however he had installed Fedora but not chosen to install the web server during the installation process and he has little experience using Linux.
He did have the the ISO file mounted as the virtual machine's DVD drive but for some reason he couldn't get the ISO file onto the Fedora virtual machine's filesystem.
The VMWare ESX server hosting the virtual machine does not have internet access, so how does he install the web server from the DVD with no internet access and no ISO file in the virtual machine's filesystem?
He approached me with a couple of printed guides he'd found on Google to ask me which one was the best approach. They were terrible, taking up pages of A4 so I knocked up the following for him...

Create and mount the ISO file 
As Fedora automounts the DVD device (/dev/sr0 under VMWare) as "/media/Fedora 10 i386 DVD" or similar we need to mount the ISO under a different mount point with no spaces in the path name, as YUM cannot support repository paths with spaces in their names.
Also as the virtual machine is not likely to ever have internet access, it'll be preferable to mount the ISO permanently as the sole active repository.
Switch user to root;
 su -  
Create the ISO file;
 dd if=/dev/sr0 of=/opt/f10dvd.iso  
 chmod 444 /opt/f10dvd.iso  
Mount the ISO file;
 mkdir /mnt/f10iso  
 echo "/opt/f10dvd.iso /mnt/f10iso iso9660 ro,auto,loop 0 0" >> /etc/fstab  
 mount /mnt/f10iso  
Setup YUM
Edit /etc/yum.conf with nano or vi.
 nano /etc/yum.conf  
Add the following lines add onto the end of the file;
 [f10iso]  
 name=local-repo  
 baseurl=file:///mnt/f10iso/  
 enabled=1  
 gpgcheck=0  
Disable the default YUM repositories
 yum repolist --disablerepo=fedora --disablerepo=updates  
Update YUM
 yum update  
You are now ready to use YUM and/or pirut or packagekit to search and install packages from the Fedora DVD ISO.
However if you setup a Fedora/Red Hat system as above and then want to start using external repositories over the internet you must disable this local repository and not use it again, otherwise you may experience some dependency problems.

Therefore if you finally get internet access on your system and you need to get YUM setup back the way it was just run the following as root...

 yum repolist --disablerepo=f10iso --enablerepo=fedora --enablerepo=updates  

Thursday, September 20, 2007

Running the QW:ET Demo on Fedora 7

Now one really cool thing that I gotta share has pretty much occupied my whole day today, and with damn good reason too.
The Quake Wars: Enemy Territory demo was released recently to much excitement and draining of bandwidth across file repository sites around the globe, I too downloaded the file and eagerly waited for the download to finish.

Now I only use Linux on my computers. I choose to not allow a certain very well known, bloated, overpriced, featureless trojan-horse of an operating system anywhere near them as I prefer my PCs to be fast, secure, stable and also include a lot of cool, leading edge stuff to play with.
There are many other reasons why I use open source software, I'm sure they'll ooze out in future posts but not today.

Therefore I had my fingers crossed hoping that this demo would work on my Fedora desktop.
I first tried Cedega as I pay for the thing (God knows why!) it didn't even install!
I installed Wine from the Fedora repositories, QW:ET installed OK and I sorted out a few other bits and bobs but the demo Didn't run :(
QW:ET came back with something along the lines of a 'Display must support 32bpp colours' message. Damn! X only supports 24bit. I walked away defeated.

Today I stumbled across an brill little how-to on the QW:ET forum which was a little collection of links & tips gathered by stoic_ails over at the forum. The original how-to can be found over at http://community.enemyterritory.com/forums/showthread.php?t=9115.
Therefore I do not take credit for this info, all I have done is correct & expand the odd bit here & there and stick it all in nice bloggy format for all to hail mightily so here goes.

Preparation
Firstly I got rid of my Yum installed Wine (0.9.42) installation as this did not have the patches required to get round the 32bit display message.

UPDATE
Wine 0.9.46 is now in many distro's repositories which works OK with the QW:ET demo without patching.

Therefore if you have Wine 0.9.46 or later from your package manager you don't have to compile Wine yourself anymore and you can skip steps 1-9c and kick off from step 10a.


I logged in as root, entered the root password and removed wine using yum;
su -
yum remove wine

If you are using a different distribution, maybe one of those crazy Debian based affairs, you may want to remove Wine as follows;
sudo apt-get remove wine

Then I was ready to go...
Do everything by the book and you'll be rocking the QW:ET with the rest of us. Until the native Linux version of the full game is released around the end of October.

I already had the Nvidia binary Linux drivers installed on my system and I assume that your system also has 3D acceleration enabled, the process of installing proprietory graphics drivers is not covered here.
If you're expecting to run QW:ET without any 3D acceleration then you are proper silly.


Oh yeah of course, download the QW:ET demo as well. I got it from Filefront.com as the downloads are fast with no queues and no registration required. Download link below.
Enemy Territory: QUAKE Wars PC Demo

The How-To
1. Get the latest wine source; in this case 0.9.44: http://prdownloads.sourceforge.net/w...0.9.44.tar.bz2

2a. In your home directory, make a directory called wine
mkdir ~/wine

2b. Copy the archive to the new directory ~/wine :
cp wine-0.9.44.tar.bz2 ~/wine/

3. Change to that directory:
cd ~/wine/

3. Unpack the archive:
tar xvfj wine-0.9.44.tar.bz2

4a. Open http://bugs.winehq.org/attachment.cg...39&action=view and copy it (ctrl+a & ctrl+c) into a file called patch1.

4b. Open http://bugs.winehq.org/attachment.cg...49&action=view and copy it (ctrl+a & ctrl+c) into a file called patch2.

4c. Change directory to where you've saved the patch1 & patch2 files too, maybe your desktop for example.
cd ~/Desktop

5a. Copy patch1 to the wine source directory:
cp patch1 ~/wine/wine-0.9.44/

5b. Copy patch2 to the wine source directory:
cp patch2 ~/wine/wine-0.9.44/

6. Change to the wine source directory:
cd ~/wine/wine-0.9.44/

6a. Patch the wine source:
patch -p1 < patch1

6b. Patch the wine source:
patch -p1 < patch2

7a. Run configure:
./configure

7b. If configure complains about missing packages, stop here and install the missing packages...
For those using Debian/Ubuntu/Linux Mint/etc. it'd go something like:
sudo apt-get install flex bison fontforge

For those very sensible lot running Fedora/Red Hat type distros:
su -
yum install
fontforge
exit

...and run ./configure again.


7c. Go ahead when configure finished successfully.

8a. Run the following command:
make depend && make

8b. Wait and hope that there's no errors.

8c. Go ahead when make finished successfully.

9a. Change to user root:

su

9b. Run:
make install

9c. When the install has finished, exit from root:
exit

10a. Run:
regedit

10b. Go to HKEY_CURRENT_USER/Software/Wine/

10c. Add the key X11 Driver

10d. Add the string ScreenDepth with the value 32 (Screenshot)

11. Download http://tacticalsites.com/~lorian/fil...stem32.tar.bz2

12. Copy the archive to your wine system32 directory:

cp system32.tar.bz2 ~/.wine/drive_c/windows/system32/

13. Change to that directory:
cd ~/.wine/drive_c/windows/system32/

14a. Unpack the archive:
tar xfvj system32.tar.bz2

15a. Run:
winecfg

15b. Set the windows version to Windows XP (Screenshot)

15c. Go to libraries and set wtsapi32 to Native (Windows) (Screenshot)


16a. Install the ET:QW Demo:
wine ETQuakeWarsDemoSetup.exe

16b. There might be some complaints, just click 'ok' :P

17. Download http://tacticalsites.com/~lorian/fil...st_x86.exe.bz2

18. Unpack it:
bunzip2 vcredist_x86.exe.bz2

19. Run:
wine vcredist_x86.exe

20. Check that msvcr80.dll, Microsoft.VC80.CRT.manifest and Microsoft.Windows.Common-Controls.manifest are neither in the system32, nor in the game directory. If they are, delete them.

21. Change to your ET:QW Demo installation, e.g.:

cd ~/.wine/drive_c/Program\ Files/id\ Software/Enemy\ Territory\ -\ QUAKE\ Wars\ Demo/
(notice any spaces in directory names have to be preceded with a backslash)

22. You can start ET:QW Demo like this:
nice -n19 wineserver && wine etqw.exe
(This way, wineserver won't use too much CPU time)
Or you can be all gung-ho like me and have a launcher icon that runs:
env WINEPREFIX="/home/vin/.wine" wine "C:\Program Files\id Software\Enemy Territory - QUAKE Wars Demo\etqw.exe"

23. Before joining a game, the mouse can behave weird in the menu. But after joining it's just fine, like the whole game.

24. You can now clean up and get rid of the ~/wine directory if you want:
rm -rf ~/wine



The Results
The guy who originally wrote this how-to also pointed out that he found that QW:ET running under Wine on Linux was actually performing better for him that under Windows XP & Windows Vista on a similar spec PC. I don't really find this surprising as I have seen similar comparisons with other games which had similar outcomes, especially against Vista as it's a dog.

When I got round to toying with the graphics settings I found that just sticking the detail on 'High' prevented the level from loading, so I chose the 'Custom' settings and set most of rendering details to "High", the Anti-Aliasing could not be enabled. I'd put that down possibly to the version of the DirectX API under Wine.

Anyway that's not really a problem as it looked fantastic at 1280x1024 resolution and I was seeing frame-rates between 30-40+ FPS on my system during online gameplay with 31 other players together with all the high-end weather, plants, 'soft particle' effects and all that fancy stuff which simply looks fantastic.
Punkbuster doesn't work so I just filtered out the punkbuster servers out of the server list, no biggy.


My system?
Fedora 7
Intel Core 2 Duo 2.33 GHz
1GB DDR2 PC8500+ RAM (1066Mhz)
Nvidia GeForce 7600GS PCIe 16x
Nvidia HD 7.1 sound


Kill ya later...