Star Trek: Armada II

Armada II w/ patch

Application Details:

Version: 1.1
Votes: 1
Latest Rating: Silver
Latest Wine Version Tested: 1.7.40

Maintainers: About Maintainership

Test Results

Old test results
The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results

What works

Single Player, Instant Action, Opening videos.

What does not



What was not tested

Campaigns to completion.

Hardware tested


  • GPU:
  • Driver:

Additional Comments

MUST be run in windowed mode or in a virtual desktop! 1.1 patch acted kinda stupid and was difficult to install, however this may only be my copy of the patch, others may not experience difficulty installing the patch.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
CurrentUbuntu 14.04 "Trusty" amd64 (+ variants like Kubuntu)Apr 12 20151.7.40Yes Yes SilverSweettheSour 
ShowUbuntu 12.04 "Precise" i386 (+ variants like Kubuntu)Oct 22 20121.4Yes Yes Silveran anonymous user 
ShowUbuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)Aug 08 20121.4Yes Yes SilverMPW 
ShowGentoo Linux x86_64Dec 03 20111.3.34Yes Yes Silverejwaxx 
ShowMac OS X 10.6 "Snow Leopard"Feb 28 20111.3.14Yes Yes PlatinumBojan Antonović 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

use winetricks vcrun6
As long as this dependency exists, according to rating can be at most gold, because vcrun6 is third party software.
Please make sure to upgrade to the newest version of wine before playing this game. Star Trek Armada 2 is known to be playable under wine (>.9.50)


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

by MPW on Thursday August 9th 2012, 11:12

I manged to fix the Version check for the multiplayer with this:

I got the S.T.A.L.K.E.R. multiplayer beta (probably the full game too) to work
with native dplay dlls. Do this (on a clean system):

- download DirectX runtime (do NOT use dlls from a windows partition):
- run the executable and select a folder to extract to
- extract using cabextract
- copy dp* from the .cab archive to windows/system32
- override dlls with winecfg: dplay,dplayx,dpnaddr,dpnet,dpnhpast,dpnlobby
- register dlls: for f in dplayx.dll dpnet.dll dpnhpast.dll dpnhupnp.dll
dpvacm.dll dpvoice.dll dpvvox.dll; do wine regsvr32 $f; done

(copied from here:

But when creating or joining a network game, Armada 2 tells me that it can't connect over TCP/IP to the LAN.

The console outputs: fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
by MPW on Wednesday August 8th 2012, 8:41

as Unity (Window Manager of Ubuntu) catches the alt-key, u can use strg+alt to activate warp :)
Highest rating gold?
by Alex on Saturday February 19th 2011, 16:20
I did not install any third party stuff using winetricks or something. Just wine and the game.
RE: Highest rating gold?
by Bojan Antonović on Saturday February 19th 2011, 17:04
"Star Trek Armada II Fleet Operations" needs additional stuff. And I know I was sloppy about some dlls for some applications.

I will retest everything when I have time and rebuild my Parallels 6 image with OpenSuse 11.3.
Sound issues under Ubuntu Maverick
by ejwaxx on Sunday January 30th 2011, 22:02
I've been away from Armada 2 for some time: the last time I played was with Ubuntu 9.10, and the game ran perfectly under Wine. I don't remember the precise revisions, but it was in the 1.1 series, probably between the high 30s up to the 1.2 release candidates, but I had no issues whatsoever. I've been trying to reinstall today under Ubuntu 10.10, and the sound is being quite peculiar.

Under the latest Wine release (1.3.12), I have perfect sound through the opening screens until the main menu, at which the sound drops out entirely. Even replaying the intro movie (which plays fine on launching the game) is without sound past this point. Despite numerous attempts to relaunch the game, this is the status quo.

Remembering that I'd been able to launch the game in the past, I immediately began regression testing, but once regression testing yielded a "bad" commit as a d3dx9 patch in 1.1.44, I suspected something was wrong with my process.

It turns out that the issue isn't a regression per se (that I can find), but rather is sporadic: some launches have functional sound, and others do not. The likelihood of functional sound seems related to the Wine revision: I've tested back as far as 1.1.10 (which reliably works), up to 1.3.12 (which reliably does not). I attempted a "best of 7" bisect -- a revision is "good" if the sound works in the best of 7 trials -- which ended up at commit 94dbeeb0adbad71d5126ec40f25a6062d2551b10, which based on my limited knowledge of programming in general and Wine in particular, is just as unlikely to be the source of the problem.

I'm at wit's end here. I'm hesitant to file a Wine bug without backup evidence, because it's been my experience that according to the Wine team it's *always* a bug elsewhere, and in this case that makes sense, since I had precisely zero issues with the same Wine revisions under 9.10. Any ideas?
by blablabloblo on Tuesday November 17th 2009, 4:19
The shortcuts just didn't work for me, because kde had a use for ALT + mouse-1.
Deactivating the shortcuts of your window-manager, should fix this problem (did for me).