Table of Contents
⛳ Purpose
Usually running DOS programs involves typing multiple commands into the DOSBox terminal, for each single launch.
Shortcuts let you skip that.
🪟 On Windows
Create a new program shortcut with its target set as described in the section below.
If you're new to creating shortcuts, here's a tutorial, however there are many more online as well.
🐧 On Unix
Create a plain text document named for example "run on dosbox.sh".
Inside it type:
#! /bin/sh
# [target]
Where `# [target] is as described in the section below.
Finally, set the document as executable. That option is usually available by right clicking on the document and selecting "properties".
🎯 Target
"[pathToDosboxExe]" [gameExeName] -fullscreen -exit
If the game needs disk images:
"[pathToDosboxExe]" -c "mount c [pathToGameDir]" -c "imgmount d [listOfPathsToDiskImages] -t cdrom" [gameExeName] -fullscreen -exit
Examples
-
dosbox run.bat -fullscreen -exit -
/my/preferred/dosbox -c "imgmount d cd/image.cue -t cdrom" game.exe -fullscreen -exit -
/my/preferred/dosbox -c "mount c path/to/game/" -c "imgmount d path/to/game/cd/image.cue -t cdrom" -c "c:" -c "start.exe" -fullscreen -exit
💿 Changing disk
Control + F4
General
How-to's
- Adding utilities
- Applications
- Config file examples
- Dual-mouse gaming
- Getting started
- Instant launch
- Joysticks and Gamepads
- Keymapper
- Multiplayer & serial ports
- Windows
Lists
- AUTOTYPE candidates
- CDDA / GUS / MIDI games
- DOS/32A compatibility
- Dual OPL2 and OPL3 games
- Games with enhanced Tandy & PCjr graphics and sound
- Shaders
- Special keys
Audio
- Audio mixer signal flow diagram
- Audio configuration recommendations
- GUS enhancements
- MIDI
- Sound cards
- True 16-bit audio games
Video
Issues
Dev
- How to contribute
- Release process
- Audio tests
- CPU tests
- DOS tests
- Input tests
- Performance tests
- Video tests — Video modes
- Video tests — CRT shaders
- Video tests — Presentation
- Learning DOS programming
- Intel compiler tips