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
- Pacific Strike: A simply magnetic sim!
Pacific Strike is the Origin WWII combat flight sim about the air war in the Pacific theater. It never received the same acclaim as the earlier Strike Commander despite being built with the same RealSpace engine. It wouldn't be until the later Wings of Glory that the engine would be given a substantial overhaul for later hardware. This game and speech pack expansion is only available on floppy disk, as the planned CD-ROM release was cancelled due to poor sales. The game also faced strong competition, as 1942: Pacific Air War was also released around the same time. Contents Strategy This guide will be trying to get Pacific Strike to run as optimally as possible under DOSBox Staging v0.83.0. This requires covering the version and patch history, creating a suitable DOSBox config and tools, covering the Sound Blaster sound and music, Roland MT-32 music and General MIDI music. A 4-axis HOTAS will be configured before the installation, patching and configuration steps are covered. Version and patch history Due to the cancellation of the CD-ROM edition there is a limited version and patch history for Pacific Strike. Its poor sales meant it wasn't included in compilations. Pacific Strike (April 1994) There was only a single Pacific Strike release in April 1994. Developed by Origin Systems and published by Electronic Arts. The game version is listed as F1.18 and the release notes are dated the 20 April 1994. The game was packaged as a multi-disk zip archive. The release notes are included below: It was distributed on: 9 x 1.44MB High Density (HD) 3.5" floppy disks. Pacific Strike: Speech Pack (April 1994) The one and only expansion was the Pacific Strike: Speech Pack released around the same time as the base game. It was developed by Origin Systems and published by Electronic Arts. The game version remains unchanged at F1.18. There are no release notes included with the speech files, however file timestamps indicate a date of March 1994. The expansion, like the base game, was packaged as a multi-disk zip archive. It was distributed on: 4 x 1.44MB High Density (HD) 3.5" floppy disks. F1.19 update patch (May 1994) The one and only patch was released in May 1994. It was a bug-fix patch fixing a variety of hardware and performance issues and also fixing various aspects of the game. The patch release notes are shown below: It was distributed as a zip archive, and remains available from: Internet Archive, Pacific Strike F1.19 Patch. Internet Archive, Pacific Strike Patch. Old-Games.RU, Games, Pacific Strike, Pacific Strike - files. The Patches Scrolls, Pacific Strike, Patches. The Patches Scrolls, Pacific Strike F1.19, Patches. WinRetro, Game, Pacific Strike. Documents Due to the relatively large number of different documents included with Pacific Strike the following list is broken down by document. The following documents are available digitally: Install Guide (pdf document, download). Pix's Origin Adventures, Download. Install Guide Changes (pdf document, download). Pix's Origin Adventures, Download. Errata Additions (pdf document, download). Pix's Origin Adventures, Download. Play Guide (pdf document, download). Internet Archive, PacificStrikePlayGuide. Old-Games.RU, Games, Pacific Strike, Pacific Strike - files. Pix's Origin Adventures, Download. Reference Card (pdf document, download). Internet Archive, PacificStrikeReferenceCard. Internet Archive, Retro Game Reference Material. Old-Games.RU, Games, Pacific Strike, Pacific Strike - files. Pix's Origin Adventures, Download. Reference Manual (pdf document, download). Internet Archive, PacificStrikeManual. Internet Archive, Retro Game Reference Material. Old-Games.RU, Games, Pacific Strike, Pacific Strike - files. Pix's Origin Adventures, Download. The above pdf documents are also available as a single zip archive from: Internet Archive, Files for 20230313, Docs, Pacific Strike (1994) (IBM PC) - Docs.zip. The following Pacific Strike: Speech Pack documents are available digitally: Speech Pack: Install Guide (pdf document, download). Pix's Origin Adventures, Download. The following strategy guides are available digitally: Playtesters' Guide (pdf document, download). Internet Archive, Pacific Strike Guide. Internet Archive, Retro Game Strategy Guides. Old-Games.RU, Games, Pacific Strike, Pacific Strike - files. Preparation This section covers the required preparation before installing or configuring the games under DOSBox. Retail media Due to the age of the media and the drives required to read them, it is recommended to rip floppy disks to either ima or img image files, to save wear and tear on media and the mechanical drives. Game management It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are: fdd - for floppy disk images. hdd - the folder used as the emulated DOSBox hard disk (see hdd folder). conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store patches. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\Pacific Strike DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed, with each game, having its own configuration file (with settings differing from the default configuration file). Config This config uses a combination of settings taken from the Strike Commander DOSBox config which uses the same RealSpace engine and from various snippets found in VOGONS threads or around the Internet. # This is the configuration file for Pacific Strike. [sdl] fullscreen = on [cpu] core = normal cpu_cycles = 35000 cpu_cycles_protected = auto cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = auto soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas midiconfig = 0 [joystick] joysticktype = ch timed = off swap34 = on deadzone = 0 [autoexec] @echo off # Example hdd folder mount mount c "D:\Games\Dos\Pacific Strike\hdd" # Example floppy disk mount mount a "D:\Games\Dos\Pacific Strike\fdd\*.img" -t floppy c: # Running the game # cd ps # pacific.exe # pause # exit # Running the launcher # call psmenu.bat This config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Pacific Strike/PacificStrike-staging.conf. In the [cpu] section the normal core is used, similar to Strike Commander. A recommended cycle count ranges from 20000 - 30000 cycles. 35000 seems to provide fairly smooth performance whilst allowing enemy aircraft to be destroyed. cpu_cycles_protected is set to auto to get its value from cpu_cycles. cycleup and cycledown are changed to values instead of percentages for consistent changes. In the [voodoo] section, emulation isn't required and is disabled. The [mixer] settings are an example and can be changed to a personal preference, however a small reverb and light chorus may be more suited to constant engine noise while in flight. Pacific Strike supports Roland MT-32 type devices. The recommended model, mt32_old, is taken from the VOGONS wiki article, List of MT-32-compatible computer games. Pacific Strike supports general MIDI so example settings are provided for the Sound Canvas, Fluidsynth and external (port) MIDI devices. See Sound for further details. The [midi] section is configured to use a Sound Canvas MIDI device by default. The midiconfig setting is only used by the external (port) device and is defaulted to 0. See Sound for further details. The [joystick] section has the joysticktype set to ch as the game supports the CH Flightstick Pro. This game also seems to benefit substantially by having timed intervals disabled. The swap34 setting and deadzone are examples appropriate for my controllers and personal preference, you may wish to adjust it. The [autoexec] section has example hard disk and floppy disk mount commands. There are examples for running the game from the DOS session or using the psmenu launcher tool. Tools A Pacific Strike launcher menu (psmenu.bat) has been created to simplify the following tasks: Running the game. Running the graphics and sound setup. Viewing the release notes. Save file backup and restore. Selecting a MIDI device: Roland MT-32, Sound Canvas, Fluidsynth or an external MIDI device. Returning to the DOSBox DOS prompt. Quitting DOSBox. The Pacific Strike launcher can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Pacific Strike/PSMENU.BAT. It should be extracted into the hdd folder. e.g. D:\Games\DOS\Pacific Strike\hdd (in Win10/11 becomes) C:\ (in DOSBox) Sound Pacific Strike supports Sound Blaster digital sound and Sound Blaster, Roland MT-32 or General MIDI music. Sound Blaster The default Sound Blaster settings set in the default DOSBox config are appropriate for Sound Blaster digital sound and music and do not require altering in the Pacific Strike DOSBox config. However, the following settings may be useful to refer to when configuring the game: Music Card: WaveBlaster/SB16 Port: 330 Speech Card: Sound Blaster PRO/SB16 Port: 220 IRQ: 7 DMA: 1 Roland Music The Roland music available when choosing the Roland option, uses a Roland standard rather than the General MIDI (GM) standard. Despite the install option for Roland music listed as Roland LAPC-1 (CM32L compatible), the recommended model is mt32_old, as taken from the VOGONS wiki article, List of MT-32-compatible computer games. The following settings enable the MT-32 synth and selects the MT-32 as the MIDI device. The romdir setting is an example folder using versioned ROMs; for more information, see Roland MT-32 in the DOSBox Staging user manual. [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 The following settings may be useful to refer to when configuring the game: Music Card: Roland LAPC-1 Port: 330 It is recommended to consult the Roland MT-32 page of the DOSBox Staging user manual. General MIDI The following settings apply to all MIDI devices below when configuring the game: Music Card: General MIDI Port: 330 Sound Canvas The following settings enable the Sound Canvas synth and selects the Sound Canvas as the MIDI device: [soundcanvas] soundcanvas_model = auto soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas The soundcanvas_rom_dir is an example only. It is recommended to consult the Roland Sound Canvas page of the DOSBox Staging user manual. Fluidsynth The following settings enable Fluidsynth and selects Fluidsynth as the MIDI device: [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [midi] mididevice = fluidsynth The soundfont and soundfont_dir are examples only. It is recommended to consult the Fluidsynth page of the DOSBox Staging user manual. External (port) The following settings enable an external (to DOSBox) MIDI synth and selects it as the MIDI device: [midi] mididevice = port midiconfig = 0 The midiconfig is an example only. It is recommended to consult the Using external MIDI devices section of the DOSBox Staging user manual. The following earlier articles cover using virtual software synths: DOSBox Staging and MIDI. VirtualMIDISynth and MIDIMapper. Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by Pacific Strike. [6][7][8]. 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 The following DOSBox config settings are suggested, depending on controller hardware: [joystick] joysticktype = ch timed = off Pacific Strike supports the CH Flightstick Pro so the ch joysticktype is used. The appropriate in-game joystick is covered by In-game configuration. Installation The order of installation is straightforward, with: Pacific Strike. Pacific Strike: Speech Pack. F1.19 update patch. Before the Pacific Strike installation can be run, loadfix must be used to reduce the amount of conventional memory, otherwise the installer app will fail. The following command should be issued: C:\> loadfix.com Then the installation app on the first mounted floppy disk image is run with: A:\> install.exe The following gallery shows the installation steps: It is recommended to use the default installation folder, PS. As the files are stored across a multi-disk zip archive, the installer reads the first disk, then last disk and then begins the install from the first disk. This means an installation requires considerable disk image swapping in DOSBox with F4. Once installation is complete, the memory allocated by loadfix can be freed with: C:\> loadfix.com -f Speech Pack installation The Speech Pack installation does not require any conventional memory to be allocated with loadfix. The installation app on the first mounted floppy disk image is run with: A:\> install.exe The following gallery shows the installation steps: The installation steps are similar to the base game, but don't require selecting a music card, speech card or local bus graphics card. As the files are stored across a multi-disk zip archive (like the base game), the installer reads the first disk, then last disk and then begins the install from the first disk. This means an installation requires disk image swapping in DOSBox with F4. Patching To apply the patch the following steps are required: In Win10/11, extract the contents of the patch to the Pacific Strike installation folder, e.g. D:\Games\DOS\Pacific Strike\hdd\PS In DOSBox, run the patch with: C:\PS> patch.exe Optional: Once the patch is installed the following patch files can be removed from the Pacific Strike installation folder: patch.exe patch.rtd patch.rtp This completes the Pacific Strike installation. Configuration The music and speech card configuration can be run from the Pacific Strike installation folder within DOSBox at any time with: C:\PS> install.exe In-game configuration In-game configuration is available while in-flight and accessed with O. Most options are left to personal preference but the gallery below shows the steps in calibrating a 4-axis HOTAS with stick, throttle and rudder. Once calibrated the Flight Ctrl and Panning Ctrl may return to the joystick option, but can be set back to FS Pro. Example video Pacific Strike in DOSBox Staging. Finally... Credit and thanks go to: Internet Archive for hosting the patch, Pacific Strike and strategy guide documents. Old-Games.RU for hosting the patch and Pacific Strike documents. The Patches Scrolls for hosting the patch. Pix's Origin Adventures for hosting Pacific Strike and Speech Pack documents. WinRetro for hosting the patch. Good hunting!
- Wing Commander I & II: Tinkering with Wing Commander
An earlier article covered running the original Wing Commander with the Wing Commander AllTinker (WCAT) mod, the optimum way to run this classic under DOSBox. The mod provided full stick, throttle and rudder support and the speed issues which had plagued the game for years were resolved. Now we have the first v1.0 release of not one but two WCAT mods one for the original Wing Commander and its sequel Wing Commander II: Vengeance of the Kilrathi. This seems like an ideal time to take a look at running both games as optimally as possible. Contents Strategy A brief analysis of the WCAT mods shows that both mods use the same DOSBox Staging config, so for this guide both Wing Commander and Wing Commander II: Vengeance of the Kilrathi (with optionally all expansions) will be installed onto the same DOSBox instance to create a compilation of deluxe editions. The WCAT Overhaul Mod is distributed in 3 releases (taken from the WCAT Overhaul Mod page): An automated installer for Windows (bundled with DOSBox Staging) which can locate an existing Wing Commander install (e.g. GOG, EA) and copy over the data files automatically. A zip file version, again bundled with DOSBox Staging. A minimal zip intended for real DOS, or custom DOSBox setups. It includes example DOSBox configs which will be useful to refer to in the latter case. This guide will be using the minimal install and providing a complementary DOSBox Staging config. This allows a single installed instance of DOSBox Staging to be used for this and many other DOS games. For the rest of the guide, the following abbreviations will be used: WC1: Wing Commander. SM1: Wing Commander: The Secret Missions. SM2: Wing Commander: The Secret Missions 2: Crusade. SM1.5: Secret Missions 1.5 WC2: Wing Commander II: Vengeance of the Kilrathi SAP: Wing Commander II: Vengeance of the Kilrathi: Speech Accessory Pack. SO1: Wing Commander II: Vengeance of the Kilrathi: Special Operations 1. SO2: Wing Commander II: Vengeance of the Kilrathi: Special Operations 2: Crusade. Version & patch history The version and patch history of WC1 and WC2 has been covered extensively in Wing Commander I & II: A primer. Once the available version is identified, the Patching strategies provide an overview of the steps required to install with the WCAT Overhaul Mod. Preparation This section covers tasks prior to configuring DOSBox or installing the game. Retail media Due to the age of the media and the drives required to read the media, it is recommended to rip floppy disks and CD-ROM media to image files to save wear and tear on media and the mechanical drives. The floppy disks should be ripped to a DOSBox compatible image format (.ima or .img). The CD-ROM can be ripped to a data-only iso image format as there is no CD audio on the disc. The bin/cue image format is also supported by DOSBox Staging. Game management It is recommended to use a game management strategy or similar method you may have adopted. The recommended game management folders are: cd - for any CD-ROM images. fdd - for any floppy disk images. hdd - the folder used as the emulated DOSBox hard disk. conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\Wing Commander 1+2 As both WC1 and WC2 are being installed to the same DOSBox hdd folder, the following sub-folders (in the hdd folder) are recommended: wc1 - for the Wing Commander game with WCAT Overhaul Mod. wc2 - for the Wing Commander II game with WCAT Overhaul Mod. DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working, and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed, with each game using DOSBox having its own configuration file (with settings differing from the default configuration file). The WCAT Overhaul Mod releases each supply a DOSBox Staging config compatible with DOSBox Staging v0.83.0. However, the below config is not a competing config but a complementary one, which is only compatible with DOSBox Staging v0.83.0-RC1 (release candidate) or v0.83.0 (release). The differences can be summarized as follows: The WCAT config is compatible with DOSBox Staging v0.83.0 and a wider range of earlier versions. It uses earlier conventions, true/false (still supported by v0.83.0) and explicitly specifies values which are defaults in v0.83.0 but are required for earlier versions. It is a highly compatible configuration. The config below is optimised for DOSBox Staging v0.83.0. It uses the current convention (on/off rather than true/false). It does not specify values which are defaults in v0.83.0. This makes it a minimal configuration (based on the WCAT configuration). Either can be used for v0.83.0-RC1 or v0.83.0 but the WCAT config should be used for earlier versions. Config Most of the settings below came from the WCAT config. Default settings in DOSBox Staging v0.83.0 have been omitted. # This is the DOSBox Staging 0.83.0 configuration for Wing Commander 1+2 using the WCAT Overhaul mod. [sdl] fullscreen = on [dosbox] memsize = 8 vmemsize = 1 [render] integer_scaling = off [cpu] cpu_cycles = 22000 [voodoo] voodoo = off [mouse] mouse_capture = onstart [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [sblaster] sbtype = sbpro2 [joystick] timed = off deadzone = 0 [dos] ems = on ver = 6.22 [autoexec] @echo off mount C "D:\Games\Dos\Wing Commander 1+2\hdd" mixer master 100 /noshow loadfix -32 c: This config can be found in the GitHub repository: DarkenedRoom/dosbox-staging-configs/Wing Commander 1+2/wc-staging.conf Voodoo emulation is not required and disabled. The [joystick] timed setting will be dependent on the hardware in use. The deadzone setting is a personal preference. The swap34 setting is omitted, as it is set by the WCAT Overhaul Mod launcher app. The [autoexec] section has an example mount commands for an emulated hard disk. This should be changed to an appropriate setting. Additional mount commands for floppy disks or CD-ROMs are covered later. The mixer command silently restores mixer volume to 100%. Loadfix allocates a memory block of 32KB, in lower memory, making it unavailable for use. Some earlier games like WC1 and WC2 require this. Tools WCAT launcher menu A WCAT launcher menu (wcatmenu.bat) has been created to call the appropriate WCAT batch files. They will run the WCAT launchers and WC1, SM2, WC2, SO1 or SO2 using the WCAT provided batch files. This is an entirely optional tool. It can be found in the GitHub repository: DarkenedRoom/dosbox-staging-configs/Wing Commander 1+2/wcatmenu.bat. It can be added to the DOSBox config with: [autoexec] ... c: call wcatmenu.bat Sound The [sblaster] sbtype is a recommended setting for the WCAT Overhaul Mod. The MT32 model is set to mt32_old as recommended by the List of MT-32-compatible computer games on the VOGONS wiki for WC1 and WC2. The romdir setting is an example and should be changed as required (see DOSBox midi). See Configuration for further WCAT Overhaul Mod launcher sound options. Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle, and rudder pedals are supported with WCAT. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor-specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers so only the vJoy virtual controllers are detected by DOSBox Staging. [6][7][8]. The physical axes mapped to Windows axes are 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 See Configuration for further WCAT Overhaul Mod launcher control options. Installation The Patching strategies indicate only the game data is applied to the WCAT Overhaul Mod. The mod provides executables to run the game and expansions, so the aim of installation is to create a suitable game data folder with the base game data and expansion data added to it, not to create a working installation (although that is the result). The game data folder is named gamedat for both WC1 and WC2. The following sections cover creating a suitable gamedat folder for various releases of both WC1 and WC2 before covering the WCAT Overhaul mod. Wing Commander If a release requires installation to a hard disk, it is recommended to use the default folder in DOSBox: C:\wing In Win10/11 this becomes (as an example): D:\Games\DOS\Wing Commander 1+2\hdd\wing It is recommended not to use wc1 as a folder as this will be used by the WCAT Overhaul Mod. Floppy disk releases Floppy disk releases should be installed to the DOSBox hard disk folder by installing the games within DOSBox. Once all components are installed, a suitable gamedat folder is available to use with the WCAT Overhaul Mod. The products should be installed in order: WC1, SM1 and SM2. The following is an example mount command to mount the installation disk images (images are assumed to be in an img format, although .ima is also supported): mount A "D:\Games\Dos\Wing Commander 1+2\fdd\*.img" -t floppy All disks can be mounted using the * wildcard, disks can be swapped with F4. The following installers are used for the game and expansions: A:\> install.exe # WC1 and SM1 A:\> install2.exe # SM2 The installation steps are shown below, they are the same for WC1, SM1 and SM2. Special CD-ROM Edition release This deluxe edition release should be installed to the DOSBox hard disk folder by installing the games within DOSBox. Once all components are installed, a suitable gamedat folder is available to use with the WCAT Overhaul Mod. The products should be installed in order: WC1, SM1 and SM2. The following is an example mount command to mount the installation CD-ROM image (images are assumed to be in an iso format, although bin/cue is also supported): mount D "D:\Games\Dos\Wing Commander 1+2\cd\WC Special Edition.iso" -t cdrom The following installers are used for the game and expansions: D:\> make_wc.bat # WC1 D:\> make_sm1.bat # SM1 D:\> make_sm2.bat # SM2 The installation steps are identical to floppy releases (see gallery above). CD-ROM Deluxe Edition releases No installation is necessary for CD-ROM Deluxe Edition releases as a suitable gamedat folder, with base game and expansion data, already exists on the CD-ROM and can be used with the WCAT Overhaul Mod. gog.com digital release The gog.com digital release should be installed using the Galaxy client or offline installer package. Once installation is complete, a suitable gamedat folder, with base game and expansion data, is available to use with the WCAT Overhaul Mod. Wing Commander II: Vengeance of the Kilrathi If a release requires installation to a hard disk, it is recommended to use the following folder in DOSBox: C:\wing2 In Win10/11 this becomes (as an example): D:\Games\DOS\Wing Commander 1+2\hdd\wing2 It is recommended not to use wc2 as a folder as this will be used by the WCAT Overhaul Mod. Floppy disk releases Floppy disk releases should be installed to the DOSBox hard disk folder by installing the games within DOSBox. Once all components are installed, a suitable gamedat folder is available to use with the WCAT Overhaul Mod. The products should be installed in order: WC2, SAP, SO1 and SO2. The following is an example mount command to mount the installation disk images (images are assumed to be in an img format, although ima is also supported): mount A "D:\Games\Dos\Wing Commander 1+2\fdd\*.img" -t floppy All disks can be mounted using the * wildcard, disks can be swapped with F4. The following installers are used for the game and expansions: A:\> install.exe # WC2 A:\> speech.exe # SAP A:\> install1.exe # SO1 A:\> install2.exe # SO2 The installation steps are shown below, they are the same for WC2 and SO1. The SAP will only ask for the installation disk and folder before beginning installation. SO2 has an additional step, asking for a DMA setting before confirming the configuration. EA Top Ten Pak release This release should be installed to the DOSBox hard disk folder by installing the games within DOSBox. Once all components are installed, a suitable gamedat folder is available to use with the WCAT Overhaul Mod. The following is an example mount command to mount the installation CD-ROM image (images are assumed to be in an iso format, although bin/cue is also supported): mount D "D:\Games\Dos\Wing Commander 1+2\cd\10pack.iso" -t cdrom The following installers are used: D:\> install.exe The installation steps are shown below. CD-ROM Deluxe Edition releases No installation is necessary for CD-ROM Deluxe Edition releases as a suitable gamedat folder, with base game and expansion data, already exists on the CD-ROM and can be used with the WCAT Overhaul Mod. gog.com digital release The gog.com digital release should be installed using the Galaxy client or offline installer package. Once installation is complete a suitable gamedat folder, with base game and expansion data, is available to use with the WCAT Overhaul Mod. Patching Once a suitable game data (gamedat) folder is available, the next step is to install the WCAT Overhaul Mod. There are versions of the mod for WC1 and WC2; they can both be obtained from: itch.io, Wing Commander AllTinker (WCAT) Overhaul Mod. These steps are for both WC1 and WC2, if only one of the games is installed, omit the steps for the other game: Obtain the WCAT Overhaul Mod (for Wing Commander) and the WCAT Overhaul Mod (for Wing Commander II). In Win10/11 create a wc1 and wc2 folder in the hdd folder, e.g. D:\Games\DOS\Wing Commander 1+2\hdd\wc1 D:\Games\DOS\Wing Commander 1+2\hdd\wc2 In Win10/11 extract the contents of the WCAT Overhaul Mod (for Wing Commander) zip file into the \hdd\wc1 folder. In Win10/11 extract the contents of the WCAT Overhaul Mod (for Wing Commander II) zip file into the \hdd\wc2 folder. Applying the game data This step can be done in Win10/11 outside of DOSBox. All that remains is to copy the contents of the installed Wing Commander and Wing Commander II gamedat folders into the gamedat folder created by the WCAT Overhaul Mods. These can be found: For Wing Commander: D:\Games\DOS\Wing Commander 1+2\hdd\wc1\gamedat For Wing Commander II: D:\Games\DOS\Wing Commander 1+2\hdd\wc2\gamedat For releases installed to the DOSBox hard disk (hdd) folder, the gamedat folder will be inside the chosen installation folder, e.g. D:\Games\DOS\Wing Commander 1+2\hdd\wing\gamedat D:\Games\DOS\Wing Commander 1+2\hdd\wing2\gamedat For Deluxe Edition CD releases the gamedat folder will be found on the CD-ROM (or CD-ROM image). Images in an iso format can be opened in Win10. Images in bin/cue format can be opened with third party utilities, e.g. Daemon Tools Lite or WinCDEmu. As an alternative DOSBox can be used to get this folder by mounting the CD-ROM/image in DOSBox and using DOS commands to copy the gamedat folder onto the DOSBox C: drive. For digital releases, it will depend on the Galaxy client installation folder or the installation folder chosen when running the gog.com offline installer, e.g. D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander\gamedat Configuration The following section covers configuration of the WCAT Overhaul mod. Initial run When the WCAT mod is run for the first time, it will verify the files in the gamedat folder to ensure WC1 (and expansions) or WC2 (and expansions) data files are present and then update any files as required (see gallery). Graphics and sound Graphics options are limited to the space environment colour and left to personal preference. It is recommended the sound options remain defaulted to the MT32 option, unless you wish to experience the Sound Blaster audio (see gallery). Controls Control options will be determined by the available controllers and personal preferences. Deadzone is left to personal preference. When using HOTAS controllers the 4 button 4 axis mode should be selected. Inverted spaceflight pitch and inverted axis is left to personal preference, it may also depend on the controller in use. Axes 3/4, rudder roll or yaw is left to personal preference. When using a dedicated throttle the linear throttle (0-100%) should be selected. When using a second joystick as throttle, the relative throttle (forward, increase/middle, static/backward, decrease) should be chosen. Swap Axis 3/4 will depend on the controllers in use. Clean up This step is entirely optional. Once Wing Commander I and II are confirmed to be working with the WCAT Overhaul Mod, any copies of the game originally installed using DOSBox in the wing, wing1, wing2 or any other chosen folder can be deleted. It is recommended to leave any digital releases in their installation folders. Example video Wing Commander 1 & 2 with WCAT Overhaul Mod. Finally... Credit and thanks go to AllTinker for all the hard work in creating the WCAT Overhaul Mods for Wing Commander and Wing Commander II. Good hunting!
- Aces Series: A primer
The Aces series was a classic set of flight sims developed by Dynamix and published by Sierra in the early 90s. This article will be taking a look at the released versions and patches of the two Aces games, Aces Over The Pacific and Aces Over Europe. Due to the high degree of commonality between them it makes sense to consider them together. Contents Strategy The strategy will be to look at each game individually. Each game will also feature some patching strategies to provide an overview if and how a particular release should be patched. Compilations featuring Aces Of The Pacific and Aces Over Europe are then covered. For the rest of the article the following abbreviations are used: AOTP: Aces Over The Pacific. AOTP: 1946: Aces Over The Pacific: WWII: 1946 (expansion). AOE: Aces Over Europe. The following abbreviations are used when referring to floppy disks: HD: High Density DD: Double Density. Aces Of The Pacific Aces Of The Pacific (AOTP) was released in floppy disk based DOS only editions from May 1992 until August 1994. A CD-ROM 'complete' edition featuring the DOS game, expansion and Win3.x manuals and config utilities was released in August 1994. This CD-ROM release would be used in the compilations, Aces: The Complete Collector's Edition (April 1995) and Aces: Collection Series (April 1997). The floppy disk based DOS only releases can be installed into a standard DOSBox environment. The CD-ROM releases can use a standard DOSBox environment to install the DOS based game and/or a Win3.x environment (in DOSBox) to install the DOS game and Windows manuals and utilities. Version and patch history The first patch for AOTP was never publicly released and instead was pre-installed with later versions of the game. This AOTP Patch A can still be found within AOTP Patch B, however, this should not be mistaken for the expansion patch, WWII: 1946 Patch A. Versions are present in the game and often, slightly different version numbers can be found in release notes. Aces Of The Pacific (May 1992) The initial retail release occurred in May 1992 and only included the DOS game. The game version listed in release notes is v1.0 and in-game it is Aces Of The Pacific, ver. A3.0. File timestamps give a date of 22 May 1992. It was distributed on: 4 x 1.2MB HD 5.25" floppy disks. 3 x 1.44MB HD 3.5" floppy disks. Aces Of The Pacific (June 1992) The June 1992 release was pre-patched with the Aces Of The Pacific Patch A and only included the DOS game. The game version listed in release notes is v1.01 and in-game it is Aces Of The Pacific, ver. 1.01. File timestamps give a date of 4 June 1992. It was distributed on: 4 x 1.2MB HD 5.25" floppy disks. 3 x 1.44MB HD 3.5" floppy disks. Aces Of The Pacific: Patch B disk (September 1992) September 1992 saw the release of AOTP: Patch B. Patch B was a cumulative patch including the unreleased Patch A. Prior to the pervasiveness of internet distribution, suppliers would occasionally supply patches on mail order patch disks. After applying the patch, the game version became v1.2 and Aces Of The Pacific, Patch B is listed in-game. The patch disk was distributed on: 1 x 720KB DD 3.5" floppy disk. The release notes for this patch cover multiple changes, can be found below, including: Manual corrections and additions. Joystick/controller changes. Flight model changes. Time scale changes. Frame rate/performance changes. During the patch update process the game is updated from v1.0 to v1.01 (running Patch A, if necessary) and then updated from v1.01 to v1.2 (Patch B). Aces Of The Pacific: Patch B (September 1992) Alongside the patch disk, Patch B was also distributed online. Supplied as either a zip archive or self extracting zip archive executable. Versions, release notes and the patching process remains identical to the patch disk. This patch is available from: Internet Archive, Aces of the Pacific patch B. Internet Archive, Wargamer Scenario Depot: Aces of the Pacific. The Sierra Help Pages, Game Updates, Aces Series Updates. Aces Of The Pacific (September 1992) A re-release of AOTP occurred in September 1992, pre-patched with Patch B and including only the DOS game. The game version listed in release notes is v1.2 and in-game it is Aces Of The Pacific, ver. 1.2. File timestamps give a date of 10 September 1992. It was distributed on: 4 x 1.2MB HD 5.25" floppy disks. 3 x 1.44MB HD 3.5" floppy disks. Aces Of The Pacific: WWII: 1946 (November 1992) The first and only expansion, Aces Of The Pacific: WWII: 1946 (AOTP: 1946) was released in November 1992. The expansion added additional alternate history scenarios and new jet aircraft of the period. It also included AOTP: Patch B. The expansion version listed in release notes is v1.0 but in game it remains Aces Of The Pacific, ver. 1.2. File timestamps give a date of 16 November 1992. It was distributed on: 1 x 1.2MB HD 5.25" floppy disk. 1 x 1.44MB HD 3.5" floppy disk. Aces Of The Pacific: WWII: 1946 (January 1993) A re-release of AOTP: 1946 occurred in January 1993 and continued to include Patch B. The expansion version is listed as v1.01 but in game it remains Aces Of The Pacific, ver. 1.2. File timestamps give a date of 19 January 1993. It was distributed on: 1 x 1.2MB HD 5.25" floppy disk. 1 x 1.44MB HD 3.5" floppy disk. WWII:1946 Patch A (March 1993) The expansion was given its one and only patch in March 1993. Confusingly called Patch A (as the first patch for the expansion), after applying the patch the in-game version remained, Aces Of The Pacific, ver. 1.2. This patch was only distributed digitally on-line, no patch disk was made available. This patch fixed saving single mission tapes and fixes related to the career mode. The release notes are shown below: This patch is available from: Internet Archive, 1942: The Pacific Air War Patch A (title refers to a different game). Internet Archive, Wargamer Scenario Depot: Aces of the Pacific. The Sierra Help Pages, Game Updates, Aces Series Updates. Aces Of The Pacific (CD-ROM edition, August 1994) The game was re-released in August 1994 on a single CD-ROM. This would be the first and only dedicated CD-ROM release of AOTP, other CD-ROM releases would be compilations. It included the base game and AOTP: 1946 expansion. The version listed in-game is Aces Of The Pacific, ver. 1.2. File timestamps give a date of 1 August 1994. This edition features both a DOS installer for the base game plus expansion and a Win3.x installer which installs AOTP plus AOTP: 1946, Windows manuals and config utilities. Aces Of The Pacific (August 1994) The game was also re-released on floppy disk at the same time as the CD-ROM release. This release only included the DOS base game. The version listed in-game is Aces Of The Pacific, ver. 1.2 but the release notes list it as v.1.21. File timestamps give a date of 2 August 1994. It was distributed on: 3 x 1.44MB HD 3.5" floppy disks. Despite the later version number, it remains compatible with the AOTP: 1946 expansion and WWII:1946 Patch A (expansion patch). During the AOTP: 1946 expansion installation, the installer will skip the included AOTP Patch B. Aces Of The Pacific: Patch B disk (August 1995) Another version of the Patch B disk was released in August 1995. This featured the same Patch B as earlier releases, with a slightly later update app. It continues to patch to v1.01 and then patch to v1.2. After applying the patch the in-game version is listed as Aces of the Pacific, Patch B. The patch disk was distributed on: 1 x 1.44MB HD 3.5" floppy disk. For further information see the earlier Aces Of The Pacific: Patch B disk (September 1992). Patching strategies Standard DOSBox refers to a 'standard' DOSBox Staging DOS environment. The alternative is using a Win3.x installer app using Win3.x running in DOSBox. Floppy disk releases (no expansion, May/June 1992) Install AOTP with standard DOSBox. Apply AOTP Patch B (from patch disk or downloaded patch). Floppy disk releases (no expansion, September 1992 and later) Install AOTP with standard DOSBox (already pre-patched with Patch B). Floppy disk releases (with WWII: 1946 expansion) Install AOTP with standard DOSBox. Install AOTP: 1946 with standard DOSBox. Apply AOTP: 1946 Patch A. CD-ROM release Install AOTP (DOS game only) with standard DOSBox and/or... Install AOTP (DOS game, Win manual and apps) with Win 3.x running in DOSBox. Documents The CD-ROM release will install a manual in a legacy Win3.x mvb format when run from Win 3.x. The following AOTP documents are available digitally: Manual (pdf version of mvb manual), pdf download. Internet Archive, Wargamer Scenario Depot: Aces of the Pacific. Old-Games.ru, Games, Aces of the Pacific, Aces of the Pacific - files. Manual (pdf version of printed manual), pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces of the Pacific, Aces of the Pacific - files. The Sierra Help Pages, Publications, Aces of the Pacific Manual. Quick Reference Card, pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces of the Pacific, Aces of the Pacific - files. MS-DOS Technical Supplement, pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces of the Pacific, Aces of the Pacific - files. The following AOTP: 1946 documents are available digitally: Manual (pdf version of printed manual), pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces of the Pacific, Aces of the Pacific - files. Aces Over Europe The floppy disk editions of Aces Over Europe (AOE) ran from November 1993 until August 1994. There was a CD-ROM release in July 1994 and a budget re-release in September 1995, with further CD-ROM bases releases occurring as part of the Aces: The Complete Collector's Edition (April 1995) and Aces: Collection Series (April 1997) compilations. The floppy disk based DOS only releases can be installed into a standard DOSBox environment. The CD-ROM releases can use a standard DOSBox environment to install the DOS based game and/or a Win3.x environment (in DOSBox) to install the DOS game and Windows manuals and utilities. Version and patch history Versions are present in the game but only ever report, Aces Over Europe ver. 1.0. Different version numbers can be found in release notes, setup scripts, on disk labels, inside executable files and derived from MD5 hash comparisons. Aces Over Europe (November 1993) The initial retail release occurred in November 1993 and only included the DOS game. The game version listed in release notes is v1.0. File timestamps give a date of 8 November 1993. It was distributed on: 3 x 1.44MB HD 3.5" floppy disks. Aces Over Europe: Patch A (December 1993) December 1993 saw the release of AOE: Patch A. Patch A would be the first and only patch for AOE. Patch A was only distributed as a download, until much later. This would upgrade the version to v1.01. File timestamps give a date of 27 December 1993. The patch release notes below cover the following fixes: Issues with Packard Bell computers. Joystick issues. This patch is available from: Internet Archive, Aces over Europe (new joystick drivers and other fixes). Internet Archive, Wargamer Scenario Depot: Aces over Europe. The Patches Scrolls, Aces over Europe, Patches. All later versions would be pre-patched with Patch A. Aces Over Europe (January 1994) A re-release took place in January 1994, including only a pre-patched version (to v1.01) of the DOS game. Since it includes Patch A, but does not have a later version label, the version is thought to be v1.01. File timestamps give a date of 25 January 1994. It was distributed on: 3 x 1.44MB HD 3.5" floppy disks. Aces Over Europe (CD-ROM edition, July 1994) The first CD-ROM edition was released in July 1994, distributed on a single CD-ROM. This would be the first edition to include both the DOS game and Windows manuals/utilities. This edition is pre-patched with Patch A. The version number listed within the executable file is v1.0.001. Aces Over Europe (August 1994) Around the same time as the first CD-ROM release another floppy disk re-release took place in August 1994. This edition was pre-patched with Patch A but disk labels listed a new version, v1.02. This edition only included the DOS game, with file timestamps giving a date of 2 August 1994. It was distributed on: 3 x 1.44MB HD 3.5" floppy disks. Aces Over Europe: Patch A disk (August 1995) A year after the last releases, Patch A, (previously only available as a download), was also released on a patch disk in August 1995. The patch disk was only applicable to the November 1993 releases and would upgrade to v1.01. The patch files are identical to the earlier Patch A (with a timestamp of 23 December 1993) with the latest file timestamp on the release notes listed as 2 August 1995. It was distributed on: 1 x 1.44MB HD 3.5" floppy disks. For further information on this patch see, Aces Over Europe: Patch A. Aces Over Europe (Sierra budget release, CD-ROM edition, September 1995) A budget re-release occurred in September 1995, on the SierraOriginals label. It used the same version as the earlier CD-ROM release, v1.0.001 and was distributed on a single CD-ROM. This edition includes both the DOS game and Windows manuals/utilities and remains pre-patched with Patch A. File timestamps list a date of 26 September 1995. Patching strategies Standard DOSBox refers to a 'standard' DOSBox Staging DOS environment. The alternative is using a Win3.x installer app using Win3.x running in DOSBox. Floppy disk release (November 1993) Install AOE with standard DOSBox. Apply AOE: Patch A. Floppy disk release (January 1994 and later) Install AOE with standard DOSBox (already pre-patched with AOE: Patch A). CD-ROM release Install AOE (DOS game only) with standard DOSBox and/or... Install AOE (DOS game, Win manual and apps) with Win 3.x running in DOSBox. Documents A CD-ROM release will install a manual in a legacy Win3.x mvb format when run from Win 3.x. The following AOE documents are available digitally: Manual (pdf version of mvb manual), pdf download. DOS Days, Games, Aces Over Europe, Supporting Documents. Old-Games.ru, Games, Aces over Europe, Aces over Europe - files. Manual (pdf version of printed manual), pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces over Europe, Aces over Europe - files. Quick Reference Card, pdf download. Internet Archive, Dynamix PC Floppy Disk Image Collection. Old-Games.ru, Games, Aces over Europe, Aces over Europe - files. Official strategy guide An official strategy guide, Aces Over Europe: The Official Strategy Guide, was written by Paul Schuytema and published by Prima Games in 1994. It is available digitally as a pdf download, from: Internet Archive, Aces Over Europe Official Strategy Guide. Internet Archive, Aces Over Europe - The Official Strategy Guide (1994) [PC]. The Video Game Library, Guide/Handbook, ACES OVER EUROPE OFFICIAL STRATEGY GUIDE. Compilations The compilations Aces: The Complete Collector's Edition (April 1995) and Aces: Collection Series (April 1997) were both CD-ROM compilations. Both compilations featured the following games, distributed on a single CD-ROM: A-10 Tank Killer. Aces of the Pacific Aces Over Europe Red Baron The Aces: Collection Series also included Aces of the Deep and Silent Thunder: A-10 Tank Killer 2 on a second CD-ROM. Version and patch history Both AOTP and AOE use the latest CD-ROM editions in the compilations, so there are no applicable patches. Aces: The Complete Collector's Edition (April 1995) The Aces: The Complete Collector's Edition was released by Sierra in April 1995. It includes Aces Of The Pacific, ver. 1.2 with the expansion included, and it uses the CD-ROM edition of Aces Over Europe, v1.0.001. Both games include a DOS installer (for the DOS game) with a Win3.x manual, installer and setup apps. Aces: Collection Series (April 1997) The Aces: Collection Series was released by Sierra in April 1997. It includes Aces Of The Pacific, ver. 1.2 with the expansion included, and it uses the CD-ROM edition of Aces Over Europe, v1.0.001. This compilation only includes Win3.x manual, installer, and setup apps, so must be installed using Win3.x. The DOS games can be run in a standard DOSBox DOS environment and do not require Win3.x to run. Patching strategies Both compilations feature the latest versions of both AOTP and AOE so there are no patches to apply. Aces: The Complete Collector's Edition Install AOTP and AOE (DOS game only) with standard DOSBox and/or... Install AOTP and AOE (DOS game, Win manual and apps) with Win 3.x running in DOSBox. Aces: Collection Series The Aces: Collection Series omits the DOS installation apps, so installation with Win3.x is required. In addition, due to the speed of DOSBox Staging the CD-ROM speed check will generate a 'divide by zero' error unless the CPU cycles are reduced when using Win3.x to 10000. Install AOTP and AOE (DOS game, Win manual and apps) with Win 3.x running in DOSBox. Documents As both games use a CD-ROM release in the compilations, a manual in a legacy Win3.x mvb format is installed, when run from Win 3.x. For digitally available documents see AOTP Documents and AOE Documents. Finally... Credit and thanks go to: The Internet Archive for hosting patches, manuals, images and game information for AOTP and AOE. The Sierra Help Pages for hosting patches, manuals and game information. Old-Games.ru for hosting manuals. The Patches Scrolls for hosting patches. DOS Days for hosting manuals. The Video Game Library for hosting the AOE strategy guide. Good hunting!
- Aces Series: Making it work
The Aces series was a classic set of flight sims developed by Dynamix and published by Sierra in the early '90s. This article will be continuing from where the earlier Primer article left off. DOSBox configs will be covered, for the Aces games, and for running Win3.x along with sound and control options. Installation of the DOS games and Win3.x supporting manuals and utilities is covered. Contents Strategy As there is a great deal of commonality between Aces Of The Pacific and Aces Over Europe, a similar DOSBox config can be used for both. This config will be used as the basis for installing and configuring the games under a DOSBox DOS session. The CD-ROM version of both games also supported Windows 3.x manuals and utilities used to config the DOS games. A Win3.x installation and DOSBox config will cover installing the Windows manual and utilities. Each game will use its own DOSBox config and hdd folder, however both the game and the Win3.x utilities will use the same emulated hard disk folder. Preparation This section covers the required preparation before installing or configuring the games under DOSBox. It is a necessary first step given the variety of releases for these two games over the years. Releases The first step is to identify the release available and the installation options it provides. The releases for both games fall into three categories. By consulting the earlier Primer, a release should be identified and the installation options determined. The categories are: DOS based releases. These include all the floppy disk based releases. Only the DOS game and installer are included so there is no need to use a Win3.1 installation. DOS and Win3.x based releases. These include dedicated CD-ROM releases and the Aces: The Complete Collectors Edition. Both the DOS and Win3.x installers are included so either a DOS only or DOS/Win3.x installation is an option. Win3.x based release. The Aces: Collection Series is a Win3.x based release as it omits the DOS installers. A Win3.x installation is required for this release. Retail media Due to the age of the media and the drives required to read them, it is recommended to rip floppy disks and CD-ROMs to image files, to save wear and tear on media and the mechanical drives. It is recommended to rip floppy disks to a supported DOSBox image format, either ima or img. CD-ROMs can be ripped to a data only iso image format as there is no CD audio on the disc. DOSBox Staging also supports CD-ROM images in a bin/cue image pair. Game management It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are: cd - for any cd images. fdd - for any floppy disk images hdd - the folder used as the emulated DOSBox hard disk (see hdd folder). conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\Aces Of The Pacific D:\Games\DOS\Aces Over Europe hdd folder When only installing the DOS game, the hdd folder can be a new empty folder. If a Win3.x installation is to be used, the hdd folder will need a 'clean' Win3.x install. The earlier article, DOSBox Staging and Windows covered creating a 'clean' Win3.x install. It is assumed a suitable hdd folder with a Win3.x install is available. DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed with each game, using DOSBox, having its own configuration file (with settings differing from the default configuration file). Game config The following is a general DOSBox Staging config for both games. [cpu] cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [joystick] timed = off swap34 = on deadzone = 0 [autoexec] @echo off mixer master 100 /noshow c: An Aces Of The Pacific example based on this config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Aces Of The Pacific/AOTP-staging.conf. An Aces Over Europe example based on this config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Aces Over Europe/AOE-staging.conf. In the [cpu] section cycleup and cycledown are changed from a percentage to a specific value to make cycle changes more consistent in DOSBox. Voodoo emulation is not required and is disabled. The [mixer] settings are an example and can be changed to a personal preference. However these settings may be appropriate due to the constant engine sounds. MIDI is configured using an original MT32 in the [mt32] and [midi] sections as an example. Other music options are covered in Sound. The [joystick] section will be dependent on the available controllers and personal preference. These options are covered in HOTAS config. The timed and swap34 options are examples for the controllers in use. The deadzone is a personal preference. The mixer command silently restores mixer volume to 100%. There are example mount commands (covered later) to run the game or invoke an AOTP or AOE menu, covered in Tools. Tools Aces Of The Pacific launcher. Launcher menus have been created for both Aces Of The Pacific and Aces Over Europe. The following options are available: Run the game. Run the DOS based setup. View release notes. Backup and restore a pilot career. Backup and restore the top aces and top mission lists. Returning to the DOSBox DOS prompt. Quitting DOSBox. The Aces Of The Pacific launcher menu can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Aces Of The Pacific/AOTPmenu.bat. The Aces Over Europe launcher menu can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Aces Over Europe/AOEmenu.bat. The launcher menu should be placed in the game installation folder after the game has been installed. Due to the variety of releases this may be one of the following default install folders. For AOTP: Win 10/11: D:\Games\DOS\Aces Of The Pacific\hdd\dynamix\aotp D:\Games\DOS\Aces Of The Pacific\hdd\sierra\aotp D:\Games\DOS\Aces Of The Pacific\hdd\sierra\aces\aotp DOSBox C:\dynamix\aotp C:\sierra\aotp C:\sierra\aces\aotp For AOE: Win10/11: D:\Games\DOS\Aces Over Europe\hdd\dynamix\aoe D:\Games\DOS\Aces Over Europe\hdd\sierra\aoe D:\Games\DOS\Aces Over Europe\hdd\sierra\aces\aoe DOSBox C:\dynamix\aoe C:\sierra\aoe C:\sierra\aces\aoe To run the AOTP launcher automatically, add the following lines to the [autoexec] section and enable the appropriate installation folder: # Using the AOTP menu # cd \dynamix\aotp # cd \sierra\aotp call aotpmenu.bat To run the AOE launcher automatically, add the following lines to the [autoexec] section and enable the appropriate installation folder: # Using the AOE menu # cd \dynamix\aoe # cd \sierra\aoe call aoemenu.bat Windows 3.x config The following is a general DOSBox Staging config which can be used to run Win3.x. This config is applicable to both games. This config is used to run Win3.x prior to a Win3.x based installation taking place. [dosbox] vmemsize = 4 [cpu] cputype = pentium cpu_cycles = 40000 cycleup = 1000 cycledown = 1000 [voodoo] voodoo = off [mouse] builtin_dos_mouse_driver_options = immediate [mixer] reverb = small chorus = light [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [autoexec] @echo off # Unmount any existing c: drive mount -u c mixer master 100 /noshow set path=%path%;c:\windows; c: An example based on this config can be found below or in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Windows 3.x/Win311.conf. More information on this config can be found in the earlier article, DOSBox Staging and Windows. The [joystick] setting is not present in this config as this config is used to run Win3.x, install the game with the Win3.x installer, view the manual or run Win3.x utilities. It is not used to play the game. The earlier game config is optimised to do this from the DOSBox DOS environment. Sound The following sound options are supported by AOTP and AOE. The [mixer] reverb setting is small and the chorus is light due to the constant engine noise whilst in flight. The default mixer master volume is 50% and this is restored to 100% in the [autoexec] section, as shown below: [mixer] reverb = small chorus = light [autoexec] ... mixer master 100 /noshow ... Sound Blaster The default Sound Blaster settings provided by DOSBox Staging v0.83.0 are fully supported by AOTP and AOE. During installation there is no need to specify IRQ, port or DMA settings. Roland sound Both AOTP and AOE support the Roland MT32 MIDI device. The following settings are used to enable the MT32. The model is set to mt32_old as recommended by List of MT-32-compatible computer games on the VOGONS wiki. The romdir setting is an example folder using versioned ROMs; for more information, see Roland MT-32 in the DOSBox Staging user manual. [mt32] model = mt32_old romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle and rudder pedals are supported by both AOTP and AOE. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers so only the vJoy virtual controllers are detected by AOTP or AOE. [6][7][8]. 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 Aces of the Pacific AOTP does not support the CH Flightstick Pro so it is recommended to use the 4axis joystick type. HOTAS profiling software can be used to control internal views with the hat switch. [joystick] joysticktype = 4axis Aces Over Europe AOE does support the CH Flightstick Pro so it is recommended to use the ch joystick type. The CH Flightstick Pro support in AOE includes the hat switch. [joystick] joysticktype = ch Aces Of The Pacific installation Releases with Windows and DOS installers should install using Windows 3.x first and then reinstall using the DOS installer. This ensures Windows 3.x manuals and utilities are available. The DOS install ensures the DOS installer is copied and is available to change game sound settings in a DOSBox DOS session. Floppy releases have no Win3.x installer, and the DOS installation is the only one available. Similarly, the Aces: Collection Series has no DOS installers, making a Win3.x installation the only one available. AOTP uses the following [cpu] cycles setting: [cpu] cpu_cycles = 20000 AOTP does not support the CH Flightstick Pro so it is recommended to use the 4axis joystick type. HOTAS profiling software can be used to control internal views with the hat switch. [joystick] joysticktype = 4axis The following DOSBox command can be used to mount a set of floppy disks or a CD-ROM: [autoexec] ... # Example floppy disk mount # mount a "D:\Games\Dos\Aces Of The Pacific\fdd\*.img" -t floppy # Example CD-ROM mount # mount d "D:\Games\Dos\Aces Of The Pacific\cd\Aces of the Pacific.cue" -t cdrom ... Win3.x installation The earlier article, DOSBox Staging and Windows covered creating a 'clean' Win3.x install. It is assumed a suitable hdd folder with a Win3.x install is available. The Win3.x installer (setup.exe) can be found on the CD-ROM root folder or AOTP folder. The following shows the installation steps when run from Win3.x: It is recommended to choose the Full Installation. Once the installation is complete, the configuration options are displayed. When choosing a Sound Card Option, the MT-32 can be selected even if it isn't detected. DOS installation The DOS installers are found on the first floppy disk of a floppy release using the installer: A:\> install.exe The DOS installers are found in the AOTP folder of CD-ROM releases, using the installer: D:\AOTP> install.bat The following shows the floppy disk release installation steps when run from DOS: Some of the following screenshots may differ slightly when using a CD-ROM release. A CD-ROM release will ask for a Full or Minimum installation. It is recommended to choose the full installation. If the game has already been installed using the Win3.x installer then both installation sizes must match (full or minimum). Patching The only release which requires the base game to be patched is a May/June 1992 floppy release that will not be using the expansion. The Aces Of The Pacific: Patch B should be applied using a DOSBox DOS session. The patch files should be copied into the game installation and run with: C:\dynamix\aotp> update c: The patching steps are shown in the gallery below: Expansion The floppy disk releases use a separate expansion installer (the CD-ROM releases already include the expansion). The Aces Of The Pacific: WWII: 1946 expansion should be installed using a DOSBox DOS session. The expansion is installed with the command: A:\> install c: The patching steps are shown in the gallery below: Patching Once the expansion is installed, it needs to be patched using WWII:1946 Patch A (CD-ROM releases are already patched). This should be installed using a DOSBox DOS session. Extract the patch files into a DOSBox DOS folder and apply the patch using the command: C:\> install c: The patching steps are shown below: Configuration Configuration can be run as often as required. To configure the game in Win3.x run the Aces of the Pacific Setup from the Aces of the Pacific program group. To configure the game in DOS, run the installer (install.exe or install.bat) from the AOTP installation folder, and select the required sound card. Running Due to the variety of releases there are a number of different commands that can be added to the [autoexec] section to run the game. You should enable the appropriate commands for the installed release. [autoexec] ... # Running a floppy release # cd \dynamix\aces # call aces.bat # exit # Running a cd release # cd \dynamix\aotp # call aotpcd.bat # exit # Running a compilation release # cd \sierra\aotp # cd \sierra\aces\aotp # call aotpcd.bat # exit In-game config The in-game config is used to select the controllers for stick, throttle and rudder, select music and sound and to select the realism options. The following gallery shows the various config menus: When using 4 axis HOTAS controllers, use the following assignments (screenshot 1): Flight: Joystick 1. Rudder: Rudder Pedals. Throttle: Slider on Joystick 1. Each controller will require calibrating separately (screenshot 2). The realism menu is available in-flight (screenshot 3). Aces Over Europe installation Releases with Windows and DOS installers should install using Windows 3.x first and then reinstall using the DOS installer. This ensures Windows 3.x manuals and utilities are available. The DOS install ensures the DOS installer is copied and is available to change game sound settings in a DOSBox DOS session. Floppy releases have no Win3.x installer, and the DOS installation is the only one available. Similarly, the Aces: Collection Series has no DOS installers, making a Win3.x installation the only one available. AOE uses the following [cpu] cycles setting, which is higher than AOTP and provides smoother gameplay when using the Tall Res setting in the game: [cpu] cpu_cycles = 30000 AOE does support the CH Flightstick Pro so it is recommended to use the ch joystick type. The CH Flightstick Pro support in AOE includes the hat switch. [joystick] joysticktype = ch The following DOSBox command can be used to mount a set of floppy disks or a CD-ROM: [autoexec] ... # Example floppy disk mount # mount a "D:\Games\Dos\Aces Over Europe\fdd\*.img" -t floppy # Example CD-ROM mount # mount d "D:\Games\Dos\Aces Over Europe\cd\Aces over Europe.iso" -t cdrom ... Win3.x installation The earlier article, DOSBox Staging and Windows covered creating a 'clean' Win3.x install. It is assumed a suitable hdd folder with a Win3.x install is available. The Win3.x installer (setup.exe) can be found on the CD-ROM root folder or AOE folder. The following shows the installation steps when run from Win3.x: It is recommended to choose the Full Installation. Once the installation is complete, the configuration options are displayed. When choosing a Sound Card Option, the MT-32 can be selected even if it isn't detected. DOS installation The DOS installers are found on the first floppy disk of a floppy release using the installer: A:\> install.exe The DOS installers are found in the AOE folder of CD-ROM releases, using the installer: D:\AOE> install.bat The following shows the floppy disk release installation steps when run from DOS: Some of the following screenshots may differ slightly when using a CD-ROM release. A CD-ROM release will ask for a Full or Minimum installation. It is recommended to choose the full installation. If the game has already been installed using the Win3.x installer then both installation sizes must match (full or minimum). Patching Only the floppy release from November 1993 requires patching. The patch files should be extracted to the game installation folder. The following command is run from within DOSBox to apply the patch: C:\dynamix\aoe> patch Configuration Configuration can be run as often as required. To configure the game in Win3.x run the Aces Over Europe Setup from the Aces Over Europe program group. To configure the game in DOS, run the installer (install.exe or install.bat) from the AOE installation folder, and select the required sound card. Running Due to the variety of releases there are a number of different commands that can be added to the [autoexec] section to run the game. You should enable the appropriate commands for the installed release. [autoexec] ... # Running a floppy release # cd \dynamix # call aoe.bat # exit # Running a cd release # cd \dynamix\aoe # call aoecd.bat # exit # Running a compilation release # cd \sierra\aoe # cd \sierra\aces\aoe # call aoecd.bat # exit In-game config The in-game config is used to select the controllers for stick, throttle and rudder, select music and sound and to select the realism options. The following gallery shows the various config menus: When using 4 axis HOTAS controllers, use the following assignments (screenshot 1): Flight: Flight Stick Pro. Rudder: Rudder Pedals. Throttle: Slider. Each controller will require calibrating separately (screenshot 2). The realism menu is available in-flight (screenshot 3). Mods Both AOTP and AOE had a strong modding community. Many of the sites hosting these mods and tools no longer exist but AlternateWars has collated a large collection of these mods and tools and uploaded them to the Internet Archive as part of the Wargamer Scenario Depot archive (although they weren't part of this depot). Aces Of The Pacific The Wargamer Scenario Depot: Aces of the Pacific archive consists of: Documentation. Gameplay mods. File editing and tactics information. Mission tapes. Tagert's AOTP: WWII 1946 mod set. Patches. New and replacement planes, flight models and livery. Tools and mission builder. This archive is available from: Internet Archive, Wargamer Scenario Depot: Aces of the Pacific. Aces Over Europe The Wargamer Scenario Depot: Aces over Europe archive consists of: ArgonV campaigns. Gameplay mods. Graphics mods. File editing information. Fan made missions. Collated mods (campaigns, planes, and landscape). Patches. New and replacement planes, flight models, armaments and livery. Tools. This archive is available from: Internet Archive, Wargamer Scenario Depot: Aces over Europe. Video Aces Of The Pacific in DOSBox Staging Aces Over Europe in DOSBox Staging. Finally... Credit and thanks go to: AlternateWars for creating the Wargamer Scenario Depot archives. Internet Archive for hosting the Wargamer Scenario Depot archives, patches and mods. Good hunting!
- Falcon 3.0: Strategic FALCON
A guide to running Strategic FALCON with Falcon Gold in DOSBox Staging. Strategic FALCON takes the dynamic campaign of Falcon 3.0/Gold and provides a complete tactical and strategic management suite. It was created by Bill White and his company Flying Muffin Enterprises around May 1994. Contents A strategic overview The following description is taken from a Strategic FALCON advert included in the 305fix.exe release notes: Tactical features Fly any allied aircraft in Falcon 3.0! Version 1.2 of StratFalc allows you to change the type of aircraft *you* fly--you can pilot, for example, A-10s for CAS runs, F-4s for SEAD, or B-52s for bombing! Although the cockpit will still look like an F-16, all external views of the aircraft and, especially, the aircraft's flight model will be that of the new plane! Add, remove, or alter F-16 flights, much like in Falcon 3.0 itself, with some important additions: Fuel remaining and Time to Waypoint are always displayed. Change the location of F-16 starting and ending waypoints (these are normally "locked" in Falcon itself). Add, remove, or alter Allied or Enemy flights. Change the types of aircraft for any flight in this mission (although your "personal plane" must always be an F-16). Change the waypoints of any flight, F-16, allied, or enemy involved in a mission. Change the temperament and skill levels of any allied or enemy pilot. Change the weapon loadout of any aircraft involved. Add or remove ground paths and ground units. Change the types, waypoints, and temperament of any ground units. Make ground columns more realistic; no more "kill me fast" in-line formations. Limit the number of killer SA-7s you face. View the mission description with the press of a key. Check mission timing with the "synchronized timing trace" feature, which shows with graphical/animated symbols where each flight in the mission will be in relation to each other! Swap your F-16 flight waypoints with those of any other F-16 flight--useful when you don't want to fly the lead mission. Load every plane correctly and automatically--up to 18 preset loadouts for each plane type! Strategic features Change the occupation of any site, to instantly capture nodes or surrender them to the enemy. Change the current strength or capacity of any site. Change the rate of growth of any site. Change the quantity of specific unit types at a site (the site's "breakdown"). Change the node structure for the theater. You can cut any site off from resupply. Change which nodes mean victory and which spell defeat. You can even fully randomize victory/defeat sites! Launch an automatic, coordinated ground attack against any site. Simulation Mode changes the way you play Falcon! Aircraft squadrons are assigned to bases, you can transfer at will, but your resources are limited! Three brigades await your orders, but if you screw up, they pay! Other features Change the current weather and the altitude of the cloud cover. Also change the predicted weather. Change the home air base--you can fly a campaign from any allied-occupied strip. Place an ILS at any base. Change the current day and time. Change the resupply and replacement days and times. Change the campaign momentum, both macro and micro--turn the tide on the enemy. Learn to properly use the "Kill Boxes" which have always been present in Falcon 3.0. If you wish, all enemy-related information can be hidden from you by checking a single box. Run Falcon or any series of programs with the press of a key and automatically return to StratFalc when you're done. Requirements Strategic FALCON requires Falcon 3.0, any version from 3.01.1 through 3.05 or Falcon Gold (version 3.05). Strategic FALCON is not compatible with the MIG-29: Deadly Adversary of Falcon or Hornet: Naval Strike Fighter expansions. Strategy The most common and easily obtained version of Falcon will be Falcon Gold (equivalent to Falcon version 3.05), due to its distribution on digital platforms. Strategic FALCON remains compatible with version 3.05, so Strategic FALCON will be installed alongside Falcon Gold. This will be a clean install of Strategic FALCON using the version 1.00 installer package before using an update patch to update it to the final version 1.22. Version and patch history The following is the version and patch history of Strategic FALCON taken from the various release notes, some distributed with the v1.22 release. Due to the rarity of Strategic FALCON and the update patches, any patch analysis is extremely limited. Strategic FALCON Version 1.0 May 1994 Strategic FALCON version 1.0 was released around May 1994. The initial version was released on a single floppy disk but the actual media remains unknown with the distribution package size compatible with 5.25" 1.2MB High Density (HD) or 3.5" 720KB Double Density (DD)/1.44MB High Density (HD) floppy disks. This version of the utility was distributed with a physical manual. The release notes are shown below: This installer package can be obtained from the Internet Archive. Version 1.1 Update October 1994 The first update was a substantial update, effectively introducing the strategic campaign management into the utility. The major updates in this release (taken from the release notes) included: Sim Mode! Strategic FALCON is now awash in strategy! Loadouts! No more overloaded planes! Speed limits will now be enforced! Updated for Falcon 3.05. This version of the utility was distributed with an update manual. The release notes are shown below: Version 1.11 Update November 1994 The Version 1.11 Update was primarily a bug-fix release for the Version 1.1 Update. However, some additional capabilities were added (taken from the release notes): Adjusting SA-7s. Running a User Batch File. Version 1.2 Update January 1995 The Version 1.2 Update was another substantial update introducing the ability to fly any allied aircraft. The major updates in this release (taken from the release notes) included: Fly any allied aircraft in FALCON 3.0! Compatibility with "Falcon Test Pilot". Better support for Allied Campaign COMMS mode. A new feature to make enemy columns' layouts a little more realistic. The 3rd Brigade (Mech Infantry) in Sim Mode has gone Airborne. Version 1.21 Update February 1995 The Version 1.21 Update occurred in February 1995, mainly as a bug-fix release for Version 1.2, though it also included the following additional enhancements (taken from the release notes): Select flight formations. Start enemy flights from airbases. Move the carrier. Alter pilot skills. Updated mission descriptions. Campaign day and time added. Fixed end-of-campaign hanging bugs. key support in dialog boxes. Version 1.21a Update March 1995 The Version 1.21a Update was a bug-fix release for Version 1.21, which introduced new bugs. The two major issues that were identified and fixed (from the release notes) were: An "F-14" bug, where wingmen you assign to flights changed into F-14s. A new version of strtsprt.com (1.5) compatible with padlock.com (another mod). This patch is available from: Internet Archive, Falcon 3.0 Strategic Falcon V 1.21 (zipped installation folder). Version 1.22 Update October 1995 The final Version 1.22 Update introduced a number of new features (taken from the release notes): Mission selection. Using the "Set Preferences..." Dialog. Override mission at 2300 hrs. "Air Tasking Orders" Dialog. F-14 and the Phoenix Missile. Email campaign support. Falcon 3.05, Windows 95, and MS-DOS 7.0 compatibility changes. This was distributed as a cumulative patch including all the preceding patches as a download (sfall.exe) from the Flying Muffin Enterprises website. Later copies of the patch would be distributed as a zip archive (sfall.zip). This patch is available from: Internet Archive, Falcon 3.0 Strategic Falcon V 1.21 (zipped installation folder). Internet Archive, Strategic Falcon 1.22 Update Patch (installer package). Documents In addition to the release notes included with each update, the following Strategic FALCON documents are available digitally: Strategic FALCON manual (pdf download). Internet Archive, Strategic FALCON 1994. Strategic FALCON Version 1.1 Update manual (pdf download). Internet Archive, Strategic Falcon Version 1.1 Update Manual. Both the manuals and release notes should be used together. Website The Strategic FALCON page remains available on the Flying Muffin Enterprises website courtesy of the Wayback Machine. Preparation This section covers the required preparation before installing Strategic FALCON under DOSBox. Due to the limited distribution available there is no need to rip any media to image files. Game management As Strategic FALCON sits alongside an existing Falcon Gold install, the game management folders used for Falcon Gold are supplemented with some additional folders for Strategic FALCON: docs - for Falcon Gold documents. strat - subfolder for Strategic FALCON documents. patch - to store any Falcon Gold patches. strat - subfolder for Strategic FALCON installer/patch. The example game folder used in this guide is: D:\Games\DOS\Falcon Gold DOSBox Strategic FALCON is compatible with the Falcon Gold DOSBox config described in the earlier article, Tech refresh 2026: Successful (DOSBox Staging) candidate part 1 (0-F). This config remains valid for DOSBox Staging v0.83.0. However earlier versions of DOSBox or different variants may require the following change: [dos] ver = 6.22 Installation Installation uses the Strategic FALCON v1.0 installer package and then updates it to v1.22 with the Strategic Falcon 1.22 Update Patch. Obtain the Strategic FALCON v1.0 installer package and extract the contents of the zip archive to a suitable DOSBox DOS folder, e.g. Win 10/11: D:\Games\DOS\Falcon Gold\hdd\sfinst DOSBox: C:\sfinst Optional, required for those using Falcon Gold. Strategic FALCON v1.0 was created before Falcon Gold was released. During the install Strategic FALCON will ask for the Falcon 3.0 installation folder and attempt to locate the falcon3.exe file. This file does not exist in Falcon Gold having been renamed to falconcd.exe, so it must be changed (in DOSBox) with: C:\FALCONCD> ren falconcd.exe falcon3.exe Run the Strategic FALCON installer from the sfinst folder with: C:\SFINST> install.exe The default strat installation folder should be used. Patching In Win10/11, obtain the Strategic FALCON v1.22 update and extract the contents of the zip archive into the strat installation folder. In DOSBox, run the self-extracting executable file from the strat installation folder with: C:\STRAT> sfall.exe In DOSBox, run the patching utility from the strat installation folder with: C:\STRAT> stratpat.exe Optional, required for those using Falcon Gold. Strategic FALCON v1.22 is compatible with Falcon Gold, so the Falcon executable should be renamed to the original name with: C:\FALCONCD> ren falcon3.exe falconcd.exe Clean up Once installed, the following files can be removed from the Strategic FALCON default installation folder, strat: dontrun.exe vertad.exe sf_all.rtp sfall.exe stratpat.exe In Win10/11, the sfinst folder can be removed from the hdd folder. Running Strategic FALCON should always be run from the installation folder with the batch file (this is important and required): C:\STRAT> strat.bat If successful, the startup menu page should be shown: Strategic FALCON v1.22. Finally... Credit and thanks for their hard work and preservation actions go to: Bill White and Flying Muffin Enterprises for all the hard work which went into Strategic FALCON. thatnicedutchguy for uploading the manuals, archived update installation folders and the Strategic FALCON installer package. Internet Archive for hosting all of the above. Good hunting!
- MiG-29: Deadly Adversary of Falcon 3.0: Operatsiya: Boyevoy Tigr release
Most sim fans are familiar with the second expansion of Falcon 3.0, MiG-29: Deadly Adversary of Falcon 3.0. However, not only was it an expansion but it later became a standalone product in its own right. One of the notable features of the standalone product was its support for an earlier expansion, Falcon 3.0: Operation: Fighting Tiger. Normally the order of installation would be: Falcon 3.0, Operation: Fighting Tiger, MiG-29 and finally Hornet: Naval Strike Fighter. This meant a later product, MiG-29 (installed first) would support an earlier expansion (installed later). This effectively makes Operation: Fighting Tiger forward compatible with standalone MiG-29. It was a more involved installation with specific Operation: Fighting Tiger installation instructions produced and included with MiG-29 standalone. These instructions are not available digitally and their contents are unknown, so reproducing this version of MiG-29 had been lost. However, one such later version of standalone MiG-29 features an installer app with dedicated installation support for Operation: Fighting Tiger, allowing us to recreate it once more. Given this is MiG-29 combined with Operation: Fighting Tiger and then patched to the latest MiG-29 v1.04 version, I've called this the MiG-29: Deadly Adversary of Falcon 3.0: Operatsiya: Boyevoy Tigr release. Strategy This guide will begin by covering the required components to build the release, followed by specific preparation steps, DOSBox settings and installation. The guide will rely heavily on earlier Falcon 3.0 guides, as a vast majority of the information is identical for MiG-29. Components The following components are required for this release: MiG-29: Deadly Adversary of Falcon 3.0 (Mile High Club compilation edition) The Mile High Club compilation was released by Velocity in 1995. It features MiG-29 pre-patched to version 1.01.1. The installer is a key component with a dedicated Operation: Fighting Tiger install option. This was released on a single CD-ROM containing MiG-29 only. For the purposes of preservation, the Mile High Club compilation is available from the Internet Archive. Falcon 3.0: Operation: Fighting Tiger The initial retail release, Falcon 3.0: Operation: Fighting Tiger v3.01 is used to build this release. This is a floppy disk release using a 3.5" 1.44MB HD floppy disk and a 3.5" 720KB DD floppy disk. MiG-29 Version 1.04 update The final component is the final MiG-29 patch, updating the game to v1.04. This is a cumulative patch with all fixes and enhancements from earlier MiG-29 patches included. This patch is available from: Internet Archive, Falcon 3.0 Patches. Preparation This section covers the required preparation before installing or configuring the games under DOSBox. Retail media Due to the age of the media and the drives required to read them, it is recommended to rip floppy disks and CD-ROMs to image files, to save wear and tear on media and the mechanical drives. It is recommended to rip floppy disks to a supported DOSBox image format, either ima or img. CD-ROMs can be ripped to a data-only iso image format as there is no CD audio on the disc. DOSBox Staging also supports CD-ROM images in a bin/cue image pair. Game management It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are: cd - for the MiG-29 cd image. fdd - for the Operation: Fighting Tiger floppy disk images hdd - the folder used as the emulated DOSBox hard disk. conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store the MiG-29 Version 1.04 update. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\MiG-29 standalone DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed with each game, using DOSBox, having its own configuration file (with settings differing from the default configuration file). Config This uses a copy of the Falcon 3.0/Gold config found in the previous article, Tech refresh 2026: Successful (DOSBox Staging) candidate part 1 (0-F). The following changes are made to the Falcon 3.0/Gold config: [autoexec] @echo off mount c "D:\Games\Dos\MiG-29 standalone\hdd" # Example floppy disk mount mount a "D:\Games\Dos\MiG-29 standalone\fdd\*.img" -t floppy # Example cd mount mount d "D:\Games\Dos\MiG-29 standalone\cd\mig29.iso" -t cdrom c: cd mig29 mig29.exe An example based on this config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/MiG-29: Deadly Adversary of Falcon 3.0 /mig29-staging.conf. Sound The following sound options are supported by MiG-29. The [mixer] reverb setting is small and the chorus is light due to the constant engine noise whilst in flight, as shown below: [mixer] reverb = small chorus = light Sound Blaster The default Sound Blaster settings provided by DOSBox Staging v0.83.0 are fully supported by MiG-29. Roland sound MiG-29 supports the Roland MT-32 MIDI device. The following settings are used to enable the MT-32. The model is set to cm32l as recommended by List of MT-32-compatible computer games on the VOGONS wiki. The romdir setting is an example folder using versioned roms. For more information see, Roland MT-32 in the DOSBox Staging user manual. [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle and rudder pedals are supported by MiG-29. The config is identical to the earlier Falcon 3.0/Gold config. As MiG-29 supports the CH Flightstick, the joystick in the DOSBox config is set as follows: [joystick] joysticktype = ch Installation All installation and patching takes place in DOSBox Staging. Before beginning installation ensure: The MiG-29 CD-ROM image is mounted as the D: drive. The first Operation: Fighting Tiger floppy disk image is mounted as the A: drive. To begin the installation use the following: D:\> install.exe The following gallery shows the installation steps: It is strongly recommended to install Operation: Fighting Tiger immediately after the MiG-29 installation has completed. Running the game and then attempting to install Operation: Fighting Tiger causes installer problems when using DOSBox Staging. Selecting the default sound and controller options is recommended during installation. They can be changed later in game. Installing Operation: Fighting Tiger for MiG-29 Operation: Fighting Tiger should be installed immediately after MiG-29. The following gallery shows the installation steps: Patching The last step is to apply the final MiG-29 patch, MiG-29 Version 1.04 update. The steps to install the patch are: In Win10/11 extract the patch zip file contents to the DOSBox MiG-29 installation folder (the readme.txt release notes aren't required and can be omitted): Win10/11: D:\Games\DOS\MiG-29 standalone\hdd\MIG29 DOSBox: C:\MIG29 In DOSBox, apply the patch with: C:\MIG29> patch.bat Once complete you should see the following (screenshot 1 and 2). When starting the game, the title menu should show v1.04 (screenshot 3) and the Operation: Fighting Tiger theatres should remain available (screenshot 4). Configuration The in-game config and in-game joystick calibration remain unchanged from Falcon 3.0/Gold. Running At present there is no launcher menu for MiG-29 so the game is run from the DOSBox config with: [autoexec] ... c: cd mig29 mig29.exe Or from a DOSBox session with: C:\MIG29> mig29.exe Finally... Credit and thanks go to the following people and groups: Das Boot for finding the MiG-29 installer that supports OFT in the Mile High Club compilation! Internet Archive for hosting the compilation and patches. The DOSBox Staging team for DOSBox Staging. Khoroshaya okhota!
- Navy Strike: Staging a strategic strike
Navy Strike, or using the full title, Navy Strike: Task Force Command is a mixture of flight sim and strategy game allowing the command of a carrier task force whilst allowing individual missions to be flown in the F/A-18E Hornet, a navalised F-22 Raptor or the A X which seems to be a fictional navalised F-117A Nighthawk. It was also released as Carrier Strike Force. The game was developed by Rowan and published by Empire Interactive like many of the Rowan sims and seems to use a similar engine as Air Power: Battle in the Skies, released a little later in 1995, again combining flight sim with an overarching strategy component. At release it received fair to middling reviews and during the heyday of flight sims, soon disappeared off many potential fans radars. Contents Strategy This guide will cover running the game as well as possible under the latest version of DOSBox Staging (version 0.83.0 at time of writing). This includes sound options, HOTAS controls and the notoriously tricky SVGA DOS drivers included with the game. Version and patch history The following is an incomplete version and patch history pieced together from various sources usually without a secondary reference, due to the limited information available. Information in this section may be incorrect or liable to change. Each release of Navy Strike used the same build with a compiled date of 16/10/95 18:34:24, and the release notes of each release are dated, 17 Oct 95. From this we can conclude the game build remained the same across all releases although some components would be replaced by a patch. Navy Strike (initial release, October 1995) The initial release by Rowan, was published by Empire Interactive around October 1995. It was distributed on a single CD-ROM. Although unconfirmed it is believed this release was on a mixed mode CD-ROM featuring game data and CD audio tracks providing dynamic music. The documentation included the manual, technical supplement and key reference guide. This release is not believed to be available on any of the digital platforms. Graphics driver update (January 1996) The one and only believed to be official patch was released around January 1996. It is a file replacement patch for DOS SVGA VESA graphics card drivers. It is believed this patch is only applicable to the initial release. This patch seems to be incompatible with later releases and partially with DOSBox Staging. This patch is available from: Internet Archive, Navy Strike Update (new video drivers). Internet Archive, Score 27 CD-ROM (1996-03). Old-Games.RU, Games, Navy Strike, Navy Strike - files. Patch notes This patch requires some explanation as its use isn't clear due to a lack of release notes. The Navy Strike installer copies the graphics drivers from the rowan folder on the CD-ROM into an identical rowan folder under the Navy Strike hard disk installation folder (e.g. c:\strike\rowan). These drivers are used by the svgaset.exe utility. The svgaset utility is used by the installer to initially select the DOS SVGA graphics drivers and can be used to reselect drivers later. The svgatest utility copies the driver files from the rowan folder, creating another copy of graphics drivers in the installation folder (e.g c:\strike). These drivers are used by the svgatest.bat, svgavesa.exe and svgademo.exe utilities to reselect DOS SVGA graphics drivers. So there are two mechanisms that can be used to select/change DOS SVGA graphics drivers, svgaset and svgatest. Both utilities scan their chosen folder for s3d and svc files to build driver lists to choose from. The patch replaces some files and adds further s3d and svc files to the installation folder (c:\strike) only. The patch includes new versions of svgatest.bat, svgavesa.exe and svgademo.exe. Therefore after applying the patch, svgatest is run to reselect new drivers and use them in the game. If the new drivers fail, svgaset can be used to reselect the original drivers from the unmodified rowan folder (c:\strike\rowan). In DOSBox Staging, svgatest can successfully update the drivers but fails to display the test image, without a small fix for svgademo, while svgaset works normally. Navy Strike (The White Label budget release, September 1996) The first budget release was published by Virgin Interactive Entertainment (VIE) on 'The White Label' budget catalogue around September 1996. It was distributed on a single CD-ROM. Unfortunately this seems to have been a data only CD-ROM without the CD music present on the original release. There seem to have been regional differences in this release with the European release featuring lower quality black and white pdf documents of the manual and separate technical supplement. The US release has a single combined technical supplement and manual but is a higher quality colour pdf document. It is believed the patch is already integrated into this release given the release date and the svgatest utility makes reference to the VIE helpline when manually selecting a driver, suggesting the utility has been updated for the release. Navy Strike (The White Label budget re-release, December 1996) A budget re-release from VIE on The White Label occurred in December 1996. It was distributed on a single data only CD-ROM without CD music. This release has a single combined technical supplement and manual using the higher quality colour pdf document. It is believed the patch is already integrated into this release given the release date and the svgatest utility continues to make reference to the VIE helpline. Navy Strike (Steam digital edition, October 2021) The Steam platform digital edition was released in October 2021 by Strategy First, to a certain degree of controversy. The release seems to be based on one of The White Label budget releases with the CD music missing. In addition it seems to use a sub-optimal DOSBox configuration. The release uses the lower quality black and white pdf documents for the manual and technical supplement. This edition is available from: Steam, All Games, Action Games, Navy Strike. Navy Strike (Zoom digital edition, March 2023) The Zoom platform digital edition was released in March 2023 by Strategy First. The details of this release aren't known, but given it is released by the same publisher, Strategy First, responsible for the Steam release, it is assumed to be identical to the Steam digital edition. This edition is available from: Zoom Platform, Navy Strike. Documents The manual and technical supplement are included on the CD with The White Label releases. None of the releases include the Key Guide. Those with the lower quality black and white pdf documents may consider it necessary to obtain the combined colour technical supplement and manual. It makes a stark difference, as shown below: The combined colour documents are available digitally: Technical Supplement/Manual (pdf document, download). Old-Games.RU, Games, Navy Strike, Navy Strike - files. The separate black and white documents are available digitally: Manual (pdf document, download). Steam, All Games, Action Games, Navy Strike, View the manual. Technical Supplement (pdf document, download). Steam, All Games, Action Games, Navy Strike, View the quick reference. Preparation This section covers tasks prior to configuring DOSBox or installing the game. Retail media Due to the age of the media and the drives required to read the media, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The initial release on a mixed mode CD-ROM featuring CD music should be ripped to a bin/cue image pair to preserve the music tracks. Later releases can be ripped to a data only iso image format as there is no CD audio on the CD-ROM. Game management It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are: cd - for cd images. hdd - the folder used as the emulated DOSBox hard disk. conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\Navy Strike DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed, with each game using DOSBox having its own configuration file (containing only settings differing from the default configuration file). Config This DOSBox config is based on earlier DOSBox configs found for Navy Strike from a variety of sources coupled with the later Air Power: Battle in the Skies config as both games use a very similar engine. # DOSBox Staging config for Navy Strike: Task Force Command [sdl] fullscreen = on [dosbox] memsize = 31 [cpu] cpu_cycles = 62500 cpu_cycles_protected = auto cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [joystick] joysticktype = ch timed = on swap34 = on deadzone = 0 [autoexec] @echo off # Example hdd mount mount c "D:\Games\dos\Navy Strike\hdd" # Example cd mounts # mount d "D:\Games\dos\Navy Strike\cd\Navy Strike.cue" -t cdrom # mount d "D:\Games\dos\Navy Strike\cd\Navy Strike.iso" -t cdrom c: # Starting the game # cd strike # strike # exit # Starting the launcher menu # call navymenu.bat This config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Navy Strike/NavyStrike-staging.conf. The [dosbox] memsize is increased to 31MB similar to the Air Power config. In the [cpu] section cpu_cycles and cpu_cycles_protected are changed to 62500 cycles, identical to the Air Power config. In the [voodoo] section, emulation isn't required and is disabled. The [mixer] settings are an example and can be changed to a personal preference, however a small reverb and light chorus may be more suited to constant engine noise while in flight. Navy Strike supports Roland MT-32 type devices. The recommended model, cm32l, is taken from the VOGONS wiki article, List of MT-32-compatible computer games. The [midi] section is configured to use the MT-32 MIDI device. The [joystick] section has the joysticktype set to ch as the game supports the CH Flightstick Pro. This game also seems to benefit substantially by having timed intervals enabled rather than disabled. The swap34 setting and deadzone are examples appropriate for my controllers and personal preference, you may wish to adjust it. The [autoexec] section has example hard disk and CD-ROM mount commands. There are examples for running the game from the DOS session or using the navymenu launcher tool. Tools A Navy Strike launcher menu (navymenu.bat) has been created to simplify the following tasks: navymenu.bat launcher. Running the game. Running the graphics driver setup with svgaset. Fixing and running the graphics driver setup with svgatest. Running the graphics and sound setup. Viewing the release notes. Viewing the free memory release notes. Save file backup and restore. Reset settings. Returning to the DOSBox DOS prompt. Quitting DOSBox. The Navy Strike launcher menu can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Navy Strike/NAVYMENU.BAT. It should be extracted into the hdd folder. e.g. D:\Games\DOS\Navy Strike\hdd (in Win10/11 becomes) C:\ (in DOSBox) Sound Navy Strike supports Sound Blaster digital sound and Sound Blaster or Roland music. Despite claims of additional support, these are the two DOSBox and Navy Strike supported devices. Sound Blaster The default Sound Blaster settings set in the default DOSBox config are appropriate for Sound Blaster digital sound and music, however the following settings may be useful to refer to when configuring the game: S.B. port No.: Port 220 (default). S.B. DMA Int.: IRQ 7 (default). S.B. DMA Chan.: 1 (default). Configuration is covered in Graphics and sound config with strike. Roland Navy Strike supports Roland music The Roland MT-32 model is set to cm32l, as recommended by the List of MT-32-compatible computer games. Configuration is covered in Graphics and sound config with strike. Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by Navy Strike. [6][7][8]. 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 The following DOSBox config settings are suggested, depending on controller hardware: [joystick] joysticktype = ch timed = on Navy Strike supports the CH Flightstick Pro so the ch joysticktype is used. Many may find the default hat buttons unintuitive, as they are used to control afterburner and airbrake rather than views. The subjective joystick 'feel' seems substantially improved by enabling timed intervals and allows the in-game calibration to work without issue. When timed intervals are disabled the in-game calibration will warn of poor calibration results. The appropriate in-game joystick is covered by In-game configuration. Installation The installation app on the mounted CD/image is run with: D:\> install.bat The following gallery shows the installation steps: Once the installation is complete, an SVGA graphics driver must be chosen by clicking on the SVGA Drivers button, rather than OK. For further details on choosing an SVGA driver see Graphics driver config with svgaset. Config As mentioned earlier there are two mechanisms for choosing SVGA drivers, svgaset and svgatest. Then there is a separate graphics and sound options configuration utility accessed through the game executable, strike.exe. Finally there are the in-game options, also used to calibrate controllers. So there are comprehensive and often confusing options to work through to get the game working optimally. For those curious as to why the ET4000 machine type is not used (as in Air Power). This machine type (svga_et4000) and SVGA graphics driver (ET4000) work, However, a thin transparent horizontal band bisects the HUD screen allowing the background to leak through. Graphics driver configuration with svgaset svgaset is used by the installer and can be run at any time after installation from within DOSBox with the command: C:\STRIKE> svgaset.exe The following gallery shows the configuration steps, starting from where installation left off: When choosing a SVGA graphics driver manually the following options will work with the DOSBox Staging machine type svga_s3: AVANCE. MACH32. Graphics driver configuration with svgatest svgatest can be run at any time after installation from within DOSBox with the command: C:\STRIKE> svgatest.bat After installation svgatest can successfully set the SVGA driver, but fails to display the test image used by svgademo.exe without a manual fix. To apply the manual fix: From DOSBox, copy the notgamed.dir file from the CD-ROM into the Navy Strike installation folder with the command: C:\> copy d:\ns\root\notgamed.dir c:\strike The following gallery shows the configuration steps When choosing a SVGA graphics driver, the following options will work with the DOSBox Staging machine type svga_s3: Q) MACH32. W) AVANCE. Running When running the game for the first time the configuration file (strike.cfg) is not present causing the graphics and sound configuration to run and create this config file. Once the config file is present, the following command runs the game, from the Navy Strike installation folder: C:\STRIKE> strike.exe The graphics and sound configuration can be run at any time within DOSBox from the Navy Strike installation folder, with the command: C:\STRIKE> strike.exe ? Graphics and sound configuration with strike The following gallery shows the configuration steps When presented with all the selected options, the Sound Blaster settings should be checked against the Sound Blaster default settings above. In-game configuration The following gallery shows the in-game configuration and calibration steps for a 4-axis HOTAS, stick, throttle and pedals using a CH Flightstick Pro joystick type: To re-calibrate existing controllers, select the Recalibrate option from Control Type. Once calibration is complete the main menu is displayed. Example video Navy Strike running DOSBox Staging. Finally... Credit and thanks go to: The Internet Archive for hosting the Navy Strike patch and Score magazine cover CDs. Old-Games.RU for hosting the Navy Strike patch and colour documents. Steam for hosting the Navy Strike black and white documents. Various VOGONS forum members, Internet Archive uploaders and maintainers of various other sites that provided snippets of information that went into this guide. Good hunting!
- F-22 Lightning II: Striking twice
An updated guide to running the NovaLogic light flight sim, F-22 Lightning II in DOSBox Staging. The original guide had incorrect or missing details and didn't provide an accurate or complete version and patch history. Contents Strategy This guide is laid out a little differently to improve consistency. There is a preparation section covering retail media image creation and game management. Installation shows the installation process with points to note, recommended patching and setup configuration options. Sound covers the various sound options both within and external to DOSBox. The control section covers joystick/HOTAS config and other controls if available. Documentation covers where to find documentation including supplemental documents often not included in re-releases. Mods & tools covers any available mods or optionally useful tools for the game. An example video section to show the results and finally credit and thanks. Hopefully this results in a far more complete guide for F-22 Lightning II (F-22 in the rest of the guide). Version and patch history The following is a corrected and more complete patch history. Due to the age of the game, overly complicated versioning and the difficulty in finding patches creating an accurate history was difficult but this history seems to be as complete as possible. All patches are available for the F-22 Lightning II (NovaLogic) patch collection at the Internet Archive. Included are the original NovaLogic self-extracting executable patches and release notes taken from the NovaLogic website. Additional patch locations are listed below. All version and patches should be installed under DOSBox. Initial retail release (September 1996) The initial retail release was published by NovaLogic in September 1996. Distributed on a single CD. This was version V 1.00.00.02. V 1.00.01.00 patch (October 1996) The first patch was a file replacement patch, replacing the game's executable (f22.exe). There were no release notes distributed with the patch. The patch originally was distributed as a self-extracting executable (fs2210001.exe) with other sources using zip or legacy arj formats. Release notes are included below: This patch is not recommended having been superseded by later patches. It is available from: Internet Archive, Score 36 CD-ROM (1996-12). V 1.00.04.00 patch (October 1996) The V 1.00.04.00 patch was an installer replacement patch, for those unable to install the game, and a cumulative patch including the V 1.00.01.00 patch. It requires files from an existing installation to be removed before the patch is extracted to the installation folder and the replacement patch installer run. This patch was originally considered a beta patch, to be replaced by the F-22 Maintenance Upgrade patch but was retained to deal with installation issues. Both sets of release notes are included below: The patch originally was distributed as a self-extracting executable (fs2210004.exe) with other sources using zip or legacy arj formats. This patch is unnecessary for DOSBox but those using legacy hardware experiencing the issue may require this patch. It is available from: Internet Archive, Score 36 CD-ROM (1996-12). The Patches Scrolls, F-22 Lightning II, fix beta 4 for video. V 1.00.05.02 patch (October 1996) The V 1.00.05.02 patch was a beta upgrade patch, for those that wished to try features prior to the full F-22 Maintenance Upgrade patch release. It is a file replacement patch replacing the game (f22.exe) and setup (setup.exe) executables. The setup must be re-run to prevent the game running in a multiplayer only client mode. The release notes are included below: The patch originally was distributed as a self-extracting executable (fs2210005.exe) with other sources using zip or legacy arj formats. This patch is not recommended having been superseded by the later F-22 Maintenance Upgrade patch. It is available from: Internet Archive, Score 36 CD-ROM (1996-12). Thrustmaster patch (October 1996) This patch was a Thrustmaster profile for the Thrustmaster F-16 FLCS (Flight Control System) and TQS (Throttle Quadrant System). The patch originally was distributed as a self-extracting executable (f22_b50.exe) with other sources using zip or legacy arj formats. This patch is unnecessary for DOSBox and modern controllers, but may be useful for those with the appropriate legacy hardware on legacy systems. It is available from: Internet Archive, Score 36 CD-ROM (1996-12). Retail re-release (November 1996) The retail re-release was published by NovaLogic in November 1996. Distributed on a single CD, this included the F-22 Maintenance Upgrade and was version V 1.01.00.18. F-22 Maintenance Upgrade patch (December 1996) The final and largest patch was a cumulative patch including the V 1.00.01.00 and V 1.00.05.02 patches but excluding installation fixes provided by the V 1.00.04.00 patch. It is an installation patch which must be installed in an existing fully working installation folder. Once complete the setup configuration options must be reapplied. This patch upgrades the version to V 1.01.00.18. The release notes are included below: The patch originally was distributed as a self-extracting executable (fs2210018.exe) with other sources using zip or legacy arj formats. This patch is recommended for the initial retail release only. It is available from: Gamepressure, Download, F-22 Lightning 2, F-22 Lightning 2 - Game Update - Download. Internet Archive, F-22 Lightning II Patch v1.01.00.18. The Patches Scrolls, F-22 Lightning II, patch 1.01.00.18. F22MOUSE (December 1996) This is an additional executable (f22mouse.exe) to be used in place of the game executable (f22.exe). It provides cursor control using a joystick for systems where mouse control is unavailable. The release notes are included below: This patch is unnecessary for DOSBox but may be required for those using legacy systems without mouse control. EA CD Classics edition release (July 1998) F-22 was re-released as part of the EA CD Classics range in July 1998. This uses version V 1.01.00.18 with the F-22 Maintenance Upgrade included, making it equivalent to the Retail re-release (November 1996). Distributed by Electronic Arts on a single CD-ROM, which also includes F22MOUSE, additional joystick profiles, manual and reference card pdf documents and a variety of demos for other NovaLogic products. Patching Strategies The following are the recommended patching strategies: Initial retail release (DOSBox) Install initial retail release. Apply F-22 Maintenance Upgrade patch. Initial retail release (legacy systems) Install initial retail release. Install using V 1.00.04.00 patch (if initial retail release installation fails). Apply F-22 Maintenance Upgrade patch. Retail re-release and EA CD Classics edition release Install retail re-release or EA CD Classics edition release with F-22 Maintenance Upgrade already included. Preparation This section covers tasks prior to configuring DOSBox or installing the game. Retail media Due to the age of the media and the drives required to read the media, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROM can be ripped to a data only iso image format as there is no CD audio on the disc. Game management It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are: cd - for any cd images. hdd - the folder used as the emulated DOSBox hard disk. conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. These management folders are placed in the following game folder (as an example), and used in the rest of the guide: D:\Games\DOS\F-22 Lightning II DOSBox This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed with each game, using DOSBox, having its own configuration file (with settings differing from the default configuration file). Config This is a revised config, changes to the default config can be found below. # This is the configuration file for F22 Lightning II. [cpu] cpu_cycles_protected = 200000 cpu_throttle = on cycleup = 1000 cycledown = 1000 [voodoo] voodoo = off [mixer] reverb = medium chorus = normal [soundcanvas] soundcanvas_model = auto soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas [joystick] joysticktype = ch timed = off swap34 = on deadzone = 0 [autoexec] @echo off mount c "D:\Games\Dos\F-22 Lightning II\hdd" mount d "D:\Games\Dos\F-22 Lightning II\cd\F-22 Lightning II.iso" -t cdrom mixer master 100 /noshow c: # Running F-22 # cd f22 # f22.exe # exit # Using the F22 menu # call f22menu.bat This config can be found below or in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/F-22 Lightning II/F22LightningII-staging.conf In the [cpu] section cpu_cycles_protected has been changed from max to a high figure with cpu_throttle enabled as this is considered better practice than using max cycles. The [mixer] settings are an example and can be changed to a personal preference. MIDI is configured using a Sound Canvas in the [soundcanvas] and [midi] sections as an example. The soundcanvas_rom_dir folder setting is an example. Other music options are covered in Sound. The [joystick] section has the joysticktype set to ch as the game supports the CH Flightstick Pro, however other options are covered in HOTAS config. The [autoexec] section has example mount commands for an emulated hard disk and CD image. These should be changed to appropriate settings. The mixer command silently restores mixer volume to 100%. There are example commands (commented out) to run the game or invoke an F-22 menu, covered in Tools. Tools F-22 launcher menu. An F-22 launcher menu (f22menu.bat) has been created to simplify the following tasks: Running the game. Running the configuration setup. Viewing the release notes. Pilot backup and restore. Switching between DOSBox MIDI options (Sound Canvas, Fluidsynth or an external MIDI synth). Returning to the DOSBox DOS prompt. Quitting DOSBox. MIDI options are required to be configured in the DOSBox config before use. The F22 launcher menu can be found below or in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/F-22 Lightning II/f22menu.bat It should be extracted into the hdd folder. e.g. D:\Games\DOS\F-22 Lightning II\hdd (in Win10/11 becomes) C:\ (in DOSBox) Sound F-22 supports Sound Blaster digital sound and Sound Blaster or General MIDI music. The game does not support Roland MT32 type devices. Sound Blaster The default Sound Blaster settings set in the default DOSBox config are appropriate for Sound Blaster digital sound and music, however the following settings may be useful to refer to when configuring the game: Digital Sound Device Setup: Sound Blaster 16 I/O: 220h IRQ: 7 DMA8: 1 DMA16: 5 KHz: 22 Mix: 16bit Music Device Setup: Sound Blaster 16-bit / OPL-3 I/O: 220h MIDI The following settings apply to all MIDI devices below when configuring the game: Music Device Setup: General MIDI I/O: 330h Sound Canvas The following settings enable the Sound Canvas synth and selects the Sound Canvas as the MIDI device: [soundcanvas] soundcanvas_model = auto soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas The soundcanvas_rom_dir is an example only. It is recommended to consult the Roland Sound Canvas page of the DOSBox Staging user manual. Fluidsynth The following settings enable Fluidsynth and selects Fluidsynth as the MIDI device: [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [midi] mididevice = fluidsynth The soundfont and soundfont_dir are examples only. It is recommended to consult the Fluidsynth page of the DOSBox Staging user manual. External MIDI The following settings enable an external (to DOSBox) MIDI synth and selects it as the MIDI device: [midi] mididevice = port midiconfig = 0 The midiconfig is an example only. It is recommended to consult the Using external MIDI devices section of the DOSBox Staging user manual. The following earlier articles cover using virtual software synths: DOSBox Staging and MIDI. VirtualMIDISynth and MIDIMapper. Controls The following section covers joystick/HOTAS setup. HOTAS config Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes. For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by F-22. [6][7][8]. 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 Using a profile Many may find the CH Flightstick Pro POV hat mapping in F-22 counter intuitive. The hat is configured to switch between the HUD and MFDs rather than the HUD and internal left/right/rear views. Those wishing to create a profile (in vendor profiling software or Joystick Gremlin) to assign additional buttons or remap the POV hat may wish to change the DOSBox config to: [joystick] joysticktype = 4axis The appropriate in-game joystick is covered in the In-game configuration. Installation The installation app on the mounted CD/image is run with: D:\> install.exe The following gallery shows the installation steps: The default installation folder (C:\F22) is recommended. A Large installation should be selected. Once the installation is complete, configuration will start automatically. Patching Patching is only required for the initial retail release at version V 1.00.00.02. The retail re-release and EA CD Classics release are already pre-patched to V 1.01.00.18. When using DOSBox, only the F-22 Maintenance Upgrade patch is required. This patch requires an installed and working copy of F-22. To apply the patch: From Win10/11, copy the self-extracting executable (fs2210018.exe) into the F-22 installation folder. Run the patch within DOSBox replacing existing files as required. Alternatively from Win10/11 extract the contents of the patch zip file (fs2210018.zip) into the F-22 installation folder, replacing existing files as required. From DOSBox, in the F-22 installation folder run the patch installer (install.exe). Configuration Configuration is run (in DOSBox) automatically after installation or run manually within the F-22 installation folder with the command: C:\F22> setup.exe The following gallery shows the configuration steps: In Video Setup, select VESA 2.0. To configure sound/music see Sound. In Performance settings the following checkboxes should be checked: Use page flipping. Use VESA for low-res. Once configuration is complete the game will run automatically. Configuration can be repeated as often as needed, by rerunning the setup.exe command. Running The game is run from the DOSBox installation folder with the command: C:\F22> f22.exe In-game configuration The following gallery shows the in-game configuration options: All graphics speed and memory options can be set to maximum. Sound options are left to personal preference. Controls: Joystick will depend on the DOSBox config. A DOSBox ch joystick type should use the CH Flightstick Pro. A DOSBox 4axis joystick type should use the 4 Button Joystick. Throttle and Foot pedals settings will depend on the available hardware. Effects settings are left to personal preference. Documents The manual and keyboard reference card are included on the CD with the EA CD Classics edition release. The following documents are available digitally: User manual Internet Archive, F 22 Lightning II Manual (pdf). Internet Archive, F-22 Lightning II (1996) PC Manual (pdf). Key reference (original and alternate version) Internet Archive, F 22 Lightning II Keyboard Comands (pdf). F-22 Lightning II QuickStart Internet Archive, F 22 Lightning II Quickstart (pdf). Game mods This section covers game mods, tools or in this case workarounds that may prove useful when playing the game. Editing the save game file There is a legitimate use for such a task as midway through the later campaigns the Promotion Point Total can increase above 199,999, which results in a crash when accessing the Player Stats Screen. A workaround for this issue requires opening the player save file (f22plyr.sav) in a hex editor, like HxD. It is recommended to take a backup copy of the player save file in case there are unexpected problems. In this example, a save file is opened in HxD, all slots in the save file have been filled with the description, DARKENEDROOM123. Each hexadecimal value, 00, 0C, A2, DF, etc. is a single character/byte. The description is always 15 characters/bytes long (with blank characters/bytes shown as '.' in HxD). After the description there is a single empty byte ('.' in HxD) and then the 3 characters/bytes storing the score (?♪♥). The highlighted parts (1st screenshot) show the maximum allowable score, 199,999 in hexadecimal (3F 0D 03) and DOS/ANSI encoded characters (?♪♥). If a score entry is selected (2nd screenshot), the panel on the right shows it's value in various formats. As a 24-bit (3-byte) integer (Int24 or UInt24) the value is 199,999. If a score entry is higher than 199,999 then the hexadecimal entry can be edited and changed to 3F 0D 03 to set it to a working maximum. Example video F-22 Lightning II in DOSBox Staging v0.83.0. Finally... Credit and thanks go to: The Internet Archive for hosting the F-22 Lightning II patch collection, images of the Score cover CDs, F-22 documents and the Wayback Machine, used to rediscover the original patches. The Patches Scrolls for hosting patches. Gamepressure for hosting a patch. John Novak and the DOSBox Staging team for DOSBox 0.83.0, wiki and user manual. Maël Hörz for HxD. Good hunting!
- Falcon 3.0: Version & patch history
A version and patch history of the classic DOS sim Falcon 3.0 and it's expansions Falcon 3.0: Operation Fighting Tiger, MiG-29: Deadly Adversary of Falcon 3.0 and Hornet: Naval Strike Fighter. This article will only be examining the official releases and patches of Falcon 3.0 and the expansions. The sheer number of patches, and expansions has left a very convoluted and confusing history of Falcon 3.0, to say nothing of the third party tools, mods and updates. This article will attempt to clarify the history in a hopefully mostly chronological order. All patches can be found on the Internet Archive. Contents Falcon 3.0 demo Demo title screen A limited demo version of Falcon 3.0 was released by Spectrum HoloByte in May 1991, featuring an instant action scenario only. In this version there are a limited number of commands and there is no War Room screen. Sound was selected at startup and was limited to PC speaker, Adlib or Soundblaster options. The size of the demo is 1.2Mb and was probably distributed on a single 'sampler' 3.5" HD or 5.25" HD floppy disk or 2 x 3.5" DD floppy disks. The demo can be found on the Falcon 3.0 section of the DOSGAMES.COM website. Falcon 3.0 Falcon 3.0 retail box The original retail release of Falcon 3.0 appeared in Dec 1991. Developed by Sphere, Inc and published by Spectrum Holobyte, Inc and MicroProse Software. Inc. It was distributed on 5 x 5.25" High Density (HD) floppy disks or 4 x 3.5" HD and 1 x 3.5" Double Density (DD) floppy disks. Falcon 3.0 box rear The first readme file covers requirements, installation issues and finding enough free memory, 600K, a huge amount for the time, and an issue requiring mentioning in numerous expansions and patches. It also covers hints, manual changes and additions. Most patches were cumulative, effectively replacing earlier patches. Falcon v3.0a The first of many patches was released in Jan 1992, updating Falcon 3.0 to v3.0a. Notable feature include an improved installer utility and a number of bug fixes. As would be the norm, VCR files created with the ACMI feature would not be compatible with earlier versions. All players wishing to use the head-to-head feature would need to be using v3.0a. A note on Falcon v3.0b Version 3.0b of Falcon was never released, the next version being v3.0c. The reason for this is given in the v3.0c readme file: The version following 3.0a of FALCON 3.0 is 3.0c. Sphere, Inc. will not release a version 3.0b of FALCON 3.0 because two unofficial versions proclaiming themselves as "3.0b" were released by hackers. To avoid potential confusion, it was decided to name this version "3.0c". Falcon v3.0c Released in Feb 1992, the Falcon v3.0c patch updated all previous versions to the v3.0c standard. Changes include a large number of game accuracy improvements and bug fixes. In addition the comms code was improved and issues caused by 'fast' machines (33Mhz 486) resolved. The readme file also includes the changes from v3.0a as well as manual corrections. Update: The above readme was taken from a Falcon v3.0c install. The elusive patch has been found and added to the Internet Archive. The patch readme file is shown below: Falcon v3.0d Released in May 1992, this patch made comprehensive changes to missile awareness, effectiveness, chaff/flares and ECM usage by the player and AI pilots. The jettison controls were also changed. This patch would erase existing campaign and squadron data. The patch readme also contained the changes from v3.0c and v3.0a. Falcon v3.0d would also be a re-release version, this version appearing on the 'Tornado Falcon 3.0 Twin Pack' compilation on a single CD-ROM. A note on compatibility sets At this point the concept of a compatibility set is introduced. The developer/publishers of Falcon 3.0 now had multiple products that players may use for head-to-head or networked gameplay. Going forward, individual products would be patched to make them communication compatible with each other for multiplayer gameplay. The suite of products at particular versions which are communication compatible is considered a compatibility set. For additional expansions and patches it is useful to consider them in terms of their compatibility set. Each compatibility set will detail the products and version comprising the set. Compatibility set: Falcon v3.0e, OFT v3.01, OFT v3.01.1 This was one of the few compatibility sets to maintain comms compatibility between two different versions of the same product. Falcon 3.0: Operation Fighting Tiger v3.01 The first expansion to Falcon 3.0, Falcon 3.0: Operation Fighting Tiger was released in August 1992. Developed by Sphere, Inc and published by Spectrum Holobyte, Inc and MicroProse Software. Inc. The expansion was distributed on 2 x 5.25" HD or 1 x 3.5" HD and 1 x 3.5" DD floppy disks. A new title screen With Operation Fighting Tiger we also see the current Falcon title screen for the first time. The readme warns that squadrons created in earlier versions would be deleted during the install process, advising that campaigns in progress be completed before installing the expansion. In addition there is advice for dealing with installation problems and a manual addendum. Operation Fighting Tiger box rear From the readme file: The tactical environment of Operation: Fighting Tiger is significantly different than that of the original Falcon 3.0 theaters. Be sure to read the Operation: Fighting Tiger flight manual to learn about the new weapons, missions and other challenges which have been added to the game. For the rest of the article we will refer to Operation Fighting Tiger (or OFT). Falcon 3.0: Operation Fighting Tiger update v3.01.1 Released in October 1992, this was named the 'Falcon 3.0: Operation Fighting Tiger update'. The patch comprises of a new OFT installer, backup and boot disk utilities and bug fixes and changes. The readme includes installation instruction, changes and a manual addendum. This patch is only applicable to Falcon 3.0: Operation Fighting Tiger v3.01. Falcon v3.0e In order to maintain compatibility between OFT v3.01 and v3.01.1 a patch was released to update Falcon to v3.0e bringing it up to an OFT v3.01/v3.01.1 standard. It was a comprehensive patch, fixing numerous bugs and introducing changes to: Night mode Objects Sound and music Weapons Campaign, missions and waypoints Wingman views and commands ILS and landing Other miscellaneous changes This patch is no longer available and is very difficult to find due to it being superseded by the preferred v3.02 patch. This patch was only applicable to Falcon v3.0d or earlier. It's not clear when this patch was released but it would have been released in conjunction with OFT, the OFT update or shortly thereafter, around August-November 1992. A comprehensive list of changes and bug fixes for v3.0e were listed within the f3readme.txt file generated by the v3.03 patch and shown below: Compatibility set: Falcon v3.02, OFT v3.02, MiG-29 v1.0 MiG-29: Deadly Adversary of Falcon 3.0 v1.0 The second expansion to Falcon 3.0 was 'MiG-29: Deadly Adversary of Falcon 3.0'. Developed by Spectrum Holobyte, Inc and published by Spectrum Holobyte, Inc and MicroProse Software, Inc. It was released in July 1993 on installation media of 1 x 3.5" DD and 2 x 3.5" HD disks. Standalone edition MiG-29 would later be released as a standalone product, which was compatible with the Operation Fighting Tiger addon. The standalone edition uses a slightly different box design but with styling consistent with the rest of the product range. The release of MiG-29 also included the complete v3.02 patch for Falcon and Operation Fighting Tiger. The MiG-29 readme suggests distributing the first two disks (or backups) to other owners of Falcon or Operation Fighting Tiger to update to v3.02 to allow head-to-head play. This was the suggested update option given the choice between the MiG-29 update utility and the Falcon/OFT v3.02 patch. MiG-29 box rear The install utility would delete existing squadrons, so campaigns in progress would need to be completed before using the installer. Once installed, Operation Fighting Tiger could not be installed and would require a clean install of Falcon, followed by OFT and finally MiG-29. The readme notes mostly cover installation and installation problems with additional readme files generated by the patch. For the rest of the article MiG-29: Deadly Adversary of Falcon 3.0 will be referred to as MiG-29. Falcon v3.02 / Falcon 3.0: Operation Fighting Tiger v3.02 The Falcon/OFT v3.02 patch was the first to update multiple products. This patch was also known as 'Falcon 3.0 with MiG-29 add-on'. This seems to have been a decision to try and simplify the patching process, given the numerous patches that had preceded it. Released at the same time as MiG-29, in July 1993, the patch readme was identical to the one provided by MiG-29. This patch would delete existing squadrons, so campaigns in progress would need to be completed before patching. Below is the additional Falcon 3.0 readme produced by the patch. A note on Falcon 3.0: Operation Fighting Tiger At this point it's worth noting that explicit references to Operation Fighting Tiger are often omitted in subsequent patch notes, with updates to OFT being implicitly included in later Falcon or MiG-29 patches. Compatibility set: Falcon v3.02.1, MiG-29 v1.01, v1.01.1 This is a rather convoluted compatibility set due to new bugs being introduced and deviation from what had become the patching norm for Falcon, as explained below. This is only compatibility set to cover two versions of MiG-29. MiG-29 v1.01 The first MiG-29 patch was released in October 1993. The patch was only applicable to the MiG-29 addon and was not compatible with the standalone product. The patch included the Falcon v3.02.1 patch and fixed a number of bugs. In addition the Acer Terminate & Stay Resident (TSR) bug fix was integrated into this patch. Unlike other patches there is no separate Falcon 3 update utility, with the patch automatically quitting once Falcon 3 is patched and MiG-29 cannot be found. This patch would introduce a comms bug allowing the MiG-29 v1.01 player to play head-to-head with a Falcon v3.02.1 player but not another MiG-29 v1.01 player! The standalone edition of MiG-29 v1.01 would later be released as one of the products on the Velocity Mile High Club 8 Pack CD-ROM Set in 1995. Falcon v3.02.1 It's not known if this was released as a separate Falcon patch or was only distributed with the MiG-29 patch, however it would have been available in October 1993. Unlike earlier patches this patch is not cumulative and only applicable to Falcon v3.02. Earlier versions of Falcon would need to apply the v3.02 patch before applying this one. The changes are covered in the MiG-29 readme file. This patch is also known as 'Falcon 3.0 with MiG-29 add-on update'. MiG-29 v1.01.1 The purpose of this patch was to address the bug introduced with MiG-29 v1.01. It was released in November 1993 as a partial cumulative update, as it included the MiG-29 v1.01 fixes, the Falcon v3.02.1 patch and the Acer TSR fix. This version retained comms compatibility with Falcon v3.02.1. Again, it was only applicable to the MiG-29 addon and was not compatible with the standalone product. Compatibility set: Falcon v3.03, MiG-29 v1.02, Hornet v1.0 With the release of Hornet: Naval Strike Fighter we begin to see standardization in patching and versioning across the product suite. Hornet: Naval Strike Fighter v1.0 The third and final addon to Falcon, Hornet: Naval Strike Fighter was released in December 1993. Developed and published by Spectrum Holobyte, Inc. Media consisted of 3 x 3.5" HD disks. The Falcon v3.03 / MiG-29 v1.02 patch was included in the installation and would automatically update any earlier version of Falcon to v3.03 and any earlier version of MiG-29 to v1.02. Hornet box rear Again it was suggested that owners of Hornet distribute the first two disks to any players of Falcon or MiG-29 to update to the latest version. Once installed, Operation Fighting Tiger could not be installed and a clean install of Falcon, OFT, optionally MiG-29 and then Hornet was required. For MiG-29 standalone owners it would be MiG-29, OFT and then Hornet. Again the installation would delete existing squadrons, so campaigns in progress would need to be completed before Hornet was installed. The installer readme contains a myriad of installation instructions for every possible combination of products as well as some undocumented features. For the rest of the article Hornet: Naval Strike Fighter will be referred to as Hornet. Falcon v3.03 / MiG-29 v1.02 A separate Falcon v3.03 patch was released in conjunction with Hornet v1.0 in December 1993, which would also update MiG-29 to v1.02, including the standalone MiG-29 product. Again the patch readme concentrates on the myriad of installation combinations available at the time. The only new change was to make both products comms compatible with Hornet v1.0 although the patch was cumulative, including all earlier fixes for Falcon and MiG-29. Compatibility set: Falcon v3.04, MiG-29 v1.03, Hornet v1.01 With the introduction of this compatibility set, the patching and versioning has become standardized. Patches are restricted to their respective product and all were made available in February 1994. In addition to product specific fixes and enhancements each patch contains the Acer BIOS compatibility fix and the Thrustmaster TM-STICK utility. Falcon v3.04 The patch notes limit the patch history to v3.02 with earlier fixes and changes described in the f3readme.txt file. This is a cumulative patch with all fixes and enhancements from earlier Falcon patches included. MiG-29 v1.03 There is a complete (if simplified) version history from v1.0. This is a cumulative patch with all fixes from all previous MiG-29 patches included. The patch is compatible with both addon and standalone editions. Hornet v1.01 As the first Hornet patch, all fixes and updates are detailed in the patch notes. Compatibility set: Falcon v3.05, MiG-29 v1.04, Hornet v1.02 This compatibility set sees each of the products reach their final release version. This set of patches was released in September 1994. Patches remain restricted to their product and in addition to the fixes and enhancements, the Thrustmaster TM-STICK utility was updated to v2.1. Falcon v3.05 The patch notes contain a complete patch history. This remains a cumulative patch with all fixes and enhancements from earlier Falcon patches included. This version would later be released on CD-ROM, featuring the readme file, a Falcon FAQ by Spectrum Holobyte and the complete manual in PDF format. MiG-29 v1.04 The patch notes contain a complete patch history. This remains a cumulative patch with all fixes and enhancements from earlier MiG-29 patches included. Addon and standalone editions of MiG-29 are supported. Hornet v1.02 The patch notes contain a complete patch history and a comprehensive description of changes. This remains a cumulative patch with all fixes and enhancements from earlier Hornet patches included. Falcon Gold Falcon Gold is a compilation comprising of Falcon v3.05, including Operation Fighting Tiger v3.05, MiG-29 v1.04 and Hornet v1.02. The release also included 'Art of the Kill', a series of instructional videos on fighter combat by Pete Bonanni. Developed by Spectrum Holobyte, Inc. and published by Spectrum Holobyte, Inc, MicroProse Software, Inc. and Tommo Inc. It was released in 1994 and later in September 1995 on a single CD. The cd contains the 3rd party Acer BIOS compatibility fix, Tseng ET4000 video card fix and the Thrustmaster TM-STICK utility. At least one release of Falcon Gold includes the earlier TM-STICK v1.9 rather than the later v2.1. The readme notes included, are for Falcon Gold edition with separate notes for Falcon, MiG-29 and Hornet. Falcon Gold is the version released on the Steam and GOG platforms. Art of the Kill The 'Art of the Kill' app received a single patch in July 1994, adding support for newer graphics cards to the video player. Official utilities There were a number of official utilities released as separate downloads or as extras in various products releases from Sphere, Spectrum Holobyte and MicroProse. Updated install program for Falcon 3.0 Released in December 1991 for Falcon 3.0 only. A number of customers had experienced difficulties in installing to a hard disk. This updated installer would be copied onto either a 3.5" or 5.25" floppy disk and run. During the installation process all five of the Falcon 3.0 disks would be required. This is probably identical to, or an earlier version of the improved installer which was included in the Falcon v3.0a patch. It can be found on the Internet Archive. Windows 95 boot disk maker Released in October 1995 by Spectrum Holobyte, after Falcon Gold was released. The boot disk maker made a boot disk that created an optimized Windows 95 configuration for use with Falcon 3.0 or a full installation of Falcon Gold. It is assumed this would be applicable to a Falcon v3.05, MiG-29 v1.04 and Hornet v1.02 install, although this has not been tested. It is not known if this is compatible with Windows 98. It can be found on the Internet Archive. Boot disk maker for MicroProse games Developed in August 1996 and released on the Falcon 3.0 CD-ROM edition. This is an integrated DOS/Windows 95 boot disk maker, creating a standard boot disk for use with both DOS and Windows 95 environments. The boot disk should free up over 600k of conventional memory, and allocate 2mb of expanded memory. It is not known if this is compatible with Windows 98. This is available on the Internet Archive. Official 3rd party utilities Official 3rd party utilities are defined as official patches/utilities released by a 3rd party supplier, specifically for Falcon, MiG-29 or Hornet that were later integrated into official patches or releases. Acer BIOS compatibility patch Owners of Acer computers, Acros computers or other computers with Acer motherboards using BIOS v1.2 could not play MiG-29 or Falcon 3.02. When either game was run, it would simply freeze with a blank screen. A Terminate and Stay Resident (TSR) utility was developed to fix this problem and a beta v1.01 was released as a separate download in September 1993. The utility was included in the MiG-29 v1.01 and Falcon v3.02.1 patches in October 1993 and later patches thereafter and remains in the Falcon 3.0 CD-ROM and Falcon Gold editions as an extra. It can be found on the Internet Archive. Thrustmaster WCS profile A set of Thrustmaster Weapon Control System (WCS) mark II (or mark I with UPROM upgrade) UPROM profile files were included with Falcon v3.02 and MiG-29 v1.0 in July 1993. They would continue to be included until Falcon v3.04, MiG-29 v1.03 and Hornet v1.01 when they were replaced by the TM-STICK utility. Thrustmaster TM-STICK utility Originally written by Ken "Stinger" Richardson, a prolific developer of Falcon utilities, and then jointly developed by Ken and Thrustmaster. There are currently three version commonly in circulation. Version 1.9 This version was, incorrectly bundled with on the Falcon Gold edition. It is not known if this mistake was corrected in the Steam and GOG digital releases. This version is compatible with: Falcon v3.02.1, v3.03 MiG-29 v1.01.1, v1.02 Hornet v1.00 Version 2.0 TM-STICK v2.0 would form the basis of joystick handling in Falcon v3.04, MiG-29 v1.03 and Hornet v1.01. These versions would include and retain compatibility with TM-STICK v2.0, allowing TM-STICK functions not included in the official patches to be used. Compatible with: Falcon v3.02.1, v3.03, v3.04 MiG-29 v1.01.1, v1.02, v1.03 Hornet v1.00, v1.01 Version 2.1 With the introduction of Falcon v3.05, MiG-29 v1.04 and Hornet v1.02 the TM-STICK utility was updated to v2.1. This is the version that should be used with the Falcon Gold edition. It can be found on the Internet Archive. Compatible with: Falcon v3.02.1, v3.03, v3.04, v3.05 MiG-29 v1.01.1, v1.02, v1.03, v1.04 Hornet v1.00, v1.01, v1.02 Tseng ET4000/w32 patch Owners of video cards using the Tseng ET4000/w32 chipset may have experienced problems with white flashing in the simulation. A file replacement patch was developed in September 1993 for MiG-29 v1.0, although this problem may have occurred across the product suite. It wouldn't be until the release of the Falcon 3.0 CD-ROM edition and later Falcon Gold that this patch would be integrated into releases as an extra. It can be found on the Internet Archive. Finally... Hopefully this is an accurate history of Falcon 3.0, Falcon 3.0: Operation Fighting Tiger, MiG-29: Deadly Adversary of Falcon 3.0 and Hornet: Naval Strike Fighter. It you notice any errors, mistakes, or stuff which is just plain wrong, please feel free to get in touch, so it can be corrected. If anyone has the Falcon v3.0e patch, please get in touch.
- Falcon 3.0: Operation DOSBox Staging
This is a guide on running Falcon 3.0 (Falcon) and it's addons, Falcon 3.0: Operation Fighting Tiger (OFT), MiG-29: Deadly Adversary of Falcon 3.0 (MiG-29) and Hornet: Naval Strike Fighter (Hornet) in DOSBox Staging. The guide will cover basic DOSBox Staging setup, High frame rate settings, controller setup, installation and patching of Falcon and the addons. some suggested official and unofficial mods & tools and finally running the sim. I normally assume that any installation disks or cd-roms will be ripped to disk/cd-rom images, as I believe this saves wear and tear on disks and drives, which are becoming more difficult to obtain as time passes. This is not an issue for those using a Steam or GOG digital release. Contents DOSBox Setup Thia guide assumes the latest version of DOSBox Staging will be used, which at time of writing is v0.82. The changes from the default configuration will be listed and any addition settings of interest. [sdl] host_rate = vrr As I have a variable refresh rate monitor, so I set this to vrr. If you don't, you may wish to leave this as the default of auto. [dosbox] vmemsize = 8 Set to the maximum, so Falcon is not affected by video memory. [render] glshader = crt-auto aspect = auto integer_scaling = auto viewport = fit These are the default values which are good settings for Falcon but if you wish to experiment with other shaders, aspect ratio or viewport size, this is where you would do it. [cpu] cpu_cycles = 18000 cycleup = 1000 cycledown = 1000 The cpu_cycles setting will be dependant on your particular pc. The accepted value for Falcon is 20000 but that 'feels' a little too fast on my PC, so I'm using 18000. A value of 20000 is a good starting point. The cycleup/down setting is a personal preference and you may wish to reduce it to a smaller increment when tweaking cycles. [voodoo] voodoo = false There is no 3dfx Voodoo acceleration so it's turned off. [mixer] reverb = medium chorus = normal These mixer settings are personal preference, but I believe they enhance the Falcon soundscape. [midi] mididevice = mt32 Midi music will use a DOSBox emulated mt32 device, which provided the optimum music experience when Falcon was developed. [mt32] model = cm32l romdir = "D:\Midi\Versioned" The later CM32L device is compatible with Falcon. Further details on how the midi was organised can be found in the 'DOSBox midi' article. [autoexec] imgmount a "D:\Games\Dos\Falcon 3.0\test\fdd\*.img" -t floppy mount c "D:\Games\Dos\Falcon 3.0\test\hdd" imgmount d "D:\Games\Dos\Falcon 3.0\test\cd\FalconGold.iso" c: # cd falcon3 # for earlier falcon install folder cd falconcd # for Falcon Gold cd-rom install folder darkmenu # my startup menu The floppy and cd-rom imgmount commands will be needed if you intend to install from floppy disk/cd-rom images. The folder used as a DOS hard disk by DOSBox is specified with the mount command. The hard disk folder and floppy/cd-rom images folders are based on my DOSBox game management strategy. The darkmenu line calls my entirely optional Falcon startup menu, described below. High frame rate setup The following details changes to apply if you wish to try High frame rate settings as described in this article by Omnicydle. [sdl] vsync = off presentation_mode = vfr [dosbox] dos_rate = 1000 [mouse] dos_mouse_immediate = true Controller setup Like many other DOS sims, Falcon requires a HOTAS setup limited to 4 axes. For those with 4 axes or less, this won't apply. For those with a HOTAS with more than 4 axes, HOTAS profiling software will need to be used to limit axes. In my case I'm able to use TM TARGET to create a suitable profile for a virtual controller with only 4 axes. They are as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle axis DX_Z_AXIS Rudder pedals DX_XROT_AXIS The corresponding settings in DOSBox Staging are set as follows: [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 The joystick type is set to 4axis corresponding to the 4 axes configured above. The other settings will be dependant on your controller/HOTAS setup and may require testing to find the optimal settings. The deadzone is personal preference and works well with my setup. My configuration My complete DOSBox Staging configuration is shown below: [sdl] host_rate = vrr vsync = off presentation_mode = vfr [dosbox] vmemsize = 8 dos_rate = 1000 [render] glshader = crt-auto aspect = auto integer_scaling = auto viewport = fit [cpu] cpu_cycles = 18000 cycleup = 1000 cycledown = 1000 [voodoo] voodoo = false [mouse] dos_mouse_immediate = true [mixer] reverb = medium chorus = normal [midi] mididevice = mt32 [mt32] model = cm32l romdir = "D:\Midi\Versioned" [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 [autoexec] imgmount a "D:\Games\Dos\Falcon 3.0\test\fdd\*.img" -t floppy mount c "D:\Games\Dos\Falcon 3.0\test\hdd" imgmount d "D:\Games\Dos\Falcon 3.0\test\cd\FalconGold.iso" c: # cd falcon3 # for earlier falcon install folder cd falconcd # for Falcon Gold cd-rom install folder darkmenu # my startup menu Installation & patching checkver utility included in some patches There is a 'relatively simple' rule of thumb when it comes to installing Falcon, the expansions and patches. Falcon, expansions and patches must be installed in an increasing compatibility set version order. You cannot apply an earlier compatibility set version to a later compatibility set version. You may apply multiple patches from the same compatibility set. If you're wondering what a compatibility set is or how a version of MiG-29 relates to a version of Falcon, given the large number of expansions and patches that exist, you may wish to take a look at the Falcon 3.0: Version & patch history article. There is a caveat to this rule, if there is specific official documentation that explains how to install an earlier expansion over a later product then this documentation should be followed. This is the case when adding the Operation Fighting Tiger expansion to the MiG-29 standalone edition. Nearly all patches can be found on the Internet Archive. Floppy disk editions Floppy disk product editions and any patches should be installed using DOSBox Staging. My personal preference is rip floppy disks into floppy disk images (.img) and mount the images in DOSBox, for reasons described earlier. Installing and patching floppy disk editions can be easier as they are usually earlier versions of the products that can be easily patched following the rule above. Falcon 3.0 This is the process for installing Falcon, each addon and the latest patches to upgrade it to a final release (or Falcon Gold) standard. The last two steps of applying the final MiG-29 and Hornet patches are often neglected (in fact missing from the v3.05 patch notes!), but are necessary to upgrade the files specific to MiG-29 and Hornet to their final versions, with most of the common files already upgraded by the Falcon v3.05 patch. We can do this as it complies with 'You may apply multiple patches from the same compatibility set.' The installation of each product and the versions installed once complete, is useful as it shows the installation/patching rule in practice: Install Falcon v3.0 Falcon v3.00 Install OFT Falcon/OFT v3.01 Install MiG-29 (expansion edition) Falcon/OFT v3.02, MiG-29 v1.0 Install Hornet Falcon/OFT v3.03, MiG-29 v1.02, Hornet v1.0 Apply Falcon v3.05 patch Falcon/OFT v3.05, MiG-29 v1.02, Hornet v1.0 Apply MiG-29 v1.04 patch Falcon/OFT v3.05, MiG-29 v1.04, Hornet v1.0 Apply Hornet v1.02 patch Falcon/OFT v3.05, MiG-29 v1.04, Hornet v1.02 MiG-29 standalone edition I don't have the standalone edition, so this is an educated guess. If you wish to install OFT then there are specific instructions included with the standalone edition that unfortunately have not been published digitally. Install MiG-29 standalone edition MiG-29 v? Install OFT (follow instructions) MiG-29 v?, OFT v? Install Hornet MiG-29 v1.02, OFT v3.03, Hornet v1.0 Apply MiG-29 v1.04 patch MiG-29 v1.04, OFT v3.05, Hornet v1.0 Apply Hornet v1.02 patch MiG-29 v1.04, OFT v3.05, Hornet v1.02 CD-ROM editions CD-ROM editions should be mounted and installed from DOSBox Staging, using either the physical CD-ROM or CD image. An iso CD image is suitable as there is no CD audio on the installation media. CD-ROM editions can be more problematic for expansions as they are often later versions released after the expansions. This means some expansions cannot be applied. For example, Falcon v3.0d released on CD-ROM, can be expanded and patched without issue as it is a relatively early version. However, Falcon v3.05 released on CD-ROM cannot use any of the expansions as Falcon is already at the final release version. The general steps are: Install CD-ROM version. Install other products in order: OFT, MiG-29, Hornet (if the expansion is a later version than installed CD-ROM product). Apply Falcon v3.05 patch (if installed and later than current installed version). Apply MiG-29 v1.04 patch (if installed and later than current installed version). Apply Hornet v1.02 patch (if installed and later than current installed version). Falcon Gold edition By comparison the Falcon Gold edition needs no sim patches with all products already at their final release version. There is just a single Art of the Kill patch to apply. Install Falcon Gold. Apply 'Art of the Kill' patch. Digital editions Digital editions are normally a digital release of Falcon Gold. At present I'm not sure if digital editions already have the Art of the Kill patch applied. Install digital edition. Apply 'Art of the Kill' patch (only if needed). Official utilities There are a number of official utilities which are not required, however they may be of some use to those running the sim on period correct legacy hardware. They are detailed in the earlier article, Falcon 3.0: Version & patch history. TM-STICK The only recommended utility is TM-STICK which reduces the joystick deadzone and allows changes to be made to the throttle detent, after which the various stages of afterburner are applied. It's usefulness will be determined by your specific controller setup but it's certainly worth trying out. Note: The Falcon Gold edition has the TM-STICK v1.9 utility included as an extra, but the latest versions of the Falcon and expansion patches were distributed with TM-STICK v2.1, available within the latest patches or separately at the Internet Archive. Unofficial utilities A huge number of utilities with various version have been distributed over the years, an earlier article. 'Falcon 3.0: Unofficial mods & tools', details them and the utilities that remain compatible with the latest versions. This guide assumes a vanilla experience for new players so the only recommended mod is F3 missile which changes the characteristics of the Stinger/SA-7B SAM missiles, making them less overpowered and more realistic. Once campaigning, you may find a campaign editor to be a valuable addition to your Falcon gameplay experience, and there are menu utilities to ease starting the sim or provide addition squadron backup and restore functions. These are detailed in the 'Falcon 3.0: Unofficial mods & tools' article. DarkMenu DarkMenu for Falcon DarkMenu is my entirely optional version of a Falcon startup menu, supporting MiG-29 and Hornet. It also supports the TM-STICK utility. It will run both earlier versions of the product suite and those found on the Falcon Gold edition. It will only show options relevant to the products installed. It is based on the PCGamingWiki addon launcher but heavily amended and enhanced. It can be found below. Installation requires, downloading, extracting and copying darkmenu.bat into your falcon3 or falconcd folder. Note: the campaign backup/restore has not been extensively tested with multiple campaigns so use at your own risk! Update: The DarkMenu has been slightly amended with the 'Quit' option replaced with 'Quit DOSBox', to close DOSBox, and 'Exit to DOS' to close the menu and return to the DOS prompt. This second option would allow any 3rd party utilities to be run during the DOSBox session. Running Falcon Running Falcon also applies any of the expansions. Start DOSBox Staging with your Falcon config. You can make things a bit easier by creating a specific Falcon shortcut to run DOSBox Staging with the Falcon config as described in the DOSBox game management article. Load the TM-STICK utility, if required and start Falcon, MiG-29 or Hornet! Remaining Issues There is an issue with the intro movies, at the required DOSBox cpu_cycles setting the intro movies will grind to a halt. There is no fix at present so skip past the intro movie. To view the intro correctly (which will slow the sim to a crawl when flying) set the cycles as follows: [cpu] cpu_cycles = 3000 In-game config Falcon system settings Unlike many other games, there is no separate config utility, with all configuration performed in-game. From the war room screen, select config and then system settings. The preferred settings are shown in the screenshot. In-game joystick calibration Simple but functional If joystick is selected as the flight control, calibration is performed the first time a mission is started. The flight control scheme can be changed and recalibration performed from the in-flight menu. After calibrating the joystick the throttle should be detected and can be calibrated. After the throttle, any rudder pedals should be detected and can be calibrated. Remember, if you are using the TM-STICK utility, make sure to load it before starting Falcon. Finally... Hopefully this guide and the supporting articles will help you understand the installation and patching strategy, the tools available and the DOSBox settings required to play the Falcon 3.0 series of classic flight sims. Good hunting...
- Tech refresh 2026: Successful (DOSBox Staging) candidate part 2 (G-Z)
This is a guide updating the various DOSBox configs produced for many of the guides, to the latest DOSBox Staging v0.83.0 release candidate 1. This version is a huge change over previous versions and was briefly covered in Tech refresh 2026: Successful (DOSBox Staging) candidate part 1 (0-F), however important changes are repeated below. Contents Overhauled frame presentation DOSBox Staging v0.82.2 required changing a few settings, so the DOS frames can be presented at a legacy friendly and more constant 70Hz rate identical to VGA card on CRT monitors . Early DOS sims seem to benefit greatly from this by running the game free of subtle timing issues which affected the subjective feel of the game. The settings were: [sdl] host_rate = sdi vsync = off presentation_mode = cfr [dosbox] dos_rate = default DOSBox Staging v0.83.0-RC1 has overhauled frame presentation providing the same 70Hz VGA rate 'out of the box'. The default settings are now: [sdl] vsync = off presentation_mode = auto [dosbox] dos_rate = default Mixer master volume The mixer master volume is now set to 50% to provide headroom to increase the volume without distortion. If the sound/music is too low it can be increased in the DOSBox cmd line or [autoexec] section of a config with: mixer master [:] # Some examples: mixer master 100 # 100% vol on both stereo channels (prev default) mixer master 75:85 # 75% vol on left, 85% on right The games Gunship 2000 Original articles. There is no specific support for a Flightstick Pro and 4axis provides stick, collective and rudder. The joystick must be timed enabled otherwise crashes in the game may occur. There are two configs for the VGA and EGA versions. In addition a launcher menu has been added. Harrier Jump Jet Original articles. The preferred joystick type is 4axis as the Flightstick Pro is not explicitly supported and this prevents the hat button from causing spurious actions in game. Throttle and rudder are supported. A revised launcher menu is included. Heroes of the 357th Original article. The defaults of DOSBox Staging means this becomes a very limited config of personal preferences and applicable joystick hardware. Hind Original article. The preferred joystick type is ch as the Flightstick Pro is supported. Voodoo is disabled as this is not supported by the DOS version. Jane's Combat Simulations: AH-64D Longbow/Jane's Longbow Gold Original article. The preferred joystick type is ch as the Flightstick Pro is supported. Voodoo is disabled as this is not supported by the DOS version. There are example [autoexec] commands for Longbow/Longbow Gold. JetFighter III Classic Original article. This config supports general midi with FluidSynth or an external (to DOSBox) MIDI component (e.g. VirtualMidiSynth). The Sound Canvas is enabled as the game supports this MIDI device. The MT32 is not properly supported due to a broken implementation (see List of MT-32-compatible computer games). Note: testing MIDI in the setup app does not work. The game supports stick, throttle and rudder but does not explicitly support the Flightstick Pro so a 4axis joystick type is used. A new launcher menu is added to run the game, setup or mission editor, view release notes or select a DOSBox MIDI device. The mission editor manual has been converted to pdf for easier use. M1 Tank Platoon Original articles. The joystick is set to 2axis as only 2 axes are supported. The original hardware was the OPL2 so Sound Blaster is set to sbpro1 to take advantage (if any) of dual OPL2 chips. MT32 is set to mt32_new as recommended in the VOGONS List of MT-32-compatible computer games. A revised and cleaned up menu has been added and should be placed in the DOSBox hard disk root folder alongside tank.bat, which it can replace. Megafortress The standalone build described in this article, uses the following updated config for the latest DOSBox Staging: GOG digital edition The GOG digital edition uses a specially created launcher app. In this earlier article, vanilla DOSBox was replaced by DOSBox Staging in this launcher app. To update DOSBox Staging follow the steps in the guide. This new version of DOSBox Staging uses this set of updated configs: Privateer 2: The Darkening The original article used a limited DOSBox Staging config to run the game once, in preparation for conversion to a Windows native version. This latest DOSBox Staging makes playing the DOS version a viable option. The game is extremely prone to freezing when playing video when general MIDI is selected, so the MIDI driver fix described in the article, 'Privateer 2: The Darkening' running in Windows 10 is still required. The joystick type has been changed to ch as there is specific support for the Flightstick Pro in the game, it must be timed enabled to allow in-game calibration to work. A launcher menu has been added to run the game, setup sound or choose a DOSBox general MIDI device. Silent Service II Original article. The joystick remains disabled. An autotype command has been added to skip past setup questions. Strike Commander Original article. The preferred joystick type is ch as the Flightstick Pro is supported. This config supports general midi with FluidSynth or an external (to DOSBox) MIDI component (e.g. VirtualMidiSynth). A CM32L is enabled as the game supports the LAPC-1 device compatible with the CM32L . A launcher menu has been added to run the game, setup sound or choose a DOSBox MIDI device. Subwar 2050 Original articles. The preferred joystick type is ch as the Flightstick Pro is supported. A throttle is available although a rudder is not. A revised launcher menu has been added. Super-VGA Harrier Original article. CPU cycles cleaned up in the config but mostly an updated config for this version of DOSBox Staging. TFX Original article. The config for TFX supports digital audio with the Sound Blaster 16 and Gravis Ultrasound. MIDI is supported with the CM32L and Sound Canvas SC-55/SCC-1. The preferred joystick type is ch as the Flightstick Pro is supported. The new launcher menu for TFX allows, running the game, running the setup app, viewing release notes and selecting a DOSBox MIDI device. A very loud Sound Canvas example video Tornado Original articles. This config continues to use the 4axis joystick type allowing the use of a relative axis throttle (rather than an absolute axis). This can be changed to the ch type as a Flightstick Pro is supported by the game. This allows the use of a POV hat at the expense of losing the throttle axis. Note: although the joystick type can be changed with a DOSBox Staging config command, the game is unable to detect any joysticks afterwards. The type must be specified in the config and remain unchanged. This game has problems with the built in DOSBox mouse driver when using the default 2 button mouse. Setting the built in driver to use a 3 button mouse resolves the issue. The launcher menu runs the game, setup or views the release notes. Wing Commander Original article. This config supports the W.C.A.T. mod. The DOSBox Staging config supplied with the mod has been updated to this DOSBox version. Some settings are omitted as they are now default settings in this DOSBox version. Wing Commander Privateer Original articles. This config switches to a 2axis joystick type as only a 2 axis stick is supported by the game. The config supports Fluid Synth or external (to DOSBox) MIDI devices (e.g. VirtualMidiSynth). It is believed that WaveBlaster, supported by the game, can be emulated with Sound Canvas support. Some options have been taken from the DOSBox Staging Wiki Game Issues for Wing Commander: Privateer. The launcher menu provides options to run Privateer, the expansion Righteous Fire, the setup utility or allows selection of a DOSBox MIDI device. Finally.. Huge thanks to John Novak and the rest of the DOSBox Staging team for such a significant DOSBox Staging release, and for help in resolving the Tornado mouse issue! Good hunting!
- Tech refresh 2026: Successful (DOSBox Staging) candidate part 1 (0-F)
This is a guide updating the various DOSBox configs produced for many of the guides, to the latest DOSBox Staging v0.83.0 release candidate 1. This version is a huge change over previous versions and includes: 100% authentic Roland Sound Canvas SC-55 emulation. Authentic CRT colour emulation. Totally overhauled frame presentation. Disk noise emulation. Improved mouse emulation. DOS command improvements, such as merging the IMGMOUNT and MOUNT commands. In short it's a huge release, and it can't be understate just how important the frame presentation changes are. The previous frame presentation discussed in Tech refresh 2026: DOSBox best practice, is now available out of the box with v0.83.0-RC1. This guide will be updating the existing DOSBox configs of earlier guides to make them fully v0.83.0-RC1 compatible. Each config will only detail the changes from the default DOSBox v0.083.0-RC1 config file. Contents Strategy Each game will receive an example config that has been tested, particular points of note will be discussed. These configs are example configs so they will need changing to take account of: Mixer volume personal preferences. Mixer reverb and chorus personal preferences. MT32 ROM folder. Soundfonts folder. Mount command folders and floppy/cd-rom image names. Joystick settings dependant on hardware. However, you will be starting with a complete DOSBox config that can be changed as required, instead of starting with an empty config. Overhauled frame presentation DOSBox Staging v0.82.2 required changing a few settings, so the DOS frames can be presented at a legacy friendly and more constant 70Hz rate identical to VGA card on CRT monitors . Early DOS sims seem to benefit greatly from this by running the game free of subtle timing issues which affected the subjective feel of the game. The settings were: [sdl] host_rate = sdi vsync = off presentation_mode = cfr [dosbox] dos_rate = default DOSBox Staging v0.83.0-RC1 has overhauled frame presentation providing the same 70Hz VGA rate 'out of the box'. The default settings are now: [sdl] vsync = off presentation_mode = auto [dosbox] dos_rate = default Mixer master volume The mixer master volume is now set to 50% to provide headroom to increase the volume without distortion. If the sound/music is too low it can be increased in the DOSBox cmd line or [autoexec] section of a config with: mixer master [:] # Some examples: mixer master 100 # 100% vol on both stereo channels (prev default) mixer master 75:85 # 75% vol on left, 85% on right The games 688 Attack Sub Original article. Mixer reverb and chorus settings follow the DOSBox Staging recommendations. A-10 Tank Killer Original articles. MT32 device set to mt32_old, as recommended in the VOGONS List of MT-32-compatible computer games. Air Power: Battle in the Skies Due to the involved installation and setup process, it's recommended to use this config with the setup guide, Air Power: Battle in DOSBox. The joystick is configured as a ch stick as the Flightstick Pro is supported. Apache (Longbow) Original article. These config files are for the Sound Blaster 16 and Gravis Ultrasound. The joystick is configured as a ch stick as the Flightstick Pro is supported. AV-8B Harrier Assault Original article. Cycles changed to reflect the new refresh rate. Black Knight: Marine Strike Fighter Original article. Black Knight does not support the MT32 properly but does support general MIDI (see List of MT-32-compatible computer games), so fluidsynth is used for music. The joystick is configured as a ch stick as the Flightstick Pro is supported. A revised menu is also provided allowing the setup utility to be run. Chuck Yeager's Air Combat Original article. There are two configs for Sound Blaster 16 and the Gravis Ultrasound. The joystick is configured as a 4 axis stick to allow a TSR to enable a throttle. A menu is also provided allowing the game or throttle setup utility to be run. EF2000 V2.0 The optimum way to run EF2000 remains the EF2000 Reloaded app utilizing a custom built DOSBox based on vanilla DOSBox. However a previous article covered running EF2000 with DOSBox Staging. This config updates the previous DOSBox Staging config. The joystick has been changed to a ch joystick type as the game supports the Flightstick Pro. The MIDI is provided by fluidsynth as the game does not properly support MT32 MIDI (see List of MT-32-compatible computer games). Elite Plus Original article. The autotype command is added as recommended in AUTOTYPE candidates. The Sound Blaster type is set to sbpro1 as the game was originally written for an Adlib OPL2 as noted in List of MT-32-compatible computer games. The joystick is set to 2axis as only 2 axes are supported. F-117A Nighthawk Stealth Fighter 2.0 Original article. The are two configs for the VGA and EGA version. Both versions use the F-117 menu from the mod article, F-117A Nighthawk Stealth Fighter 2.0 & Black Knight: Marine Strike Fighter: A PixelWings update. F-15 Strike Eagle II: Deluxe Edition Original article. The MT32 model is set to mt32_new and the Sound Blaster type is set to sbpro1 as the game was originally written for an Adlib OPL2 as recommended in List of MT-32-compatible computer games. F-15 Strike Eagle III Original article. The MT32 model is set to mt32_new as recommended in List of MT-32-compatible computer games. The joystick is set to ch as the Flightstick Pro is supported by the game. F-16 Fighting Falcon Original article. The joystick is set to ch as the Flightstick Pro is supported by the game. F-19 Stealth Fighter Original articles. The MT32 model is set to mt32_new and the Sound Blaster type is set to sbpro1 as the game was originally written for an Adlib OPL2 as recommended in List of MT-32-compatible computer games. The Innovation sound card is enabled as it is supported by the game. Cycles are adjusted to 3000 for the new refresh rate which seems to increase the effectiveness of weapons which never seemed to work properly as shown in this short video: F-22 Lightning II Original articles. The joystick is set to ch as the Flightstick Pro is supported by the game. F29 Retaliator Original article. The joystick is set to 2axis as only 2 axes are supported by the game. Falcon 3.0/Gold Original articles. The joystick is set to ch as the Flightstick Pro is supported by the game. There are two configs, the first using the new frame rate settings only, which doesn't sync the intro videos properly but is less intensive on the graphics card. The second changes the dos_rate and vmem_delay settings to sync the videos but at a higher graphics card usage. Both configs improve the subjective feel of the sim bringing it closer to the legacy hardware experience. A separate config is added for the Art of the Kill video app. Fleet Defender Gold Original article. The joystick is set to ch as the Flightstick Pro is supported by the game. There are two configs, the first is for the DOS only version of the game while the second is for the Gold version and supports a Win3.x install to run the video presentation app. Both versions set the joystick to ch as the Flightstick Pro is supported by the game. MIDI support is configured for external (to DOSBox) port devices (e.g. VirtualMidiSynth), MT32/CM32L, FluidSynth and Sound Canvas. Once the Sound Canvas ROMs are obtained the Jukebox app provides a useful way of comparing MIDI music. There is an enhanced launcher menu which allows the selection of MIDI output. Flight Unlimited Original Article. The joystick is set to 4axis as the Flightstick Pro, supported by the game, does not support a throttle. The animations in the FBU seem much improved with this DOSBox version. Finally.. Huge thanks to John Novak and the rest of the DOSBox Staging team for such a significant DOSBox Staging release! Good hunting!










