Как пользоваться dosbox

Known DOSBox-X forks

  • DOSBox-X Emscripten port (runnable in a web browser) by Yksoft1

    Significant changes are made in order to run efficiently within the web browser when compiled using LLVM/Emscripten.
    These significant changes require dropping some useful features (including the menus) but are required for performance.

    URL: https://github.com/yksoft1/dosbox-x-vanilla-sdl/tree/emscripten (look for clone URL and use the emscripten branch)

  • DOSBox-X-App (for Windows and macOS) by emendelson

    DOSBox-X-App is a slightly customized version of DOSBox-X, combined with external programs and commands that make it
    easy to print and create PDFs from DOS applications. It is customized for use with applications, not games.

  • DOSBoxWP (for WordPerfect for DOS) by emendelson

    DOSBoxWP is a customized version of DOSBox-X targetted for users of WordPerfect for DOS.

  • Win31DOSBox (Windows 3.1 for 64-bit Windows) by emendelson

    Win31DOSBox aims to be an easy method of running Windows 3.x software for 64-bit Windows systems.
    The system uses a custom build of DOSBox-X when running Windows 3.1x.

Build instructions

Read BUILD.md for the comprehensive compilation guide.

Linux, macOS

Install build dependencies appropriate for your OS:

# Fedora
sudo dnf install ccache gcc-c++ meson alsa-lib-devel libpng-devel \
                 SDL2-devel SDL2_net-devel opusfile-devel fluidsynth-devel \
                 mt32emu-devel
# Debian, Ubuntu
sudo apt install ccache build-essential libasound2-dev libpng-dev \
                 libsdl2-dev libsdl2-net-dev libopusfile-dev libfluidsynth-dev

# Install Meson on Debian-10 "Buster" or Ubuntu-20.04 and older
sudo apt install python3-setuptools python3-pip
sudo pip3 install --upgrade meson ninja

# Install Meson on Debian-11 "Bullseye" or Ubuntu-21.04 and newer
sudo apt install meson
# Arch, Manjaro
sudo pacman -S ccache gcc meson alsa-lib libpng sdl2 sdl2_net opusfile \
               fluidsynth
# openSUSE
sudo zypper install ccache gcc gcc-c++ meson alsa-devel libpng-devel \
                    libSDL2-devel libSDL2_net-devel opusfile-devel \
                    fluidsynth-devel libmt32emu-devel
# macOS
xcode-select --install
brew install ccache meson libpng sdl2 sdl2_net opusfile fluid-synth

Build and stay up-to-date with the latest sources

  • Checkout the master branch, which will include the submodules:

    # commit or stash any personal code changes
    git checkout master -f
  • Pull the latest updates. This is necessary every time you want a new build:

    git pull
  • Optionally, you can clean your ccache and working directories. This is only
    advised if you have unexpected build failures:

    ccache -C
    git clean -fdx
  • Setup the build. This is a one-time step either after cloning the repo or
    cleaning your working directories:

    meson setup \
        -Dbuildtype=release \
        -Ddefault_library=static \
        -Db_asneeded=true \
        -Dtry_static_libs=png \
        -Dfluidsynth:enable-floats=true \
        -Dfluidsynth:try-static-deps=true \
      build/release

    The above enables all of DOSBox Staging’s functional features. If you’re
    interested in seeing all of Meson’s setup options, run: .

  • Compile the sources. This is necessary every time you want a new build:

    meson compile -C build/release

    Your binary is: — have fun!

Windows — Visual Studio (2019 or newer)

First, you need to setup vcpkg to install build dependencies. Once vcpkg
is bootstrapped, open PowerShell and run:

PS:\> .\vcpkg integrate install
PS:\> .\vcpkg install --triplet x64-windows libpng sdl2 sdl2-net libmt32emu opusfile fluidsynth gtest

These two steps will ensure that MSVC finds and links all dependencies.

Start Visual Studio and open file: . Make sure you have
selected as the solution platform. Use Ctrl+Shift+B to build all projects.

Windows (MSYS2), macOS (MacPorts), Haiku, others

Instructions for other build systems and operating systems are documented
in BUILD.md. Links to OS-specific instructions: MSYS2, MacPorts,
Haiku.

DOSBox-X supported platforms and releases

