And what is the real problem here?

...That I can't automatically run games on the proper speed setting they need by using batch files, and using Ctrl+F11 and F12 is annoying and in many cases, not specific enough.

create a config, then edit the cycles option 😀

Thanks for the suggestion, but I already tried that to no avail. But nevermind, I just found a workaround: using an older version of DOSBox, or another CVS build. It seems like the bug appeared in the last DOSBox version.

cycles=fixed 50000 would be the command

h-a-l-9000 wrote:

cycles=fixed 50000 would be the command

...It works now! 😳

So it wasn't a bug... Why did they change the line?

Anyway, thank you. I feel so dumb now 😜

why not ?
anyway get a recent cvs build and be happy

you have to read what is written in the dosbox.conf file:

# cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropo […]
Show full quote

# cycles: Amount of instructions DOSBox tries to emulate each millisecond. Setting this value too high results in sound dropouts and lags. Cycles can be set in 3 ways:
# 'auto' tries to guess what a game needs.
# It usually works, but can fail for certain games.
# 'fixed #number' will set a fixed amount of cycles. This is what you usually need if 'auto' fails.
# (Example: fixed 4000)
# 'max' will allocate as much cycles as your computer is able to handle

sometimes, stuff gets changed because it makes more sens this way to the devs. But if it gets changed the commands are either documented in the readme or the dosbox.conf (or both 😀).
So next time, if something won't work anymore, look at those two (and generating a new dosbox.conf is highly recommended when you switch versions of Dosbox)

MiniMax wrote:

And what is the real problem here?

Answer: Not reading the documentation.

Real answer: people using dev versions, where people==peoplewhoshouldn't. Closed.