WineHQ

Heroes of Might and Magic III

All versions (2.0-2.2) of the first expansion pack.

Application Details:

Version: Armageddon's Blade: 2.x
License: Retail
URL:  
Votes: 1
Latest Rating: Gold
Latest Wine Version Tested: 1.1.8

Maintainers: About Maintainership

Link Download patch 2.0-2.2 Link Download other patches Link New maps

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

single player game (single map, campaign, random map), hotseat multiplayer, map editor

What does not

-

Workarounds

What was not tested

multiplayer except hotseat

Hardware tested

Graphics:

  • GPU:
  • Driver:

Additional Comments

Russian version from Buka Entertainment. Fullscreen mode doesn't work with NVidia x86 linux v. 169.07 drivers. With 100.14 everything works perfect

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
Workaround?
RatingSubmitter
ShowUbuntu 8.04 "Hardy" i386 (+ variants like Kubuntu)Nov 15 20081.1.8Yes Yes Goldan anonymous user 
ShowFreeBSD 7.0Nov 20 20081.1.7Yes Yes Goldan anonymous user 
ShowUbuntu 8.04 "Hardy" amd64 (+ variants like Kubuntu)Aug 04 20081.1.2Yes Yes GoldZhenya 
ShowUbuntu 7.10 "Gutsy" amd64 (+ variants like Kubuntu)Apr 05 20080.9.58.Yes Yes GoldZhenya 
CurrentSlackware 12.0Jan 02 20080.9.49.Yes Yes Goldaffect 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

HOWTO

Multiplayer
To get multiplayer working, you need native directplay dlls. The old howto had a link pointing to outdated directplay dlls which cause problems with wine and generally don't work as expected. However with the latest dplay from DirectX 9.0c multiplayer is (almost - see note for details) flawless.
In the wine wiki is described how to get native direct play dlls.
Personally I would recommend using winetricks directplay which installs dplay dlls and sets overwrite in winecfg, however you may choose do install manually those files in which case you need to:

  1. Place the following dplayx.dll, dpnet.dll, dpnhpast.dll, dpwockx.dll, dplaysvr.exe in your .wine/drive_c/windows/system32
  2. Set those files to overwrite (native, builtin) in winecfg

NOTES: The game always freezes when exiting a multiplayer game.
Sometimes when you host a TCP/IP game, no one is able to connect (any client trying receives an "IP address not found" error.) In this case just rehost and the problem will be gone.

 

HOWTO

Upgrade to the latest version to avoid the copy protection.

Fixing performance problems
If you encounter performance problems (lagging sound or slow animation), try changing HKEY_CURRENT_USER\Software\Wine\Direct3D\DirectDrawRenderer key value from gdi to opengl. For additional info check this page http://wiki.winehq.org/UsefulRegistryKeys
NOTE: Heroes3HD and HD+

You can now play Heroes 3 in HD, utilizing the full size of your screen, thanks to Heroes3HD mod. It doesn't change anything gameplay wise.

With recent Wine releases, Wine prefixes are set to Windows 7. Currently, it causes rendering issues when HD or HD+ mod are installed.

Running winecfg and setting the Windows version to Windows XP solves the rendering issues.

Comments

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

upgraded wine and still crashes
by Geoffrey Lee-Dadswell on Sunday June 21st 2009, 14:24
I've upgraded so I am now running

family@aragorngardens:~/.wine/drive_c/Program Files/3DO/Heroes3$ wine --version
wine-1.1.7

I installed Armageddon's Blade and it complained about the wrong DivX version and then gave a small window saying

2. A small window, labeled PMInfo popped up reporting:
"DDE Additem Failed"

When I ran it from command line I got

wine: Unhandled page fault on read access to 0xe35eef12 at address 0x40aae2 (thread 003b), starting debugger...
Unhandled exception: page fault on read access to 0xe35eef12 in 32-bit code (0x0040aae2).
Register dump:

...followed by a large register dump.

When I submitted a similar crash to this last time my post was deleted with the explanation "No logs!" Was that because I'd included the register dump and so the post was very long?

Thanks,
Geoff
Back