DOSBox-X is a cross-platform DOS emulator, so all major host operating systems are officially supported, including:

  1. Windows (XP or higher), 32-bit and 64-bit

  2. Linux (with X11), 32-bit and 64-bit

  3. macOS (Mac OS X) Sierra 10.12 or higher 64-bit

  4. DOS (MS-DOS 5.0+ or compatible)

For running DOSBox-X in a real DOS system (MS-DOS or compatible), you can find the HX-DOS package that makes use of the freely-available HX DOS Extender. Type DOSBOX-X to run it from a DOS system. There is also the DOS LOADLIN package which can run from within DOSBox-X itself in addition to a DOS system. Note, however, that not all features of DOSBox-X that are supported in other platforms can be supported in the real DOS environment.

The full source code is officially provided with each DOSBox-X release, which may be compiled to run on the above and possbily other operating systems too. You can also get the latest development source code from the repository directly. See also the BUILD page for information on building/compiling the DOSBox-X source code.

M

  • M1 Tank Platoon
  • Magic Carpet
  • Mad TV
  • Mad News works correctly since DOSBox 0.73
  • Maniac Mansion
  • Mario Teaches Typing
  • Mario’s Game Gallery
  • Master of Magic
  • Master of Orion
  • Master of Orion II
  • MDK
  • Mechanized Assault & Exploration
  • MechWarrior
  • MechWarrior 2
  • Mega Man
  • Mega Man 3
  • Metaltech: Earthsiege
  • Metal Rage
  • Micro Machines
  • Might and Magic 1
  • Might and Magic II
  • Might and Magic III: Isles of Terra
  • Might and Magic IV: Clouds of Xeen
  • Might and Magic V: Darkside of Xeen
  • Mine Bombers
  • Mines of Titan
  • Modem Wars
  • Monkey Island Madness
  • Monkey Island 2: LeChuck’s Revenge
  • Monopoly Deluxe
  • Monster Bash
  • Monty Pythons Flying Circus
  • Moraff’s World

Build DOSBox

  • After downloading the source code, open the Visual Studio solution: dosbox\visualc_net\dosbox.sln
  • Allow it to automatically convert to the latest version.
  • Right click the dosbox project in the Solution Explorer and open its Properties.
    • When editing the properties, edits will have to be made for each configuration you may want to build. In the top left there is an option for Debug, Release and All Configurations. The Release build is most commonly used, but All Configurations will let you conveniently edit both at once wherever the two configurations have the same options.
    • Click the drop down triangle on Configuration Properties > C/C++ > General > Additional Include Directories and edit this list. Add the appropriate include path for each library prepared above. Keep in mind that paths are relative to the dosbox\visualc_net folder.
    • Edit Configuration Properties > Linker > General > Additional Library Directories and add the path to each library (.lib) file prepared above.
    • Edit Configuration Properties > Linker > Input > Additional Dependencies to add or remove libraries. (You will have to select either the Debug or Release configuration for this, as the Debug build uses a different list of libraries than the Release.)
      • Remove zlib.lib and libpng.lib if not using these. Rename libpng.lib as libpng16.lib if you are using it.
      • Remove sdl_net.lib if not using it.
      • Add an entry for SDL_sound if using it.
      • Remove curses.lib if not using it.
  • Find dosbox\src\platform\visualc\config.h and open it (in the solution explorer it is under dosbox \ Source Files \ visualc).
    • C_SSHOT to 0 if not using zlib/libpng.
    • C_MODEM and C_IPX to 0 if not using SDL_net.
    • Add #define C_SDL_SOUND if using SDL_sound.
    • C_DEBUG to 1 if using the PDCurses.
  • After all of this is set up, you may build the dosbox project. Choose a Debug or Release configuration (recommend: Release) and use the build menu to build the solution. One of the following will be built:
    • dosbox\visualc_net\Release\dosbox.exe
    • dosbox\visualc_net\Debug\dosbox.exe
  • Finally, take the SDL.dll and SDL_net.dll files prepared above and place them in the same directory as dosbox.exe. It should now be ready to run.

§ New Features in Detail

New features originating from our upstream (DOSBox) are marked with «SVN».

Upgrade to SDL 2.0

SDL 2.0 is a major update to the SDL 1.2 codebase, which has been unmaintained
since 2013. SDL 2.0 supports more input devices; more output interfaces such as
Wayland, and OpenGLES 1 and 2; low-latency audio using OpenSL ES; and improves
cross-platform consistency.

