Answered Plainly
Display: Text size:

Leer esta guía en español

King’s Quest in DOSBox: Tandy Sound — In Plain Words

Short answer: Set machine=tandy in the [dosbox] section of the configuration file. That one line is the fix on DOSBox Wiki’s own King’s Quest pages: the first games were written for the IBM PCjr’s three-voice sound, so on a plain emulated PC you only hear the one-note speaker beeps, while Tandy emulation gives you the fuller music the games were composed for. If the music then wobbles out of tune, that is a separate, documented fault — the wiki’s block pairs Tandy with core=normal and cycles=10000, while a well-known GOG forum fix uses cycles=fixed 500 instead (1,000 for games II and III). Both are printed below, labeled.

Honest labels, up front. Every setting on this page is a documented starting point copied from the public sources in the Sources box — including the two different cycles fixes, printed as two, not blended into one. None of these settings has been tested by playing the game for this page: the DisBox settings collection this page belongs to holds 0 settings verified by actual play.

These settings live in 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.

Why the music sounds wrong in the first place

A GOG forum thread about fixing the GOG editions (edited August 2015) explains the history plainly: the ordinary IBM PC of the time “only had a harsh-sounding monophonic speaker, but King’s Quest was actually designed for the IBM PCjr, which has polyphonic speakers.” The music has harmonies — “the originally intended experience” — that most players never hear. The Tandy 1000’s sound chip is the close relative of the PCjr’s, which is why telling DOSBox to emulate a Tandy brings the missing voices back. The DOSBox manual rates its Tandy 3-voice emulation as complete with one honest exception: the noise channel is “not very well documented” and is a best guess.

The setting, from DOSBox Wiki’s own game pages

DOSBox Wiki’s King’s Quest page says the game “works fine under DOSBox, but you can get enhanced sound from the original version by changing your dosbox.conf file to emulate a Tandy computer,” and prints this block for “the 1987 version and enhanced remake (1990)”:

[dosbox]
machine=tandy

[render]
aspect=true

[cpu]
core=normal
cycles=10000

The wiki’s King’s Quest II page gives the same route for the 1987 version there — its block is just the one line, machine=tandy — and the GOG thread confirms the choice for the DOS versions of games 1–3: “pcjr also seems to work, but tandy is a better bet for this DOS version.” Note where the line lives: the wiki puts machine= in the [dosbox] section, so put it there. The same thread notes the setting “seems to also add a few additional sound effects here and there,” and that machine=cga is a different experiment — muted composite colors, and back to the monophonic music.

If the music wobbles: the two cycles fixes

The GOG thread lists three faults in the GOG editions’ shipped settings, and two of them are speed faults: the music “sounds awful and out of tune (the notes fluctuate up and down instead of being a pure tone),” and the game’s Fast speed setting goes “hundreds of times faster than normal.” It blames DOSBox’s dynamic core, which “makes the game run as fast as possible.” Its fix, for the [cpu] section of each game’s dosboxKQx.conf file:

core=auto
cputype=auto
cycles=fixed 500
cycleup=100
cycledown=100

— with the poster’s own update: for King’s Quest II and III, which add a “Faster” setting, use cycles=fixed 1000 instead of 500. The wiki’s block above takes the other road to the same place: core=normal with cycles=10000, which also keeps the emulator off the dynamic core. This page does not pick between them: they were written for different copies of the game (the wiki for the original releases, the thread for the GOG editions), and either is a documented starting point. If one still wobbles, try the other — and while you play, Ctrl+F11 and Ctrl+F12 lower and raise cycles live, as the thread points out.

Which versions this applies to

The one-minute version: Beeps instead of music → add machine=tandy under [dosbox] (DOSBox Wiki’s own fix for King’s Quest I and II). Music wobbling out of tune, or the game racing at Fast speed → the core is the problem: use the wiki’s core=normal, cycles=10000, or the GOG thread’s cycles=fixed 500 (1,000 for II and III). Booter disks from 1984/1985 don’t use this page — they boot with machine=cga.

Sources

DOSBox Wiki — “GAMES:King’s Quest: Quest for the Crown” — the enhanced-sound sentence, the config block printed for the 1987 version and the 1990 enhanced remake (machine=tandy, aspect=true, core=normal, cycles=10000), and the 1984 PC Booter route (machine=cga, boot KQ.img). http://www.dosbox.com/wiki/GAMES:King%27s_Quest

DOSBox Wiki — “GAMES:King’s Quest II: Romancing the Throne” — the machine=tandy route for the 1987 version, and the 1985 booter route (machine=cga, boot KQ2-1.img KQ2-2.img, Ctrl+F4 to change floppies). http://www.dosbox.com/wiki/GAMES:King%27s_Quest_II:_Romancing_the_Throne

GOG.com forum — “Optimizing King’s Quest 1–3 (sound/music and speed)” (mgiuca, edited August 1, 2015) — the PCjr history, the three faults in the GOG default, the [cpu] fix (core=auto, cputype=auto, cycles=fixed 500, cycleup=100, cycledown=100; fixed 1000 for games II and III), tandy over pcjr for the DOS versions, and the machine=cga note. https://www.gog.com/forum/kings_quest_series/optimizing_kings_quest_13_soundmusic_and_speed/page1

DOSBox (dosbox.com) — “DOSBox v0.74-3 Manual” — the sound-hardware list: Tandy 3-voice emulation complete except the noise channel, which is a best guess. https://www.dosbox.com/DOSBoxManual.html

Checked November 7, 2026

Related guides: Master of Orion II Sound Crackles in DOSBox, DOSBox Sound Stuttering, SimCity 2000 Has No Sound in DOSBox? What the Tests Show, Lemmings Has No Sound in DOSBox? The Fix and Sound Blaster Settings in DOSBox.