edit: forgot to add, im running version 0.72

Please upgrade.

First of all you should get latest DOSBox 0.73 from DOSBox website.

Then, you should try experimenting with different cpu cores (see the readme).

Updated, and it still crashes after combat.
Been reading the README and i think i will do some changes in the cpu settings.. If i could find the config file? =o
As core=dynamic
and cycles=max
In 0.72 there was a conf file in the folder but there doesnt seem to be one now with 0.73?

Done some changes, and the crashmessage (some of it atleast):
DOS/4GW error (2001): exception 0Eh (page fault) at 238:100D1681
TS32: prev_tsf32 52A0
xxx
xxx
(alot of codes following, then finally the msg ends with:)
Crash address (unrelocated) = 1:00088681

Should i try to change some memory usage/sounds?... guess i should mention im already far out of my league with computer usage.. =/

try loadfix

tried loadfix.. crash still there.

Also tried to change the following:
fixed cycles (23300)
ems=false
xms=false
(no idea what it does but the game seemed alot slower afterwards)
But the crash was still there..

Turned off all the sound from the game menu, and the crash thats been haunting me today seems to be gone. Guess it might return later on but for now it seems to work.

Changed cycles back to max and set ems/xms back to true.

Is there a way to tell the game about your sound hardware? Games will often crash if their sound settings don't match what DOSBox is set to emulate.

I vaguely recall having an issue with sound back in the ~95 when i played it. And i think there was a setup reachable from the folder where you installed the game. Not sure how to access it when there isnt an installed folder for the game. But it works just fine with it turned off, its not really a big deal tbh. But if i do find the setup, should i set what soundcard i actually have installed on the comp or should i use something that DosBox uses? (Did that make any sense? =o )

DOSBox is an EMULATOR. It emulates a DOS PC, including the hardware. Even when it runs an Solaris workstation, an Wii, or Symbian phone.

MiniMax wrote:

DOSBox is an EMULATOR. It emulates a DOS PC, including the hardware. Even when it runs an Solaris workstation, an Wii, or Symbian phone.

que?

guess you missed post nr. 5.

Will your DOS game support the sound hardware on the Symbian phone? 😉

So with the sound turned off it worked fine, til now... It looks like the same crash as before.. any ideas what i can try to change in order to fix it? =/

edit: Been changing the cpu cores and when using "simple" it worked fine (but slow) for about an hour then the crashes returned. I cant help but to feel that something is building up in either Dosbox or the game itself and then finally it just cant hold anymore and starts to crash repeatedly. Some fixes removes the crashes, but never entirely, they keep reapperaing after a while. =/

edit2: When the crash occurs, DosBox's main window change "display name" from the game name Program: HDM to Program: DOSBOX. Dunno if it means anything but.. anything to sort this, i really wanna play this ol game again ^^

Could there be an idea to change the "machine" value under the [dosbox] section in the config?

Read my 60 Seconds Guide to DOSBox (and don't just read it - follow it too).

If that doesn't help, come back with details on how you mounted your C and D drives, how you did the install, how you configured sound, music etc.

Reading the aptly named README file will be a good idea too.

I guess reading the different posts to gather the information you ask for would be much to ask. I'll compile them into 1 (one) neat little post for you later on.
Funny you mention your 60 second guide (which i've obviously read already), but there is nothing in it about crashes? You tell us noobs how to actually start a game using Dosbox, which in itself is very nice of you to tell since its far from obvious. But in order to actually have a crashing game you would need it installed and you would have needed to mount your c / d wouldnt you?

anyway, think i've had it with pricks thinking to high of themself, i thought a programmer would actually want ppl to use their product. Guess i was wrong.
bb

Well, unfortunately very few of the people that frequent this forum has a a working crystal ball which makes it hard to know what is wrong. And many, many things can lead to a crash. So instead we start with the basics, to make sure that the game at least is installed and configured in a semi-reasonable manner. Only when that foundation was been established is it worth our time to investigate what else might be causing the crash.

We have no obligation to help you, but you have an obligation to supply us with the requested and necessary information if you want our help. It does not get much simpler than that. For a more elaboration explanation as why a programmers world works this way, please see the "How to ask questions" link in my signature.