Retro PC gaming on Windows 10, technical aspects, flight sims and space sims a speciality
Search Results
Search this site
221 results found with an empty search
- The Elite series: Elite back then
Elite Plus retail box This will be the first in a couple of articles covering the classic granddaddy space sim of them all, Elite. In this first article we'll be taking a look at the last version released for the PC, 'Elite Plus', in all of it's 256 colour, VGA glory, and a modern take on the original classic, 'Elite: The New Kind'. This article won't be covering the Frontier or Frontier: First Encounters games. One for a future article! Elite Plus Elite Plus title screen Elite Plus is a re-implemented version of the classic Elite on the PC with graphics improved from CGA to EGA, VGA or MCGA (256 colour VGA). Sound has also been enhanced with the original PC Speaker supplemented with Adlib (Soundblaster compatible) or Roland music. The PC version of Elite was created by Ian Bell and David Braben and published in 1984, while Elite Plus was published in 1991. The retail release was distributed on 2 x 5.25" Double Density (DD) 360k floppy disks, or a single 3.5" 720k DD floppy disk. If you wish to use your existing floppy disks I would recommend converting them to floppy disk images to save wear and tear on the media, they are over 30 years old now! Where to get it Docking at a Coriolis station The easiest place to pick up Elite Plus is digitally through a free download on Ian Bell's PC Elite page. This version also has the added advantage of disabled copy protection. This digital version is distributed as a zip archive. Controller support Elite Plus supports keyboard, mouse or joystick control. It does not support a throttle or rudder pedals. However, since I have a joystick, throttle and rudder pedals, I configured them as part of the virtual controller, even if they won't be used. This will make it easier for DOSBox to assign the correct virtual controller axes to the DOSBox joystick device axes. Configuring axes may not be required if your setup has 4 axes or less. The physical axes to Windows axes were configured as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_XROT_AXIS DOSBox Staging config This config assumes the latest version of DOSBox Staging, at time of writing v0.82.0. Changes from the default values are described below: [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] core = simple cycleup = 100 cycledown = 100 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = medium chorus = normal [midi] mididevice = mt32 [mt32] romdir = "D:\Midi\Versioned" [sblaster] sbtype = sbpro1 [joystick] joysticktype = 4axis timed = true swap34 = false deadzone = 0 [autoexec] imgmount a "D:\Games\Dos\Elite Plus\fdd\*.img" -t floppy -ro mount c "D:\Games\Dos\Elite Plus\hdd" loadfix c: cd elite elite The [sdl], [dosbox] and [mouse] settings are suitable for high frame rate gaming as described in this article by Omniclyde. These settings aren't strictly required and can be omitted to use the default settings. The simple core is used to increase compatibility with earlier DOS games. The default 3000 cycles count seems fine and doesn't need to be adjusted. Voodoo emulation isn't required and can be disabled. The [mixer] settings are a personal preference to enhance sound and music. The [midi] and [mt32] settings are based on info from the VOGONS wiki article 'List of MT-32-compatible computer games'. The rom folder needs to be specified, as described in DOSBox midi. As the CM32L device is supported the mt32 model can be left as default. In the [sblaster] section, the sbtype is changed to a Soundblaster Pro, this is to take advantage of stereo audio provided by (emulated) dual OPL chips. I'm not sure if this makes a difference but the VOGONS wiki article has a note about Adlib OPL2, so setting the type to sbpro1 may provide an enhancement? The [joystick] settings use a 4axis joystick type, as I'm using a 4 axes virtual controller, and this will help DOSBox assign axes correctly. If you only have a 2 axes controller or your device(s) allows unused axes to be disabled, then this could be changed to a 2axis joystick type. The timed settings seemed to be required by my HOTAS setup and as the throttle and rudder pedals aren't used the swap34 setting can be left as default. The deadzone is a personal preference. The [autoexec] has example imgmount commands for a floppy disk image, if you wish to use your retail release. The imgmount and mount commands make use of a folder structure described in my DOSBox game management article. The loadfix command is required to limit the amount of conventional memory. This is often needed by early DOS games or increases compatibility. The rest of the autoexec commands go to the DOSBox folder where Elite was installed and runs the game. Installation There is no installer utility with Elite Plus so installation is just a manual file copy. To install the digital release, simply create a folder under the DOSBox hard disk folder and extract the archive into this folder. This can all be done in Windows. In my case I created an ELITE folder, so I had to extract the archive into D:\Games\Dos\Elite Plus\hdd\ELITE. This folder becomes C:\ELITE in DOSBox. To install a retail release with floppy disk images, from within DOSBox, create an installation folder on the C: drive and copy the contents of any disk(s) into this folder, e.g. c: # Go to the c: drive md elite # Create an elite folder a: # Go to the floppy disk copy *.* c:\elite # Copy the contents into the elite folder Running Each time Elite Plus is run, the sound/music and graphics options are chosen. The sound/music options are: PC speaker Adlib compatible (Soundblaster) Roland LAPC1 (recommended) The DOSBox config settings allow Adlib/Soundblaster or Roland to be chosen. The graphics option can then be chosen: EGA 16 colours VGA 16 colours MCGA 256 colours (recommended) Cobra MkIII, feels like home! MCGA is fully compatible with VGA, so the MCGA option is effectively VGA with 256 colours. Once in game you will need to select your controller option, either keyboard (default), mouse or joystick. Saved games have the file extension .cdr for Commander. Background and documentation When it comes to background information Ian Bell's Elite Home Page is second to none, well worth a read if you want to dig into the history and the various versions of Elite. Of particular note are: The Space Traders Flight Training Manual The novella included with retail releases, 'The Dark Wheel'. Written by Rob Holdstock it provides background to the galaxies you'll be flying, fighting and trading within and a pretty good Elite story as well! Update: The Elite Plus manual in pdf format courtesy of Pix's Origin Adventures. If you are using a joystick I would also recommend trying to find a pdf version of the PC retail manual as the joystick control options are covered. Elite: The New Kind I'd recognize a Cobra MkIII anywhere! Elite: The New Kind (also known as Elite: TNK or E:TNK) is the work of Christian Pinder. The original 8-bit BBC Model B version was reversed engineered and redeveloped into a Windows version. What is remarkable is that the 'feel' of the original has been preserved in E:TNK coupled with graphics that are reminiscent of the Acorn Archimedes version (often considered the best version of Elite) has resulted in a modern day equivalent that plays like the classic Elite of previous years. Definitely one for the purist Elite connoisseur! Not without its issues, it was unavailable when Christian was asked to remove the download for legal reasons, but following the 30th anniversary of Elite, E:TNK was granted a reprieve and has been available to download ever since! Where to get it The latest version is v1.2 available digitally as zip archive from the download section of 'The New Kind' website. Installation and running A clean and harmless Commander DarkenedRoom! As a zip archive, installation only requires extracting the archive into a folder, that's it. There are installation and running instructions on the download page of the website. There is no joystick or mouse option, it being a port of the original BBC Model B version, so it's old school keyboard flying in this version! Even if you've never played the earlier 8- or 16-bit versions of Elite, I'd recommend E:TNK if only to get a taste of what the original was like. Finally... We've taken a brief look at Elite for the PC as it was then, with the PC port and a modern PC interpretation of the 8-bit classic Elite. In the next article we'll take a look at a 21st century Elite and why I think it's as revolutionary today, as the original was 40 years ago. Credit and thanks go to Lord_Kane for finding the Elite Plus manual in pdf format. Good hunting!
- F-19 Stealth Fighter: North Cape secret airstrip fixed?
North Cape Has a bug that prevented the North Cape secret airstrip missions been found and fixed? The GitHub user, debugcom has done some very impressive analysis work in figuring out how to trigger the secret airstrip missions in F-19 Stealth Fighter and F-117A Nighthawk Stealth Fighter 2.0. The analysis revealed that there was a bug in the North Cape theatre that prevented the missions from being completed. Part 2 of the analysis went on to identify and document the fix for the North Cape data file responsible for these missions, nc.wld , fixing a 34 year old bug! That's some pretty impressive work and it's well worth a read! You can find the analysis here on GitHub, debugcom / Hacking-F117A It's not known if there's anything else that may be preventing North Cape secret airstrip missions from working, but if this mission appears it should be completable now! I've applied the fix to this version of nc.wld . To use it, take a backup of your current nc.wld file, and unzip this one to your F-19 Stealth Fighter installation folder. Update : The article by debugcom has been expanded to four parts including a section specific to getting secret airstrip missions working in the Libya and North Cape scenarios of F-19 Stealth Fighter. I've applied the fixes detailed in the article and can receive secret airstrip missions, as the below screenshots show. Libya secret airstrip mission North Cape secret airstrip mission This zip archive includes the changed libya.wld and nc.wld files with secret airstrip missions enabled, it should be extracted to your F-19 installation folder: If you get these mission and manage to complete them, let me know! Finally a big thank you to debugcom for the work on fixing this bug!
- Tech refresh 2025: F-19 Stealth Fighter
This is a tech refresh article describing any changes since the original articles ' F-19 Stealth Fighter: Running in DOSBox ' and ' F-19 Stealth Fighter: Optimized settings for DOSBox Staging ' were published. Since the original article the version of DOSBox Staging has changed from v0.80.1 to v0.82.0. The only change is an updated DOSBox Staging configuration shown below, the rest of the advice in the previous articles remains valid. DOSBox Staging configuration These are the settings which differ from the DOSBox Staging defaults. Note : At higher cycles the weapons effectiveness drops and Air-to-air missiles and Mavericks will begin to miss targets, so testing with some training missions may be required and the cycles setting tweaked to ensure consistent weapons performance. This may be dependant on your setup, however the cycles shown below should be a good starting point. [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] core = simple cpu_cycles = 5200 cycleup = 100 cycledown = 100 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = medium chorus = normal [midi] mididevice = mt32 [mt32] model = auto romdir = "D:\Midi\Versioned" [sblaster] sbtype = sbpro1 [innovation] sidmodel = auto [joystick] joysticktype = 4axis timed = true swap34 = false deadzone = 0 [autoexec] loadfix mount C "D:\Program Files (x86)\GOG Galaxy\Games\F-19 Stealth Fighter" mount C "D:\Program Files (x86)\GOG Galaxy\Games\F-19 Stealth Fighter\cloud_saves" -t overlay mixer master 50 mt32 70 c: call f19scen.bat The sdl settings are appropriate for a variable refresh rate monitor. They can be left as default or omitted for standard monitors. The sdl, dos_rate and mouse settings are also applicable for high frame rates as described in this article by Omnicycle. The voodoo emulation is disabled as it isn't required. The mixer settings are a personal preference to enhance the music and audio. The Soundblaster type is changed to take advantage of the Soundblaster Pro dual OPL2 chips. Innovation sound is enabled as it supported by the game and can be selected at startup with the setup game menu, if you would like to try it out. Joystick settings will be dependant on your particular HOTAS setup and may require adjustment. In the autoexec section the mixer volumes are changed with the mixer command to a personal preference. The damson menu ( f19scen.bat ) is used to optimise startup options and allow aircraft model and scenario changes. Enhancements Earlier this year PixelWings produced a mod for F-19. In the words of PixelWings: This mod is a small and simple graphic and sound improvement, featuring a freshly drawn cockpit panel for the aircraft, new RWR type sprites for the tactical MFD screen, as well as a new original title screen, credits screen and a one-game advert screen. Even if you wish to use the vanilla cockpit initially, it's still worth getting this immediately, as the revised Roland MT32 rsound.exe file removes the annoying low altitude warning! So a big thank you to PixelWings, the mod can be found on the PixelWings website . Updates The ' F-19 Stealth Fighter: North Cape secret airstrip fixed? ' article has been updated following an update from the analysis author debugcom. The fixes have been implemented for the Libya and North Cape scenarios and a new download is available. Good hunting!
- Harrier Jump Jetting into DOSBox Staging
Harrier Jump Jet, MicroProse 1992 This is a guide to running the 1992 MicroProse Harrier sim, Harrier Jump Jet in DOSBox Staging. It will cover patching both the digital and retail releases to the latest version, the DOSBox Staging config and setting up a HOTAS. As usual floppy images will be used to save wear and tear on disks and drive. This guide references the earlier work by @damsonn in a Steam guide , so a big thank you for the hard work that went into that. Version The only retail version I have been able to find is v2.16. The digital release on gog.com is the same v2.16 version. I'm assuming the Steam release is also v2.16 given the game comes from the same publisher. Differences between digital and retail releases Despite digital and retail releases being at the same version there are some minor differences in the files present between the two releases, detailed in the table below. The descriptions of the differences are a subjective best guess. aces.dat An additional data file, present in the digital release, to change the entries on the Aces page in game. Following application of the v2.40 patch, this file is removed. frontend.exe This looks like an uncompressed and cracked version of the executable containing the manual based copy protection disabled in digital releases. The retail releases uses the original file with copy protection intact. Following application of the v2.40 patch this file is replaced with a new version with the copy protection intact. harrier.bat Created by the installer, so full and small installs create different harrier.bat files. intro.fli A file containing the intro movie visuals. This is present in the retail release but missing in the digital release. This suggests the digital releases were built using the small install option. t.1 This looks like a scratch file created as the digital release was being produced. This isn't present in the retail release. wwf.com This seems to be a remnant from the original third party copy protection crack. This isn't present in the retail release. readme.now A short readme explaining the differences between a full and small install. Not present in the digital release. xmusic.imp Present in digital and retail releases, but different sizes. I believe this is created once a music/sound option is chosen in the installer. So the default Soundblaster sound in the digital release may explain this. xsound.imp As xmusic.imp but for digital sound effects. *.cfg Game config files, differences in digital/retail game defaults result in different config files. *.$$$ Game temp files, expected to be different between individual copies. Patches There are two patches available, the v2.40 patch (also known as the US patch) provides bug fixes, controller and game enhancements. The v2.40 patch is an update patch which must be installed using DOSBox. The v2.41 patch (also known as the UK patch) provides a bug fix to rudder control. This is a file replacement patch, with files from the patch archive replacing existing files in the Harrier installation folder. I believe the US and UK patch names are inaccurate and both patches are applicable to either European/UK or US editions, depending on game version. I believe these names may have come about due to re-release versions of the game, which may have been different for European/UK and US markets. The patches are recommended for both digital and retail releases. The patching strategy is summarized below: Game version is v2.16, apply v2.40 (US) patch. Game version is (or patched to) v2.40, apply v2.41 (UK) patch. Game version is (or patched to) v2.41, patching complete. For specific installation and patching instructions, see ' Installation and patching ' below. HOTAS config As it is a DOS based sim a maximum of 4 axes are supported. Harrier supports all 4 axes, including throttle and rudder. When using HOTAS/controller profiling software to limit the controller to a maximum of 4 axes the following device axes to Windows axes mappings were used: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_XROT_AXIS DOSBox config This DOSBox Staging config for Harrier assumes the latest version (at time of writing), v0.82.0 will be used. The changes to the default config are shown below: [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] cpu_cycles = 12000 # cpu_cycles = 20000 cpu_cycles_protected = auto cycleup = 1000 cycledown = 1000 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = large chorus = normal [midi] mididevice = mt32 [mt32] romdir = "D:\Midi\Versioned" [joystick] joysticktype = 4axis timed = true swap34 = true deadzone = 0 [autoexec] imgmount a "D:\Games\Dos\Harrier Jump Jet\fdd\*.ima" -t floppy -ro mount c "D:\Games\Dos\Harrier Jump Jet\hdd" c: cd mps\harrier call harrier.bat The [sdl], [dosbox] and [mouse] settings are suitable for high frame rate gaming as described in this article by Omniclyde. These settings aren't strictly required and can be omitted to use the default settings. In [cpu] settings, 12000 cycles seems appropriate for my setup. @damssonn has recommended 20000 cycles in a Steam guide, so you may need to tweak this setting to find an optimum speed for your setup. The cpu_cycles_protected setting will use the same cycle count as cpu_cycles when set to auto. Voodoo emulation isn't required and can be disabled. The [mixer] settings can be changed to enhance sound and music to personal preference. The [midi] and [mt32] settings enable high quality Roland midi music. The model value, auto, will default to a CM32L device. Harrier supports a CM32L device, so the model can be left as default. The midi roms folder is described in the DOSBox midi article. The [joystick] settings are appropriate for my HOTAS setup so you may need to alter these. The timed setting must be set to true for my HOTAS, as the game has issues with timed set to false, although this may depend on your own setup. The deadzone setting is a personal preference. The [autoexec] has example imgmount commands for the floppy images which may be needed for a retail edition. As there are multiple floppy images the imgmount command uses the '*' wildcard. The imgmount and mount commands make use of a folder structure described in my DOSBox game management article. Installation and patching The digital release install is somewhat different, given the need to patch, clean up and repair the release. Both the retail and digital installs use my DOSBox game management strategy. The top level game folder is D:\Games\Dos\Harrier Jump Jet, with hdd (DOSBox hard disk), fdd (floppy disk image), patches and conf (config files) sub folders. Retail edition installation The game should be installed from within DOSBox. The first floppy disk has an installer ( install.exe ) which should run and complete without issue. It is recommended to select the 'Full install '. Game files are copied to C:\MPS\HARRIER (in DOSBox) or in my case D:\Games\Dos\Harrier Jump Jet\hdd \MPS\HARRIER (in Windows). Once files are copied the installer will require a music/sound option to be selected. The DOSBox config above supports Soundblaster or Roland music/sound, so this is left to personal preference. When exiting the installer, you may be asked to calibrate your joystick, if one is detected. At this stage, just skip through without calibrating properly. Digital edition installation The game should be installed in Windows using the appropriate gog or Steam client. My recommendation is then to copy the game files from this client installation folder into a suitable DOSBox hard disk, retail release folder (C:\MPS\HARRIER). So in my case, my gog digital edition was installed in D:\Program Files (x86)\GOG Galaxy\Games\Harrier Jump Jet\C\AV8B by the gog client. I copied the game files into D:\Games\Dos\Harrier Jump Jet\hdd \MPS\HARRIER (in Windows). So when I start DOSBox the Harrier game files can be found in C:\MPS\HARRIER . I recommend not patching or repairing the client installation directly, as using the gog/Steam client to verify or repair game files may remove any patches or fixes applied. Patching to v2.40 The v2.40 (US) patch can be found on the Internet Archive . The patch should be downloaded and the files in the zip archive copied into the DOSBox game installation folder, overwriting any existing files. So in my case the files would be copied to: D:\Games\Dos\Harrier Jump Jet\hdd\MPS\HARRIER Once copied the update utility ( update.bat ) should be run from within DOSBox. Once the update is complete the installer will be run again allowing music/sound options to be selected. When exiting the installer, you may be asked to calibrate your joystick, if one is detected. You will be asked the following: Use the detected joystick: Y. Is it a Thrustmaster Joystick (FCS): N. Is a Thrustmaster Weapons Control System present: N. Then follow the instructions to calibrate your joystick. Patching to v2.41 The v2.41 (UK) patch can be found on the Internet Archive . The patch should be downloaded and the files in the zip archive copied into the DOSBox game installation folder, overwriting any existing files. So in my case the files would be copied to D:\Games\Dos\Harrier Jump Jet\hdd \MPS\HARRIER (in Windows). As this is a file replacement patch, this completes the patching to v2.41. Cleaning up the digital release This is an optional step to remove unneeded files in the DOSBox game installation folder for the digital edition only. The following files can be removed: t.1 wwf.com Adding the intro movie back into the digital release This is an optional step for the digital edition only. The missing into movie ( intro.fli ) can be found in the Steam guide created by @damsonn . It should be copied into the DOSBox game installation folder. So in my case intro.fli would be copied to the Windows folder: D:\Games\Dos\Harrier Jump Jet\hdd\MPS\HARRIER Then the text in harrier.bat should be replaced with the text in full.bat (the commands are described in the Steam guide). If the game is run with full.bat or harrier.bat the intro movie will be played. Removing copy protection from the digital release This is an optional step for the digital edition only. The v2.40 patch replaced the cracked frontend.exe file with newer version with the copy protection enabled. To use the cracked version, copy it from your client game installation folder into your DOSBox game installation folder. So in my case, in Windows, I would copy frontend.exe from: D:\Program Files (x86)\GOG Galaxy\Games\Harrier Jump Jet\C\AV8B into: D:\Games\Dos\Harrier Jump Jet\hdd\MPS\HARRIER Quitting with the cracked frontend.exe Note: There are issues using the cracked frontend.exe with v2.41, so far I have only encountered the one issue described, however there may be others. The 'Exit to DOS (Y/N) screen is no longer shown. Selecting the quit option from the command centre, will change the colour palette in the command centre screen but won't show the 'Exit to DOS' screen. The options still work, so selecting Y will exit to DOS and N will return to a working command centre screen. My personal preference is to use the newer copy protection enabled frontend.exe. Thanks to a carefully laid out manual and being given the first letter of the copy protection word, finding it in the manual is straight-forward. However, it is left to personal preference as to whether the copy protection should be enabled or disabled. Running With the digital and retail releases the small.bat file will run the game without the intro movie, while full.bat will run it with the intro movie. With the retail release harrier.bat will run with the intro movie if a full install was selected and without if a small install was selected. With the digital release harrier.bat will run without the intro movie by default, or with the intro movie if the ' Adding the intro movie back into the digital release ' instructions were followed. Game setup Once the game is running, select the Fly mission option from the command centre screen. Once in mission, the pause menu can be used to: Check version Checking the version Select the Quit menu and About option to check the version. The version should be listed as v2.41 in the dialog box. Enable Controllers Select the Config and Control menus. There are options to select a joystick, enable throttle/rudders, change joystick sensitivity and re-calibrate the joystick. When enabling throttle and rudders the controllers must be centred. This is easy for rudder pedals and little more tricky for the throttle. The lowest throttle position should correspond to 26% RPM and at the highest throttle position, 100% RPM. It may take a few attempts to centre and optimise the throttle. The first time the throttle and rudders are enabled there may be some spurious aircraft movement. Simply move your controllers and then re-centre them and the spurious movement should settle. Enable all sounds At the start of each mission, engine sounds are disabled by default and can be enabled by selecting the Config and Sound menus and the All effects option or by using the keyboard shortcut listed in the manual. Documentation Manual The manual is absolutely essential for a MicroProse sim. Fortunately the manual has been added to the gog.com digital release. I'm not sure if this is the case for the Steam digital release but @damsonn comes to the rescue again with a link to the manual in the Steam guide ! Good hunting!
- Playnite and modern DOSBox variants
Playnite game entry This is a guide on integrating modern variants of DOSBox, like DOSBox Staging or DOSBox-X with the Playnite game launcher. I'm not a Playnite plug-in developer or expert so there may well be a better way of integrating DOSBox Staging or DOSBox-X but this method seems to work well (at least it does for me). I've been using it for a while now, so hopefully it's at least an acceptable way of doing things. This process won't be changing existing emulators or settings but adding new ones. This guide assumes you have already installed your preferred modern variant of DOSBox. Note: I'm not an expert, so you may encounter issues I didn't. You do this at your own risk, so make sure you're comfortable with all the steps involved before you start making changes! If you have any suggestions or alternative methods, feel free to get in touch! What is Playnite The Playnite website says it best (far better than I could): Playnite is an open source video game library manager with one simple goal: To provide a unified interface for all of your games. Well worth having a read of this website to discover more about what Playnite can do! The ones we are most interested in are: Integration with game libraries It provides 'out of the box' integration with a wide variety of existing game libraries. I use it to link to my Steam and gog libraries. Games can be automatically imported and added to Playnite. Integration with DOSBox The Playnite website says it supports a wide variety of console emulators, which although true, is very modest of them. It has 'out of the box' support for a huge number of emulators including vanilla DOSBox and can automatically import DOSBox games. I tend to not use that feature as I have many configuration files for each game due to testing and trying things out, and don't want to create lots of spurious game entries but it is available if you wish to try it. As for modern DOSBox variants, this article will be covering those! Before we begin It's useful to cover a few points before we begin. Where can Playnite be obtained? The latest version of Playnite is available from the Playnite website. Installation should be straightforward and complete without issue. Where is Playnite installed? After installation Playnite can be found in the: C:\Users\\AppData\Local\Playnite folder, where is your Windows username. The AppData folder is hidden by default so you'll need to unhide this in File Explorer to make the changes described below. A note on the YAML file format The process involves editing YAML configuration files. With YAML files the indentation is meaningful which means you should use spaces instead of tabs for indentation . Tabs aren't allowed for indentation. You can read more about YAML on Wikipedia . Integration with DOSBox Staging Adding a new emulator spec The first thing we need to do is add a new emulator spec for DOSBox Staging, to do so: Go to the Playnite emulators folder at: C:\Users\\AppData\Local\Playnite\Emulation\Emulators Copy the existing DOSBox emulator folder and rename the copied folder to something appropriate, I chose DOSBoxStaging . Inside the new DOSBoxStaging folder there should be a single emulator.yaml file. Using a text editor, edit the file so it reads: Id: dosbox-staging Name: DOSBox Staging Website: ' https://dosbox-staging.github.io/ ' Profiles: - Name: Default StartupArguments: '-conf "{ImagePath}" -noconsole' Platforms: [pc_dos] StartupExecutable: ^dosbox\.exe$ ImageExtensions: [conf] Save the file and close your text editor. Adding the DOSBox Staging emulator With a new DOSBox Staging spec, a DOSBox Staging emulator can now be added: Open Playnite and go to the Playnite menu (looks like a console controller icon) and select ' Library ' and ' Configure Emulators... ' Add an emulator, I called it ' DOSBox Staging ' and set it up as shown below in the screenshot. You will have to specify your own DOSBox Staging installation folder. Make sure you choose the new DOSBox Staging emulator spec. Adding the DOSBox Staging emulator Integration with DOSBox-X The process is very similar to the integration with DOSBox Staging process. Adding a new emulator spec The first thing we need to do is add a new emulator spec for DOSBox-X, to do so: Go to the Playnite emulators folder at: C:\Users\\AppData\Local\Playnite\Emulation\Emulators Copy the existing DOSBox emulator folder and rename the copied folder to something appropriate, I chose DOSBox-X . Inside the new DOSBox-X folder there should be a single emulator.yaml file. Using a text editor, edit the file so it reads: Id: dosbox-x Name: DOSBox-X Website: 'https://www.dosbox-x.com/' Profiles: - Name: Default StartupArguments: '-conf "{ImagePath}" -noconsole' Platforms: [pc_dos] StartupExecutable: ^dosbox-x\.exe$ ImageExtensions: [conf] Save the file and close your text editor. Adding the DOSBox Staging emulator With a new DOSBox-X spec, a DOSBox-X emulator can now be added: Open Playnite and go to the Playnite menu (looks like a console controller icon) and select ' Library ' and ' Configure Emulators... ' Add an emulator, I called it ' DOSBox-X ' and set it up as shown below in the screenshot. You will have to specify your own DOSBox-X installation folder. Make sure you choose the new DOSBox-X emulator spec. Adding the DOSBox-X emulator You may notice I've also added a couple of custom profiles, these are profiles I used for testing and don't need to be added. Configuring a game This section won't cover all the steps of adding a game, just those steps necessary to configure a game to use the modern DOSBox emulators. If fairly new to Playnite, when setting up a game I would recommend getting it configured and working in DOSBox first and then configure it in Playnite. With a little experience it becomes a pretty simple process and normally I will configure DOSBox and Playnite at the same time as I setup a new game! Manually added game In this example the game F-15 Strike Eagle III has been manually added. It uses my DOSBox game management strategy, so the game installation folder is D:\Games\Dos\F-15 Strike Eagle III. When configuring the game manually this installation folder should be specified as shown below: F-15 Strike Eagle III Installation tab We can now create the actions to run the game from either DOSBox Staging or DOSBox-X using the actions tab shown below. We can also use the Playnite variable {InstallDir} as the installation folder has been specified, so we don't have to specify the entire path to the relevant DOSBox config file. F-15 Strike Eagle III Actions tab Library imported game In this example F-19 Stealth fighter has been imported from my gog library. In this case the installation folder is the gog installation folder. F-19 Stealth Fighter Installation tab We can now create the actions to run the game from either DOSBox Staging or DOSBox-X using the Actions tab shown below. Even when the game is installed via Steam or gog, I use my DOSBox game management strategy to store DOSBox configs, TM Target configs, patches and additional docs not provided by Steam or gog. So in this case all my F-19 Stealth Fighter files not provided by Steam or gog will be under the D:\Games\Dos\F-19 Stealth Fighter folder. The DOSBox config files sit in a conf folder, so this time the entire path to the DOSBox config file must be specified. F-19 Stealth Fighter Actions tab Integrating 'DOSBox-X with Glide wrapper' (Advanced) This is a bit of an advanced topic so if you're just starting out with Playnite you may wish to skip it for now and return later when you've got a bit more experience with adding games. It also requires an understanding of the concepts covered in the earlier ' Glide Wrappers: Last Man Standing or Peace and Harmony? ' article. Adding 'DOSBox-X with Glide wrapper' This section assumes you've created a DOSBox-X folder and added a local Glide wrapper as described in the earlier ' Glide Wrappers: Last Man Standing or Peace and Harmony? ' article, specifically the ' Can DOSBox-X use different versions of nGlide? ' and ' How would DOSBox-X use dgVoodoo2? ' sections. As DOSBox-X is still being used, the existing DOXBox-X emulator spec can still be used, so there is no need to create a new spec. However a new emulator is required and can be added with the steps: Open Playnite and go to the Playnite menu (looks like a console controller icon) and select ' Library ' and ' Configure Emulators... ' Add an emulator, I called it ' DOSBox-X with ' and set it up as shown below in the screenshot. You will have to specify your own 'DOSBox-X with wrapper' installation folder. Make sure you choose the DOSBox-X emulator spec. Adding a DOSBox-X with Glide wrapper emulator As you can see the process is very similar to adding the DOSBox-X emulator. In the above example the ' -noconsole ' custom argument was omitted for testing purposes, but can be added back in once confirmed to be working. Configuring a game In this example the game JetFighter III Classic has been manually added. It uses my DOSBox game management strategy, so the game installation folder is D:\Games\Dos\JetFighter 3. When configuring the game manually this installation folder should be specified as shown below: JetFighter III Classic Installation tab We can now create the actions to run the game from 'DOSBox-X with Glide wrapper' using the Actions tab shown below. As we have specified the installation folder the {InstallDir} variable can be used, similar to the F-15 Strike Eagle III example earlier. JetFighter III Classic Actions tab Finally... Hopefully this guide leaves you with your chosen modern variant of DOSBox configured and ready for use within Playnite, now start adding those games! Good configuring!
- Falcon 3.0: Running Gold Falcon Utilities in DOSBox Staging
GFU Menu The Gold Falcon Utilities (GFU) are a collection of shareware utilities design to enhance the Falcon experience. Compatible with Falcon and the expansions MiG-29 and Hornet, you can read more about it in the earlier ' Falcon 3.0: Unofficial mods & tools ' article. A quick description of the utilities, taken from the GFU readme: The GOLD FALCON UTILITIES is a set of irreplaceable helpers for the Spectrum Holobyte(r) family of flight simulators! Formerly commercial, now shareware, they include the latest versions FalcCalc, F3Maps, F3Requisition, Show F3, and GFU Menu. This fully integrated package brings out many of the best features of Falcon 3.0(t), MiG-29(t), and Hornet(t). Although the other utilities worked, the GFU Menu utility which tied them all together in an integrated package would generate an error when run under DOSBox Staging and other modern DOSBox variants. Thanks to VOGONS members rfnagel, for highlighting the issue and ripsaw8080 for coming up with a workaround, now the GFU Menu utility can be made to work with DOSBox Staging. So a big thank you to both for their work on this! This guide will cover installation and setup of the Gold Falcon Utilities to work under DOSBox Staging. Before we begin The GFU installer will add files to your Falcon installation folder so it is recommended to take a backup copy of this folder, in case you run into issues. Using the DarkMenu If you use my DarkMenu to run Falcon then you'll want to grab the latest version which has been amended, with the 'Quit' option replaced with 'Exit to DOS' and 'Quit DOSBox' options. The 'Exit to DOS' option will be useful to get back to a DOS prompt to install GFU. The latest version can be found in the ' Falcon 3.0: Operation DOSBox Staging ' article. Obtaining Gold Falcon Utilities A download link to the Gold Falcon Utilities zip archive can be found in the earlier ' Falcon 3.0: Unofficial mods & tools ' article. Installation and setup The installation steps are as follows: Create a folder under the DOSBox Staging mounted C: drive folder, to hold the GFU installation files. In my case I created a GFUINST folder, as I use my DOSBox game management strategy I ended up with D:\Games\Dos\Falcon Gold\hdd\GFUINST. Extract the GFU installation files from the zip archive into your GFU installation folder. Start a DOSBox Staging session for Falcon, go to the GFU installation folder and run the GFU installer ( install.exe ). Follow the installer instructions, I recommend using the default installation folder, C:\GFU as suggested by the installer. The installation should complete without issue. The GFUINST folder is no longer needed and can be deleted, but I recommend keeping it in case you need to install GFU again. If you try and run the GFU Menu ( gfu.bat ), you will probably see an error similar to: Path not found in module GFUMENU at address 0255:6987 To avoid this error, create a DEV folder under the DOSBox Staging mounted C: drive folder, you can exit DOSBox and do this in Windows or within DOSBox if you're familiar with DOS commands. In my case I ended up with: D:\Games\Dos\Falcon Gold\hdd\DEV. Start a DOSBox Staging session for Falcon, if needed. Go to the GFU folder and run the GFU Menu ( gfu.bat ). The GFU Menu should now start successfully. Try running one of the utilities. If you are returned to the DOS prompt there is an additional step to take. Go to the GFU folder and run the setup batch file ( run.bat ). This resets a GFU setting and then deletes itself, so it's a run once batch file. The utilities should now run from GFU Menu without issue. Note : The first time you run some of the utilities, they may ask you to specify your Falcon folder. Setting up a text editor The GFU Menu utility has the ability to run the default DOS text editor ( edit.com ). However this is not available in DOSBox Staging, so a different editor needs to be obtained and configured in GFU Menu. I recommend the FreeDOS text editor, 'FreeDOS Edit' ( edit.exe ). It can be downloaded from the FreeDOS Edit page. At present I've not spent a lot of time on the GFU utilities, so I'm not sure if this is a 'required' facility of GFU Menu and the other utilities, or more of a 'nice to have' facility. So this part of the setup may be more optional than absolutely required. Installation Create a folder under the DOSBox Staging mounted C: drive folder, to hold the FreeDOS Edit files. In my case I created a DOS folder, so I ended up with: D:\Games\Dos\Falcon Gold\hdd\DOS. Extract the FreeDOS Edit zip archive to this folder. It should now contain edit.exe and edit.hlp . DOSBox Staging config changes If you try and run the editor from a folder in which it doesn't exist, it will fail to run. e.g. If you go the Falcon folder and try and open one of readme files with the editor, it will fail as the editor is in the DOS folder not the Falcon folder. To resolve this issue, the DOSBox path environment variable is extended to search for files (including the editor) in the new DOS folder. Below is a DOSBox Staging config fragment showing the required path change in the [autoexec] section: [autoexec] mount c "D:\Games\Dos\Falcon Gold\hdd" imgmount d "D:\Games\Dos\Falcon Gold\cd\FalconGold.iso" set path=%path%;c:\dos c: cd falconcd call darkmenu.bat GFU Menu config change GFU Menu Edit Configuration File page The final step is to change the GFU Menu config to use FreeDOS Edit ( edit.exe ) rather than the default DOS Edit ( edit.com ). Open GFU Menu. Go to the 'Config' menu. Select the 'Edit Configuration File' option. On the 'Edit Configuration File' page change the 'Ascii Text Editor' field to EDIT.EXE (as shown in the screenshot). Exit and save. Running GFU Menu Once setup is complete running the GFU Menu is straightforward. Simply get to the DOSBox DOS prompt and from the C: drive top level folder, use the following commands: C:\> cd gfu C:\GFU> gfu So that should be the Gold Falcon Utilities fully working under DOSBox Staging. They provide a lot of additional help and info when running campaigns, a very useful addition for any Falcon fans! Good campaigning!
- TFX (Tactical Fighter eXperiment) in DOSBox Staging
The second of Digital Image Designs (DID) flight sims is TFX: Tactical Fighter eXperiment, the first being F29 Retaliator, with future flight sims being the classic EF2000 and F-22 series. Remembered fondly by fans as a graphically impressive flight sim for 1993. This guide will cover running TFX under DOSBox Staging emulation. Versions The original retail release version of TFX, was developed by DID and published by Ocean in 1993. The original release was distributed on 8 x 3.5" 1.44Mb High Density (HD) Floppy Disks or a single cd-rom. The cd-rom version would be re-released, pre-patched to version 2.05. This version does not require patching. Versions numbers are only shown in the configuration utility (see Patching below). A cd-rom release is recommended as this includes cd music, is easier to install and may not require patching. CD images This guide assumes the cd will be ripped to a cd image. This saves wear and tear on the disc and the drive. The cd-rom should be ripped into a bin/cue image pair to preserve the red book cd music present on the disc. HOTAS config As it is a DOS based sim a maximum of 4 axes are supported although only 3 will be used by TFX. When using HOTAS/controller profiling software to limit the controller to a maximum of 4 axes the following device axes to Windows axes mappings were used: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_XROT_AXIS DOSBox Staging config This DOSBox Staging config for TFX assumes the latest version, 0.82.0 will be used. The changes to the default config are shown below: [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] cpu_cycles = 30000 cpu_cycles_protected = auto cycleup = 100 cycledown = 100 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = off chorus = off [midi] mididevice = mt32 [mt32] model = auto romdir = "D:\Midi\Versioned" [joystick] joysticktype = ch timed = true swap34 = true deadzone = 0 [autoexec] imgmount d "D:\Games\Dos\TFX\cd\TFX.cue" -t cdrom mount c "D:\Games\Dos\TFX\hdd" mixer mt32 50:50 mixer cdaudio 50:50 c: cd tfx call tfx.bat exit The [sdl], [dosbox] and [mouse] settings are suitable for high frame rate gaming as described in this article by Omniclyde. These settings aren't strictly required and can be omitted to use the default settings. In [cpu] settings, 30000 cycles seems appropriate, you may need to tweak this setting but this seems like a good starting point. The cpu_cycles_protected setting will use the same cycle count as cpu_cycles. Voodoo emulation isn't required and can be disabled. The [mixer] settings can be changed to enhance sound and music to personal preference. My personal preference is to use the default chorus and reverb settings to prevent the music from overpowering other sounds. The [midi] and [mt32] settings enable high quality Roland midi music. The model value, auto, will default to a CM32L device. TFX supports the LAPC1 sound card which is equivalent to a CM32L device. The midi roms folder is described in the DOSBox midi article. The [joystick] settings are specific to TFX. The ch joystick type corresponds to the CH FlightStick which is supported by TFX. The timed and swap34 setting must be true to allow the throttle to be used. The deadzone setting is a personal preference. The [autoexec] has example imgmount commands for a cd image. The imgmount and mount commands make use of a folder structure described in my DOSBox game management article. The mixer commands reduce the volume of the Roland midi music and cd music to prevent the music from overpowering other sounds, this is a personal preference. The remaining commands will go to the TFX folder, run TFX and close DOSBox once the game is quit. They can be used once TFX is installed and configured. Installation Installation should be performed within DOSBox using the install utility on the cd (image) or floppy disk (image). Once complete the installer may begin configuring the game (see Setup below). The installer may also suggest copying the did.dat file and tfx.bat file to the TFX installation folder, if there is sufficient disk space (see below). Optimisation The did.dat file is approximately 11Mb in size and the cd installer utility will leave this file on the cd (image) and suggest manually copying it to the TFX installation folder, only if there is sufficient disk space. These days this is not an issue so the file can be manually copied. The tfx.bat file is a amended batch file that no longer uses the did.dat file on the cd. This batch file may be present on the cd and can be copied to the TFX folder, replacing the previous tfx.bat file. If not the command in the batch file should change as follows, from: start DID=D: tfx with the start executable told to use the did.dat file on the D: cd drive, to: start tfx with the start executable using the did.dat file from the current folder. The DOS4G extender library is used by the config utility, but not the game. Therefore, even though it is possible to replace the extender library with a newer version, it is probably not worth doing so, given how infrequently the config utility will be used. Patching ABOUT page with version number There were three patches released for TFX with separate patches for floppy disk and cd-rom releases. The patches are not cumulative , each patch must be installed in order. Some later cd-rom re-releases may already be patched but the version number isn't shown in-game. However in the config utility (see Setup ) the 'ABOUT' button shows an information page, including the version number. Patches are not required for version 2.05. Patch 1 This is a bug fix patch which fixes the "unexpected interrupt" error message due to hardware conflict. It should fix most other unexplained crashes. The floppy disk patch ( tfxpat_1.zip ) and cd patch ( tfxcd_1.zip ) can be found at the Internet Archive. Patch 2 An enhancement patch to take TFX to version 2.0, although the patch doesn't list any changes. The floppy disk patch ( tfxpat_2.zip ) and cd patch ( tfxcd_2.zip ) can be found at the Internet Archive. Patch 3 This patch has no associated readme file, so it isn't known what this patch does. The floppy disk patch ( tfxpat_3.zip ) and cd patch ( tfxcd_3.zip ) can be found at the Internet Archive. Setup Config utility Some of the installer apps will automatically start the config utility ( config.exe ), once installation is complete. The config utility can also be run at any time to change config options. The options should be set as follows: The swap file should be turned OFF. The control method is set to JOYSTICK. The detail level is set to HIGH. The flight model can be set to MILITARY SPEC or reduced as a personal preference. Sound FX hardware is set to SB16. Music hardware is set to LAPC1 for Roland midi music or SB/CD for Soundblaster/CD music. Joystick type is set to FLIGHTSTICK PRO. Language is personal preference. In addition the 'CONF JOYSTICK' button should be used to calibrate the throttle and joystick. Running In flight options When 'in flight' there is an alternative configuration page available. This page has a joystick scale/sensitivity option. The flight controls, world detail and flight model are the same options as shown in the config utility. There are simplified sound and music options and additional options listed under the REALISM MENU page. These options are down to personal preference. Documentation TFX in DOSBox Staging The following documents can be found on various websites: The manual in pdf format. The reference card as an image. The Amiga version of the game never had a retail release but was later released on a magazine cover disk. The magazine published two articles which some may find useful: A limited play guide for the Amiga version. A later guide covering weapon use and hints for other aspects of the sim. Good hunting!
- F-15 Strike Eagle II in DOSBox Staging
MicroProse well known for detailed deep sims was not adverse to making something lighter, and the result was F-15 Strike Eagle II. Based on the same engine as F-19 Stealth Fighter, it was less technical, more fly and fight. It was even converted into an arcade version. This guide will show you how to get the DOS version running in DOSBox Staging. Versions & expansions F-15 Strike Eagle II (Version 451.01) This was the initial retail release created and published by MicroProse in 1989. It was distributed on either 2 x 5.25" 360k Double Density (DD) floppy disks or a single 3.5" 720k DD floppy disk. F-15 Strike Eagle II (Version 451.02) A re-release version was published by MicroProse in 1990. This release included a number of number of bug fixes but no additional enhancements. If F-19 Stealth Fighter was also owned, the North Cape and Central Europe theaters could be imported into either version. Instructions for doing so were included in the technical supplement document. F-15 Strike Eagle II: Operation Desert Storm Scenario Disk (Version 451.03) The one and only expansion disk was published by MicroProse in 1992. This release included the Desert Storm theater and the North Cape and Central Europe theaters that were originally created for F-19 Stealth Fighter. In addition the Roland sound driver and updated Adlib drivers were included, as well as a small number of bug fixes. This release was a cumulative release, including the bug fixes from v451.02. Later re-releases, like the Deluxe Edition would include the base game and scenario disk as a compilation. A pattern also repeated with later cd-rom releases. The Deluxe Edition or later cd-rom releases are recommended as most patches have already been included, simplifying installation. Patches All patches are available within an archive of the MicroProse FTP site on the Internet Archive. Roland patch (mpsrol.zip) The Roland sound patch added the Roland sound drivers to a number of earlier MicroProse titles that were initially released without Roland support. This patch is only required for v451.01 or v451.02. Version 451.03 includes Roland sound drivers. 486 Sound patch (486snd.zip) The 486 Sound patch fixed speed sensitive sound issues for the Adlib drivers across a number of MicroProse titles. It also fixed OPL3 stereo issues on Soundblaster cards for some titles, but not F-15 SE2. This patch is only required for v451.01 or v451.02 experiencing sound issues but is recommended as it allows higher cycles to be used/tested in DOSBox. Version 451.03 already includes improved Adlib drivers. Adlib drivers patch (mpsadl.zip) This was a simple patch to increase engine volume for the Adlib drivers. It isn't recommended, but is left to personal preference. Key Disk Eliminator patch (f152key.zip) Following the release of F-15 Strike Eagle III, the Key Disk Eliminator patch was released to remove key disk copy protection, requiring an original retail floppy disk to be present. This is a file replacement patch, requiring a v451.02 or v451.03 copy of the f15.com file to replace the original. Later cd releases would have this copy protection removed. This is not recommended as it was superseded by the Pentium patch. Pentium Update patch (p5upd.zip) Following the introduction of fast 486 and Pentium class machines the Pentium patch was released ro reduce the speed sensitivity of earlier titles. This patch effectively superseded any key disk patches, as it is a file replacement patch with the copy protection removed. There are two files present for F-15 SE2, one per version. One file should be renamed to f15.com and used to replace the original f15.com file: f15v2.com is for v451.02. f15v3.com is for v451.03. This is a recommended patch. Controller setup The game only supports the Joystick x and y axes. However, if your controller has more axes and you are unable to disable the additional axes, then configuring them as shown below, as a '4axis' joystick device will allow DOSBox to correctly map the axes. Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_XROT_AXIS If you only have a 2 axis controller or can disable additional axes then you only need to define the Joystick axes. DOSBox Staging configuration The following config is suitable for DOSBox Staging v0.82.0. The settings below differ from the default configuration. [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [cpu] cpu_cycles = 8000 cpu_cycles_protected = auto cycleup = 100 cycledown = 100 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = large chorus = normal [midi] mididevice = mt32 [mt32] model = mt32_new romdir = "D:\Midi\Versioned" [sblaster] sbtype = sbpro1 [joystick] joysticktype = 4axis timed = false deadzone = 0 [autoexec] imgmount a "D:\Games\Dos\F15 Strike Eagle II\fdd\disk1.img" -t floppy -ro imgmount d "D:\Games\Dos\F15 Strike Eagle II\cd\f15.iso" -t cdrom mount c "D:\Games\Dos\F15 Strike Eagle II\hdd" loadfix c: cd mps/f15 f15.com /J /GM /D3 /AR exit The [sdl], [dosbox] and [mouse] settings are suitable for high frame rate gaming as described in this article by Omniclyde. These settings aren't strictly required and can be omitted to use the default settings. 8000 cycles seems appropriate, you may need to tweak this setting but 6000-8000 cycles seems like a good starting point. The higher the cycle count the higher the accuracy needed to make a gun kill, in addition ineffective hits by Mavericks seem to increase. Voodoo emulation isn't required and can be disabled. The [mixer] settings are a personal preference to enhance sound and music. The [midi] and [mt32] settings are based on info from the VOGONS wiki article ' List of MT-32-compatible computer games '. The rom folder needs to be specified, as described in DOSBox midi . In the [sblaster] section, the sbtype is changed to a Soundblaster Pro, this is to take advantage of stereo audio provided by (emulated) dual OPL chips, as described in the VOGONS wiki article. The [joystick] settings use a 4axis joystick type, as I'm using a 4 axes virtual controller, and this will help DOSBox assign axes correctly. If you only have a 2 axes controller or your device(s) allows unused axes to be disabled, then this could be changed to a 2axis joystick type. If you experience joystick drift, you may wish to change the timed setting. The deadzone is a personal preference. The [autoexec] has example imgmount commands for a floppy disk image and a cd image. The imgmount and mount commands make use of a folder structure described in my DOSBox game management article. The loadfix command is required to limit the amount of conventional memory. This is often needed by early DOS games. The f15.com command is run with command line switches to set various options. These are described in the Setup section below. The exit command will close DOSBox once the game is quit. Vanilla settings These are the additional settings required to play original unpatched versions without the recommended patch(es). [cpu] core = normal cputype = 386_prefetch The [cpu] settings have been found to be the most compatible with disk or cd based releases. The cd releases in particular seem to require the 386_prefetch cpu type which in turn requires the normal DOSBox core. Without these settings the f15.com command seems to freeze, if not patched with the Pentium update patch. Installation Installation will depend on your particular release, the disk based releases normally come with an install utility (e.g. install.exe) to install to hard disk. Any installation utilities should be run using DOSBox. Some of the cd releases lack this, requiring the F-15 folder on the cd to be copied to the hard disk or run the game from the cd (or cd image). It's recommended to copy the appropriate folder to the DOSBox hard disk folder and run the game from there. Once installed it's recommended to install the Pentium Update patch with DOSBox. Setup There is no separate setup utility with setup options being specified on the command line or through menus when the game is started. Detail level, graphics, sound and controls are all configured this way. The technical supplement document contains a list of setup options, shown below: /J if you use a joystick /NJ if you use a keyboard without a joystick /GE if you use EGA 16-color graphics /GM if you use MGCA or VGA 256-color graphics /GC if you use CGA 4-color graphics /GT if you use Tandy 1000 16-color graphics /GH if you use Hercules monochrome graphics /D3 to invoke detail level 3 /D2 to invoke detail level 2 /D1 to invoke detail level 1 /D0 to invoke detail level 0 /AA invokes the Ad Lib sound driver /AT invokes the Tandy sound driver /A? replace the ? with the code of the sound driver you want The command I use to start the game with Roland sound becomes: f15.com /J /GM /D3 /AR Documentation There are a number of useful documents, available from various websites, for F-15 Strike Eagle II, these include: The F-15 Strike Eagle II manual. The HUD and keyboard reference card. The technical supplement. The Operation Desert Storm expansion manual. ONC maps of Libya, Persian Gulf, Vietnam and Middle East theaters. In addition, the strategy guide, The Official F-15 Strike Eagle Handbook by Richard Sheffield is available digitally at FlightSimBooks.com . Miscellaneous Some releases of the game included a demo app ( demo.exe ) which provides a slideshow of what were the future Gunship 2000 and F-117A Nighthawk Stealth Fighter 2.0 titles. You may need to drop the cycles to a lower value to give yourself time to view the short slideshow. Good hunting!
- Tech refresh 2025: F/A-Hornet 2.0
This is a tech refresh article describing any changes since the original article ' A sting in the tail: F/A-18 Hornet 2.0 ' was published. Updated emulation will be examined along with any resulting changes. The optimised settings in the article ' F/A-Hornet 2.0: Optimum settings ' remain valid. Much of this article will be identical to the earlier F/A-18 Hornet tech refresh article. Joystick setup The original article suggested mapping the mouse x/y axes to the joystick x/y axes which although correct, lacked detail. The joystick axes to Windows axes mappings are shown below: Physical axis Windows axis Joystick x-axis MOUSE_X_AXIS Joystick y-axis MOUSE_Y_AXIS Only the joystick axes are supported. It is recommended to use throttle buttons to control the throttle power. This mapping should be placed in your HOTAS profile software or Joystick Gremlin. SheepShaver At time of writing the latest version of SheepShaver is SheepShaver-Windows-20-10-2024 . This new version still fails to run the flight engine of F/A-18 Hornet 2.0, however the original article suggested using SheepShaver as a far easier way of transferring software onto a Qemu emulated hard disk. The upgrade info is included below so as to reduce the number of SheepShaver installations. When published the latest version was SheepShaver-Windows-27-08-2023-framebuffer . To upgrade the settings shown in the SheepShaverGUI app should be copied from the older version to the newer version. This will allow the existing emulated Mac to be run. If creating an emulated Mac or installing the game, the existing advice in the article ' A sting in the tail: F/A-18 Hornet 2.0 ' should continue to be followed. Keycodes The keycodes facility of SheepShaver has been improved to support both ANSI and ISO keyboards. Within the Keyboard/Mouse tab of the SheepShaverGUI app either the keycodes_ansi or keycodes_iso file should be chosen, depending on your keyboard. You should also take the opportunity to check the keyboard layout with the Keycaps app within the emulated Mac. Qemu m68k The recommended version of Qemu for single or multi-monitor emulation remains Qemu-m68k-Win64-qfb-experimental-05-10-2022 . Later versions of Qemu, including later version of the experimental multi-monitor version all suffer from the same issue. Using SDL as the rendering engine, the Windows key is not handled properly as a modifier key and cannot be held down. This affects the sim as the Windows key is used as the Mac cmd key. The issue is known to affect the following versions: Qemu-system-m68k-Win64-06-10-2023 Qemu-system-m68k-8.2-Win64-20-12-2023 Qemu-m68k-Win64-qfb-experimental-26-12-2023 Qemu-system-m68k-9.0-Win64-24-04-2024 If creating an emulated Mac or installing the game, the existing advice in the article ' A sting in the tail: F/A-18 Hornet 2.0 ' should continue to be followed. Old versions of the builds are not hosted at the Emaculation website, but I've been kindly allowed to host the old experimental build here, so a big thank you to Cat_7 and the people at Emaculation, (this version has been superseded, see the update below). Update : A brand new version of the experimental multi-monitor build has been created by Cat_7. The latest version is qemu-system-m68k-9.2-Win64-qfb-experimental-28-12-2024 and can be found on the Emaculation forums . This version correctly handles the Windows key as a modifier. MAME The original article was published when the current version of MAME was v0.260 . The current version of MAME is v0.272, available at the MAME download page . The download is a self extracting exe file, open the self extracting exe and choose a folder. Once installed the following files/folders should be copied from your original MAME installation folder into your new MAME folder: cfg folder diff folder nvram folder roms folder If you are using the MacFlight plugin, it should be copied from your original MAME plugins folder to your new MAME plugins folder. Any batch (.bat) files created. Any hard disk images in a .chd (compressed hunks of data) format . The Mac Quadra 800 ini file (macqd800.ini). Run the MAME executable once to recreate any other necessary .ini files. You should then be able to start the an emulated Mac using the new version of MAME with the batch files in the new MAME folder. The advice to create a new virtual Mac with MAME and installing F/A-18 Hornet 2.0 remains unchanged. The ScrLk key will continue to enable/disable the MAME UI and the Tab key will open/close the MAME config menu. Using the MacFlight plugin The MacFlight plugin continues to work with MAME v0.272. The advice in the article ' MacFlight: A MAME plugin for retro Mac flight sims ' should continue to be followed. The MacFlight plugin will attempt to identify any connected joysticks, so the above joystick mapping is not required if using the plugin, however you may still create a virtual controller for button mappings if required. The plugin should find your virtual device. It's worth noting that the role of MacFlight plugin was to convert joystick input into an appropriate mouse input for Mac flight sims. It does not control any button mappings, only the joystick x and y axes. Rather than duplicate functionality, the comprehensive facilities provided by your HOTAS profile software, Joystick Gremlin or the MAME control settings should be used to map HOTAS buttons. Good hunting!
- Tech refresh 2025: F/A-18 Hornet
This is a tech refresh article describing any changes since the original article ' Just deserts: F/A-18 Hornet Classic ' was published. Updated emulation will be examined along with any resulting changes. Versions When the original article was written, only the PowerPC version of the game was widely available, F/A-18 Hornet Classic (equivalent to v1.12). However F/A-18 Hornet v1.1 became available, this meant this version of the game could be patched to the final beta version, becoming F/A-18 Hornet v1.13b2 for the m68k architecture Macs. As the PPC architecture Macs were backwardly compatible with m68k Macs both versions of the game can be run with SheepShaver. All patches can be found at the Macintosh Repository . Joystick setup The original article suggested mapping the mouse x/y axes to the joystick x/y axes which although correct, lacked detail. The joystick axes to Windows axes mappings are shown below: Physical axis Windows axis Joystick x-axis MOUSE_X_AXIS Joystick y-axis MOUSE_Y_AXIS Only the joystick axes are supported. It is recommended to use throttle buttons to control the throttle power. This mapping should be placed in your HOTAS profile software or Joystick Gremlin. SheepShaver At time of writing the latest version of SheepShaver is SheepShaver-Windows-20-10-2024 . When published the latest version was SheepShaver-Windows-27-08-2023-framebuffer . To upgrade the settings shown in the SheepShaverGUI app should be copied from the older version to the newer version. This will allow the existing emulated Mac to be run and allow the game to be played. If creating an emulated Mac or installing the game, the existing advice in the article ' Just deserts: F/A-18 Hornet Classic ' should continue to be followed. Keycodes The keycodes facility of SheepShaver has been improved to support both ANSI and ISO keyboards. Within the Keyboard/Mouse tab of the SheepShaverGUI app either the keycodes_ansi or keycodes_iso file should be chosen, depending on your keyboard. You should also take the opportunity to check the keyboard layout with the Keycaps app within the emulated Mac. Qemu m68k The recommended version of Qemu for multi-monitor emulation remains Qemu-m68k-Win64-qfb-experimental-05-10-2022 . Later versions of Qemu, including later version of the experimental multi-monitor version all suffer from the same issue. Using SDL as the rendering engine, the Windows key is not handled properly as a modifier key and cannot be held down. This affects the sim as the Windows key is used as the Mac cmd key. The issue is known to affect the following versions: Qemu-system-m68k-Win64-06-10-2023 Qemu-system-m68k-8.2-Win64-20-12-2023 Qemu-m68k-Win64-qfb-experimental-26-12-2023 Qemu-system-m68k-9.0-Win64-24-04-2024 Old versions of the builds are not hosted at the Emaculation website, but I've been kindly allowed to host the old experimental build here, so a big thank you to Cat_7 and the people at Emaculation (this version has been superseded, see the update below). Update : A brand new version of the experimental multi-monitor build has been created by Cat_7. The latest version is qemu-system-m68k-9.2-Win64-qfb-experimental-28-12-2024 and can be found on the Emaculation forums . This version correctly handles the Windows key as a modifier. MAME The original article was published when the current version of MAME was v0.260 . The current version of MAME is v0.272, available at the MAME download page . The download is a self extracting exe file, open the self extracting exe and choose a folder. Once installed the following files/folders should be copied from your original MAME installation folder into your new MAME folder: cfg folder diff folder nvram folder roms folder If you are using the MacFlight plugin, it should be copied from your original MAME plugins folder to your new MAME plugins folder. Any batch (.bat) files created. Any hard disk images in a .chd (compressed hunks of data) format . The Mac Quadra 800 ini file (macqd800.ini). Run the MAME executable once to recreate any other necessary .ini files. You should then be able to start the an emulated Mac using the new version of MAME with the batch files in the new MAME folder. The advice to create a new virtual Mac with MAME and installing F/A-18 Hornet remains unchanged. The ScrLk key will continue to enable/disable the MAME UI and the Tab key will open/close the MAME config menu. Using the MacFlight plugin The MacFlight plugin continues to work with MAME v0.272. The advice in the article ' MacFlight: A MAME plugin for retro Mac flight sims ' should continue to be followed. The MacFlight plugin will attempt to identify any connected joysticks, so the above joystick mapping is not required if using the plugin, however you may still create a virtual controller for button mappings if required. The plugin should find your virtual device. It's worth noting that the role of MacFlight plugin was to convert joystick input into an appropriate mouse input for Mac flight sims. It does not control any button mappings, only the joystick x and y axes. Rather than duplicate functionality, the comprehensive facilities provided by your HOTAS profile software, Joystick Gremlin or the MAME control settings should be used to map HOTAS buttons. Good hunting!
- Tech refresh 2025: Tornado
This is a tech refresh article describing any changes since the original article, ' The Tornado (Digital Integration) guide ' was published. Since the original article the version of DOSBox Staging has changed from v 0.81.2 to v0.82.0. The only change is an updated DOSBox Staging configuration shown below, the rest of the advice in the previous articles remains valid. DOSBox Staging configuration These are the settings which differ from the DOSBox Staging defaults. [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] memsize = 31 dos_rate = 1000 [cpu] cpu_cycles = 20000 cpu_cycles_protected = auto cycleup = 1000 cycledown = 1000 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = large chorus = normmal [midi] mididevice = mt32 [mt32] model = mt32_new romdir = "D:\Midi\Versioned" [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 [autoexec] mount c "D:\Games\Dos\Tornado\hdd" C: call go.bat pause exit The sdl settings are appropriate for a variable refresh rate monitor. They can be left as default or omitted for standard monitors. The sdl, dos_rate and mouse settings are also applicable for high frame rates as described in this article by Omnicycle. The voodoo emulation is disabled as it isn't required. The mixer settings are a personal preference to enhance the music and audio. The midi and mt32 sections allow both Soundblaster and MT32 to be used in the sim for an optimum audio experience. Joystick settings will be dependant on your particular HOTAS setup and may require adjustment. Good hunting!
- Tech refresh 2025: Wing Commander: Privateer
This is a tech refresh article describing any changes since the original article, ' Running Wing Commander: Privateer in DOSBox Staging ' was published. Since the original article the version of DOSBox Staging has changed from v 0.81.2 to v0.82.0 and a revised config is shown below. The rest of the article remains valid and provides background for many of these settings. DOSBox Staging configuration These are the settings which differ from the DOSBox Staging defaults. [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] memsize = 64 dos_rate = 1000 [render] viewport = 89% [cpu] cpu_cycles = 12000 cpu_cycles_protected = auto cycleup = 100 cycledown = 100 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = large chorus = normal [midi] mididevice = fluidsynth # mididevice = mt32 [fluidsynth] soundfont = "D:\Midi\Soundfonts\Shan SGM-X48 v1.0.SF2" [mt32] model = cm32l romdir = "D:\Midi\Versioned" [sblaster] irq = 5 [joystick] joysticktype = 4axis timed = true swap34 = false deadzone = 0 [dos] ems = false [autoexec] mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer" mount C "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\cloud_saves" -t overlay imgmount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander Privateer\game.gog" -t iso -fs iso mixer FSYNTH 33:33 c: call gog-menu.bat The sdl settings are appropriate for a variable refresh rate monitor. They can be left as default or omitted for standard monitors. The sdl, dos_rate and mouse settings are also applicable for high frame rates as described in this article by Omnicycle. The voodoo emulation is disabled as it isn't required. The mixer settings are a personal preference to enhance the music and audio. The midi setting include fluidsynth (enabled) and MT32 (disabled) allowing both to be tried if desired. Joystick settings will be dependant on your particular HOTAS setup and may require adjustment. In the autoexec section the mixer volumes are changed with the mixer command to a personal preference. The startup menu (gogmenu.bat) is used, as described in the previous article. Good hunting!











