I loaded up Dosbox .72 and installed M.A.X.
It plays fine (a bit jerky during later 'rounds'). Sound is fine. During the beginning of the game when there isn't much construction, it runs fine.
Playing a long game, around turn 200, M.A.X. crashes totally with a STACK OVERLOAD error. It does it every time. I have no idea why...
Anyone have any help?
If I recall correctly, that was MAX's natural behavior at times. Save and reload might help. By the way, I've been looking for Western Hemispheric residents to play. If you're interested...
wrote:If I recall correctly, that was MAX's natural behavior at times. Save and reload might help. By the way, I've been looking for Western Hemispheric residents to play. If you're interested...
Save and reload only gives the same stack overload error.
tried a fixed cycle count instead of auto ?
(e.g 5000)
Water flows down the stream
How to ask questions the smart way!
Have you tried loadfix?
wrote:tried a fixed cycle count instead of auto ?
(e.g 5000)
Changing the cycle rate to anything but AUTO or MAX and the game doesn't run at all... (is really at the end of my rope here...)
wrote:Have you tried loadfix?
No, and I have no idea what it is or how to use it... can you explain?
wrote:Have you tried loadfix?
I did a google on loadfix (found out what and how), loaded it, and voila... crash... stack overload.
Here is my config:
fullscreen=false
fulldouble=false
fullresolution=original
windowresolution=original
output=surface
autolock=true
sensitivity=100
waitonerror=true
priority=higher,normal
mapperfile=mapper.txt
usescancodes=true
language=
machine=vga
captures=capture
frameskip=0
aspect=false
scaler=none
core=auto
cycles=auto
cycleup=500
cycledown=20
nosound=false
rate=22050
blocksize=2048
prebuffer=10
mpu401=intelligent
device=default
config=
sbtype=sb16
sbbase=220
irq=7
dma=1
hdma=5
mixer=true
oplmode=auto
oplrate=22050
gus=true
gusrate=22050
gusbase=240
irq1=5
irq2=5
dma1=3
dma2=3
ultradir=C:\ULTRASND
pcspeaker=true
pcrate=22050
tandy=auto
tandyrate=22050
disney=true
joysticktype=auto
timed=true
autofire=false
swap34=false
buttonwrap=true
serial1=dummy
serial2=dummy
serial3=disabled
serial4=disabled
xms=true
ems=true
umb=true
keyboardlayout=none
ipx=false
mount e e:\ -t cdrom
mount c c:\intrplay\
loadfix c:\intrplay\max
IMO, this is a bug native to MAX and not a DosBox issue at all. I remember it happening to me back in the day. You might try restarting the mission altogether and yes, I do know how long it takes to run 200+ turns in a game.
I'm having a problem with MAX as well, although I don't think it's stack overflows. The game just gets really sluggish later on and it's really annoying. I know it wasn't like this originally back when DOS was native to Windows. Is there something I can do to reduce or even get rid of the sluggishness at all?
Sorry for hijacking your thread but theres no point in making a new one about the same thing.
I have a problem too... i cant get it work with ipx....
When ever i start multiplayer and choose host it crashes after a while... but when i chose to join game, menu comes up and doesnt crash. i tried this on 2 comps and cant do anything... any help?
Edit: I got 1.04 version.