The migration to SDL 2.0:

  • dropped 3,211 lines of SDL 1.2 code in place of 1,664 lines, for just
    under a 50% reduction in code-size.
  • eliminated several OS-specific branches and all SDL1-specific kludges.
  • eased support for modern graphic APIs, and opened the field for new features
    and improvements.

One example includes the new mode, which uses SDL’s 2D
hardware-accelerated API rendering to a platform-specific backend.

For example, Windows users can test:

macOS users can try Metal:

and everyone can use OpenGL as texture backend:

Or just use to let SDL pick the backend appropriate
for your Operating System.

Разработка

До Windows XP ориентированные на потребителя версии Windows основывались на MS-DOS . Windows 3.0 и ее обновления были операционными средами, которые работали поверх MS-DOS, а серия Windows 9x состояла из операционных систем, которые все еще основывались на MS-DOS. Эти версии Windows могли запускать приложения DOS. И наоборот, операционные системы Windows NT не основывались на DOS. Членом этой серии является Windows XP, которая дебютировала 25 октября 2001 года и стала первой ориентированной на потребителя версией Windows, не использующей DOS. Хотя Windows XP могла эмулировать DOS , она не могла запускать многие из своих приложений, поскольку эти приложения работали только в реальном режиме для прямого доступа к оборудованию компьютера, а Windows XP предотвращал такой прямой доступ по соображениям безопасности. MS-DOS продолжала получать поддержку до конца 2001 года, а вся поддержка любой операционной системы Windows на базе DOS закончилась 11 июля 2006 года.

Разработка DOSBox началась с выпуска Windows 2000 — системы Windows NT — когда ее создатели, голландские программисты Питер Винстра и Сьерд ван дер Берг, обнаружили, что операционная система перестала поддерживать программное обеспечение DOS. В то время оба знали о решениях, но они не могли запускать приложения в оконном режиме или масштабировать графику. Проект был впервые загружен на SourceForge и выпущен для бета-тестирования 22 июля 2002 года.

Other issues

  • Game save files are written into the Emscripten file system, which is by
    default an in-memory file system. Saved games will be lost when you close
    the web page.
  • Compiling in Windows is not supported. The build process requires a
    Unix-like environment due to use of GNU Autotools. See Emscripten
    issue 2208.
  • The same origin policy prevents access to data files when running via a
    file:// URL in some browsers. Use a web server such as
    instead.
  • Firefox may use huge amounts of memory when starting asm.js builds which have
    not been minified.
  • The FPU code uses doubles and does not provide full 80 bit precision.
    DOSBox can only give full precision when running on an x86 CPU.

Software security comments

DOSBox-X cannot claim to be a «secure» application. It contains a lot of
code designed for performance, not security. There may be vulnerabilities,
bugs, and flaws in the emulation that could permit malicious DOS executables
within to cause problems or exploit bugs in the emulator to cause harm.
There is no guarantee of complete containment by DOSBox-X of the guest
operating system or application.

If security is a priority, then:

Do not use DOSBox-X on a secure system.

Do not run DOSBox-X as root or Administrator.

If you need to use DOSBox-X, run it under a lesser privileged user, or in
a chroot jail or sandbox.

If your Linux distribution has it enabled, consider using the auditing
system to limit what the DOSBox-X executable is allowed to do.

Disney Sound Source

The Disney Sound Source was an external audio device that connected to a PC via a Parallel Port, also known as the Printer Port. An enhanced version of the Covox Speech Accelerator with «Mickey Mouse» ears on top, the device was surprisingly capable of producing polyphonic audio and voice. The sound quality is distinctive and tinny, though by no means high quality. One notable game that supported the device was Sierra’s King’s Quest 6 which managed to provide an audio experience similar to the Sound Blaster audio card.

The Disney Sound Source became popular due to its brand name and ease of configuration: There are no Base Address, IRQ, or DMA settings because it connects to any available Parallel Port. However, applications that utilize a printer might lock up if they try to talk to this device by mistake, so if you are having parallel port trouble and are not using this device for audio, you may want to consider disabling it.

A Windows driver exists (as with the PC Speaker) that can let the device work as an audio device in Windows 3.11.

The Disney Sound System is configured under the speaker category. As mentioned before, it has no special configuration. (And does not even have a rate setting.)

Windows Packages (Installer or Portable)

