perhaps...(it's a suposition) it's caused by a "funny/rare" timing programming of the game itself....

don't know really....no idea... 😵

I just tried it (on a 32bit machine), but it runs just fine for me, with the same settings.

88200. Wow. That's high! I doubt there's much point in having it higher than 44100. I don't think any DOS games used sound samplerates higher than 44100, and most use 22050 or less. The higher you go, the more CPU time the sound emulation takes.

Try *decreasing* cycles, and/or switching to normal core (a few games do not like dynamic).

Btw, you know that you can't actually damage your machine by setting cycles really high. After a point dosbox's timing will get messed up, and sound will start breaking up, but that's all.

Changing the cycles has no effect at all (unless I set it low enough that the game runs rediculously slow). Changing the core from dynamic to normal has sped things up to normal speed. Weird.

The downside is that I end up with tearing until I go and fiddle with some game options (the "SVGA Compatibility Fix" and "Fix Jerky Motion" options). The odd thing is that toggling one of these and then going back to the game seems to fix the problem. Weird.

The GUS and OPL sound does sound a bit better with a higher mixing rate. It's small, but noticeable (if you have good headphones). 88200 isn't that high compared to the 192000 my sound card can output.

I know that setting the cycles high won't actually damage the computer, but I do know how things end up if it gets set too high.