pkg.soopen package index

cask

Install dosbox with Homebrew Cask

Emulator for x86 with DOS. Version 0.74-3,3 via Homebrew Cask; verified from local package data. Also installable with dnf: sudo dnf install dosbox-staging.

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask dosbox

local Homebrew cask metadata

overview

Package summary

Emulator for x86 with DOS

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

DOSBox is an open-source x86 and DOS environment emulator primarily used to run DOS games on modern operating systems.

Project history

Dutch programmers Peter Veenstra and Sjoerd van der Berg created DOSBox around 2000 to restore DOS-game compatibility as Windows moved away from its DOS-based lineage. The first public version, DOSBox 0.1, was released on 31 January 2002.

DOSBox combines an x86 CPU emulator, a DOS-like environment, and emulation of period graphics, audio, input, and networking hardware. This avoids requiring users to install a separate copy of DOS.

Adoption history

DOSBox became the de facto way to run MS-DOS games on modern operating systems. Its portability brought DOS software to Windows, macOS, Linux, BSD, and less-common host platforms after native DOS compatibility had disappeared from mainstream systems.

Commercial storefronts and publishers adopted it as packaging infrastructure for rereleased DOS games: the original game files, a private DOSBox build, configuration, and a launcher can be shipped together as a self-contained modern application.

How it is used

Users mount a host directory or disk image as a DOS drive, change to that virtual drive, and start an executable. The configuration file controls emulated machine type, CPU speed, memory, graphics, sound, input, networking, drive mounts, and startup commands.

Why package nerds care

DOSBox is a canonical example of an emulator functioning as a compatibility runtime. Packagers can preserve an unchanged DOS executable while declaring its virtual drives, emulated hardware, CPU speed, sound devices, and startup commands in configuration.

Its long-lived stable series and open development also produced an extensive ecosystem of frontends, downstream builds, libretro cores, and specialized forks such as DOSBox Staging and DOSBox-X.

Timeline

  • 2002-01-31: DOSBox 0.1 became the first public release.
  • 2010-05-12: DOSBox 0.74 was released and became the long-lived stable baseline.
  • 2019-06-26: DOSBox 0.74-3 delivered security and rendering fixes.

Related projects

  • DOSBox Staging
  • DOSBox-X
  • DOSBox Pure
  • ScummVM
  • FreeDOS

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for dosbox. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Linux
~/.dosbox/dosbox-{version}.conf
macOS
~/Library/Preferences/DOSBox {version} Preferences
Windows
%LOCALAPPDATA%\DOSBox\dosbox-{version}.conf

executables

Installed executables

CommandKindExposureNote
No executable data was present.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version0.74-3,3
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://www.dosbox.com/

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://www.dosbox.com/none confidence

install metadata

Package metadata

Package keycask:dosbox
Version0.74-3,3
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/dosbox
Homepagehttps://www.dosbox.com/
Upstream docshttps://www.dosbox.com/
Source archivehttps://downloads.sourceforge.net/dosbox/dosbox/0.74-3/DOSBox-0.74-3-3.dmg
SHA-25683493d149318cb7bfe5d68d98d1cd10b003db2f0519374bf06de285dc0bb2768
Bottlenot recorded
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokendosbox
Names
  • DOSBox
Artifacts
Deprecatedno
Disabledno

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

dnf95%

dosbox-staging 0.82.2-6.fc45

Modern continuation of DOSBox with advanced features

https://www.dosbox-staging.org/

sudo dnf install dosbox-staging
  • License: GPL-2.0-or-later AND Unlicense AND (MIT-0 OR Unlicense) AND MIT AND GPL-3.0-or-later AND LicenseRef-Fedora-Public-Domain AND Fair AND LGPL-2.1-or-later AND
  • Category: Unspecified
  • Architecture: x86_64
  • Source Package: dosbox-staging
  • 20 dependencies
  • 5 provides
  • normalized package name match
  • Matched by: Dosbox
Fedora Rawhide package metadata · dl.fedoraproject.org · Fedora Rawhide package metadata: dosbox-staging from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/652278618dec9c023176a80c435a32a2c8154869fb0eb662c267a54df28d77d9-primary.xml.zst

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment