my game doesn't crash after 125 turns. I crushed my enemy in about 180 turns.

The memory error is the thing that really wrecks this wonderful game. I am surprised that Interplay never fixed it and I've been wishing for many years now that someone would eventually do something about it.

What are your DOSbox settings? I give the game a full 63 MB ram and I've made it past round 125 with no crashes.

Over on Linux Game Tome [source of open source gaming] I saw a post about a project which involves MAX. It possibly might have fixed this problem though I am not entirely certain.
OH and link is possibly >>TIS??>>[url=]http://happypenguin.org/show?M.A.X.%20Reloaded[/url]
Regardless, CDP still rocks and GOG is TE PLACE TO BE!

You actually can use the GOG version. The MAXR installer just wants to know where the files for the original are located. Point the installer at the GOG folder where MAX is and it installs and plays.

I havn't tryed the gog-version throughly enough to see this bug.

But I remeber it crashing from time to time (round about every 100 turns), even on a real MS-DOS machine. And sometimes CPU-Players never ended their turn. Not a real big problem when you save the game frequently enough (not sure if the autosave always did the trick).


I've just started playing the gog-version of MAX2 in turn-based mode, and feel that from time to time, units get more or less random orders, triggerd either by end of turn or sometimes by selecting some unit. For example, 2 tanks of mine standing there a couple of turns near a group of CPU-units. Then, suddenly, on end of turn, one of the tanks starts an attak, moving into the group of CPU units, as if the command came from a multiturn-command.

Has anyone ssen the same problem? Or is it just me being confused by some of the changes made in MAX2 compared to MAX?

Some source of unpredictable behaviour in MAX2 seems to be the use of rectangular Multi-Unit selections. Immediately after using Multi-Unit selections, I've seen:

* one unit getting nearly infinate movemt points (an AWAC was able to move over the complete map multiple times within a single turn)

* more frequently unexpected unit actions

* crashes similar to those known from MAX1 (CPU turns didn't end)

Looks like the algorithm to handle Multiunit selections probably somehow corrupts the game memory.

I noticed this too.