Armageddon is an addon for Hearts of Iron II: Doomsday. When installed from the anthology, it installs as an entirely separate folder as a standalone game.
Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results (selected in 'Test Results' table below)
What works
Installing.
Single-player.
Sound.
What does not
Nothing.
What was not tested
Multiplayer.
Scenario editor.
Third party modifications.
Additional Comments
The only problem I have is when I initially start the game, the intro cinematic window is spawned, but not is not focused properly. The solution is to simply switch window.
Would probably give it platinum if it wasn't for the alt-tab annoyance, and due to the fact that I can't test Multiplayer properly (no servers found).
I had no problems with the music or sound in general.
To install the game, Hearts of Iron Anthology users may need to run the setup.exe file directly from the CD rather than clicking the link.
After installing, disable movies by renaming the avi folder.
To play multiplayer, you will have to install native DirectPlay. See http://wiki.winehq.org/DirectPlayGames
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
Crashes in singleplayer
by Jon Severinsson on Monday December 8th 2008, 14:32
After installing the game (and DirectPlay DLLs) it seemed to work just fine, music and all, in both singleplayer and multiplayer. However, after playing a few years in singleplayer it started to crash randomly. When playing the 1936 scenario the crashes began about 1940, but the further into the game I get the more frequent they become, and by 1947 it crashes multiple times per month (though occasionaly it may run a few months with no crash). After loading a savegame the crash never occurs on the exact same date (even if I do absolutely nothing but let the game run), but sooner or later it happens again.
So far no multiplayer (LAN) game has crashed for me, but then we've not gotten any farther than 1941 in that, so that may just be a matter of time...
Relevant parts of the console output posted at pastebin.ca/1280032 The memory address is always either 0x000007a8 or 0x00000000, but all other hex codes varies from crash to crash. If anyone has any idea what is going on or what to do about it, I would be very grateful for your input.