You probably want to use the all-in-one Windows installation packages for the ease of installation, which are especially recommended for new and non-expert users. With the installer the installation process will be automated while allowing you to change the install folder and the default build to run if you prefer (and the option to install all builds to subdirectories), so that you will be able to start DOSBox-X as soon as the installation ends. A quick start guide is also included in the package, and shell context menus can be automatically added for a fast launch of DOSBox-X from the Windows Explorer. The Windows installers for the current DOSBox-X version 0.83.17 are available from:

  • dosbox-x-win32-0.83.17-setup.exe (32-bit Windows builds; Windows XP or later)
  • dosbox-x-win64-0.83.17-setup.exe (64-bit Windows builds; Windows Vista or later)

If you see the message when running an installer, you can solve it by clicking the link «More info» in the dialog and then «Run anyway».

You can easily upgrade from a previous version of DOSBox-X to the new version with the Windows installer. The Windows installer in fact offers an option to automatically upgrade the config file (dosbox-x.conf) to the new version format while keeping all the user-customized settings already made. When you select this (recommended), the config file will include all options of the latest DOSBox-X version and also will keep all the changes already done previously by the user.

Apart from the Windows installers, you can find six zip packages (three before 0.83.13) for each DOSBox-X version for the Windows platform in the Releases page as an alternative way to install DOSBox-X. These zip files are portable packages containing binaries built with Visual Studio 2019 (Win32, Win64, ARM32, ARM64 respectively), MinGW (Win32 and Win64 respectively). For the current DOSBox-X version 0.83.17, these portable builds are separately available from:

  • dosbox-x-vsbuild-win32-20210831224158.zip (Visual Studio Win32 builds)
  • dosbox-x-vsbuild-win64-20210831224158.zip (Visual Studio Win64 builds)
  • dosbox-x-vsbuild-arm32-20210831224158.zip (Visual Studio ARM32 builds)
  • dosbox-x-vsbuild-arm64-20210831224158.zip (Visual Studio ARM64 builds)
  • dosbox-x-mingw-win32-20210831230534.zip (MinGW Win32 builds)
  • dosbox-x-mingw-win64-20210901044459.zip (MinGW Win64 builds)

The Visual Studio builds are the default Windows builds to use, but they may require Windows Vista and later (Windows 7, 8, and 10). On the other hand, the MinGW builds may run in Windows XP but will not have the debugger. You may also want to use one of the MinGW builds (plain, lowend, etc) if you encounter specific problem(s) with the Visual Studio builds, or you want the Slirp backend support for the NE2000 networking. In addition, while the SDL1 version is the default version, the SDL2 version may be prefered over the SDL1 version for certain features (particularly related to input handling) such as better international keyboard support.

If you prefer to use one of the portable packages, please select the zip package you want to download for your platform and unzip, then you will find various folders or subdirectories, which are some supported targets. For Visual Studio builds, these correspond to Win32 (x86), Win64 (x64), ARM32 and ARM64 (either SDL1 or SDL2 version), which are the build platforms. For MinGW builds, the targets are plain MinGW SDL1 build (mingw), MinGW SDL1 build for lower-end systems (mingw-lowend), MinGW SDL1 build with custom drawn menu (mingw-sdldraw), and MinGW SDL2 build (mingw-sdl2). Go to a target folder for your platform and run dosbox-x.exe inside it, then DOSBox-X will be launched and ready to be used. Unlike the Windows installer version however, there is no documentation included in these packages, and you may not see all such packages for some DOSBox-X versions.

Short Version

This is the quick version for people familiar with Windows, giving the basic information.

  • Create a new shortcut to the DOSBox .exe file, or copy the one created when you installed DOSBox.
  • Edit the properties of the shortcut.
  • At the end of the «Target» line, add, in quotes, the full path of the main game executable that you wish to launch.
    • For example, if «The Settlers 2» was installed into the folder C:\Games\Settlers 2\, and DosBox is installed at it’s default location, the target box would contain:
    • «C:\Program Files\DOSBox-0.72\dosbox.exe» -conf «C:\Program Files\DOSBox-0.72\dosbox.conf» «C:\Games\Settlers 2\S2.exe»
  • NB: the -conf command line option, which is specified in the line above, is optional, since it refers to the default config file. However, if you use a custom config file, then you will need to retain this line, suitably amended to refer to your custom .conf file.

использование

С января 2011 года разработчики уровня совместимости Wine интегрировали DOSBox в Wine, чтобы облегчить выполнение программ DOS, которые изначально не поддерживаются машиной Wine Virtual DOS .

