The small practical win in our Prehistorik 2 experiment was a Finder launcher for the DOS demo. The more useful lesson was to read the demo's own instructions before guessing which executable to run.

This article documents work recorded on 14 October 2026. The launcher was re-read for publication; the game was not re-run for this article. The result is a startup note with a reusable setup pattern, not a claim of complete compatibility.

Start with the demo's entry point

The demo notes in FILE_ID.DIZ and LEEME.DOC identify PRE2.EXE. The local launcher uses that file. Another executable in the folder should not be treated as equivalent just because its name looks plausible. When a game has a loader, installer and main executable, guessing can send troubleshooting in the wrong direction.

The recorded environment

The experiment used DOSBox Staging 0.83.0 on Mac. This is the historical version in the record, not a statement that it is the newest or the version everyone should install. Use the official DOSBox Staging project for current documentation and downloads.

The launcher runs the demo from its own directory and invokes the installed DOSBox Staging application. It uses --noprimaryconf and --nolocalconf to avoid loading the usual primary and local configuration files for that run. Check the help for the version actually installed before relying on those options.

A launcher with explicit assumptions

The following matches the recorded pattern. It assumes DOSBox Staging is installed in Applications and PRE2.EXE is beside the launcher. It contains no game data:

#!/bin/zsh
set -e
GAME_DIR="${0:A:h}"
cd "$GAME_DIR"
exec '/Applications/DOSBox Staging.app/Contents/MacOS/dosbox' --noprimaryconf --nolocalconf "$GAME_DIR/PRE2.EXE"

Save it as a .command file in your legally obtained demo folder and make that file executable before opening it from Finder. Review the path and command first. If DOSBox is installed elsewhere or the game files have a different layout, adapt the launcher rather than changing unrelated system settings.

The first obstacle was file access

In the recorded experiment, access to the demo under Downloads was blocked. Moving that demo to a games folder resolved that specific setup obstacle. This does not mean moving files fixes every Mac permission problem, and it is not a reason to disable system protection globally.

A useful troubleshooting note names the failing operation and the one change that altered the result. “It did not open, then it worked” is much harder for the next person to use.

Startup is one row in the test record

The recorded output reached 320 × 200 EGA graphics mode. That proves less than a completed gameplay check. Controls, action input, sound, stability over a stated play duration and progress behavior still need explicit observation.

For your own record, separate “emulator launches,” “demo enters graphics,” “controls tested,” “audio tested” and “duration tested.” Keep unknowns visible. Preserve your original demo files and keep any experiment notes separate.

We do not host the demo or commercial game data in this article. The reusable parts are the method, the launcher pattern and the honest test record. Our Heart of Darkness note explores the different route of building a replacement engine.