DOSBox CPU Core: Auto, Normal, Dynamic or Simple — In Plain Words
core line in the [cpu] section of your DOSBox config file decides how DOSBox carries out a game’s instructions. The default, core=auto, uses the careful normal core for older real-mode games and the fast dynamic core for protected-mode games. You rarely change it — but when a game crashes, hangs, or behaves strangely, the DOSBox manual’s own troubleshooting list says to try core=normal. The dynamic core is the speed option, and the manual warns in plain terms that some games “work worse/crash with the dynamic core… or do not work at all.”
Honest labels, up front. Everything on this page is copied from the DOSBox manual, the DOSBox Wiki, the configuration file DOSBox itself writes out, and — in one clearly marked section — the DOSBox Staging manual, which describes a different program and is never blended with the DOSBox 0.74 directions. Nothing here was tested by playing a game for this page: the DisBox settings collection this page belongs to holds 0 settings verified by actual play.
These settings are part of the DisBox collection. DisBox OS — the system being built to run games with settings like these — is in the works; its interface comes first, so there is no finished OS to download yet.
The four cores, in the Wiki’s words
The DOSBox Wiki’s CPU configuration page describes the [cpu] section as controlling “how DOSBox tries to emulate the CPU, how fast the emulation should be, and to adjust it.” The four working choices for core are:
- normal — “The program is interpreted instruction by instruction. This approach is a lot more CPU demanding than dynamic core but allows for a more fine-grained time emulation and is needed on platforms for which DOSBox doesn’t have a dynamic core.”
- simple — “Basically the same as normal, but optimized for real-mode (older) games. In case a protected-mode game is started, it automatically switches back to normal core.”
- dynamic — “The program instructions are, in blocks, translated to host processor instructions that execute directly.” The Wiki calls this more efficient than interpretation in most cases, “except for programs that employ massive self-modifying code,” and notes the dynamic core “is not present on all host platforms.”
- auto — “Real-mode programs are run with the normal core. For protected mode programs it switches to dynamic core, if available.” This is the default.
(The Wiki also lists a fifth value, full, marked simply “Deprecated” — it is a leftover, not a choice to use.)
When the manual tells you to change it
The manual reaches for the core setting in two opposite situations:
- For speed (section 10, “CPU Core (speed up)”): “On x86 architectures you can try to force the usage of a dynamically recompiling core (set core=dynamic in the DOSBox configuration file). This usually gives better results if the auto detection (core=auto) fails. It is best accompanied by cycles=max. But you may also try using it with high amounts of cycles (for example 20000 or more).” Then the warning, which this page will not soften: “Note that there might be games that work worse/crash with the dynamic core (so save your game often), or do not work at all!”
- For a crash (section 11, Troubleshooting): when “a certain game closes DOSBox, crashes with some message or hangs,” the manual’s list of configuration entries to try leads with
core=normal, alongside fixed cycles (its example is cycles=10000) and a short list of other switches. The manual’s no-sound answer gives the same advice in miniature: “set the core to normal in DOSBox configuration and use some lower fixed cycles value (like cycles=2000).”
The setting lives in the [cpu] section of the config file — the file DOSBox writes out documents it with the comment “core: CPU Core used in emulation. auto will switch to dynamic if available and appropriate,” and lists the possible values as auto, dynamic, normal, simple:
[cpu] core=auto
The neighbour setting: cputype
Right under core sits cputype — which kind of old CPU the game believes it is talking to, as opposed to how DOSBox does the work. The Wiki gives the choices as auto | 386 | 386_slow | 486_slow | pentium_slow | 386_prefetch (present since DOSBox 0.73), and says of the default: “auto is the fastest choice.” For almost every game, cputype=auto is where this setting stays; it is here so you know the line is not a second speed control.
Core is not cycles. The two [cpu] settings most often confused: core picks the method above; cycles picks the speed. The Wiki’s definition of the cycles default: with cycles=auto, real-mode games run at a fixed 3000 cycles (or a number you give), and when a game switches to protected mode the cycles switch internally to max. Speed problems — a game running too fast or too slow — are cycles questions, and the per-game guides in this collection cover them; this page is only about the core.
If you run DOSBox Staging instead
DOSBox Staging is a separate program; its own CPU page keeps the same four core names but describes the trade-off with numbers, printed here as Staging’s facts, not DOSBox 0.74’s. In Staging, auto is likewise “normal core for real mode programs, dynamic core for protected mode programs.” Staging’s reference says the normal core “yields the most accurate timings, but puts 3–5 times more load on the host CPU compared to the dynamic core,” that normal “is also necessary for programs that self-modify their code,” and that the dynamic core “is a necessity for demanding DOS programs (e.g., 3D SVGA games)” while self-modifying programs “might misbehave or crash on the dynamic core; use the normal core for such programs.” Its rule of thumb: “the dynamic core is recommended above about 20,000 cycles.” Staging’s cputype list is its own (it adds values such as 386_fast, 486 and pentium_mmx that 0.74 does not have, and its 386_prefetch “Requires core = normal”) — do not copy Staging’s cputype values into a 0.74 config file, or the other way round.
The one-minute version: Leave core=auto alone while things work. If a game crashes, hangs, or acts strangely, the manual’s own first prescription is core=normal (with a modest fixed cycles value). If a heavy protected-mode game is too slow and auto-detection seems to be the problem, core=dynamic with cycles=max is the manual’s speed recipe — with its warning kept attached: some games work worse, crash, or do not work at all on the dynamic core, so save often.
Sources
DOSBox Wiki — “Configuration:CPU” — the four core definitions (normal interpreted instruction by instruction; simple optimized for real-mode and switching back to normal for protected mode; dynamic translating blocks of instructions to host instructions, not present on all platforms; auto = normal for real-mode, dynamic for protected mode), full marked deprecated, cputype’s value list and “auto is the fastest choice,” and the cycles=auto definition used in the “Core is not cycles” box. https://www.dosbox.com/wiki/Configuration:CPU
DOSBox (dosbox.com) — “DOSBox v0.74-3 Manual” — Section 10 (the “CPU Core (speed up)” passage: forcing core=dynamic when auto detection fails, best accompanied by cycles=max, the 20000-or-more example, and the warning that games might work worse, crash, or not work at all), Section 11 (the crash list leading with core=normal and fixed cycles), and the Start FAQ’s no-sound answer (core to normal with cycles=2000). https://www.dosbox.com/DOSBoxManual.html
The configuration file DOSBox 0.74 writes out — the [cpu] section’s own comments (“auto will switch to dynamic if available and appropriate”; possible values auto, dynamic, normal, simple; cputype’s value list with “auto is the fastest choice”). Read in full; two printings of the shipped file agree on this section.
DOSBox Staging — “CPU” manual page — the labelled Staging section: its core reference (normal = most accurate timings at 3–5 times the host load and necessary for self-modifying code; dynamic = 3–5 times less load, a necessity for demanding 3D SVGA games, self-modifying code may misbehave or crash), the 20,000-cycles rule of thumb, and its own differing cputype list (386_prefetch requires core = normal). Staging is a separate program; its facts are labelled as such on this page. https://www.dosbox-staging.org/0.83/manual/system/cpu/
Checked November 7, 2026
Related guides: DOSBox Mouse Too Fast? The Sensitivity Fix, DOSBox Save States, DOSBox Scalers and Aspect Correction, DOSBox Screenshots and Video Capture and DOSBox Sound Stuttering.