С января 2015 года Интернет-архив добавил в свою библиотеку программного обеспечения тысячи игр для DOS. Его вилка DOSBox, Em-DOSBox, использует Emscripten для преобразования кода C ++ эмулятора в JavaScript , что делает игры доступными в веб-браузере. Сборник предназначен «только для стипендий и исследований». По состоянию на октябрь 2019 года библиотека DOS содержала 6934 игры.

Коммерческий

DOSBox также был и наиболее часто используемым эмулятором DOS, и, из-за простого процесса создания игр на современных компьютерах, самым популярным программным обеспечением для эмуляции для разработчиков, повторно выпускающих устаревшие версии своих игр. ID Software использовала DOSBox перевыпустить старинные игры , такие как Wolfenstein 3D и Commander Keen на Valve «s пару . Сообщалось, что в процессе они нарушили лицензию программы, GNU GPL; нарушение, о котором было сообщено как о недосмотре, было оперативно устранено. Activision Blizzard также использовала его для переиздания DOS-игр Sierra Entertainment . LucasArts использовала его для переиздания Star Wars: Dark Forces и Star Wars: TIE Fighter для современных машин в Steam и GOG.com . Продюсер 2K Games Джейсон Бергман заявил, что компания использовала DOSBox для перевыпусков Steam некоторых частей серии XCOM . Bethesda Softworks порекомендовала DOSBox и предоставила ссылку на сайт DOSBox на странице загрузок для The Elder Scrolls: Arena и The Elder Scrolls II: Daggerfall . Он также включал DOSBox с обеими играми в выпуске The Elder Scrolls Anthology .

Electronic Arts ‘ Первый клиент использует DOSBox для DOS игр платформы, в том числе названия Electronic Arts , такие как Syndicate и SimCity 2000 .

DOS Packages (Portable)

(To be updated for version 0.83.17)

Besides Windows, Linux and macOS packages, there are also packages released for the DOS operating system. Yes, DOSBox-X can officially run on DOS systems as well, as some DOS users seem to prefer to run DOS applications and games through a DOS emulator. With DOSBox-X running in DOS you are able to emulate another DOS system with a different PC configuration (such as different machine types, video and sound cards etc) that works better for the purpose of the users. But please note that due to the limitations of this environment not all features of DOSBox-X that are available in other platforms can be supported in the DOS version.

For the previuos DOSBox-X version 0.83.16, the official DOS version is available in the following zip package:

dosbox-x-mingw-hx-dos-20210801212637.zip

The HX-DOS package allows you to run DOSBox-X in a real DOS system (MS-DOS 5.0+ or compatible) with the help of the freely-available HX DOS Extender, which is already included in the recent DOS release packages. Once you unzip the package you can directly type to run in DOS. See the README.TXT file inside the DOS package for more information.

dosbox-x-dos-0.83.16-loadlin.zip

With this LOADLIN DOS package you can run DOSBox-X right from DOSBox-X’s DOS shell. Start the outside DOSBox-X with the setting and (perhaps also and/or ). Go to the directory where the files are extracted and type . Then just wait for DOSBox-X to be automatically loaded within DOSBox-X.

Note: You may not see DOS packages for some DOSBox-X versions. For example, the official DOS package is not available for DOSBox-X version 0.83.1.

Alternate methods for running a game

The steps described above are closely aligned with how DOS Based operating systems behave natively. However modern operating system allow for more user friendly (although less authentic) ways of playing your favorite games. If the steps above seem tedious or confusing you can try some of these other guides. In most cases these guides will still require you to setup a working DOSBox environment.

  • Using Frontends
  • Creating desktop shortcuts

NOTE: If you have problems with launching the game, unrecognizable errors being spit out, saving settings, or having the game drop out while running it, one thing to try is to make sure all the files are not set to Read Only. In Windows, select the folder of the game, right click and hit properties, uncheck Read Only if it is checked, and apply to all sub folders.

Performance

Slow games/applications

Q. My game/application runs slowly, how do I improve speed?

A. Increase cycles. Use core=dynamic. Try different output modes (e.g. output=overlay). Increase Frameskip. Disable unneeded components in the dosbox.conf such as Sound, mouse or joystick emulation. A nice speedup can be achieved by using a different compiler than GCC. If all else fails, find a faster computer to run DOSBox on.
Also be sure to check the compatibility section of this FAQ as some game/applications are more trouble (or resource hogs) than others.

