

- CURRENT VERSION BOXER FOR MAC HOW TO
- CURRENT VERSION BOXER FOR MAC INSTALL
- CURRENT VERSION BOXER FOR MAC MAC
The recommended best practice for modern OS X applications is to always include a file extension, and this makes it easier to interoperate with DOSBox config files from other OSes. In addition, Boxer uses the ".conf" file extension for config files instead of no extension.
CURRENT VERSION BOXER FOR MAC HOW TO
The majority of games function just fine without it, and it's a major scare for new users if their mouse cursor suddenly disappears with no advice on how to get it back - especially if Cmd-Q doesn't work (which it doesn't in DOSBox.app by default - Boxer implements it with a custom keymapper file.) (/tmp isn't even visible in Finder, so most users won't know how to access their screenshots!) This is where screenshots go by default in OS X. "capture" changed from "/tmp" to the current user's desktop folder.

Otherwise, DOSBox.app will create mapper.txt files in the current location of DOSBox.app, which is usually Applications. "mapperfile" changed to point to a file in the current user's preferences folder. "output" changed from "surface" to "openglnb" because surface prevents OS X from taking screenshots of the DOSBox window (instead the window appears empty.) Indeed, you could just cut-and-paste keys from Boxer's ist in order to do so.īoxer makes the following changes to the default DOSBox Preferences file:
CURRENT VERSION BOXER FOR MAC MAC
On a more practical note for the developers of the Mac DOSBox port: most of what Boxer does to make DOSBox behave better on the Mac could be done instead by DOSBox.app itself.įor instance, making DOSBox.app open files or folders from Finder (or by drag-and-drop) simply involves modifying the ist file inside the package to add the appropriate filetype keys for exe/com/bat files and folders. That's quite far away though, and will almost certainly require its own fork of DOSBox. Boxer automatically creates per-user preference files for itself if none are present, so there's no installation or initial setup hassles.īoxer will probably evolve into a fully-fledged Cocoa GUI application (coded in a proper language) which wraps DOSBox completely: using individual DOSBox processes as its document windows, giving you proper menus for controlling the focused window, and preferences panels for tweaking global/game-specific settings. When you run Boxer it inspects the file/folder you're opening with it, chooses an appropriate DOSBox configuration, sniffs the current user language, then feeds the appropriate settings to DOSBox for launch. So if you have a Mac, try it out and tell me what you think!Ĭurrently, Boxer is an applescript wrapper for the standard DOSBox.app.
CURRENT VERSION BOXER FOR MAC INSTALL
Boxer lets you install and bundle games into their own elegant click-to-play game packages, either by using the included game-installer droplet or just by renaming the game's folder.īoxer also makes DOSBox behave more like a native OS X application: with better file handling (run programs and mount folders and ISOs from Finder), standard Mac keyboard shortcuts, auto-detection of mounted CDs and ISOs, auto-detection of resolution and keyboard layout, friendlier default settings and automatic localization. This means automatic game configuration, no profile setup and no big game database you have to fill: just click on a game in Finder and it runs. Clearer dialogs and friendlier choices when you quit a game.īoxer isn't a frontend (like DBGL/Dapplegrey) but a repackaging of DOSBox: it contains its own copy of DOSBox 0.72, and it does not need any special installation or supporting files.īoxer aims to make it as easy to play a DOS game as it is to play a game in any console emulator.

