Ok, relax everybody... I think I've elaborated quite a bit that I did not expect anybody to change the way DOSBox works or to put a lot of work in something that is not worth the effort. I just wanted to know if I stumbled upon something that was worth checking out for the developers. From the way that people react on this, I _guess_ that what I experience is the way DOSBox works and is meant to work. That is okay with me. But if anyone was interested to find out how I got it to crash, I could at least give the executables. But I too realize that it may be a lot of work for just a single case where things crash. And that the source of the problem is an executable that may not be stable in the first case. So I wondered if that would be even worth the effort, and what the official view is concerning crashing applications. Well, I think I get it now.
@Dominus: I have tried almost every combination of core and cpu type, and also via only, svga s3 and vesa, but the result is the same. I expect the executable to use some non standard cpu instruction or memory driver, demoes were notorious for using awkward and home built protected mode systems.
I've tested your SVN snapshot, and it does not crash and quit, but it seems to hang and stop to respond to user input. For example: when a DOS program hangs, I can still quit the DOSBox with the red close button. That will not work in this case.
@h-a-l-9000: For now, the demo that does weird things is Misguided by Haujobb, to be found at http://www.scene.org/file.php?file=/demos/gro … sg.zip&fileinfo