See also How to speed up/slow down DOSBox

Problems in sound/music

Q. The Sound/Music for my DOS game/application sounds terrible what can I do?

A. This is a complicated issue covered in the Sound section of the wiki. It’s important to remember to install or setup game/applications correctly to use the correct sound devices (INSTALL.EXE, SOUNDSET.EXE and SETUP.EXE are popular program names to look for). The capabilities of the hardware as well as the preferences of the programmer vary: Therefore what may sound «best» on one particular game may not be the «best» for another. Sometimes changes need to be made to the dosbox.conf file (or a new conf file) to get the best results.
Also, game sound/music may have an impact on the speed at which the game/application runs and running DOSBox with limited resources may result in incomplete or ‘choppy’ sound being heard. (see previous question)

Increasing memory size

Q. How do I change the memory size so that I can run programs that require more than the default settings (eg. Windows 1.01 or some other demanding OS)?

A. See the memsize option detailed in Configuration:DOSBox.

General MIDI (MPU-401)

General MIDI isn’t a specific piece of hardware so much as a standard that has been supported by various sound cards (and other devices such as mixers, instruments, lighting control panels, etc…) throughout computing history. DOSBox is able to emulate MIDI in either regular or uart modes.

Since MIDI support is still common on computers, DOSBox passes MIDI data along to any MIDI synthesizer installed on your system rather than trying to emulate a particular device. General MIDI in DOSBox sounds exactly like any other program on your host computer that plays MIDI files because it is generating its output through the same device. You can think of the General MIDI as more a pass-though interface than a piece of emulated hardware.

General MIDI is configured under the midi category. There are several options, which are explained briefly in the comments in the configuration file and at greater length in the README file. Owners of Yamaha MIDI Synthesizers and other external synthesizers may find this guide useful, while those without may want to use the guide to software emulation of MIDI instead.

Roland

The Roland synthesizers, particularly the MT-32, are worth mentioning separately. Many DOS games included separate support for the MT-32 (or the MT-100, LAPC-I, CM-32L, or CM-64) in addition to basic General MIDI support. People who have a real Roland MT-32 or a software synthesizer that emulates one can take advantage of this support. Since DOSBox only passes along MIDI data to your synthesizer without looking at it, simply route DOSBox’s General MIDI to your Roland and configure your DOS software to use Roland mode.

A Roland MT-32 can be connected to the PC using a USB to MIDI adapter. The MT-32 output can be connected to the line-in on a sound card. Dosbox can be configured to use the MT-32 for music when it is connected this way. At the Dosbox command prompt, type mixer /listmidi to get a list of the midi devices attached to the machine. Locate the USB midi adapter in the list and note the number that it is associated with. Change to the ID of the USB midi device (e.g. midiconfig=0) Once that is done, the MT-32 should operate.

C

  • Captain Comic
  • Captain Comic II
  • Capture the Flag
  • Cannon Fodder
  • Cannon Fodder 2
  • Carmageddon Works on DOSBox 0.73 (Windows 7 x64)
  • Castle of Dr. Brain
  • Castles II
  • Cavewars
  • Centurion: Defender of Rome
  • Chasm: The Rift
  • Chuck Yeager’s Air Combat
  • Civilization
  • Clyde’s Adventure: Lost Treasure Of Tahookaboo
  • Cobra Gunship
  • Codename: Iceman
  • Colonization, Sid Meier’s
  • Colors by Jim Bonczyk
  • Coldreams
  • Comanche: Maximum Overkill
  • Command & Conquer
  • Command & Conquer: Red Alert
  • Commander Keen: Invasion of the Vorticons
  • Commander Keen: Keen Dreams
  • Commander Keen: Goodbye Galaxy!/Aliens ate my Babysitter!
  • Companions of Xanth
  • Constructor
  • Cosmo’s Cosmic Adventure: Forbidden Planet
  • Countdown
  • Crazy Drake
  • Creature Shock
  • Crusader: No Remorse
  • Crusader: No Regret
  • Crystal Caves: Trouble with Twibbles
  • Crystal Caves: Slugging It Out

Introduction to DOSBox-X

