For those of you having the crash when the game gets up there in turn numbers, I seem to have fixed it for my dad. If you go into the game's folder, you'll see a called "dosboxMAX1.conf"
Default Path:
C:/Program Files/GOG.com/MAX1 and 2/MAX/dosboxMAX1.conf
Open this file up in notepad, and under the second heading or so, you'll see 'memsize=16'. Changing this to 'memsize=32' seems to have fixed it for us; your results may vary.
memsize=16
change to:
memsize=32
If this works for you, please post here. If not, I'd also like to know about it :)
-Tel

This was one of the first things I tried back in 2007 when I was fiddling around with all kinds of DOSBox settings and it did not work for me at least. But I did not have the GOG version and instead made the changes to the main dosbox.conf file.

Tried that, gave me an extra turn, and then crashed again
gave it 64 MB and got another turn
will try 128MB.... standby for updates...

I jumped straight for 128mb as the setting and so far no problems going over the limit (where before it would crash on me). I will try to get a few more games in to test this.
If we can get a few more to test this out and see how different people fair with it then it could be a good solution to the problem (At least for some uses) and GoG could even patch it into the game - 128mb should be easily usable by most modern computers - older ones being used to run the game might suffer, but I am not sure. IT could be made an optional part with a short macro to control the on/off aspect of it in an out of game menu (for those on older systems who don't want/know how to edit the files themselves)

Maybe we can ask GOG can update their dosbox.conf file?..

I tried this fix and ended up setting it pretty high, 128mb. But I still get crashes around turn 150.

I sure wish gog would fix this, as I'm not savvy enough to attempt the other fixes listed in the forum.

thing is, the memory crash is not the fault of dosbox or gog. back in 1999, when i first played the game on my intel 486, it crashed. and today in 2010 when i play it on my quadcore in a dosbox, it crashes exactly the same way.

i am in turn 114 and it crashes at every beginning of a turn. it is able to autosave before, but this completely kills the fun out of the game.

i still hope i missed something back then and now. there are people who say the game does not crash on them.

Sounds like a memory leak. If it is, would require a bunch of debugging to find.

You can test that - Open Task Manager (ctrl-alt-delete), open the process list. Sort it alphabetically; find DOSBox (at this point, M.A.X. should be running. Check how much memory it's using. If it starts small and suddenly shoots up, it's a memory problem and the most common is a memory leak. Could also be stuck in an allocation loop.

Beyond that - Bug GoG to fix it, I guess. Or hope for/work on an unofficial patch.

when i increase memory size over 16, dosbox crashes. I tried 32 and it crashed. Any clue why?

Running 400 turn games here fine (no patch installed) without problems anymore, but for safety you always have to use CTRL+S to save the game every turn before ending the turn, don't trust the auto save LOL

Only modification is using 40000 cycles fixed and putting memory to 63MB as in Carmageddon. Nothing else. The -t cdrom thing is important too.

mount d: d:\ -t cdrom
mount c: r:\jogos\max1
c:
cd max
max

My dosbox CONF file here:
http://www.mediafire.com/view/?l6yit63e3lvumet

Tried this in windows7 64-bit. Doesn't work for long, regardless of what value you choose.
It's a memory leak; this only buys you some time. Pile on a few more turns and it crashes again.
This is not a user-serviceable part. It needs to get fixed by an actual GoG programmer. You know, that convenience and reliability we're paying them for, instead of grabbing this off Abandonia or some torrent?

Does CPU temperature effect game performance in the M.A.X. series?

No.

Or for the long version: While technically speaking, the CPU temperature can affect the performance of any and all process being processed by the processor, the game is so old, and therefore so light by today's standards, that in any computer from the last decade and a half, the difference would be so small to be completely negligible to the point that I would doubt even another computer could notice the difference, let alone someone with human reaction speed.

Well, at least unless the CPU temperature goes so high it crashes the whole computer, but that's obviously a completely different issue.

Thanks for the reply!
:)
Yeah, I agree. Running a pc game like M.A.X./M.A.X.2 on today's processors (even a low end notebook) is akin to running Minesweeper from your desktop.

Solution doesnt work for me... game crashes around turn 150. Even with 128 memory.

Win7 64-bit. Relativly new Computer
Any other ideas?