Does something change when you set the cycles very low,
like 2000 or below?

You could also try dos32a (a dos4gw replacement)

Thanks for the reply.

The cycles made no difference.

I then downloaded dos32a and copied the sb.exe and dos32a.exe files to the game directory and tried to run the game using the command "sb -r 3DPINBAL" but since the game is initiated by a bat file, containing RUNCD, it game an error in opening.

I then tried renaming DOS32A to DOS4GW, and got exactly the same error as before. 🙁

Has anybody got this game to run?

Is runcd the executable? (ie. there exists a runcd.exe?)
Then first load univbe, and then start the game with
"dos32a runcd.exe", maybe this behaves different.

Tried every combination I could, and still nothing 🙁

> Tried every combination I could, and still nothing

Do you still get the DOS4/GW error, or does dos32a
display this (similar) error?

I don't have the game, but some general things to try:
- try ems=false/xms=false in dosbox.conf (or combinations)
- disable the sound
- load the game WITHOUT univbe
- use the full core/dynamic core (dosbox.conf)
- try the debugger-enabled version of dosbox (does more
logging output and cpu-checks)

If you're handy with a debugger, you could see where the
divbyzero comes from (basically set a breakpoint at
1e0:10cc, ie. BP 1e0:10cc, and see what opcode triggers
the exception, and try to get an idea where the zero
comes from).

Good luck 😀