Army Builder is used for creating rosters for miniature games, automatically checking them for errors, displaying vital information about it and it's components.
What does not
What was not tested
Actual running of the program as it would not run after installation.
Get the following page fault when trying to run Army Builder after a successful installation: wine: Unhandled page fault on read access to 0x00000004 at address 0x504f75 (thread 001a), starting debugger... Unhandled exception: page fault on read access to 0x00000004 in 32-bit code (0x00504f75). I'm not going to post the rest of the dump, but maybe that'll help someone want to take a look at it...
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Ubuntu 8.10 "Intrepid" i386 (+ variants like Kubuntu)||Feb 28 2009||1.1.14||Yes||No||Garbage||an anonymous user|
|Show||Gentoo Linux||Jul 25 2008||1.1.0||Yes||No||Garbage||an anonymous user|
|Show||openSUSE 11.0||Jun 06 2008||1.0-rc3||Yes||Yes||Silver||Heine Salte|
|Show||Ubuntu 8.04 "Hardy" amd64 (+ variants like Kubuntu)||May 30 2008||1.0-rc2||Yes||No||Garbage||Scott Ritchie|
|Show||openSUSE 10.3||Apr 17 2008||0.9.59.||Yes||No||Garbage||Heine Salte|
Unfortunately, Army Builder (AB) doesn't run with standard Wine binaries, as a bug prevents anything but the splash screen from loading. However, there is a patch to the Wine source available that fixes this issue. However, the patch isn't yet included in the main source tree, as there are apparently other issues with this patch on other applications. However, I haven't noticed anything other than another bug that prevents the mouse from clicking on the buttons in the applications. What? I hear you say, how can I then use AB? Well, it is a bit cumbersome, but it works for me, and I'd rather use this method and get my snazzy AB3.1c running than using old AB2.2.
The mouse pointer can't click the buttons, but they get focus, so a simple press of the Enter key activates the button. So, press with pointer, press Enter, a small extra step, but if you feel it's not worth it, either use 2.2 or wait for someone to fix this issue as well, if not, read on intrepid adventurer :)
patch -p1 < filename_of-patch
./configureNow, you must decide if you want this wine to live where it normally does in your distro, and first uninstall any wine package you may have installed there before you do this, or if like me, you like to have this "testing" version in, say, /opt. If so, you can add a "--prefix=/opt/wine" to the configure script, and it will safely tuck itself away there, letting you keep the original version as it is.
make installThis step has to be done as root, as you install the files to your desired location.
There, you should be all set, remember to call the right wine version if you installed it in /opt, and enjoy AB3.1c
If there are any problems with this HOWTO (my first), please contact me and we'll work out any problems.