I've noticed on some games, DOSBox goes from the specified "Auto" cycle setting to exactly 3000 cycles with no error or explaination. This happens once certain games are run. I don't understand why. Is there something else I should know about? Am I doing something wrong?

For instance... here is a shortcut to Frontier:

"C:\Program Files (x86)\DOSBox-0.70\dosbox.exe" "D:\FRONTIER\FRONTIER.EXE" -exit -conf "D:\FRONTIER\dosbox.conf" -noconsole

DOSBox boots with 3000 cycles per second in the above example. Below is the same shortcut used for Daggerfall:

"C:\Program Files (x86)\DOSBox-0.70\dosbox.exe" "D:\DAGGER\DAGGER.BAT" -exit -conf "D:\DAGGER\dosbox.conf" -noconsole

It boots using "Auto" cycles.

The "dosbox.conf" file is the same for both games. Frontier's config file is literally a copy of Daggerfall's. But this is not about Frontier or Daggerfall. Most everything I use with DOSBox works great. Only a handful of titles have this strange behavior. In fact, there are some games that have a two-part bootup: the main executable loads the title screen and credits and then loads another exectuable for the main menu at which time DOSBox goes directly to a 3000 cycle setting.

Is this a known issue or am I just lucky? 😀

Thanks for any insight you may have!