Like DOSBox, it emulates a PC necessary for running many MS-DOS games and applications that simply cannot be run on modern PCs and operating systems. However, while the main focus of DOSBox is for running DOS games, DOSBox-X goes much further than this. Started as a fork of the DOSBox project, it retains compatibility with the wide base of DOS games and DOS gaming DOSBox was designed for. But it is also a platform for running DOS applications, including emulating the environments to run Windows 3.x, 9x and ME and software written for those versions of Windows. DOSBox-X additionally features support for DOS/V and NEC PC-98 emulations so that you can play DOS/V and PC-98 games with it.

DOSBox-X is completely open-source and free of charge to use and distribute. It is released under the GNU General Public License, version 2.

This project has a Code of Conduct, please read it for general information on contributing to or getting support from the project.

Brought to you by: joncampbell123 (Jonathan Campbell)

Step 3: Running DOSBox & Using the Command Line

If everything is configured correctly, when you run DOSBox you’ll see something like this:

DOS Commands

Now you will need to use some simple DOS command prompt commands to navigate to the correct directory (folder) and run the game. If you’ve used DOS before (or Windows Command Prompt) this should be easy. If not, here are some basic commands:

CD — Change directory — Use this command to change to a sub-directory of your current directory. So if you are in C:\ (ex, you mounted your C:\DOSGAMES directory as C:\ in DOSBox) and want to play Commander Keen which is in your C:\KEEN directory in DOSBox (in C:\DOSGAMES\KEEN on your actual hard drive) you would type cd keen and press Enter.

CD .. — Change to parent directory — Use this special version of the CD command to go to the parent directory. So if you are in C:\DOOM and type cd .. you will then be in C:\.

DIR — Directory listing — Use this command to display a list of files in a directory. Add the /w option (dir /w) to display a more compact view. Add the /p option (dir /p) to pause the screen at the end of each page. You can also list all files of a certain type with a command like dir .exe (shows all executable files in the current directory).

[filename.EXE/COM/BAT] — Run the game — There are three kinds of files you can run in DOS. The most common is .EXE. A second less common is .COM. A third is .BAT, which is actually a list of several commands that run in sequence. The file that starts the game will likely be a .EXE file, although if a .BAT file exists, you can also try that. If neither exists, look for a .COM file. (Note that you don’t need to type the extension; so to run PLAYME.EXE you can just type PLAYME.)

Typical Usage

Typically after running DOSBox, you will use a CD command to change to the directory of the game you want to play, then type [name of .exe/com/bat file] to start the game. Type DIR to list the files if you forget which file to run.

More info on DOS commands: For a full list of DOS commands and much more details, see Computer Hope’s Basic overview of MS-DOS commands

After running the game, hopefully it will start up and you can begin to play!

In-game Hotkeys

Here are some common hotkeys that you may find useful:

ALT-ENTERALT-PAUSECTRL-F10Windows keyCTRL-F11CTRL-F12

Full list: See the DOSBox Special Keys page for a full list.

Подготовка

Естественно, сначала не забываем про такую мелочь, как установка эмулятора. В Linux дистрибутивах все как обычно банально и упрощено до одной строчки. На примере Ubuntu это делается при помощи терминала и строчки:

sudo apt-get install dosbox

Пользователи Windows и дистрибутивов, которые по какой-либо причине не могут установить DOSBox из репозитория, могут скачать нужный файл с официального сайта.

Дальше предлагаю сразу создать структуру каталогов, куда мы будем складывать игры. В принципе это не обязательно, если вы не планируете устанавливать много игр, но я предпочитаю делать так. На самом деле ничего сложного выдумывать не нужно: в корне одного из разделов жесткого диска, например на диске D в Windows или домашнем каталоге пользователя в Linux, создаем папку «DOSBox» и уже в ней создаем еще две папки — «Apps» если Вы планируете пользоваться приложениями и «Games«, непосредственно для игр.

Теперь пришло время скачать архив с игрой. Этот вопрос вы уже решаете сами, сайтов в интернете с таким добром полно. После скачивания распаковываете папку с игрой в каталог Games и можно приступать к ее запуску.

What is DOSBox?

DOSBox is an emulator program which emulates an IBM PC compatible computer running a DOS operating system. Many IBM PC compatible graphics and sound cards are also emulated. This means that original DOS programs (including PC games) are provided with an environment in which they can run correctly, even though the modern computers have dropped support for that old environment. DOSBox is the standard way to play DOS games on modern computers. It has been compiled for Windows, Mac, Linux, and many other operating systems and platforms. It is free software released under a GNU General Public License.

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *

Adblock
detector