it looks like dynamic/normal core and higher/max cycles doesn't help
(game always starts randomly from 15-45 seconds)

The only thing that helps is alt-f12

[Moved to DOSBox Games/Apps. Section]

Both games attempt to set the system time with INT 21/2D, which DOSBox does not allow. The second game gets a bit confused if the time is not altered; but if the time *is* altered the startup only takes about 2 seconds at max cycles and 4 seconds at 3000 cycles on my system. Booting real DOS in DOSBox works, because real DOS allows the time to be set.

I'm only a beginner to DosBox. Could you please explain how to do this in DosBox or DFend Reloaded (DosBox Frontend)?

Also I found that if I camp in the game it kills/stalls/lockups DosBox. Can anyone give any idea what's up with that?

Thanks

for both problems keep alt-f12 pressed (it fast forwards dosbox)

Alt+F12 does seem to be a good work around to make the game playable. Thanks for the help 😀

There are a number of places the timing is off because of not being able to set the system time. When you die is another one.

Sounds like it could work in MB5. And a reason to add it to SVN 😀

but it doesn't 😀

Hope you have consistency in all the times/dates.

As consistency is blown to mars when DOSBox reaches midnight and no such complaint has hit the forum AFAIK it can't be that important.

But since it doesn't work anyway... forget it 😀

I don't know what the case is with MB5, but the timing in the game DOES work normally if INT 21/2D is properly implemented. And IMO, DOSBox is "inconsistent" in that it lets you set the date but not the time.

EDIT: I checked the MB5 source, and INT 21/2D is not implemented.