A guide to running DOS versions of Wing Commander III: Heart of the Tiger in DOSBox Staging. Converting DOS version to Windows compatible versions and optimising these to run natively in Win10. The third game in the Wing Commander series marked a radical change in the technology. The colorful animated cutscenes of I and II replaced with Full Motion Video featuring Hollywood actors, Mark Hamill, Malcolm McDowell, Tom Wilson, Jason Bernard, Ginger Lynn and featuring the voice acting talents of Tim Curry. The bitmaps of the previous games replaced with texture mapped polygons. The campaign marks a culmination of 30 years of war with the Kilrathi with the conflict ending one way or another. At the time it was considered groundbreaking blurring the lines between game or interactive movie and breaking records in game production costs at $3m. For the rest of this guide Wing Commander III: Heart of Tiger will be referred to as WC3. This guide will only be covering DOS and Windows versions. For further background information on WC3 it's recommended to take a look at the Wing Commander CIC. Contents Strategy Version & patch history CD retail edition (November 1994) ATI Mach 64 Patch (1994) Alternate Joystick Routines (January 1995) Joystick Patch for Notebook Gameport (May 1995) QVision Video Patch (May 1995) Joystick Patch for Thrustmaster FCS (TM) and 100%-compatible joysticks (Logitech Wingman Extreme) (May 1995) Kilrathi Saga edition (September 1996) EA CD-ROM Classics edition (1997) Windows 2000 Update (Kilrathi Saga edition) (May 2004) Movie Crashing Patch (Kilrathi Saga edition) (March 2009) DDHack (2010) Digital edition (September 2011) Wing Commander Loader (March 2020) Wing Commander 3 HD Video Pack (March 2021) Wing Commander III Enhancement Patch (May 2024) Wing Commander III Enhancement Patch VLC libraries (March 2025) Restored Scenes IFF Packs (February 2026) Patching strategies CD Retail, EA CD-ROM Classics and digital editions (DOSBox) CD Retail, EA CD-ROM Classics and digital editions (Windows 10/11) Kilrathi Saga edition Retail media Game management HOTAS config DOS editions HOTAS config DOSBox Staging config Installation and configuring Retail CD edition Merging discs Digital edition Sound options Sound Blaster Roland music Roland MT-32/LAPC-1 Roland Sound Canvas General MIDI music VirtualMIDISynth and MIDIMapper WC3 Launcher Installing Windows editions Wing Commander Loader (DOS editions) Retail CD version Creating a WingLoader compatible install Digital version Creating a fresh install Kilrathi Saga edition Installing Wing Commander III Enhancement Patch (all editions) Optional: Installing Wing Commander 3 HD Video Pack (all editions) Patching with Wing Commander Loader (DOS editions) Running Configuring Enhancement patch config (optional) In-game config HOTAS config (optional) Documents Digital edition Extras Novels Strategy guides Kilrathi Saga edition Other editions Strategy guides Example videos Finally... Strategy This guide is split into two main sections. The first covers the DOS version of the game, either the CD retail or the digital release running in DOSBox Staging. It will cover the various options for running the DOS version including recommendations. One advantage of the DOS version is the wide range of MIDI music options available. The second section covers converting the DOS releases to a native Windows release. It will also cover the fan made patches available to support the game under Win10 and optional patches to run an enhanced version of the game. It covers the steps necessary to convert one edition of the game in another and then the steps to create an enhanced version of the game compatible with Win10/11. Version & patch history The version and patch history provides an overview of the various releases over time and the patches they support. Not only is this useful for a DOS based DOSBox release or native Win10 release but may also be of use to those wishing to run the game on legacy hardware. This also helps avoid downloading patches that aren't required. CD retail edition (November 1994) The original CD retail edition was distributed in November 1994 on 4 x CD-ROM's. This is a DOS only release. ATI Mach 64 Patch (1994) An official patch from Origin Systems Inc. This patch fixes distorted videos in the Wing Commander III demo only for the ATI Mach 64 video card. It is not a recommended patch as it is only applicable to specific legacy hardware running the demo. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, ATI Mach 64 Patch. Alternate Joystick Routines (January 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: This alternate joystick DLL (set of alternate routines) is being provided for users who are experiencing problems with Wing Commander III's initial joystick calibration phase during the install program. You must have a joystick to use this patch. This is not a recommended patch and is only applicable for those having issues with legacy joysticks on legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III joystick calibration-fix. Internet Archive, Game Patches and Fixes Archive Letter W Wing Commander CIC, Wing Commander Encyclopedia, Alternate Joystick Routines. Joystick Patch for Notebook Gameport (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: WC3JOY.DLL is a set of alternate joystick routines used to provide support for Colorado Spectrum's Notebook Gameport. Joysticks tested with the Notebook Gameport in combination with this patch include the CH Flightstick, the CH Flightstick Pro, the Thrustmaster FCS, and the Gravis Analog Pro. This is not a recommended patch and is only applicable for those having issues with legacy joysticks on specific legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Colorado Spectrum Joystick Patch. QVision Video Patch (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: VIDEO.DLL is an alternate set of video routines used to provide support for certain video cards. VIDEO.DLL installs itself when Wing Commander III is initialized. The VIDEO.DLL that accompanies this text file is to be used for the Compaq QVision card only. During initialization, the patch will attempt to detect the Compaq QVision. If the Compaq QVision is not detected, the patch will not install itself and display a message asking you if you wish to continue. If the Compaq QVision is detected, a message will let you know the DLL was installed and you should be able to use the SVGA capabilities of the Compaq QVision. This is not a recommended patch and is only applicable for those having issues with specific legacy hardware. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III SVGA-patch for Compaq Qvision. Wing Commander CIC, Wing Commander Encyclopedia, QVision Video Patch. Joystick Patch for Thrustmaster FCS (TM) and 100%-compatible joysticks (Logitech Wingman Extreme) (May 1995) This is an official patch from Origin Systems Inc. Taken from the release notes: WC3JOY.DLL is a set of alternate joystick routines used to provide support for Thrustmaster (TM) and 100%-compatible joystick (such as the Logitech Wingman Extreme). Joysticks tested include the Thrustmaster FCS, the Thrustmaster FLCS, and the Logitech Wingman Extreme. This is not a recommended patch and is only applicable for those having issues with specific legacy joysticks. It is not required when using DOSBox on Win10/11. It is available from: Internet Archive, Wing Commander III Thrustmaster support. Wing Commander CIC, Wing Commander Encyclopedia, Thrustmaster Joystick Patch. Kilrathi Saga edition (September 1996) The Kilrathi Saga is the a compilation of Windows ports of Wing Commander, Wing Commander II and Wing Commander III. This was released on 5 x CDs with the first CD for WC1 & 2 and the remaining 4 for WC3. This was considered the optimum version of WC1 (and still is for WC2) until the AllTinker W.C.A.T. mod for WC1, due to unofficial fan made patches for these games supporting later versions of Windows. EA CD-ROM Classics edition (1997) The EA CD-ROM Classics edition remains the DOS version of the game enhanced with a WIn95 installer app. It was distributed on 4 x CDs. Although not explicitly covered in this guide, once installed in Windows the DOSBox setup process and conversion to a Windows version should be very similar. Windows 2000 Update (Kilrathi Saga edition) (May 2004) Created by NStriker. This patch may also fix compatibility issues in WinXP. Taken from some creator notes: I've created patches for WC3 Kilrathi Saga, WC4 CD, and WC4 DVD that fix an offending API call and allow them to run under Win2K. There still seem to be some outstanding issues like WC3 being unstable in general and I have yet to get my joystick to work in WC4, though I believe neither are related to my patches. This is no longer a recommended patch for WC3 having been superseded by a later 'Mash' patch. Unfortunately it can't be downloaded as Windows 10 reports a probable virus false positive. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Windows 2000 Update (Kilrathi Saga edition) Movie Crashing Patch (Kilrathi Saga edition) (March 2009) Created by by 'Mash' Matt Wells the first version was released in 2009. The latest release of this patch, v1.2, occurred in May 2011. This patch is compatible with the DDHack patch. Taken from the release notes: This patch is an attempt to fix some of the problems associated with running the Windows version of Wing Commander 3 on modern OSes and on modern hardware. This release includes a fix for the 'Ingame Movie Crashing Bug', a slowdown fix for the Nav Map Screen and a series of slowdown fixes for the Pre Flight Power-up Screen. This patch was created and tested on Windows 7 64 Bit but should also work fine on XP or Vista, 32 or 64 Bit. It will probably work with Windows 2000 as well. No Game files are modified to install this patch. Instead the patch works by pretending to be the Direct Sound Library file (dsound.dll) which the Wing Commander EXE loads itself when it is run. As well as modifying the game the patch also redirects calls made to the real "dsound.dll" where it resides in the Windows System Directory. Note: This patch now exploits the "dsound.dll" rather than the "ddraw.dll" as the previous version. This was done to avoid clashing with Sol_hsa's "DirectDraw Hack" graphics patch. This is no longer a recommended patch for WC3 having been superseded by a later 'Mash' patch. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Movie Crashing Patch (Kilrathi Saga edition) DDHack (2010) Created by Jari Komppa (Sol). The latest version of this patch is v1.0. Taken from the release notes: This is a replacement ddraw.dll designed to work better with the host environment. Meaning, no palette corruption, no switching the whole system to a different graphics mode, no 256 color mode windows, no need to kill explorer.exe, etc. Technically, it's a DLL that implements the directdraw interface (directdraw, directdraw2, directdrawsurface and directdrawpalette) - or well, the parts of it that I have implemented so far. Then it takes what the game wants to display, dumps it into an OpenGL texture and renders this on screen. ddhack is still at a very early stage, and may be somewhat unstable. It has been mainly tested with the 'kilrathi saga' wing commander 1, wing commander 2, wing commander 3 and wing commander 4 CD. If any other directdraw programs work, it's a miracle! This is no longer a recommended patch for WC3 having been superseded by later patches. It is available from: Google Code Archive, ddhack Wing Commander CIC, Wing Commander Encyclopedia, DirectDraw Hack Digital edition (September 2011) The digital edition is comparable to the CD retail edition. The 4 x CDs of files are merged into a single image file, removing the need for swapping between CD images when playing. The digital edition is available on gog.com and at Electronic Arts. Wing Commander Loader (March 2020) The Wing Commander Loader (or WingLoader) is a utility for launching optimised versions of the Kilrathi Saga versions of WC1 and WC2. However, it also includes patching support for WC3. Created by Destro. the latest version of the WingLoader is v0.92. Taken from the release notes: Wing Loader is a launcher for the Kilrathi Saga versions of Wing Commander 1 & 2 that aims to deliver the most complete versions of these classic masterpieces. Features: Wing Commader III, IV, Prophecy & Secret Ops GOG Support and Wing Commander Saga! What fun! This is the recommended utility for converting from DOS WC3 releases to a Windows compatible release. This utility is available from: MEGA, WingLoader v0.92 - Hotfix.zip Wing Commander CIC, Forums, Wing Commander Chat Zone, Fan Projects & Editing, Wing Loader (KS/WCDX) Loader & Voice Over Mod Wing Commander 3 HD Video Pack (March 2021) The Wing Commander 3 HD Video Pack, created by ODVS is an AI upscaled set of WC3 movies played throughout the campaign. It also includes restored content which was originally missing. The current version of the pack is v2.0. When first released this was not integrated into the game, a situation remedied with the Wing Commander III Enhancement Patch. Taken from ODVS notes: As well as improving remaster quality over V1.0, V2.0 contains the following improvements: All FMV footage remastered to 1080p Full HD using Machine Learning AI Original low frame-rate of 15fps remastered to full 30fps using Machine Learning AI Improved contrast balance in all footage This is a recommended pack for Windows versions of the game, for an optimised experience. It is available from: Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander 3 HD Video Pack Wing Commander III Enhancement Patch (May 2024) The Wing Commander III Enhancement Patch, created by 'Mash' Matt Wells, adds higher resolutions and improved window handling with DirectX 11. It also supports the Wing Commander 3 HD Video Pack and adds native controller support to the game allowing the use of stick, throttle and rudder. The latest version of the patch is v0.14.1. Taken from the GitHub description: This patch was created for the Windows version of the PC game "Wing Commander III". Which came as part of the "Wing Commander Kilrathi Saga" compilation. It can also be used with the GOG DOS version of the game. But will require some extra files and a little more work to set things up. The best and easiest option is to install Wing Loader. Wing Loader also has some upgrades and fixes for other Wing Commander games. This patch uses DirectX 11 for rendering and will likely require Windows 10 or greater to use. This patch makes use of DLL injection to make changes to the game's executable file. And is loaded by the game itself by pretending to be the Direct Draw library file "ddraw.dll". It is thus incompatible with patches which use the same method to load eg. DirectDraw_Hack. HD Movie playback is achieved using libvlc. This is the recommended patch for enhancing WC3 and providing compatibility with Win10/11. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch Wing Commander III Enhancement Patch VLC libraries (March 2025) As the above description notes, 'HD Movie playback is achieved using libvlc.'. This required obtaining all the VLC libraries as part of one complete [package. The Wing Commander III Enhancement Patch VLC libraries (libvlc_min_pack_3.0.21) are the minimal set of VLC libraries required by the enhancement patch. This is recommended patch when running the enhancement patch. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch, Releases, libvlc_min_pack_3.0.21 Restored Scenes IFF Packs (February 2026) The Wing Commander III Enhancement Patch supports the Wing Commander 3 HD Video Pack. The HD Video pack also includes restored content videos, however, having the videos is not enough to restore them in-game. The Restored Scenes IFF Packs (Restored_Scenes_IFF_Packs) are the set of files that restore the restored video content to the game campaign. This is recommended patch when running the Wing Commander III Enhancement Patch and Wing Commander 3 HD Video Pack. It is available from: GitHub, mattwells77, Wing_Commander_III_Enhancement_Patch, Releases, Restored_Scenes_IFF_Packs Patching strategies The following are the recommended patching strategies for each edition. CD Retail, EA CD-ROM Classics and digital editions (DOSBox) Install Wing Commander III release. CD Retail, EA CD-ROM Classics and digital editions (Windows 10/11) Install Wing Commander III release. Install WingLoader utility. Apply Wing Commander III Enhancement Patch. Apply Wing Commander III Enhancement Patch VLC libraries. Optional: Apply Wing Commander 3 HD Video Pack. Optional: Apply Restored Scenes IFF Packs. Patch with WingLoader utility. Kilrathi Saga edition Install Wing Commander III (Kilrathi Saga) release. Apply Wing Commander III Enhancement Patch. Apply Wing Commander III Enhancement Patch VLC libraries. Optional: Apply Wing Commander 3 HD Video Pack. Optional: Apply Restored Scenes IFF Packs. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CDs. Game management It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders for the DOS version are: cd - for any cd images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. When using the DOS version of the game, these management folders can be found in the following game folder (as an example): D:\Games\DOS\Wing Commander 3 When using the Windows version of the game (or converting to the Windows version, these management folders can be found in the following game folder (as an example): D:\Games\Win\Wing Commander 3 Setup HOTAS config 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 controller is detected by DOSBox. [6][7][8]. There are separate configs for DOS and Windows versions. DOS editions This section of the guide deals with the DOS editions of the game and optimising the DOSBox and installation as much as possible. The DOS version may be preferable for a legacy retro experience or for MIDI music which has a variety of options. HOTAS config Only the joystick is supported with the DOS version. 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 DOSBox Staging config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing). # This is the configuration file for Wing Commander III: Heart of the Tiger. [render] deinterlacing = on [cpu] cpu_cycles_protected = 75000 cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mt32] model = cm32l romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] # Other valid options: mt32, fluidsynth, port mididevice = soundcanvas [joystick] joysticktype = ch timed = off swap34 = on deadzone = 0 [autoexec] @echo off # Hard disk folder # mount c "D:\Games\Dos\Wing Commander 3\hdd" # Digital edition install folder # mount c "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III" # Retail CD images # mount d "D:\Games\Dos\Wing Commander 3\cd\wc3*.iso" -t cdrom # Merged retail CDs image # mount d "D:\Games\Dos\Wing Commander 3\cd\data.dat" -t cdrom # Digital edition CD image # mount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III\data.dat" -t cdrom mixer master 100 /noshow d: wc3.exe pause exit The following zip file contains this example DOSBox Staging config. It should be changed to match your hardware and personal preferences. DOSBox Staging introduces a new deinterlacer feature to remove black lines from full motion videos (FMVs). This is enabled in the [render] section of the config, there are additional settings to control the strength of the deinterlacing. The cpu_cycle setting of 75000 as recommended in the DOSBox Staging wiki. cycleup/down settings are changed to values rather than percentages. Voodoo emulation isn't required and is disabled. The mixer settings are a personal preference. WC3 supports a wide variety of MIDI sound devices including Roland MIDI and general MIDI devices. Sound Blaster is also another option for music. The default Sound Blaster settings are appropriate for Sound Blaster music and digital sounds. Multiple general MIDI devices are configured in the [mt32], [fluidsynth] and [soundcanvas] sections. A Win10 MIDI synth can also be used with DOSBox Staging (see Compatibility tools). The optimum Roland sound settings use the CM32L device, as described in List of MT-32-compatible computer games. The FluidSynth soundfont is a personal preference. In the above example, Shan SGM Pro v15 is used, an excellent general purpose soundfont. DOSBox Staging v0.83.0-RC1 introduces Sound Canvas support. The Sound Canvas config, like the Roland MIDI config, requires a model to be selected and a folder containing the Sound Canvas ROMs to be specified. The MIDI section specifies a the soundcanvas MIDI device as this was the original hardware the game was designed for as noted in List of MT-32-compatible computer games. Alternate DOSBox MIDI components can be chosen or an external Win10/11 MIDI synth (see VirtualMIDISynth and MIDIMapper). The joystick settings are a personal preference and suitable for my joystick hardware. A ch joystick type allows the joystick hat to be used in-game. The autoexec mount settings are examples only, demonstrating how to mount multiple floppy disk images or a cd image for CD or digital editions. The mixer setting restores the master volume to 100%. The game is run from the CD/image. If game config settings aren't available, this will run the installation and configuration utility built into the game. Installation and configuring The DOS version has an unusual installer integrated into the game executable and most game files remain on the CD/image. The first time WC3 is run there are no config files available and the installer utility is run, which created these config files. If the config files are available, the game is run without invoking the install utility. To run the install utility the first time, simply run the game: D:\> wc3.exe Once config files are created the installation utility can be run again with: D:\> wc3.exe -i The steps to configure and install are shown in the gallery below: Retail CD edition For the retail CD version the following mount commands should be used: [autoexec] ... # Hard disk folder mount c "D:\Games\Dos\Wing Commander 3\hdd" # Retail CD images mount d "D:\Games\Dos\Wing Commander 3\cd\wc3*.iso" -t cdrom ... It's assumed the names given to the WC3 CD images will start wc3. The wildcard in the mount command mounts all CD images to the same drive, use Ctrl + F4 to swap between images. Merging discs To prevent CD image swapping mid-game the 4 x CD images can be merged into a single image. The process to do so in Win10 is: Mount the CD image of WC3 disc 1 in Win10 and copy the contents of the CD image to a folder, e.g. D:\Games\DOS\Wing Commander 3\cd\merged Do this for each of the other 3 CD images, replacing duplicate files as required. Use a CD burning/imaging utility (e.g. ImgBurn) to create a CD image of the merged folder contents. Note: only the folder contents/files should be added to the CD image, not the folder itself. Open the new single CD image in Win10 and make sure files can be seen and accessed, e.g. open the readme.txt file. Eject the CD image. The final single CD image can be renamed to data.dat. This creates a suitable CD image suitable for conversion to a Windows version. The following mount command replaces the earlier CD mount command: [autoexec] ... # Merged retail CDs image mount d "D:\Games\Dos\Wing Commander 3\cd\data.dat" -t cdrom ... Digital edition The digital edition should installed using the digital platform client app (e.g. gog.com Galaxy) or digital platform offline installer package. This guide uses the following folder as a digital edition installation folder example: D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III For the digital version the following mount commands should be used: [autoexec] ... # Digital edition install folder mount c "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III" # Digital edition CD image mount d "D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III\data.dat" -t cdrom ... Sound options WC3 supports a wide variety of digital sound and music options. The WC3 Launcher can swap between MIDI devices during a DOSBox session, and coupled with VirtualMIDISynth allows switching between soundfonts 'on-the-fly'. However once a preference has been settled on, you may wish to make this the default without having to choose the preferred sound/music devices each time. When reconfiguring music/sound devices the following command should be used: D:\> wc3 -i Sound Blaster Can be selected for music and sound. The default DOSBox config Sound Blaster settings are Ideal. Music/sound should be set in the config utility to Sound Blaster 16. Sound Blaster 16 digital settings: Digital I/O port: 220 Digital IRQ: 7 Digital DMA Lo: 1 Digital DMA: Hi: 5 Sound Blaster 16 music settings: N/A, simply select Sound Blaster 16 as the music device. Roland music This includes the Roland MT-32 and Roland Sound Canvas. Can be selected for music only. The music setting for both devices is: I/O port: 330 Roland MT-32/LAPC-1 In the DOSBox Staging config, the optimum Roland MT-32 setting is the cm32l device, as described in List of MT-32-compatible computer games. [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 In the config utility, under music device, select: Roland MT-32/LAPC-1. Roland Sound Canvas In the DOSBox Staging config, the optimum Sound Canvas setting is the sc55 device, as described in List of MT-32-compatible computer games. [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = soundcanvas In the config utility, under music device, select the dedicated MIDI driver: Roland RAP-10/SCC-1 or the general MIDI driver: MPU-401 General Midi. General MIDI music Can be selected for music only. In the config utility, under music device, select: MPU-401 General MIDI. The music setting for General MIDI devices is: I/O port: 330 DOSBox Staging built-in MIDI devices includes FluidSynth or Sound Canvas, e.g. [fluidsynth] soundfont = "Shan SGM Pro 15.SF2" soundfont_dir = "D:\Midi\Soundfonts" [midi] mididevice = fluidsynth # or mididevice = soundcanvas DOSBox Staging also supports external (to DOSBox) MIDI devices. For further info consult, DOSBox Staging and MIDI, e.g. [midi] mididevice = port midiconfig = 0 VirtualMIDISynth and MIDIMapper These are optional MIDI tools that can be used by DOSBox Staging and WC3, as General MIDI (GM) is supported as a WC3 music option. The built in features of DOSBox Staging can do the job of these tools but they may make things easier for those who wish to try out multiple soundfonts (VirtualMIDISynth) or switch between different Win10/11 MIDI synths (MIDIMapper). For a further discussion on using these tools with the latest DOSBox Staging, see DOSBox Staging and MIDI. WC3 Launcher This is a batch file menu launcher (wc3menu.bat) that performs a number of functions: Start the game. Run the install/setup utility to reconfigure music/sound settings. Switch to a different DOSBox MIDI device (MT32, FluidSynth or Sound Canvas). Switch to an external (Port) MIDI device (e.g. VirtualMIDISynth, MIDIMapper). Return to the DOSBox command prompt. Close DOSBox. This launcher should be compatible with cd retail and digital editions. It allows switching MIDI devices to try out various MIDI options, to find a preference. Installing Download the launcher below: In Win10./11, extract the menu to the game installation folder. Change the WC3 DOSBox Staging config as shown: From [autoexec] ... d: wc3.exe pause exit To [autoexec] ... c: cd \ call wc3menu.bat Windows editions The WIndows version of WC3 includes the Kilrathi Saga edition or a DOS edition converted into the Windows version. The Windows version replaces MIDI for digital music, losing the ability to change MIDI synths or soundfonts. The enhanced version also adds native controller support allowing the game to support stick, throttle and rudder pedals. The steps to install and enhance the Kilrathi Saga or converted DOS versions are as follows: Wing Commander Loader (DOS editions) For those converting a DOS edition, the first step is download and install the Wing Commander Loader (WingLoader). Download Wingloader and extract the contents of the zip archive. An example folder used in the rest of this guide is: D:\Games\Win\WingLoader Within the WingLoader installation folder create a Wing Commander III folder, e.g. D:\Games\Win\WingLoader\Wing Commander III Retail CD version Th retail CD version is not officially supported by WingLoader, however the digital (gog.com) edition is. This section covers creating a 'digital edition like' install compatible with WingLoader, from an existing CD retail install. Creating a WingLoader compatible install These steps should be performed in Win10/11: Copy the following files from the following game folders in Win10/11: D:\Games\DOS\Wing Commander 3\hdd\WC3 OBJECTS.TRE WC3.CFG WC3.CON D:\Games\DOS\Wing Commander 3\cd DATA.DAT Into the WingLoader WC3 folder: D:\Games\Win\WingLoader\Wing Commander III Digital version The digital edition is compatible with WingLoader but it recommended to create a fresh install in the WingLoader WC3 folder. The WingLoader and Enhancement patches will apply comprehensive changes. Using the original digital edition installation folder is possible, but if the game install is validated or reinstalled after patching, then all the patch changes will be lost. A fresh install in a new folder means the patch changes cannot be accidentally lost. Creating a fresh install These steps should be performed in Win10/11: Copy the following files from the following digital edition game folder in Win10/11: D:\Program Files (x86)\GOG Galaxy\Games\Wing Commander III OBJECTS.TRE WC3.CFG WC3.CON DATA.DAT Into the WingLoader WC3 folder: D:\Games\Win\WingLoader\Wing Commander III Kilrathi Saga edition The Kilrathi Saga edition is already a Windows edition of the game. There is no need for the WIngLoader patch to convert this edition. The Kilrathi Sage uses a 32-bit installer app making it compatible with Win10/11. When installing, only WC3 needs to be installed in a suitable installation folder of your choosing. For the rest of this guide the following example is used: D:\Games\Win\Kilrathi Saga\Wing Commander III Installing Wing Commander III Enhancement Patch (all editions) These steps should be performed in Win10/11: Download the Wing Commander III Enhancement Patch and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder: D:\Games\Win\WingLoader\Wing Commander III D:\Games\Win\Kilrathi Saga\Wing Commander III Download the Wing Commander III Enhancement Patch VLC libraries and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Optional: Installing Wing Commander 3 HD Video Pack (all editions) If the optional Wing Commander 3 HD Video Pack is to be installed and used in-game, follow these steps in Win10/11: Download the Wing Commander 3 HD Video Pack and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Download the Restored Scenes IFF Packs and extract the contents of patch into the WingLoader WC3 folder or Kilrathi Sage installation folder. Patching with Wing Commander Loader (DOS editions) The following gallery shows the WingLoader patching steps: Go to the WingLoader folder: D:\Games\Win\WingLoader Run WingLoader.exe. Once patching is complete, simply close the WingLoader window. Running When running the Kilrathi Saga or converted DOS editions the following game executable should be used: D:\Games\Win\WingLoader\Wing Commander III\wc3w.exe D:\Games\Win\Kilrathi Saga\Wing Commander III\wc3w.exe Configuring With the addition of the patch and native controller support, there's some additional configuration to optimise the game. Enhancement patch config (optional) There is a separate config file (wc3w_en.ini) for the Wing Commander III Enhancement Patch. Each setting is explained in the file, however the following settings were used in combination with the Wing Commander 3 HD Video Pack: [MOVIES] SHOW_ORIGINAL_MOVIES_INTERLACED=0 ENABLE_ORIGINAL_MOVIES_LIMITED_SCALING=0 ENABLE_ORIGINAL_MOVIES_LINEAR_UPSCALING=1 In-game config Configuration options are shown in the gallery below. In-game config options set from the Main Terminal (in-game). The Joystick Calibration button now opens a new native controller configuration dialog. Finally when on a mission (or in the in-game simulator) Alt + O will open the in-flight options. HOTAS config (optional) The new controller support means the game can now support stick, throttle and rudder pedals. It would seem there is no need for an external HOTAS config, however, the Controller Setup dialog will list all controller devices as 'HID compliant device'. This makes configuration 'trial and error' until the correct controller and axis is located. Note: this is an entirely optional step. Creating a virtual controller with the 4 axes supported in-game means only a single controller is available with only the required 4 axes, which may make thing easier. This also allows the advanced facilities available to the HOTAS profiling software to be used, e.g. button macros, chained commands, etc. It is recommended to map physical to Windows axes as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_ZROT_AXIS Documents The following documents are available: Digital edition Additional resources downloaded separately. 'Victory Streak' manual. Playguide. Reference Card. Warbirds (fighter datasheets). Extras WC3 Behind the Scenes Tape. WC3 Deleted Scenes. WC3 Script. WC3 Wallpaper. The Wing Commander Universe Bible. Novels Fleet Action. Strategy guides Origin's Official Guide to Wing Commander III. Wing Commander III Authorized Combat Guide. Kilrathi Saga edition Kilrathi Saga manual, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander: The Kilrathi Saga Manual Other editions 'Victory Streak' manual, pdf download. Internet Archive, Wing Commander III (Victory Streak) Wing Commander CIC, Wing Commander Encyclopedia, Victory Streak Playguide, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander III: Heart of the Tiger Playguide Reference Card, pdf download. Wing Commander CIC, Wing Commander Encyclopedia, Wing Commander III Reference Card (PDF) Warbirds datasheets, jpg/pdf download. Internet Archive, Wing Commander III (Foldout) Wing Commander CIC, Wing Commander Encyclopedia, Warbirds (JPG) Wing Commander CIC, Wing Commander Encyclopedia, Warbirds (PDF) Wing Commander III Additional Troubleshooting, pdf download. Internet Archive, Wing Commander III (Troubleshooting) Strategy guides Origin's Official Guide to Wing Commander III. Internet Archive, Wing Commander III Guide Wing Commander III Authorized Combat Guide. Internet Archive, Wing Commander III Combat Guide Wing Commander III The Ultimate Strategy Guide Internet Archive, Wing Commander III The Ultimate Strategy Guide Example videos Wing Commander III in DOSBox Staging v0.83.0-RC1 Wing Commander III running natively in Win10 Finally... Credit and thanks for all the hard work involved goes to: Wing Commander CIC, for all the patches, forums, contributors, documents, in fact the premiere resource for Wing Commander franchise information on the Internet. Internet Archive for hosting documents and patches. NStriker. for Windows 2000 Update (Kilrathi Saga edition) fan patch. 'Mash' Matt Wells for Movie Crashing Patch (Kilrathi Saga edition), Wing Commander III Enhancement Patch and associated fan patches. Jari Komppa (Sol) for the DDHack fan patch. Destro for the Wing Commander Loader. ODVS for the Wing Commander 3 HD Video Pack. John Novak and the DOSBox Staging team for DOSBox Staging v0.83.0-RC1. CoolSoft developers for VirtualMIDISynth and MIDIMapper. Good hunting!

A guide to the fan-made USNRaptor campaigns for Jane's Fighters Anthology (JFA). Those old-hands of JFA are probably already well aware of the dedicated work by USNRaptor in creating some of the premier fan-made JFA campaigns available. For those that are new to JFA or to those that have only played the official campaigns and are looking for more JFA, the USNRaptor campaigns provide a huge amount of high quality extra JFA. This is a quick guide on what's available, where to find them and some hints on running fan-made campaigns. Website and Discord For those interested in USNRaptor's campaigns, it is highly recommended to visit USNRaptor's Jane's Fighters Anthology for more information and many other resources related to JFA. For those that frequent Discord, the Combat Flight Sim Tavern server hosts a number of Jane's Fighters Anthology channels. Existing game preparation If JFA has already been installed then there is some preparation work to ensure the campaigns will work properly. This advice applies to any JFA fan made campaign not just the USNRaptor campaigns. Standard game library timestamps The issue is described in USNRaptors Installation Guide for Win10/11 Users. To summarize: If JFA has been recently installed, the timestamps on the standard JFA game libraries will match the installation date, e.g. 1st August 2026. Fan made campaigns created prior to this date, will use libraries with an earlier timestamp, e.g 1st March 2020. JFA will use data from the latest library it can find. This means that incorrect data could be used, if taken from a standard library (with a later timestamp, 1st August 2026) rather than from the intended campaign library (with an earlier timestamp, 1st March 2020). If you wish to use your existing game installation with these campaigns you may need to change the standard game libraries timestamps to a much earlier date. Fortunately this is straightforward using the Win10/11 PowerShell. Note: Powershell can be found in the Start Menu. It should be run as Administrator. Assuming D:\Fighters Anthology is the installation folder then: PS C:\WINDOWS\system32> cd "D:\Fighters Anthology" PS D:\Fighters Anthology> (Get-Item FA_1.LIB).creationtime=$(Get-Date "1/1/1998 1:00am") PS D:\Fighters Anthology> (Get-Item FA_1.LIB).lastwritetime=$(Get-Date "1/1/1998 1:00am") ... PS D:\Fighters Anthology> exit Changes the creation and last modified date of the FA_1.LIB standard JFA library to a much earlier 1st Jan 1998 at 1:00am timestamp. This should be repeated for the other standard JFA libraries listed below: FA_2.LIB FA_3.LIB FA_4B.LIB FA_4C.LIB FA_4D.LIB FA_7.LIB FA_10.LIB FA_10B.LIB FA_11.LIB FA_11B.LIB This ensures fan-made campaigns will always be using the correct data from campaign libraries, if required.. Shapefix library This library uses aircraft models imported from some of earlier games comprising the anthology to improve aircraft models in JFA. This library is not compatible with the USNRaptor campaigns and should not be used. Campaigns All campaigns are stand-alone, and only require a properly installed JFA, patched to v1.02, and libraries properly time stamped using the year 1998.. All missions playable as both single and campaign missions.The campaigns are listed alphabetically. Aegean Campaign 1997 Aegean Campaign 1997 is a 40 mission fictional campaign. Missions involve seven different mission types flying eight different aircraft. The campaign includes new aircraft and vehicle textures. A great campaign for beginners and returning players. Note: This campaign is bundled with the Ukraine Campaign 1994. Available from Aegean Campaign 1997. Baltic Campaign 1976 Baltic Campaign 1976 is a 40 mission NATO campaign and a 40 mission USSR campaign, based on a customised JFA Baltic 2009 campaign. Missions involve six mission types flying nine aircraft for NATO and seven mission types flying ten aircraft for the USSR. The campaign includes a wide range of shapes/textures from many other user mods and improved aircraft, ordnance, ships, and weapon systems. Moderately difficult missions, making it suitable for the experienced JFA player. Available from Baltic Campaign 1976. Egypt Campaign 1995 Egypt Campaign 1995 is a 40 mission campaign, based on a customised JFA Egypt campaign. Missions involve six mission types flying eight aircraft. A great campaign for beginners and returning players. Note: This campaign is bundled with the Israel Campaign 2001. Available from Egypt Campaign 1995. Israel Campaign 2001 Israel Campaign 2001 is a 40 mission campaign based on a highly customised version of an earlier USNRaptor Israel Campaign 2001. Missions involve eight mission types flying nine aircraft. Moderately difficult missions, making it suitable for the experienced JFA player. Note: This campaign is bundled with the Egypt Campaign 1995. Available from Israel Campaign 2001. Korea Campaign 2024 Korea Campaign 2024 is a 40 mission campaign. This campaign is a culmination of 20 years of work from various JFA modders across a multitude of projects. The campaign uses modified aircraft, weapons, ships and SAMs in addition to all new terrain. Changes include Chinese Aircraft Carrier, armed Guard Towers, IRBMs, M48 Patton Tanks, Trains, and suicide-bomb Trucks. Modified AN-2, IL-76, MiG-19, and P-3. Missions involve thirteen aircraft and a driveable M163 Vulcan AAA vehicle, updated Korean Map & In-Flight Map, new information files for the MIM-104 and S-300, six new voice-sound files, and several new scenery objects. Expert missions, suitable for seasoned FA players. Available from Korea Campaign 2024. Kuril Islands Campaign 2018 Kuril Islands Campaign 2018 is a 35 mission campaign featuring a new Su-27 Flanker, improved SAMs and an F-35B with stability and texture improvements. Missions involve seven mission types using three aircraft, AV-8B+, F/A-18D, and F-35B. A mix of fairly easy and very challenging missions. Note: This campaign is bundled with the Taiwan Campaign 2014. Available from Kuril Islands Campaign 2018. Taiwan Campaign 2014 Taiwan Campaign 2014 is a 40 mission campaign. It features new aircraft, ships, and self-propelled AAA units, improved AT-3, F-CK-1C/D, C-2A and P-3 textures. Missions involve eight mission types using eight aircraft. Moderately difficult missions, making it suitable for the experienced JFA player. Note: This campaign is bundled with the Kuril Islands Campaign 2018. Available from Taiwan Campaign 2014. Ukraine Campaign 1994 Ukraine Campaign 1994 is a 50 mission campaign. It is a completely new campaign drawing inspiration from the original JFA Ukraine campaign. Missions involve seven different types flying four different aircraft, A-6E, F-14B and F/A-18C/D. New and improved aircraft, ships, and weapon systems including C-2A, Su-27, P-3 and F-14. Moderately difficult missions, making it suitable for the experienced JFA player. Note: This campaign is bundled with the Aegean Campaign 1997. Available from Ukraine Campaign 1994. Vietnam Campaign Set This is a compilation of all four USNRaptor Vietnam Campaigns: Rolling Thunder, Linebacker and Yankee Station 1964 & 1972, packaged together into one set. It comprises of 130 missions across the entire duration of the war. Eight different mission types flown with over a dozen aircraft. An advanced campaign suitable for expert players. Available from Vietnam Campaign. Finally... Credit and huge thanks goes to USNRaptor for all the hard work in creating this extensive set of campaigns and for allowing their use in this article. Good hunting!

Jane's Fighters Anthology (JFA) has received a couple of new widescreen patches recently. These patches allow the cockpit to be shown in a widescreen resolution. These are file replacement patches replacing the original fa.exe file. There are three patches: FA_Widescreen_zip: Created by ohyeah2389. FA_Widescreen_1920x1080.zip: Created by ohyeah2389. FA_Widescren_nocd.zip: The widescreen patch modified by kuoyichen (hawke) so the CD is no longer needed, this does not support 1920x1080. FA_1920x1080_nocd.zip: The 1920x1080 widescreen patch modified by kuoyichen (hawke) so the CD is no longer needed. FAex.zip: A general purpose resolution and HUD patch by kuoyichen (hawke). The resolution can be specified in a config file. Patch release notes The widescreen patch has been created by ohyeah2389 and was released on the 24 June 2026. The following notes have been edited from those provided by ohyeah2389. So here's FA.EXE with the following changes: 16bit scanline counter 800x600 now runs at 1024x600 (with HUD support) 1024x768 now runs at 1280x768 (without HUD support) 640x480 was not changed to a widescreen variant as it's the mode the menus use, and it would corrupt their drawing. This WILL NOT WORK if your display driver does not support 1024x600/1280x768, which my system does not. You can work around this by using a DDraw wrapper that supplies this display mode, such as cnc-ddraw. Otherwise, FA will try to set the video mode a few times, and then fail with an error "Could not set video mode X". Note: The 1920x1080 resolution should be supported by a majority of display drivers, it replaces the original 1024x768 (without HUD support). Further notes Issues remain when trying to access the Jane's reference material in-game, this has been a long-standing issue with JFA. A previous article provided a workaround by using an alternative wrapper (not compatible with this patch). A suggestion is to take a copy of an existing JFA installation folder and apply the patch and cnc-ddraw wrapper to this new installation and use it for running missions. The existing JFA installation can be used to access the reference material. Obtaining Both patches can be obtained from the Internet Archive at the Jane's Fighters Anthology widescreen patch archive. They are also available at the Combat Flight Sim Tavern, janes-fa channel. Installation Installation is simple, the steps are as follows: Extract one of zip archives to the JFA installation folder. Optional: backup the existing fa.exe file. Rename the patch executable to fa.exe. cnc-ddraw As discussed in the release notes the patch requires a display driver support 1024x600/1280x768. The DirectX wrapper cnc-ddraw can provide this support if needed. cnc-ddraw can be obtained from the cnc-ddraw GitHub repository Releases. The cnc-draw zip archive should be extracted into the JFA installation folder. Screenshots There is no example video as recording with cnc-ddraw active, resulted in a video recorded in the original 4:3 aspect ratio. However, the following screenshots should provide examples of the patch. General purpose resolution & HUD patch This is a general purpose resolution patch (FAex.zip) created by hawke. From some (edited) notes supplied by hawke: We only have two resolutions supported (1920x1080, 1280x1024), maybe a startup program with config file will be a good solution. So here is the FAex. Here is 3 files you will need, FAex is written with python (include source), there is also a standalone version (FAex.exe), so you don't need install python env, the FA.exe just use 1.02F NOCD version. change the resolution in FAex_Config.txt file, then you can enjoy all different resolution. By the way, I also put the hudpatch in, if you set hudPatch = true in FAex_Config.tx, then you will have Hud in any resolution (still a little problem, the little round still in the middle of screen). Obtaining This can be obtained from the Internet Archive at the Jane's Fighters Anthology widescreen patch archive. They are also available at the Combat Flight Sim Tavern, janes-fa channel. Installation, configuration & running The patch allows the configuring a resolution supported by display drivers. As a valid display driver should be used, it can be used without cnc-ddraw, which means it is compatible with DxWrapper as used in the previous article, Bringing it all together with Jane's Fighters - Anthology. The steps are: Download and extract FAex.zip to the JFA installation folder. Open FAex_Config.txt and set the resolution and HUD settings. An example is shown below: # Thank ohyeah2389 in Discord # By kuoyichen (hawke), https://sites.google.com/site/fashape/home # Show HUD graphic regardless of resolution hudPatch = true bgPolyFix = false # Force specific resolution # Note that in sim options you must select 1024x768 to use thisforceResolution = true resolutionWidth = 1280 resolutionHeight = 720 Run the game with FAex.exe. Playnite config When using the Playnite game library manager, the scripts should be configured as follows: Playnite scripts The FAex.exe process ends after starting JFA. This causes Playnite to think the game has been quit, causing Playnite to become the active window. After the game starts a 20 second delay gives the game time to start the intro video, this will be interrupted by Playnite, but you can switch back to the game. Without this delay, the game hangs at the first splash dialog. Scripts to close any joystick/HOTAS profiling apps should not be used. These apps should be closed manually. Example video Playing in 1280x720 resolution with a HUD Finally... Huge credit and thanks for all the hard work, goes to: ohyeah2389, for creating the widescreen patch. kuoyichen (hawke), for creating the no CD version of the patch and the general purpose resolution patch. FunkyFr3sh, for cnc-ddraw. Good hunting!

One of the Interactive Magic (or I-Magic) series of flight sims, iF-22 (also known as iF-22: The Raptor simulator) never reached the heights of classic sim. At the time of release it was considered a fun and entertaining sim, with scenery based on satellite imagery. However it was also considered very resource heavy both in mission loading times, and disk space and using sat imagery for the scenery may have been a little ambitious for 1997. It seems to have been a very diversive sim with some loving it, but for others the textures and scenery felt a little off. Wingman and enemy AI also came in for some criticism. Not quite the study sim we have today but far from casual at the time, it seems to have tread the fine line between seriousness and fun rather effectively. It received some pretty favourable reviews at the time but the player base remained divided. It went through some comprehensive changes culminating in the version 3.3 patch which which made major changes but still left some issues some fundamental issues unresolved. More enhancements would result in version 5.0, effectively the 'gold compilation' edition featuring the original game and Persian Gulf scenario expansion. In 2026 we can put the resourcing issues to rest, missions will load quickly and the disk space issues are trivial by today's standards. However the sim has been notoriously difficult to run on a modern OS, until now... Contents Strategy Version and patch history iF-22 original retail (July 1997) Version 3.0 patch iF-22 rerelease (September 1997) Version 3.1 patch (September 1997) Version 3.2 patch (7 October 1997) iF-22 Peacekeeping Mission - Persian Gulf expansion (October 1997) Version 3.3 patch (27 October 1997) Version 3.3.1 patch (December 1997) iF-22 v5.0 release (March 1997) Version 5.0.1 patch (March 1997) iF-22 v5.0 rerelease (March 2001) Narzoul's uiwindow.dll patch (June 2026) Retail media Game management Installation Earlier iF-22 versions Compatibility tools DDrawCompat Delta Patcher vJoy Joystick Gremlin HidHide ViGEm Bus Driver XOutput RetroBridge Alternative compatibility tools x360ce JoystickGremlinEx Unsupported tools Gamepad Phoenix Steam Big Picture Xidi HOTAS config HOTAS strategy Creating the vJoy virtual joystick Creating the Joystick Gremlin(Ex) profile Configuring HidHide Creating the ViGEm virtual Xbox 360 controller XOutput x360ce Scripting Applying the RetroBridge WinMM wrapper Configuration Configuring DDrawCompat Applying narzoul's uiwindow patch Compatibility settings Running First run In-game configuration Documents Example video Finally... Strategy There are two main issues to address with iF-22, the graphics and controller issues. The graphics issues affected both the flight engine and menu system, making the menus difficult if not impossible to use. The graphics issues have all but been eliminated thanks to the work or narzoul (creator of DDrawCompat), with just some minor issues remaining. The sim did not seem to support DirectInput controllers which meant in a majority of cases the sim simply wouldn't start. The controller issues have been partially resolved resulting in support for a 2 axes, 4 button, 1 hat stick to work with the sim, so no throttle or rudder. This is huge step forward in playability from a sim which just didn't work under Win10. Most of this guide will be covering the (rather involved) steps required to resolve these two issues. This guide will be using iF-22 v5.0 for the rest of this guide. Version and patch history The is a brief version and patch history which may help make sense of the odd version number scheme. iF-22 original retail (July 1997) The original retail version was developed and published by Interactive Magic in around July 1997. The original release was published on 2 x CD-ROMs, one for each of the campaign theaters, Bosnia and Ukraine. This release uses a 16-bit Windows installer incompatible with Win10, due to the Win95 version check carried out by the installer. This version was given the version number v2.7 and had 2 manuals, a basic sim and menu system usage manual, that would be included in later releases and a non-nuclear weapons delivery manual, that would not. Version 3.0 patch The v3.0 patch was a comprehensive patch featuring a number of improvements and fixes. This patch is currently unavailable. Changes included: Improved frame rates. Addition of the reduced Radar Cross Section (RCS) option. Additional HUD colours An improved 'white-out' effect. Confirmation of a destroyed ground target. Improved AIM-120 AMRAAM maneuverability. Many other fixes. iF-22 rerelease (September 1997) A rerelease of the original game occurred in September 1997, this release was pre-patched to v3.0. It was again distributed on 2 x CD-ROMs. Both manuals were available with this version. Again, this release uses a 16-bit Windows installer incompatible with Win10, due to the Win95 version check. Version 3.1 patch (September 1997) The v3.1 patch was a cumulative patch which included an earlier v3.0 patch. It was distributed as zip archives. To update saves, this patch had to be applied to an unpatched version of the game. This patch is currently unavailable but was distributed as two self extracting archives (iF22_p1a.exe and iF22_p1b.exe) for easier downloading. Changes included: Random crash bug fixed. Improved waypoint drag-and-drop. Improved mission planning grid. Version 3.2 patch (7 October 1997) The v3.2 patch was a cumulative patch which included the earlier v3.0 and v3.1 patches. It was distributed as two zip/self extracting archives (iF22_p1a.zip/exe, iF22_p1b.zip/exe) for easier downloading. These patch files used the same names as the previous v3.1 patch. To update saves, this patch had to be applied to an unpatched version of the game. Changes included: Allows users to play the Persian Gulf Theater. Displays clouds at correct heights. This patch is available from: GamePressure, Download, iF-22 Persian Gulf version 5.0, Game Update - 3.2 (incorrectly listed as being for iF-22 v5.0). Internet Archive, iF-22 v3.2 Patch. Internet Archive, Score 47 CD-ROM (1997-11). iF-22 Peacekeeping Mission - Persian Gulf expansion (October 1997) The one and only expansion was developed and published by Interactive Magic. It was distributed on a single CD-ROM. This expansion added the Persian Gulf theater and campaign. It came with it's own 30 page manual and was pre-patched with the v3.2 patch. Version 3.3 patch (27 October 1997) The v3.3 patch was a cumulative patch which included the earlier v3.x patches. It was distributed as two zip archives (iF22_33A.exe, iF22_33B.exe) for easier downloading. In addition to the previous patch changes there were comprehensive changes made to: Enemy and wingman AI. Mission planning and briefings. Other menu system changes. Other simulation fixes. A complete set of release notes from v3.0 to v3.3 is available below: This patch is available from: Internet Archive, Pelit CD-ROM 2 (1997). Version 3.3.1 patch (December 1997) This patch is applicable to the German language version only. The changes relate to keyboard functions: Because of difficulties using 'AltGr' key combinations in iF-22, radar ranges can now be changed using the '(' and ')' keys. Also, you can select Air-to-Ground weapons using the '?' key. This patch is available from: The Patches Scrolls, iF-22 Raptor, patch 3.31. iF-22 v5.0 release (March 1998) Version 5.0 of iF-22 was an improved compilation release. This compilation includes the expansion, featuring all 3 theaters, Bosnia, Ukraine and the Gulf. The texture storage had been improved resulting in a release on a single CD-ROM. Aircraft models have also been revised and improved. The installer was changed to a 32-bit installer making it compatible with Win10. In this release the non-nuclear weapons delivery manual is missing. Version 5.0.1 patch (March 1998) This patch is applicable to the German language version only. The changes relate to keyboard functions: The key combination [SHIFT] + [8] (open parenthesis) increases, and the combination [SHIFT] + [9] (close parenthesis) decreases the radar range. The combination [SHIFT] + [ß] (question mark) selects the next surface-to-air weapon. This patch is available from: The Patches Scrolls, iF-22 Raptor v5.0, patch 5.01. iF-22 v5.0 rerelease (March 2001) This rerelease is identical to the April 1998 v5.0 release, the only difference being a slightly different build version number. Distributed on a single CD-ROM, it has the same improvements as the April 1998 v5.0 release. A 32-bit installer is used and the non-nuclear weapons delivery manual remains missing. Narzoul's uiwindow.dll patch (June 2026) Narzoul (of DDrawCompat fame) has found and provided a fix for the menu background colour issues present in iF-22. Taken from the DDrawCompat GitHub issue thread: Meanwhile, I also found the issue with the menu colors. The game is using SetClassLong with GCL_HBRBACKGROUND to change the background brush of some built-in window classes (e.g. buttons). It passes a custom brush created with CreateSolidBrush to this function. Sometimes it sets this custom brush, sometimes it restores the original NULL brush. But at some point it deletes the brush (via DeleteObject) while it's still assigned to some of the classes. Worse, it keeps using the deleted brush and trying to assign it again and again, which clearly fails. I don't see a clear solution to this from a generic wrapper and I've no idea how this ever worked correctly. The only "workaround" I found is hex editing uiwindow.dll to bypass the problematic call to DeleteObject with the following hex replacement: 8B 86 68 32 00 00 85 C0 74 -> 31 C0 89 86 68 32 00 00 EB There should be only one instance to replace. Now this isn't the greatest solution, as this might cause a GDI handle leak instead. But after clicking around in the menus for a while I didn't notice any clear issues, so perhaps it's viable as a long term solution too, unless someone wants to find a better fix. Since this has nothing to do with DDrawCompat I'm unlikely to mess with this further. For easy of use this has been converted into an xdelta patch, available below: Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CDs. Game management It is recommended to use my game management strategy or similar strategy you may have developed. The recommended game management folders for iF-22 are: cd - for any cd images. conf - to store HOTAS configuration files. docs - for documents. install - for downloaded compatibility tool installation zip/exe files. patch - to store any patches. tools - as a compatibility tool installation folder. The iF-22 management folders would be found in the following game folder (as an example): D:\Games\Win\iF-22 Setup Installation Installation is a simple and straightforward process due to the iF-22 v5.0 32-bit installer being supported in Win10. It is recommended to install the game alongside the game management setup folder, e.g. # Setup folder D:\Games\Win\iF-22 Setup # Game installation folder D:\Games\Win\iF-22 The setup.exe should be run from the CD and the installation steps are shown below: Earlier iF-22 versions Earlier versions of iF-22 used a 16-bit installer, unsupported by Win10 and normally requiring the use of the OTVDM compatibility tool to run. However the 16-bit installer also checks the Windows version and will not allow the installation to proceed if it does not find Win95. It is suggested to create a Win95 Virtual Machine (VM) using a VHD hard disk image with PCem (or reuse an existing Win95 VM if you have one). Missing device drivers, missing sound or default graphics are all fine, as long as iF-22 can be installed. Once installed the VM can be shutdown and the VHD hard disk image mounted in Win10. The iF-22 installation folder can then be copied into Win10. A video tutorial to building a PCem virtual machine for Win98 is available from PhilsComputerLab, PCem Windows 98 Setup (Pentium II +Voodoo 3, all files provided). The process for installing Win95 will be very similar. Compatibility tools This section covers the compatibility tools used to get iF-22 working and where to find them. It does not cover how to configure them, that comes later. It also covers some alternatives to the suggested toolset and some tools which were tried but didn't work (in case you wish to try some other tools). It is recommended to download installation packages to the game management install folder for safekeeping and if things go badly the existing tools can be uninstalled and reinstalled using these installation packages, e.g. # XOutput installation package D:\Games\Win\iF-22 Setup\install\XOutput v3.3.2.zip It is recommended to use the game management tools folder as a compatibility tool installation folder, if the tool can be installed to a selectable folder, e.g. # XOutput D:\Games\Win\iF-22 Setup\tools\XOutput.exe If any of the following compatibility tools are already installed, they can continue to be used from their existing installation folder: Delta Patcher HidHide Joystick Gremlin ViGEm Bus Driver vJoy XOutput DDrawCompat DDrawCompat created by narzoul is the graphics wrapper used to provide compatibility with iF-22. The latest version is v0.7.1, however the standard release isn't used. Instead a patched wrapper has been created (based on v0.7.1) for the following issues in iF-22, identified and fixed by narzoul: There is one more problem that hasn't been mentioned yet, because I think it only affects Windows 10 and 11. There is a new UserAdapterWindowClass (or SystemUserAdapterWindowClass in Windows 11) window class that tends to show up in the message loop for messages retrieved by PeekMessage/GetMessage. This causes an issue with this game where it stops rendering in the 3D scene after the first keypress, and only continues briefly after each further key press or whenever the mouse is moved. The problem is technically in the message loop of the game, because it does some crazy things: if PeekMessage returns FALSE, it uses lpMsg->hWnd anyway (even though PeekMessage doesn't fill it in this case, so it contains whatever garbage was there before), queries GWL_USERDATA with GetWindowLong, and if it's not 0, executes some callback function stored there. This callback function is presumably responsible for exiting the message loop and continuing the rendering. When the garbage value has the game's own window handle, then this works correctly, but when the window belongs to (System) UserAdapterWindowClass, which has a 0 value in GWL_USERDATA, the game just loops back to PeekMessage again and returns the same "garbage" value as long as no new messages enter the loop, causing an "infinite" rendering pause loop. I added a patch to DDrawCompat that tries to hides these special windows from PeekMessage/GetMessage, which seems to fix this issue. Additionally, I also found a fix for the Windows 8 FullscreenMode=borderless issue. Here is a combined patch for both of these issues: The patch (ddraw.zip) is available in this DDrawCompat GitHub thread. Delta Patcher Delta Patcher, developed by marco-calautti is a utility to create and apply xdelta patches compatible with the xdelta tool developed by Joshua McDonald. The recommended version is the latest 64-bit version, v3.1.6 (at time of writing), available from the Delta Patcher GitHub repository in Releases. vJoy vJoy is a virtual joystick driver, it is used to replace physical joystick/HOTAS controllers with a virtual controller. It is supplied as a suite of utilities including a configuration utility. The recommended version is the latest jshafer817 release, vJoy v2.1.9.1 as this is fully compatible with Joystick Gremlin. It is available from the jshafer817 / vJoy GitHub repository in Releases. Joystick Gremlin Joystick Gremlin is the joystick/HOTAS profiling utility mapping physical controller inputs to a virtual joystick, provided by vJoy. The recommended version is the latest one (at time of writing), Joystick Gremlin release 15. It is available from Joystick Gremlin Download. This site also provides a quickstart guide to using Joystick Gremlin. HidHide HidHide is a device firewall created by nefarius, hiding devices from any app not explicitly allowed through the firewall. It is often used in conjunction with vJoy and Joystick Gremlin to ensure a game can only access the vJoy virtual controller, whilst the physical controllers remain hidden from it. Joystick Gremlin would be allowed through the HidHide firewall. When the firewall is active, only the vJoy virtual controller would be seen by a game. As Joystick Gremlin can still see the physical devices through the firewall it can still translate physical inputs into vJoy virtual controller inputs. The recommended HidHide version is the latest one, HidHide Drivers v1.5.230, available from GitHub HidHide repository, Releases. ViGEm Bus Driver The ViGEm Bus Driver is a 'virtual Xbox 360 controller' driver (supporting the XInput library) created by nefarius. It can be thought of as vJoy for virtual Xbox 360 controllers. Unlike vJoy it does not come with it's own configuration utility The ViGEm Bus Driver is no longer under active development. The recommended ViGEm Bus Driver version is the latest one, ViGEmBus Setup 1.22.0 "It's dead, Jim" Release available from GitHub ViGEm Bus Driver repository, Releases. XOutput XOutput, created by Ármin Csutorás, is a configuration utility for a virtual Xbox 360 controller provided by the ViGEm Bus Driver. XOutput is required as ViGEm does not provide a configuration utility. It takes a physical or virtual DirectInput controller and maps it to a virtual XInput controller. It can be thought of as a 'vJoy config tool/Joystick Gremlin' for virtual Xbox 360 XInput controllers. The recommended XOutput version is the latest one, XOutput 3.32, available from GitHub XOutput repository, Releases. RetroBridge RetroBridge created by VOGONS forum member rkk, is multi wrapper suite for PowerVR, Glide, DDraw and DSound for all versions of Ultim@te Race, allowing the game to be played on Win10/11. It's use in getting iF-22 to run with joystick support is a completely unintended use. RetroBridge provides a winmm.dll wrapper that can map an XInput controller into a virtual 2 axes, 4 button, 1 POV hat joystick that is compatible with iF-22. This is key in getting iF-22 joystick support working. RetroBridge was also tolerant of the DDrawCompat wrapper used in this tool chain. RetroBridge (RetroBridge - 0.1.139 - Preview.zip) is available from the VOGONS forum thread, RetroBridge - A multi wrapper for PowerVR (SGL) + Glide + DDRAW + DSound for all versions of Ultim@te Race (1t/3t/Pro). Alternative compatibility tools The following tools may provide sufficient advantages over the above tool chain that some may wish to try. x360ce x360ce is a configuration utility for a virtual Xbox 360 controller provided by the ViGEm Bus Driver. It can be used in place of XOutput. One of the advantages of x360ce is that it can be started with a default profile. This means it can be used in batch or PowerShell scripts when starting iF-22. XOutput requires the emulated controller to be manually started making it less suitable. However the configuration of x360ce is more complex than XOutput. The recommended x360ce version is the latest one, X360CE 4.17.15.0, available from GitHub x360ce repository, Releases. JoystickGremlinEx JoystickGremlinEx (or GremlinEx), created by muchimi, is a fork of the Joystick Gremlin project, supporting functions that would have been difficult to integrate with the Joystick Gremlins plugin facility. It is built as a 64-bit app using a later version of Python/QT. Advantages over Joystick Gremlin: GremlinEx will map physical controllers directly to a ViGEm virtual controller. This removes Joystick Gremlin, vJoy and XOutput/x360ce from the tool chain, replaced by GremlinEx. Disadvantages over Joystick Gremlin: GremlinEx is still a work in progress, later releases should be considered developmental releases and may not be stable. GremlinEx uses the older Joystick Gremlin release 13 configuration model. Those accustomed to the release 14/15 model may find it tricky to use. Encountering errors/exceptions during configuration should be expected. Those familiar with the JG release 13 model may find the smaller tool chain easier to deal with, despite any issues. The latest GremlinEx version, M77 seems fairly stable at present. It is available from JoystickGremlinEx GitHub repository, Releases. Unsupported tools This section is for those that wish to try and improve on the tool chain. The following tools were tried but failed to provide adequate joystick support for iF-22. NOTE: This is not a criticism of the tools below, just that they were unable to help in getting iF-22 to support a joystick. Gamepad Phoenix Gamepad Phoenix is a tool for Windows to play any game (old or new) with any gamepad (old or new). Despite supporting the WinMM API, Gamepad Phoenix was unable to supply a joystick that could be used by iF-22. Steam Big Picture Steam Big Picture has gamepad support for games added to Steam, including non-Steam games. Despite adding iF-22 and configuring a controller, iF-22 could not find a joystick to use. Xidi Xidi created by Samuel Grossman provides both DirectInput and WinMM interfaces for games to use and communicates with XInput-based game controllers natively using XInput, translating between the two interfaces as needed. Despite supporting the WinMM API, Xidi was unable to add a suitable controller that could be used with iF-22. However, Xidi in combination with Hookshot (also created by Samuel) was pivotal in discovering that WinMM API joystick functions were used by iF-22. HOTAS config The following section differs from the usual HOTAS config due to the complexities involved in configuring a joystick/HOTAS for use with iF-22. HOTAS strategy Before considering detailed steps it is worth considering the overall approach. This can be summarized as the following: Joystick Gremlin provides a profile mapping from physical controllers to a vJoy virtual controller. HidHide is used to hide physical controllers from other tools/iF-22. XOutput or x360ce provides a profile mapping from a vJoy virtual controller to an Xbox 360 XInput virtual controller (provided by the ViGEm driver). RetroBridge provides a mapping from an XInput virtual controller to the RetroBridge emulated joystick supported by iF-22. When using Joystick GremlinEx the steps become: Joystick GremlinEx provides a profile mapping from physical controllers to an XInput virtual controller (provided by ViGEm). HidHide is used to hide physical controllers from other tools/iF-22. RetroBridge provides a mapping from an XInput virtual controller to the RetroBridge emulated joystick supported by iF-22. Using Joystick Gremlin(Ex) allows unused physical controller buttons to be mapped to keyboard commands used in IF-22. XOutput is prone to crashing or freezing when more than one controller is mapped to a virtual XInput controller. It works far better with a single controller (the vJoy virtual joystick in this scenario) mapped to a virtual XInput controller. x360ce will freeze and become non-responsive once iF-22 is quit. It can be closed from the taskbar or PowerShell script. This occurs after the game is quit, so it is considered a minor issue. Although the RetroBridge emulated joystick only supports 2 axes, the HOTAS config will use 4 axes for any future updates that add support for throttle and rudder axes. Creating the vJoy virtual joystick If the vJoy virtual joystick driver is not installed then: Download the driver install package (vJoySetup.exe) and place in the game management install folder for safe-keeping. Run the installer and use the default installation folder. If the vJoy virtual joystick driver is installed it can continue to be used. The configuration tool should be run as an Administrator. The following vJoy config was used, as shown in the screen shot. This is equivalent to the following vJoy commands: vJoyConfig.exe Enable on vJoyConfig.exe 1 -f -a X Y Z Rz -b 4 -p 1 To disable vJoy: vJoyConfig.exe -r vJoyConfig.exe Enable off Creating the Joystick Gremlin(Ex) profile If Joystick Gremlin is not installed then: Download the driver install package (Joystick.Gremlin.R15.zip) and place in the game management install folder for safe-keeping, or similar for Joystick GremlinEx). Unzip to a Joystick Gremlin folder in the game management tools folder, or if you wish to use it for further games in the future, to a more appropriate higher level folder, e.g. D:\Games\Win\JoystickGremlin D:\Games\JoystickGremlin If Joystick Gremlin(Ex) is already installed it can continue to be used. As the game is running as Administrator, Joystick Gremlin must also run as Administrator for any mapped keypresses to be registered in the game. Creating the profile is not covered as it will be specific to the physical joystick/HOTAS hardware present. It is recommended to store the iF-22 profile in the game management conf folder. To run from the command line or script: joystick_gremlin.exe --start-minimized --enable --profile "D:\Games\Win\iF-22 Setup\conf\iF-22.xml" Configuring HidHide If HidHide is not installed then: Download the HidHide install package (HidHide_1.5.230_x64.exe) and place in the game management install folder for safe-keeping. Run the installer and use the default installation folder. If HidHide is already installed it can continue to be used. The following screenshots show an example HidHide configuration (the config will be specific to the physical joystick/HOTAS hardware present): Only Joystick Gremlin and/or Joystick GremlinEx need to see the hidden physical devices through the HidHide firewall. The HidHide entries are automatically added and should be left alone. Only physical devices need to be hidden, the vJoy virtual joystick should remain visible. To enable HidHide from the command line or script: HidHideCLI.exe --cloak-on To disable: HidHideCLI.exe --cloak-off Creating the ViGEm virtual Xbox 360 controller If ViGEm, XOutput or x360ce is not installed then: Download any missing tools: ViGEm install package (ViGEmBus_1.22.0_x64_x86_arm64.exe), XOutput (XOutput.zip) or x360ce (x360ce.zip) install packages and place in the game management install folder for safe-keeping. ViGEm: Run the installer and use the default installation folder. XOutput/x360ce: Unzip to an XOutput/x360ce folder in the game management tools folder, or if you wish to use it for further games in the future, move it to a more appropriate higher level folder. If ViGEm or XOutput is already installed it can continue to be used. x360ce can continue to be used if it does not have a default configuration in use. Before configuring XOutput/x360ce ensure Joystick Gremlin is running (as Administrator) and the iF-22 profile is enabled. XOutput The following screenshots show the XOutput configuration mapping the vJoy virtual joystick (above) to a virtual XInput controller: Once the XInput controller is started, XOutput should be minimised to the taskbar and left running until the game is quit. x360ce x360ce is a little more complex than XOutput, however the following screenshots show the XOutput configuration mapping the vJoy virtual joystick (above) to a virtual XInput controller: It is recommended to run x360ce as Administrator. A 'default' profile is a profile used when the x360ce utility is running, this is shown in the Game dropdown menu at the top of each page. The Issues tab should be checked to ensure there is nothing wrong with the installation, as shown, it should be empty. In the Settings tab ensure the vJoy virtual joystick is mapped to controller 1. In the x360ce config the y-axis is not inverted (compare this to XOutput where the y-axis is inverted). The 'Enable 1 mapped device' checkbox starts and stops controller emulation. Once the XInput controller is started, x360ce should be minimised to the taskbar and left running until the game is quit. Scripting The following PowerShell script will start and configure the compatibility tools for an iF-22 joystick, it can be used as a Playnite script: # Enable vJoy Start-Process -Wait "C:\Program Files\vJoy\x64\vJoyConfig.exe" -ArgumentList "Enable on" -Verb RunAs Start-Process -Wait "C:\Program Files\vJoy\x64\vJoyConfig.exe" -ArgumentList "1 -f -a X Y Z Rz -b 4 -p 1" -Verb RunAs # Enable HidHide Start-Process -Wait -FilePath "C:\Program Files\Nefarius Software Solutions\HidHide\x64\HidHideCLI.exe" -ArgumentList '--cloak-on' # Enable JG Start-Process -FilePath "D:\Games\Joystick.Gremlin.R15\joystick_gremlin.exe" -ArgumentList '--start-minimized --enable --profile "E:\IF-22 Setup\conf\if-22v5.xml"' Start-Sleep -Seconds 5 # Enable x360ce (minimised to taskbar) Start-Process -FilePath "D:\Games\x360ce\x360ce.exe" -WindowStyle Minimized Start-Sleep -Seconds 10 The following PowerShell script will stop and reset the compatibility tools used to create the joystick, it can be used as a Playnite script: # Disable x360ce (Get-WmiObject -Class Win32_Process -Filter "name = 'x360ce.exe'").Terminate() # Disable JG (Get-WmiObject -Class Win32_Process -Filter "name = 'joystick_gremlin.exe'").Terminate() Start-Sleep -Seconds 10 # Disable HidHide Start-Process -Wait -FilePath "C:\Program Files\Nefarius Software Solutions\HidHide\x64\HidHideCLI.exe" -ArgumentList '--cloak-off' # Disable vJoy Start-Process -Wait "C:\Program Files\vJoy\x64\vJoyConfig.exe" -ArgumentList "-r" -Verb RunAs Start-Process -Wait "C:\Program Files\vJoy\x64\vJoyConfig.exe" -ArgumentList "Enable off" -Verb RunAs Applying the RetroBridge WinMM wrapper Download the RetroBridge install package (RetroBridge - 0.1.139 - Preview.zip) and place in the game management install folder for safe-keeping. Unzip only the following files into the iF-22 installation folder: retrobridge.config.yml retrobridge_core.dll winmm.dll Configuration The following section covers the remaining compatibility tools and settings required to get iF-22 running. Configuring DDrawCompat The DDrawCompat patch for iF-22 (ddraw.zip) should be downloaded and placed in the game management patch folder for safe-keeping. The ddraw.dll file in the zip archive should be extracted to the iF-22 installation folder. The configuration file required by DDrawCompat is available below. It should downloaded to the game management conf folder for safe-keeping. The DDrawCompat.ini file in the zip archive should be extracted to the iF-22 installation folder. The config is as follows: # DDrawCompat config file for iF-22 AlternatePixelCenter = on Antialiasing = msaa4x CapsPatches = DDCAPS.dwCaps2|=0x800 FullscreenMode = exclusive ViewportEdgeFix = scale(50) Applying narzoul's uiwindow patch The next step is to patch the uiwindow.dll file with Delta Patcher to fix the menu graphics. The Delta Patcher (windows_bin_x86_64.zip) should be downloaded and placed in the game management install folder for safe-keeping. The contents of the Delta Patcher zip archive should be extracted to a delta patcher folder in the game management tools folder. The uiwindow-xdelta.zip archive should be downloaded and placed in the game management patch folder for safe-keeping. The contents of the archive (uiwindow.xdelta) should also be extracted to the patch folder. Run the Delta Patcher tool, select the original uiwindow.dll file in the iF-22 installation folder. Select the uiwindow.xdelta patch in the patch folder. Click Apply patch and the success dialog box should be displayed as shown in the gallery below: Optionally copy the patched uiwindow.dll file from the iF-22 installation folder to the patch folder for safe-keeping. Compatibility settings The only compatibility settings required are the Run this program as an Administrator setting on the game executable (if22.exe), as shown in the screenshot. Running The following covers the steps to setup controllers and run the game. If this is the first time running the game, consult First run for some specific actions to be performed. Open the vJoy config tool and enable vJoy. Configure the device to have X, Y, Z and Rz axes, 4 buttons and 1 POV hat. Open HidHide and hide devices. Open Joystick Gremlin as an Administrator and enable the iF-22 profile. Start the ViGEm XInput virtual controller: XOutput: Open XOutput and start the controller used by iF-22. x360ce: Open x360ce as Administrator, if the profile is not enabled then enable it. Run iF-22 (if22.exe). If everything has worked the title page should be displayed, clicking on the cockpit should take you to the main menu, as shown below: After the game has closed: Stop the ViGEm XInput virtual controller: XOutput: Stop the controller used by iF-22 and close XOutput. x360ce: Disable the profile and close x360ce. Disable the iF-22 profile and close Joystick Gremlin. Disable device hiding and close HidHide. Disable vJoy and close the config tool. First run When first running the game, a crash/freeze will occur unless the following actions are taken: Start the game, and continuously click the mouse to skip intro videos. The game will automatically open the joystick calibration screen, click either Accept or Cancel. The game will automatically start an instant action mission. Use Ctrl + Q to quit the mission. Continuously click the mouse to skip a video. When back at the main menu, select System Setup and check the Disable animations checkbox. In-game configuration From the main menu, System Setup will allow you to configure the game. The option to Calibrate the joystick is on the System Setup menu, as shown below. If not already done so the Disable animations checkbox should be checked. All graphics settings can be maximised. If all components were installed, all of the theater files will be shown on the Theater Setup page. If the iF-22 CD/image is mounted in Win10, you will have the option of copying any missing optional theater files from the CD onto the hard disk, as shown below. Documents As with any sim the documentation is very important to properly use the sim. The available documents are shown below: iF-22 Manual (pdf download) Steam, All Games, Simulation Games, iF-22, View the manual. NONNUCLEAR WEAPON DELIVERY MANUAL Styled to look like an official USAF document, but published by Interactive Magic, containing iF-22 sim keyboard commands. This manual provides details on weapons management and use within the sim. It is available as a pdf document on the CD of early iF-22 retail releases. iF-22 Reference Card Lists the 2 and 4 button joystick layout, keyboard layout and command reference. Example video Testing iF-22 v5.0 with a joystick Finally... Credit and thanks goes to: GamePressure, Internet Archive and The Patches Scrolls for hosting iF-22 patches. Narzoul for the DDrawCompat and uiwindow patches and the DDrawCompat config. PhilsComputerLab for his PCem tutorial video. marco-calautti for Delta Patcher. jshafer817 for the vJoy release. The work done by the Joystick Gremlin team. nefarius for the ViGEm Bus Driver. Ármin Csutorás for XOutput. rkk for RetroBridge. The work done by the x360ce team. muchimi for Joystick GremlinEx. Bernhard Schelling for Gamepad Phoenix. Steam for Steam Big Picture and hosting documentation. Samuel Grossman for Xidi. Good hunting!

A guide to running Rowan's Battle of Britain under Windows 10. This is a World War II flight sim set in the British theater during the Battle of Britain timeframe. Fly as a pilot or commander for the British RAF of German Luftwaffe with a dynamic campaign. There is a choice of the Hawker Hurricane and Supermarine Spitfire for the RAF or Junkers Ju-87 "Stuka", Messerschmitt Bf-109 or Messerschmitt Bf-110 for the Luftwaffe. Generally considered one of the better WW2 flight sims on release, it had a dedicated fan following. Once Rowan stopped developing flight sims the source code for this (and MiG Alley) was released and development continued by the fan led Battle of Britain/MiG Alley Development Group (BDG). The rest of the guide will use BoB for Rowan's Battle of Britain. Contents Strategy Patch and version history Initial retail release (November 2000) CD-ROM copy protection fix (January 2001) Battle of Britain Mini-Patch (April 2001) Update patch (July 2001) BDG patch (November 2001) Xplosiv budget release (October 2002) Digital release (October 2008) Retail media Game management HOTAS config Installation Patching Compatibility tools DDrawCompat Compatibility settings Creative ALchemy In-game configuration BDG patch configuration Head tracking Running recommendations Mods and enhancements Graphics mod for original Rowan's BoB Cloud replacement fix D-type hangar fix Rowan's BoB Update 1 City texture mod Rowan's BoB 2024 mod Documents Example video Finally... Strategy This is a very tricky game to get running well in Windows 10. It may run in Windows 11 but this is untested. This game is very crash/freeze prone with most crashes/freezes occurring when exiting the 3D flight engine to return to menus/campaign. There seem to be specific settings and actions which seem to greatly increase the chance of a crash, so this guide includes 'rules' for running the sim, with recommended actions to reduce the likelihood of a crash and actions to absolutely avoid. There are also settings which may slightly increase the crash/freeze risk but you may wish to try with your own setup, including 3D sound, DirectSound wrappers (e,g, Creative ALchemy), CPU affinity and Compatibility settings. It is unlikely that a 'one size fits all' optimal solution could be found, applicable for every machine but this guide should provide a good starting point for your own setup. This first part covers running a fairly vanilla version and the second part covers the optional graphics mods available. Patch and version history The following is a brief patch and version history for BoB. The graphics mods are covered in Mods and enhancements. Initial retail release (November 2000) The initial retail release occurred in November 2000, developed by Rowan and published by Empire Interactive. The game required a Pentium II machine, Windows 95 and DirectX 7. This is version 1.00 of the game. This was distributed on a single CD-ROM. Like MiG Alley, BoB was released with native controller support. CD-ROM copy protection fix (January 2001) An official patch, released in January 2001. This patch was for systems having problem with the game's copy protection not detecting their CD-ROM drives properly. This corrects the copy protection, it is not a 'no-cd' patch. It is not a recommended patch having been superseded by later patches. It is available from: CNET Download, Windows, Games, Simulation, Rowan's Battle of Britain CD-Protection Fix UK patch. Battle of Britain Mini-Patch (April 2001) An official patch, released in April 2001. Taken from the release notes: This patch fixes the following problems: 1. Sky banding in 16 bit graphics modes has been fixed. 2. "Stuttering" seen on certain high-end PC configurations has been reduced. It is not a recommended patch having been superseded by later patches. Update patch (July 2001) An official patch, released in July 2001. Taken from the release notes: Previous stutter fixes - use 10,13,20, or 40 as minimum fametime in ms. If that does not remove your stutter then try reducing the 3d detail level. Improved range of supported 3D cards. Fixed campaign bugs to do with RAF squadron selection. Fixed missing damage report target names (English only). This patch preceded any BDG patch and is not a recommended patch, having been superseded. It is available from: The Patches Scrolls, Rowan's Battle of Britain, Patches. BDG patch (November 2001) The Battle of Britain Development Group (later the Battle of Britain/Mig Alley Development Group) (BDG) patch development began with the v0.60 patch released in November 2001. Development would continue until November 2004 with the v0.99 patch. Not so much a patch rather a fan led development effort, the extensive comprehensive changes are too numerous to list here, and resulted in an entire manual (BDG v0.99 Patch Manual) describing the patch changes, installed alongside the patch. This is the only recommended patch which incorporates or supersedes earlier patches. It is available from: Dropbox, bob_v099. Xplosiv budget release (October 2002) This budget release occurred in October 2002 and was published by Empire Interactive under the Xplosiv budget label. This was distributed on a single CD-ROM. This is identical to the initial retail release with the game remaining at v1.00. The CD also contained the Battle of Britain Mini-Patch and Update patch. Documentation is included with the BoB Manual and Key Guide. Digital release (October 2008) The game was released on the GamersGate platform in October 2008. This is the only known digital release at present. It's not known what this release includes. Retail media Due to the age or the media and the drives required to read it, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives. The CD-ROMs can be ripped to a data only .iso image format as there is no CD audio on the CDs. Game management It is recommended to use my game management strategy or similar strategy you may have developed. The recommended game management folders for BoB are: cd - for any cd images. conf - to store HOTAS configuration files. docs - for documents. patch - to store any patches. The BoB management folders can be found in the following game folder (as an example): D:\Games\Win\Rowans Battle of Britain Setup HOTAS config BoB supports 5 axes, X & Y stick axes, single throttle axis (for single engined fighters), split throttle axes (for the twin engined bomber) and a rudder axis. Fortunately BoB has native controller support so multiple controllers from multiple vendors are supported. However, this does mean some of the advanced functionality provided by profiling software will not be available if only native controller support is relied upon. First the bad news, the HidHide, vJoy and Joystick Gremlin suite has problems with BoB. Testing has revealed that, for some unexplained reason, changing the throttle axis/axes also affects the ailerons causing unwanted dramatic manoeuvres with the Thrustmaster Warthog. Therefore this controller software suite isn't recommended for BoB when using this controller. Alternative HOTAS controllers may function better, but testing is required. This issue does not affect the TM TARGET profiling software and software from other vendors may also be unaffected. For those with a multiple vendor setup, a combination of native controller support for axes plus additional software such as JoyToKey, or the BDG Keyboard Manager (included in the BDG patch) for button assignment may be sufficient. Native controller support means axes can be configured as required, the below is a suggested axes setup which is known to work. 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 (single) DX_Z_AXIS Throttle (split) DX_ZROT_AXIS Rudder DX_XROT_AXIS Note: Those with a DX_SLIDER_AXIS or DX_THROTTLE_AXIS may wish to use these axes instead, depending on the controller. Note: With my Thrustmaster setup there is better controller response using a single virtual controller rather than using each controller natively. Controller response seems to be linked to the number of controller used in the game, so the fewer the better. Note: One (for single engined fighters) or two (for the twin engined bomber) axes can be assigned to prop pitch if they are available. Installation BoB uses a 32-bit installer (setup.exe) compatible with Win10. Setup is straightforward and the setup steps are shown below: Patching The only patch required is the BDG v0.99 patch. This is a file replacement patch distributed as an executable (bob_v099.exe). The patching steps are shown below: Compatibility tools The following compatibility tools and settings are used to run BoB. DDrawCompat DDrawCompat is used at a DirectX wrapper, created and maintained by narzoul. The recommended version is the latest one, version v0.7.1 (at time of writing). DDrawCompat is available from the DDrawCompat GitHub repository, in Releases. The following DDrawCompat configuration (DDrawCompat.ini) is used: # DDrawCompat config file for Rowan's Battle of Britain ConfigHotkey = shift+ctrl+f11 StatsHotKey = shift+ctrl+f12 CpuAffinity = 1 CpuAffinityRotation = on The config and stats hotkeys are changed as the default hotkeys are also used by BoB. Only one of the CPU's is made available for the game as this seems to reduce crashes/freezes. The spread the CPU load/heat, CPU affinity rotation is enabled. Note: Ensure that Antialiasing is disabled as this causes very bad landscape 'pop-in' to occur and dramatically increases the risk of crashes. Multiple CPU's may causes crashes/freezes when the Remove cockpit view (F8) is active. If not used, then using multiple CPU's may be possible, with the following: CpuAffinity = all A copy of this config is included below: To install the ddraw.dll and DDrawCompat.ini files need to be copied into BoB installation folder. bob.exe compatibility properties Compatibility settings The following Windows compatibility settings were applied to the game executable (bob.exe). The compatibility mode is set to Windows XP (Service Pack 2) which allows intro movies to play full screen. Other settings seem to reduce the risk of crashes/freezes but you may wish to experiment with your own system. The following screenshot, shows the Compatibility tab of bob.exe Properties. Creative ALchemy BoB has support for EAX 2.0 which is no longer support in Win10 but can be enabled with the Creative ALchemy wrapper (for Creative sound cards) or Creative ALchemy Universal (for any sound card). DSOAL would be another option, if it didn't seem to increase the risk of a crash/freeze. So for now, DSOAL isn't recommended. If crashes/freezes occur you may wish to disable 3D sound and revert to Stereo. In-game configuration The following shows the in-game configuration menus. The following settings are considered mandatory to prevent crashes/freezes: Do not use anti-aliasing in the DDrawCompat wrapper. Do not use a resolution higher than 1280 x 1024 (5:4 aspect ratio). The aspect ratio is less important so 1280 x 960 (4:3), 1280 x 800 (16:10), 1280 x 720 (16:9) or lower should be ok. Either 16 or 32-bit colour depth should be fine. Always turn Ground Collisions: Off from the options. This prevents the 'spin of death' a known cause of crashes/freezes. Set Town and forest raises to Off when using BDG patch textures (BDG textures are enabled by default). When making config changes it is recommended to quit immediately afterwards as this ensures changes are written to the config file. BDG patch configuration Some of the BDG patch options are available through the in-game options above. Additional options can be found in the BDG patch configuration file (bdg.txt), located in the BoB installation folder. It is recommended to consult the BDG Patch 0.99 Manual in the Docs folder when changing BDG patch options. The following options differ from the default options initially set in this file: # (floating point) numbers : VIEW_DIST_FACTOR = 0.530000 INFOLINE_COLOUR = ffffffff # On/Off switches: ENEMY_POSITION_INDICATOR=ON DRAW_PADLOCK_CENTER_BOX=OFF GET_KEY_MAPS_FROM_FILE=ON HEAD_BOBBING=OFF SHOW_INFOLINE_BACKGROUND=ON BOB_DISABLE_STALL_HORN=ON REINIT_JOYSTICK_OFTEN=OFF SHORTENED_LABELS=ON HIDE_AMMO_COUNTER=OFF BOB_SMOOTHER_DEADZONE=OFF START_FROM_PEN=OFF HIDE_POWER_INFO=OFF # AutoGen stuff (experimental): ENABLE_AUTO_GEN=ON TEMP_AG_SN[14,0]=59 TEMP_AG_SN[15,2]=62 TEMP_AG_SN[15,3]=62 The INFOLINE_COLOUR and SHOW_INFOLINE_BACKGROUND are personal preferences to make info line text easier to read at higher resolutions. Head tracking Head tracking is supported through TrackIR. To enable head tracking enable the TrackIR setting in the BDG patch game options config menu (in-game), or enable it within the BDG patch config file (bdg.txt) with: # On/Off switches: TRACKIR=ON The AITrack and OpenTrack software is also compatible with BoB. However, enabling TrackIR may significantly increase the risk of a crash/freeze. Running recommendations The following recommendations are suggested to reduce the risk of freezes/crashes. They should not be considered definitive and may well depend on the machine/OS combination. These settings seem to work well for my machine, but feel free to experiment and let me know if you discover other settings which seem to help. Do not use anti-aliasing in the DDrawCompat wrapper. Do not use a resolution higher than 1280 x 1024 (5:4 aspect ratio). The aspect ratio is less important so 1280 x 960 (4:3), 1280 x 800 (16:10), 1280 x 720 (16:9) or lower should be ok. Either 16 or 32-bit colour depth should be fine. Always turn Ground Collisions: Off from the options. This prevents the 'spin of death' a known cause of crashes/freezes. Always quit a mission (Alt + X) from within the cockpit (F7). Do not try and quit from an external view. Gun camera footage can be recorded and played, with the following recommendations: Use the gun camera toggle (C) to enable/disable the gun camera. Disable before quitting. Wait 10-20 seconds after firing the guns and disabling the gun camera, before quitting the mission (from within the cockpit). After viewing the footage (from an internal or external view) return to the cockpit before quitting the playback (Alt + X) or using the eject button on the playback controls. Mods and enhancements Following the BDG patch a number of graphics mods were released to increase the fidelity of textures. These mods and fixes were taken from the The A2A Simulations Community, BOB2 General Discussion forum, GRAPHIC MOD FOR ORIGINAL ROWAN BOB post. All mods and fixes were created and released by rogeroger. The order of installation is important and each of the mods are described below. The order of installations is: Graphics mod for original Rowan's BoB. Cloud replacement fix. D-type hangar fix. Rowan's BoB Update 1. City texture mod. Rowan's BoB 2024 mod. Graphics mod for original Rowan's BoB The Graphics mod for original Rowan's BoB was posted in the forum on 14th May 2019. The Graphics mod for original Rowan's BoB is available from: MediaFire, RR ROWANBOB GRAPHICS MOD. Before installation it's recommended to backup the BDG patch config file (bdg.txt) and the Keyboard config (keys.xml in the KEYBOARD folder), if it has been edited, as this mod supplies alternative config files. In addition to the graphics mod it also includes BDG patch v0.98 and manual, BDG patch v0.99 and manual, alternative water textures and the creator's JoyToKey settings. To install: Extract the contents of the 7zip archive (RR ROWANBOB GRAPHICS MOD.7z). Copy the contents of the bob main folder into your BoB installation folder, replacing files as required. Optional: Extract the contents of the alternative water texture 7zip archive (alt water texture.7z) and copy the contents into the Landmap2 folder (in the BoB installation folder). Copy your backup BDG patch config file (bdg.txt) back into the BoB installation folder, replacing the graphics mod config file. Apply the following setting to the BDG patch config file (bdg.txt): # (floating point) numbers : ... VIEW_DIST_FACTOR = 0.530000 ... Delete the Keyboard config (keys.xml in the KEYBOARD folder) and replace with the backup. You can also delete the keys.xml file without replacing it, as a new default version will be created when the game is started. Cloud replacement fix This cloud replacement fix replaces one of cloud shapes with a hard outline with an alternative version. It was posted in the forum on 15th May 2019. This fix is available from: MediaFire, Cloud replacement fix Rbob. To install: Extract the contents of the 7zip archive (Cloud replacement fix Rbob.7z). Copy the .dds files into the Maskmap16 folder (in the BoB installation folder), replacing any existing files. D-type hangar fix This D-type hangar fix replaces the D-type hanger texture with a higher quality one. It was posted in the forum on 15th May 2019. This fix is available from: MediaFire, d type. To install: Extract the contents of the 7zip archive (d type.7z). Copy the .pcx file in IMAGEMAP folder (in the BoB installation folder), replacing the existing file. Rowan's BoB Update 1 This is a texture and sound update. It includes brighter terrain, tree, ME-109 and spitfire textures. The RAF cockpit sight texture has been changed. RAF and Luftwaffe engine sounds have been ported from Battle of Britain 2. Some additional textures have been changed. It was posted in the forum on 27th December 2019. This fix is available from: MediaFire, ROWANBOB UPDATE1. To install: Extract the contents of the 7zip archive (ROWANBOB UPDATE1.7z). Copy the folders into your BoB installation folder, replacing files as required. City texture mod This is an alternate city textures mod. It was posted in the forum on 28th December 2019. This fix is available from: MediaFire, city texture mod. To install: Extract the contents of the 7zip archive (city texture mod.7z). Copy the .dds files into the Landmap2 folder (in the BoB installation folder) replacing any existing files. Rowan's BoB 2024 mod This mod contains new terrain, water and road textures. It replaces missing textures on an airfield building. It was posted in the forum on 26th May 2024. This fix is available from: MediaFire, rowanbob 2024 mod. To install: Remove existing tree .txt files from the ObjectAdds folder (in the BoB installation folder). Extract the contents of the rar archive (rowanbob 2024 mod.rar). Copy the folders into your BoB installation folder, replacing files as required. Documents The game documentation is available in pdf format of the installation CD of the Xplosiv budget release. It consists of: Manual, pdf download. pdfcoffee, Rowan's Battle of Britain Key Guide The BDG Patch v0.99 also has a manual, installed alongside the patch. It is found in the Docs folder of the BoB installation folder. Example video Win10, with HOTAS, DDrawCompat, Creative ALchemy and TrackIR Finally... Credit and tanks goes to the following, for their contribution in getting the game running in WIn10: The Battle of Britain/MiG Alley Development Group for the BDG patches. narzoul for DDrawCompat. CNET, The Patches Scrolls, Dropbox and MediaFire for hosting patches. rogerroger for the graphics mods. NaturalPoint, AITrack and OpenTrack devs for head tracking software. And this is the 200th article on this website! Good hunting!

A guide to running ATAC: The Secret War Against Drugs in DOSBox Staging. Also known as Advanced Tactical Air Command, ATAC pits you against Colombian drug barons. Your job is conduct a strategic battle plan against the cartels utilising a fleet of F-22 Raptors and AH-64 Longbow attack helicopters. Once a mission is planned it's time to fly and fight! This marks a departure from the usual Microprose single missions career and introduces a strategic campaign to plan and execute (much like AV-8B Harrier Assault). Unfortunately it received fairly average reviews and never seemed to capture the interest of sim fans making it one of MIcroProse's lesser known sims. Contents Version & patch history Retail media Game management HOTAS config DOSBox Staging config Installation Running In-game configuration Documents Example video Finally... Version & patch history ATAC is unusual in there only having been a single retail release on 2 x 3.5"/5.25" High Density (HD) floppy disks or 3 x 3.5"/5.25" Double Density (DD) floppy disks. It was developed by Argonaut and published by MicroProse in 1992. There were no patches released for ATAC. The only compilation with ATAC appears to be Mile High Club 8, with the game distributed on a single CD-ROM. Again, no patches were produced for this edition. Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy disk and cd-rom media to image files, to save wear and tear on media and the mechanical drives. Floppy disks can be ripped to an ima or img format compatible with DOSBox Staging. 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 my DOSBox game management strategy or similar strategy you may have developed. 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. conf - to store DOSBox and HOTAS configuration files. docs - for documents. These management folders can be found in the following game folder (as an example, and used in the rest of the guide): D:\Games\DOS\ATAC HOTAS config 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 controller is detected by DOSBox. [6][7][8]. Stick, throttle and rudder are supported. The physical axes to Windows axes were configured as follows: Physical axis Windows axis Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Throttle DX_Z_AXIS Rudder DX_XROT_AXIS DOSBox Staging config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing): # This is the configuration file for ATAC: The Secret War on Drugs. [cpu] cpu_cycles = 25000 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 = off swap34 = on deadzone = 0 [autoexec] @echo off # mount a "D:\Games\Dos\ATAC\fdd\*.img" -t floppy # mount d "D:\Games\Dos\ATAC\cd\ATAC.iso" -t cdrom mount c "D:\Games\Dos\ATAC\hdd" mixer master 100 /noshow c: cd atac call atac.bat pause exit The following zip file contains this example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown. The cpu_cycle setting of 25000 is suggested. It is equivalent to a 486DX/2 66Mhz machine. cycleup/down settings are changed to values rather than percentages. Voodoo emulation isn't required and is disabled. The mixer settings are a personal preference but a light chorus may be more suitable for aircraft engine sounds. The default Sound Blaster settings are appropriate for Sound Blaster music and digital sounds. The optimum Roland sound settings use the CM32L device, as described in List of MT-32-compatible computer games. The joystick settings are a personal preference and suitable for my joystick hardware. A ch joystick type allows the joystick hat to be used in-game. The autoexec mount settings are examples only, demonstrating how to mount multiple floppy disk images or a cd image. The mixer setting restores the master volume to 100%. The game is run using the installed atac.bat batch file. Installation To install from floppy or CD image run the following command, from the first floppy or CD in DOSBox: A:\> install.exe Note: there is no graphics or sound setup during the installation. The steps to install from floppy are shown below: The CD installation steps are shown below: Running Running the game is the same with floppy or CD editions, run the following batch file from the installation folder, e.g. C:\ATAC> atac.bat In-game configuration There are fairly minimal graphics and sound options configured in game, as well as joystick/HOTAS calibration as the following steps show: Documents The following documents are available: Manual, pdf document, rar archive Old-Games.RU, Games, ATAC: The Secret War Against Drugs, files Technical Supplement, pdf document, rar archive Old-Games.RU, Games, ATAC: The Secret War Against Drugs, files Key Guide, pdf document, rar archive Old-Games.RU, Games, ATAC: The Secret War Against Drugs, files Example video Instant action in ATAC: The Secret War Against Drugs Finally... Credit and thanks go to Old-Games.RU for hosting the documentation and to John Novak and the rest of the DOSBox Staging team for DOSBox Staging v0.83.0-RC1. Good hunting!

Falcon v3.05 title screen A look at the unofficial mods and tools that have been created for Falcon 3.0, MiG-29: Deadly adversary of Falcon 3.0 and Hornet: Naval Strike Fighter, over the years. Where a number of mods and tools were produced or distributed by the same individual or group, those mods and tools are grouped together as a collection. Where possible the product and version applicable to the mod or tool will be identified along with the distributed zip archive. Finally, the mods and tools applicable to the latest versions of Falcon, MiG-29 and Hornet will be listed. The purpose of this guide is to help bring a little order to the myriad of mods and tools at different versions, in different locations (and often unordered) to help new and old Falcon players alike, find the mods and tools that can help manage the Falcon experience and avoid those that are incompatible. Barnson collection Jay Barnson was the developer of the SARGE series of squadron/supply editors, comprising of FALCON SARGE, MIG SARGE and F-18 SARGE. Unfortunately FALCON SARGE is unavailable. MIG SARGE v1.00 Created May 1994 Version MiG-29 v1.03 Description (From the readme):This program allows you to view, edit, and print out information on your pilots and your supplies within a campaign for MiG-29: DEADLY ADVERSARY OF FALCON 3.0 by Spectrum Holobyte. Distribution migsarge.zip F-18 SARGE v1.00 Created April 1994 Version Hornet v1.01 Description (From the readme):This program allows you to view, edit, and print out information on your pilots and your supplies within a campaign for HORNET: NAVAL STRIKE FIGHTER by Spectrum Holobyte. Distribution f18sarge.zip F3Supply Developer Ian "Terminator" Kent Created August 1993 Version Falcon v3.02 Description (From the readme): F3Supply allows you, as the Squadron Commander, to requisition additional supplies of all stores, armament and F-16 aircraft for use in your Campaigns. It has been developed for use with Falcon 3.0 ver. 3.02 and it is intended to be just a simple, quick solution to your logistic problems. Distribution f3supply.zip Falcon 3.0 Startup Menu Developer Aaron "Pirate" Anderson Created January 1992 Version N/A Description (From the readme): As we all know, with the first release of Falcon 3.0 came many bugs and configuration problems. One of the big problems I encountered was a nasty tendency for F3 to trash all my Squadron Files and the FALCON3.DEF file. To solve this problem, I created a menu program that boots prior to F3. It allows me several ways of starting F3. I can back-up before boot, I can restore before boot, or I can go into F3 without any backup or restore. Distribution f3menu.zip Falcon Campaign Editor (FCE) Developer Frank W. Racis Created v0.9: August 1993 v1.0: March 1994 v1.1a: September 1994 v1.2: October 1994 v1.3: July 1995 Version v0.9: Falcon v3.02, MiG-29 v1.0 v1.0: Falcon v3.04, MiG-29 v1.03 v1.1a: Falcon v3.04, MiG-29 v1.03 v1.2: Falcon v3.05, MiG-29 v1.04, Hornet v1.02 v1.3: Falcon v3.05, MiG-29 v1.04, Hornet v1.02 Description (From the readme): Falcon Campaign Editor (FCE) is a program which allows you to change the characteristics of the pilots in your Falcon/MiG29 squadrons, as well as control the supply status of an ongoing campaign. Distribution v0.9: fce09.zip v1.0: fce10.zip v1.1a: fce11a.zip v1.2: fce12.zip v1.3: fce13.zip Flying Muffin Enterprises collection The Flying Muffin Enterprises collection comprises a number of tools and mods produced by various individuals. Some of those tools and mods would be repackaged as the Gold Falcon Utilities, see below. Courtesy of the Internet Archive and Wayback machine the Flying Muffin Enterprises website can still be found. 305FIX.EXE Developer Bill White Created January 1995 Version Falcon v3.05 Description (From the readme): 305FIX.EXE is a small file that will patch FALCON3.EXE or FALCONCD.EXE to eliminate the "Cannot Create File" error when playing multi-player comms in Falcon. It should (and can) be applied to version 3.05 only. Distribution 305com.zip, 305fix.zip F3 Missile Developer Bill White Created June 1995 Version Falcon v3.04, v3.05, MiG-29 v1.03, v1.04, Hornet v1.02 Description (From the readme): F3MSL.EXE will patch Falcon (ver 3.04-3.05), MiG (ver 1.03-1.04) and Hornet (ver 1.02) to make missiles act more realistically. Version 1.0 offers support only for the shoulder-launched weapons (SA-7s and Stingers). Distribution f3msl.zip Gold Falcon Utilities The 'Gold Falcon Utilities' comprises of FalcCalc, Falcon Mapper, F3Maps, F3Requisition, Show F3, and GFU Menu. These utilities were initially released for free/as shareware, until later versions were packaged together and sold commercially as the 'Falcon Commander Utilities' and 'MiG-29 Commander Utilities' from Keyboard Commander Corps (KCC). At some point KCC ceased offering the products and the latest versions of the utilities were repackaged as the 'Falcon Gold Utilities' and distributed as shareware by Flying Muffin Enterprises. FalcCalc Developer Bill White Created v2.51: March 1993 Version v2.51: Falcon v3.01, v3.01.1 Description The Falcon 3.01 Mission Planning Assistant. (From the readme): Was written using the data given in the various charts and pages of both Falcon manuals, the original and OFT. It gives you a lot of information to help you fly successful missions and wage a successful campaign. Distribution v2.51: flclc251.zip Falcon Mapper Developer Greg Prete Created v3.1: April 1992 v3.1d: May 1992 v4.1: October 1992 Version v3.1: Falcon v3.0c v3.1d: Falcon v3.0d v:4.1: Falcon v3.01.1, OFT v3.01.1 Description (From the readme): Falcon Mapper is a freeware tool that allows you to painlessly modify FALCON3.EXE and change the geographical locations for Instant Action (IA) and Red Flag (RF) modes to any part of the Falcon world. Distribution v3.1: f3mp31.zip v3.1d: f3mapr.zip v4.1: f3mapr.exe SHOWF3 Developer Steve Kramp Created v1.0: March 1992 Version v1.0: N/A Description (From the readme): SHOWF3 is a utility to allow viewing of the screen shot files that are produced from the Falcon 3.0 debug screen. Distribution v1.0: showf3.arj, showf3.zip Gold Falcon Utilities package Developers Craig Allen (Gold Falcon Utilities Menu v1.2) Steven Kramp (SHOWF3 v2.2) Greg Prete (Falcon Mapper v8.0) Bill White (FalcCalc v3.55, MiGCalc v1.05, F18Calc v1.02, F3 Requisition v1.55, MiG Requisition v1.05, F18 Requisition v1.02) Created June 1995 Version FalcCalc v3.55: Falcon v3.02 - v3.05 MiGCalc v1.05: MiG-29 v1.00 - v1.04 F18Calc v1.02: Hornet v1.00 - v1.02 F3 Requisition v1.55: Falcon v3.02 - v3.05 MiG Requisition v1.05: MiG-29 v1.00 - v1.04 F18 Requisition v1.02: Hornet v1.00 - v1.02 Falcon Mapper v8.0: Falcon v3.01 - v3.05, MiG-29 v1.00 - v1.04, Hornet v1.00 - v1.02 Gold Falcon Utilities Menu v1.2: N/A SHOWF3 v2.2: N/A Description (From the readme): The GOLD FALCON UTILITIES is a set of irreplaceable helpers for the Spectrum Holobyte(r) family of flight simulators! Formerly commercial, now shareware, they include the latest versions FalcCalc, F3Maps, F3Requisition, Show F3, and GFU Menu. This fully integrated package brings out many of the best features of Falcon 3.0(t), MiG-29(t), and Hornet(t). F3, MiG, F18 Requisition: Squadron and Supply Management Utilities. (From the readme): With F3 Requisition you never have to worry about running out of aircraft, weapons, fuel, or qualified pilots. But that's not what sets it apart. F3 Requisition is different from other Falcon resupply programs because it can be a true "Requisition Simulator," as well as a straight "data editor," (otherwise known as a cheat program!). Gold Falcon Utilities Menu v1.2: A Powerful DOS Based Menu for Flight Simulation Enthusiasts. (From the readme): The Gold Falcon Utilities menu is a powerful DOS based menu which puts you just a keystroke or mouse click away from running your favorite program. SHOWF3: The Falcon 3 File Viewer. (From the readme): SHOWF3 is a Falcon 3 utility that allows you to do two things: 1) View screen shot files that are produced from Falcon 3's own screen-capture program (Yep! It's been on your hard drive all along!) 2) Convert screen shot files to standard PCX or GIF format. Distribution gfutil.zip Strategic FALCON (demo version) Developer Bill White Created October 1994 Version Falcon v3.05 (assumed, based on created date) Description (From the readme): This will give you a taste of what Strategic Falcon is all about. It's a working demo; it does just about everything but allow you to save your changes to Falcon 3.0. Even without the save capability, this is an extremely useful information gathering and planning tool. What you can learn about a campaign using only this demonstration file is much greater than any data you can get with any other "free" software. (In other words, it *is* worth the download!) Distribution sfdemo.zip FTP-SET Developer Victor "Duke" Zaveduk Created August 1995 Version Falcon v3.05 (assumed, based on requirements) Description The FALCOMM and FTPCOM utilities mentioned, form part of the Stinger collection (see below). (From the readme): A file management program for Falcon competitions using the new series of FALCOMM and FTPCOMM TSRs. SET-FALC will help manage your ARMSDATA directory and your AIRVARS file in order to make using the new communication/competition TSRs easy. In order for FALCOMM and FTPCOMM to work properly, very specific files must be installed in your FALCON and ARMSDATA directories. The TSRs rely on having matching files on both ends of the connection, or your CRC values will not match. If your CRCs don't match, you're not in compliance with current ladder rules. Distribution ftp-sets.zip Heittman collection Rob "Orinoco" Heittman was the developer of Falconer. During the development of Falconer v3.0, there was a another release of v2b which also packaged the GAS-UP utility, a Falcon tactics document and a transcript of a publicly hosted chat with Falcon developers. The chat transcript provides an interesting snapshot of Falcon history and what the future plans were, at the time. Falconer Created v2b: January 1992 v2b (later release): February 1992 v3.0: May 1992 v3.1: September 1992 Version v2b: Not listed v3.0: Falcon v3.0d v3.1: Falcon v3.0d. v3.01 (Operation Fighting Tiger) Description (From the readme): Falconer is a freeware tool that lets you control every important aspect of your FALCON 3.0 ("F3") squadron. You can: Automatically reorganize the roster Automatically create "super squadrons" with max abilities for each pilot, and no fatigue Automatically eliminate all fatigue from your squadron Edit pilot ability scores Edit pilot rank Edit pilot status (KIA, MIA, Active, etc.) Export a single pilot to a file Give or rescind any pilot's awards Import a single pilot from a file Print a pilot dossier Print your Sierra Hotel sheet Print a squadron roster Reactivate/resurrect lost pilots Replenish any planes lost in combat Distribution v2b: falcnr.zip v2b (later release): fal3util.zip v3.0: falcnr_d.zip v3.1: falcnr.zip GAS-UP Created February 1992 Version Not listed Description (From the readme): you give this thing your squadron number (as Falconer supplies it), and it will charge up your squadron with 290,000 gallons or so (not an exact science here)... so you can keep rocking until the cows come home. Distribution fal3util.zip Howard collection Investigation has so far revealed, two tools that were released by Richard A. Howard, Convert and the Falcon Squadron Manager. Convert Created August 1993 Version Falcon v3.02, MiG-29 v1.0 Description A utility to convert Falcon v3.01.1 squadrons to Falcon v3.02 squadrons. Distribution convert.zip Falcon Squadron Manager Created v1.6: August 1993 v1.8: January 1994 Version v1.6: Falcon v3.02, MiG-29 v1.0 v1.8: Falcon v3.03, MiG-29 v1.02, Hornet v1.0 Description (From the v1.6 readme): This program will allow you to modify your pilot roster for Falcon 3.02 and MiG-29 1.0 during a campaign. You can create an all-powerful super squadron that will wreak havoc on the enemy or, for a serious test of skill, create a weak group of last-in-the-class trainees. Either way, FSM 1.6 gives you the flexibility you need. Included are some utilities to give you an edge or take one away. (From the v1.8 readme): This program allows you to modify your squadron rosters for Falcon 3.03, MiG-29 1.02, & Hornet 1.0 during a campaign. Distribution v1.6: fsm.zip v1.8: fsm18.zip Jungle Camo v2.0 Developer Eduardo "Edster" Mangual Created June 1993 Version Falcon v3.01 (Operation Fighting Tiger and later but no definitive versions) Description (From the readme): The files in the junglef3.zip file will allow you to change the color of your F-16 and other planes to match the environment of the Israel, Kurile Islands, and Panama campaigns. Distribution junglef3.zip Maps of the Falcon world v2 Developer Don Tatarelli Created April 1993 Version N/A Description (From the readme): These maps are taken right from the Falcon screen. On them, you can plan missions, plot flight paths, note radar ranges, make notes while in flight of enemy activity, etc. You can note your waypoints and those of other flights you've planned. You can maintain your orientation in relation to everything around you. The maps are in PCX format. There is one color map of each theater which shows the entire theater. There is one black and white map of each theater which shows the entire theater. The remaining are maps of zoomed target areas in each theater. Distribution mapsf3v2.zip NITE_EYES Developer Jason "Desperado" Irby Created October 1993 Version Not listed Description (From the readme): This is just a little program I did just for fun one night that I thought you'all might like to play with. I've always had trouble with night missions (i.e. running into the ground!) and I find it real hard to get gun kills. This program alters the night palette so that it simulates the pilot wearing infra-red night vision goggles. It makes thing a little easier to see. Really cool to take through terrain at night like the Canyon. The program makes it easy to take back off if you don't like it so give it a try! Distribution niteeye2.zip PCGamingWiki Addon Launcher Developer Unknown Created Unknown Version N/A Description A startup menu for Falcon, MiG-29 and Hornet. Allows squadrons, high scores and config options to be reset. Allows an allied campaign to be saved. Can load the TM-STICK utility. Distribution PCGamingWiki Polymap Developer Jay Lee Created February 1994 Version Falcon v3.02 - v3.04 (assumed MiG-29 v1.0 - v1.03, Hornet v1.0 - v1.01) Description (From the readme): Polymap is a shareware utility that allows you to re-map Red Flag and Instant Action theatres from the default of Nellis and Kuwait. Polymap works with Falcon3, MiG29, and Hornet. All versions of MiG29 and Hornet are supported. Falcon versions F3.02 through F3.04 are supported. When mapping Hornet Red Flag theatres, the file "NELLIS.MSF" is copied to the new theatre. i.e., if you re-map RF for India, "NELLIS.MSF" is copied to "INDIA.MSF". I'm not positive just what the .MSF file DOES, but Hornet won't function without it. Distribution polymap.zip "Stinger" collection Ken "Stinger" Richardson was a prolific developer of Falcon utilities. The TM-STICK utility is not included, as although originally written by Ken, it was subsequently jointly developed with Thrustmaster and eventually became an official utility and was distributed with official patches and releases. It is described in the earlier Falcon 3.0: Version & patch history blog post. In addition to individual releases, a suite of utilities would be packaged together as a compilation release. CHATTSR Created January 1993 Version Falcon v3.01.1 Description (From the readme): CHATTSR is a terminate and stay resident program that allows "canned" messages to be sent to another player connected via modem or other comms modes. Distribution f3chat.zip F3COOLIE Created August 1993 Version Falcon v3.02 Description (From the readme): F302COOL is a Terminate and Stay Resident (TSR) program that will work with the ThrustMaster FCS allowing you to program the "Coolie Hat" and Buttons 3 and 4 to any keystroke on the keyboard, (including SHFT/CTRL/ALT keys). You can also program "double-click" functions to any button or hat position. Distribution f302ch.zip F3PADLK F3PADLK was initially released without the COM port remap functionality, which was added to later releases. Created For Falcon v3.01.1: February 1993 For Falcon v3.01.1 with COM remap: May 1993 For Falcon v3.02: August 1993 Version Falcon v3.01.1, v3.02 Description (From the readme): F3PADLK is a terminate and stay resident program that will add small indicator lights to Falcon's Padlock view. These lights indicate when your Afterburners are on or when your AirBrake is extended. The Afterburner light is located in the upper left of the centre window in Falcon's padlock view and is Yellow in color. The Brake light is located in the upper right of the same window and is Red in color. Distribution For Falcon v3.01.1: f3pad.zip For Falcon v3.01.1 with COM remap: f3pad2.zip For Falcon v3.02: f302pad.zip FALCOMM & FTPCOMM These are utilities used by the FTP-SET utility. Created August 1995 Version Falcon v3.05 Description (From the readme): FALCOMM & FTPCOMM provide Falcon with the capability to use high speed communications and will significantly reduce your connect times as well as give you smoother game play. FALCOMM & FTPCOMM eliminate potential "cheats" or "abuses" of the rules used by most competitions. Specific keys and key combinations have been blocked. Weapons Effectiveness settings are forced to "LOW" levels. Radar mode choice is displayed to ensure that players are abiding by settings specified in the rules. And checks are made to ensure that players are using approved flight models, weapons load-outs and visuals and that "Falcon Test Pilot" (FTP) has not been used to modify these files. Distribution f3-comm.zip M29COOL Created August 1993 Version MiG-29 v1.0 Description (From the readme): M29COOL is a Terminate and Stay Resident (TSR) program that will work with the ThrustMaster FCS allowing you to program the "Coolie Hat" and Buttons 3 and 4 to any keystroke on the keyboard, (including SHFT/CTRL/ALT keys). You can also program "double-click" functions to any button or hat position. For example: By default the Hat is programmed to switch between forward, back, right and left views depending on what direction you push it. If you push the Hat up twice, it will switch to Padlock view. Distribution m29ch.zip, m29coo.zip M29PAD Created August 1993 Version MiG-29 v1.0 Description (From the readme): M29PAD is a terminate and stay resident program that will add small indicator lights to MiG-29's Padlock and "Scrolled up" views. These lights indicate Afterburners, AirBrake, Radar, and ECM. Each indicator has it's own color for easy identification. Distribution m29pad.zip V42 patch The V42 communication patch was known as V42PATCH or F302V42. The earlier V42PATCH v1.01 also included the CHK_UART utility which would identify the UART chipset of a PC. In compilation releases it would also be named F302COMM, M29COMM or COMMTSR. Created V42PATCH v1.01: October 1992 F302V42: August 1993 Version V42PATCH v1.01: Falcon v3.01.1 F302V42: Falcon v3.02 Description The V42 patch improves Falcon multiplayer communication when using a modem supporting the V.42bis standard. (From the readme): V42PATCH will make numerous changes to Falcon 3.01.1 to enable Falcon to check the CTS line before it attempts to send data. It will allow data to be transferred between the two computers error free and up to 57,600bps. It will rename your original FALCON3.EXE file to F3ORIGIN.EXE. Then it will create a new FALCON3.EXE file with the V42 patch installed. You will need 1.3Meg of free disk space. Distribution V42PATCH v1.01: f3v42a.zip F302V42: f302v42.zip Falcon compilations Created For Falcon v3.01, v3.01.1: August 1993 For Falcon v3.02: September 1993 For Falcon v3.04: February 1994 Version Falcon v3.01, v3.01.1, v3.02, v3.04 Description (For Falcon v3.01, v3.01.1): F3PADLK for FALCON 3.0 version 3.01.1 F3COOLIE for FALCON 3.0 version 3.01.1 V42PATCH ver 1.01 CHK_UART V1.0 (For Falcon v3.02): F3PADLK for FALCON 3.0 version 3.02 F3COOLIE for FALCON 3.0 version 3.02 F302COMM for Falcon version 1.00 (a later version of the V42 patch, version number refers to F302COMM version) (For Falcon v3.04): PADLOCK for FALCON/MIG/HORNET Version 1.02 COOLIE for FALCON/MIG/HORNET Version 1.02 COMMTSR for Falcon/MiG/Hornet Version 1.03 (V42 patch) Distribution For Falcon v3.01, v3.01.1: f3hat.zip For Falcon v3.02: f32pak.zip, f32pak2.zip For Falcon v3.04: f304comm.zip MiG-29 compilations Created For MiG-29 v1.0: September 1993 For MiG-29 v1.01: November 1993 Version MiG-29 v1.0, v1.01 Description (For MiG-29 v1.0): M29COMM for MiG-29 version 1.00 (V42 patch) M29COOL for MiG-29 version 1.0 M29PAD for MiG-29 version 1.0 (For MiG-29 v1.01): M29COMM for MiG-29 version 1.01 (V42 patch) M29COOLIE for MiG-29 version 1.01 M29PAD for MiG-29 version 1.00/1.01 Distribution For MiG-29 v1.0: m29pak.zip, m29pak3.zip For MiG-29 v1.01: m101pk.zip All products compilations (simpak) Compilations compatible with Falcon, MiG-29 and Hornet, also known as simpaks. Created Jan 94 release: January 1994 Aug 94 release: August 1994 Version Jan 94 release: Falcon v3.03 (and later), MiG-29 v1.02 (and later) Aug 94 release: Falcon v3.03 (and later), MiG-29 v1.02 (and later), Hornet v1.0 (and later) Description (Jan 94 release): COMMTSR for Falcon/MiG/Hornet Version 1.00 (V42 patch) COOLIE for FALCON/MIG/HORNET Version 1.00 (also compatible with Hornet v1.0 and later) PADLOCK for FALCON/MIG/HORNET Version 1.00 (compatible with Falcon v3.02 and later, MiG-29 v1.01 and later, Hornet v1.0 and later) (Aug 94 release): COMMTSR for Falcon/MiG/Hornet Version 1.04 (V42 patch) COOLIE for FALCON/MIG/HORNET Version 1.03 PADLOCK for FALCON/MIG/HORNET Version 1.03 (compatible with Falcon v3.02 and later, MiG-29 v1.01 and later, Hornet v1.0 and later) Distribution Jan 94 release: simpak.uue Aug 94 release: simpak.zip, simpk2.zip Compatible mods & tools This is a brief summary of the unofficial mods and tools which are compatible with the latest releases, those being, Falcon v3.05, MiG-29 v1.04 or Hornet v1.02. Given those versions are released digitally on the Steam and GOG platforms, they are the versions most likely to be used by new Falcon players. Assuming the release notes for each mod and tool are accurate. Where more than one version is compatible, the latest version will be listed. The following are listed as compatible: Falcon Campaign Editor v1.3 F3 Missile Gold Falcon Utilities package Strategic FALCON (demo version) simpak (Aug 94 release) The following are listed as compatible (for multiplayer games), but not confirmed: 305FIX.EXE FTP-SET FALCOMM & FTPCOMM The following tools and mods 'might' be compatible, but not confirmed: Jungle Camo v2.0 NITE_EYES The following tools do not require a specific version of Falcon, MiG-29 or Hornet: Falcon 3.0 Startup Menu PCGamingWiki Addon Launcher Maps of the Falcon world v2 Finally... If you notice anything wrong or misleading or just plain confusing, please let me know, so I can fix it. Hopefully this provides a useful resource to help navigate the myriad of old Falcon tools hiding in the recesses of the Internet! Good hunting!

A guide to running the floppy, CD and digital releases of 1942 Pacific Air War and 1942 Pacific War Gold in the DOSBox Staging emulator. 1942 The Pacific Air War (PAW) is a World War 2 sim set in the pacific theater. Playing as part of US or Japanese forces, missions and the campaigns are staged from carriers. The expansion would add US and Japanese army aircraft staging from island airstrips. Table of contents Version & patch history Initial retail version (May 1994) Roland sound fix for 1942 PAW (July 1994) 1942 PAW Modem Update (October 1994) 1942 PAW Modem Extra Files (October 1994) 1942: The Pacific Air War Scenario (December 1994) 1942: Pacific Air War Version 1.4 Update (January 1995) 1942: The Pacific Air War Gold (December 1994/February 1995) Updated digital sound driver for 1942 (January 1995) 1942: Pacific Air War Version 1.5b Update (May 1995) 1942: Pacific Air War GOLD Update Volume Install Problems (October 1995) Compilation editions (1994-1997) 1942: The Pacific Air War digital release (2015) Patching strategies 1942: The Pacific Air War retail release only 1942: The Pacific Air War retail release & Scenarios expansion 1942: The Pacific Air War Gold edition CD compilation releases 1942: The Pacific Air War digital edition Retail media Game management HOTAS config DOSBox Staging config Compatibility tools Jemm Expanded Memory Manager (EMM) Installation Gold edition installation Digital edition installation VirtualMIDISynth and MIDIMapper Installation 1942: The Pacific Air War floppy retail releases Install 1942: The Pacific Air War Install Jemm Configure 1942: The Pacific Air War Install 1942: The Pacific Air War Scenarios (optional) 1942: The Pacific Air War CD compilation Install 1942: The Pacific Air War Install Jemm Setup 1942: The Pacific Air War Configure 1942: The Pacific Air War 1942: The Pacific Air War Gold edition Obtaining 16-bit Windows Installing Windows for Workgroups DOSBox Staging config (Windows apps only) 1942: The Pacific Air War Gold installation preparation 1942: The Pacific Air War Gold installation Configuring 1942: The Pacific Air War Gold Install Jemm 1942: The Pacific Air War digital release Switching to DOSBox Staging Upgrading Jemm (optional) Patching 1942: Pacific Air War Version 1.4 Update 1942: Pacific Air War Version 1.5b Update Sound options Sound Blaster Roland sound CM32-L MT-32 Sound Canvas FluidSynth External MIDI devices Running In-game configuration PAW Launcher Installing Gold edition Windows app config Documents Gold & digital edition Gold edition Digital edition Example videos Finally... Version & patch history This is a brief look at the version and patch history of the game. When running under DOSBox Staging all versions of the game (patched and unpatched) require the Jemm expanded memory manager. Initial retail version (May 1994) The initial retail release occurred in May 1994. It was released on 6 x 3.5" 1.44MB High Density (HD) floppy disks. This version is assumed to be version 1.0 as no version number can be displayed on the in-game main menu. The installer only allows for the selection and configuration of a single digital audio/music sound card. Roland sound fix for 1942 PAW (July 1994) The Roland sound fix for 1942 PAW is a single replacement file ((rsound.ft). Taken from the Microprose FTP archive: This file replaces the Roland sound driver supplied with 1942 Pacific Air War. A couple sound effects, like the guns, did not work correctly on the original MT-32, though they worked fine on the LAPC-1 version. This has now been corrected. If you don't have an MT-32, you don't need this patch. This patch is not recommended, having been superseded by later patches. This patch can be found at: Internet Archive, Microprose FTP archive. Internet Archive, Microprose FTP mirror archive. 1942 PAW Modem Update (October 1994) The 1942 PAW Modem Update is a zip archive (pawmodem.zip). Taken from the release notes: The files MODM28_8.TXT, MODM14_4.TXT, MODM9600.txt, and MODMINIT.TXT will be installed into your 1942 directory with this update. 1942 will read the file MODMINIT.TXT to find the initialization string for your modem. The other three files contain recommended initialization strings for 28.8K, 14.4K and 9600 baud modems. This is a modem enhancement patch only. It must be installed using DOSBox, once unzipped. This patch is not recommended, as it concerns legacy modem hardware only. This patch can be found at: DOS Days, 1942: The Pacific Air War, Versions of the game known to exist. Internet Archive, 1942: The Pacific Air War Modem Patch. Internet Archive, Microprose FTP archive. 1942 PAW Modem Extra Files (October 1994) The 1942 PAW Modem Extra Files is a zip archive (pawmod1.zip). Taken from the Microprose FTP archive: The very initial release of the PAWMODEM.ZIP file did not contain a couple necessary files. This would ONLY apply to downloads on the evening of Oct 12 and the early morning of Oct 13. This PAWMOD1.ZIP file contains the missing files and is only available to save you from having to download another 500K. All files contained in this .zip are included in the current version of PAWMODEM.ZIP. This is a modem enhancement patch only. It must be installed using DOSBox, once unzipped. This patch is not recommended, as it concerns legacy modem hardware only. This patch can be found at: Internet Archive, Microprose FTP archive. 1942: The Pacific Air War Scenario (December 1994) The one and only expansion, 1942: The Pacific Air War Scenario allowed the player to fly for US and Japanese armies. Six new aircraft are included: P-38 Lightning, P-40 Warhawk, P-51 Mustang, Ki-61 'Tony', Ki-84 'Frank' and N1K 'George'. There are also additional missions for the Philippines and New Guinea campaigns. The expansion was distributed on 3 x 3.5" 1.44MB HD floppy disks. The installer allows the selection of separate digital sound and music cards. Following installation the version is Scenario Ver 1.0. 1942: Pacific Air War Version 1.4 Update (January 1995) A comprehensive enhancement patch, taken from the Microprose FTP archive: This is the 1942:PAW v1.4 update. This update implements digital sounds, 6 new airplanes, and new flight models. To update, UNZIP the file PAWV14.ZIP to a TEMP directory, change to that directory and type "INSTALL". Follow the prompts for installation. IMPORTANT: Do **NOT** UNZIP the file to your 1942 directory. Also, to update correctly, the update REQUIRES that you have played the game at least once to create a sound and joystick configuration file. Please note: While digital sounds (gun, cannon, explosion, etc) have been added, digital SPEECH has NOT been added. Also, the 6 new planes are available ONLY via the mission builder - there are NO pre-generated missions. Speech and hundreds of historically accurate missions are available in the commercial release of the 1942:PAW SCENARIO DISK! This patch must be installed using DOSBox, once unzipped. This is a recommended patch for any version of PAW below v1.4. This patch can be found at: DOS Days, 1942: The Pacific Air War, Versions of the game known to exist. Internet Archive, 1942: Pacific Air War 1.4 Patch. Internet Archive, Microprose FTP archive. Internet Archive, Microprose FTP mirror archive. 1942: The Pacific Air War Gold (December 1994/February 1995) The Gold edition was a compilation of the original game and expansion published as a single game and pre-patched with the v1.4 update patch. The Gold edition also featured a Windows 3.x installer and utilities to configure digital sound and music under Windows. It also featured a multimedia app featuring instruction and history videos. This version was distributed on a single CD-ROM. The base game, scenario disk, and Gold edition was a product release cycle also used by the Microprose sim, Fleet Defender. Updated digital sound driver for 1942 (January 1995) This is a bug fix patch for specific legacy sound cards for v1.4 only. Taken from the Microprose FTP archive: This is an updated digital sound file for Pacific Air War 1942 that fixes a compatibility problem with the DigiSpeech Port*able sound card by disabling some error checking. It MAY fix other compatibility problems also. This patch is ONLY for the ver 1.4 update, scenario disk and Gold versions. It will NOT work with the original game. Once unzipped, this is a file replacement patch. This patch is only recommended for legacy hardware and is not required for DOSBox Staging. This patch can be found at: DOS Days, 1942: The Pacific Air War, Versions of the game known to exist. Internet Archive, 1942: The Pacific Air War Sound Patch. Internet Archive, Microprose FTP archive. Internet Archive, Microprose FTP mirror archive. Old-Games.RU, 1942: The Pacific Air War, 1942: The Pacific Air War - files. 1942: Pacific Air War Version 1.5b Update (May 1995) Once unzipped, this is a file replacement patch providing bug fixes/enhancements. From the release notes: This version of 1942: THE PACIFIC AIR WAR corrects the following problems: Lack of aggressiveness for enemy planes and players wingmen. Enemy planes always taking the fight down to near sea level or ground level. Planes crashing into the ground for no apparent reason. Planes under fire performing lazy left and right hand turns. Lack of vertical maneuvers for enemy and wingmen planes. This patch requires version 1.4 and is a recommended patch for v1.4. Following installation the game is upgraded to v1.5b. This patch is available from: DOS Days, 1942: The Pacific Air War, Versions of the game known to exist. Internet Archive, 1942: Pacific Air War 1.4 to 1.5b Patch. Old-Games.RU, 1942: The Pacific Air War, 1942: The Pacific Air War - files. 1942: Pacific Air War GOLD Update Volume Install Problems (October 1995) Once unzipped, this is a file replacement patch providing compatibility with alternate CD volume labels. Taken from the Microprose FTP archive: This update contains a new version of the file, 1942cd.com, which will correct a problem seen if your copy of this program has a volume label of "paw_1942" instead of "1942_paw", where the game would not run from a minimum installation. This is a only recommended for those using a Gold edition cd with an alternate label. It should not be required by DOSBox Staging as a full install is recommended. This patch is available from: DOS Days, 1942: The Pacific Air War, Versions of the game known to exist. Internet Archive, 1942: Pacific Air War Gold (volume label fix). Internet Archive, Microprose FTP archive. Internet Archive, Microprose FTP mirror archive. The Patches Scrolls, 1942: Pacific Air War Gold. Compilation editions (1994-1997) From 1994 - 1997 PAW appears in a number of compilation editions. Most compilations featured the original game and expansion pre-patched to v1.4. Most compilations were distributed on 1 or more CD-ROMs. Compilations included a budget re-release featuring the original game and expansion and the Conquer the Skies compilation. The compilation editions did not not feature the Windows 3.x installer or apps. The budget rerelease with base game and scenario disk, but without Windows 3.x components was a product release cycle also used by the Microprose sim, Fleet Defender. The Conquer the Skies compilation features an install utility that allows the selection and configuration of a single sound card, supplemented with a setup utility that allows the selection of separate digital audio and music sound cards. 1942: The Pacific Air War digital release (2015) The digital edition is equivalent to the Gold edition but without the Windows 3.x components, making it similar to compilation editions, but also pre-patched to the latest v1.5b update patch. The installer allows music and digital sound to use separate devices and cloud saves are available on the gog.com digital platform. The digital edition of the game is also available on Steam. Patching strategies The following are recommended patching strategies for the various releases of PAW. 1942: The Pacific Air War retail release only Install 1942: The Pacific Air War retail release. Patch with 1942: Pacific Air War Version 1.4 Update. Patch with Updated digital sound driver for 1942 (optional, only for affected legacy hardware). Patch with 1942: Pacific Air War Version 1.5b Update. 1942: The Pacific Air War retail release & Scenarios expansion Install 1942: The Pacific Air War retail release. Install 1942: The Pacific Air War Scenarios expansion. Patch with 1942: Pacific Air War Version 1.4 Update. Patch with Updated digital sound driver for 1942 (optional, only for affected legacy hardware). Patch with 1942: Pacific Air War Version 1.5b Update. 1942: The Pacific Air War Gold edition Install 1942: The Pacific Air War Gold edition. Patch with Updated digital sound driver for 1942 (optional, only for affected legacy hardware). Patch with 1942: Pacific Air War Version 1.5b Update. Patch with 1942: Pacific Air War GOLD Update Volume Install Problems (optional, if required). CD compilation releases Install 1942: The Pacific Air War (expected to include expansion and pre-patched to v1.4). Patch with Updated digital sound driver for 1942 (optional, only for affected legacy hardware). Patch with 1942: Pacific Air War Version 1.5b Update. 1942: The Pacific Air War digital edition Install 1942: The Pacific Air War digital edition (no patches required). Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy 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 staging compatible .ima or .img image format. The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd. When ripping cds it is recommended to use a combined ISO9660 and Joliet file system for the image, this is to preserve files with a .$00 extension, which are not supported under a ISO9660 only file system. A digital edition of the game is available on gog.com, and Steam. Game management It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders for the DOS version are: cd - for any cd images. fdd - for any floppy images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents. patch - to store any patches. win - to store any Windows install images and drivers (optional). These management folders can be found in the following game folder (as an example): D:\Games\DOS\1942 Pacific Air War 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 controller is detected by DOSBox. [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 DOSBox Staging config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing). This config is suitable for the PAW game. A suitable DOSBox config for Windows for Gold edition Windows apps is covered later. # This is the configuration file for 1942: The Pacific Air War. [cpu] cpu_cycles = 20000 cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = cm32l romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 14.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] # Other valid options: mt32, fluidsynth, port mididevice = soundcanvas midiconfig = 0 [joystick] joysticktype = ch timed = off swap34 = on deadzone = 0 [dos] xms = off ems = off umb = off [autoexec] @echo off # Base game floppy images # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\paw*.img" -t floppy -ro # Scenario expansion floppy images # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\scen*.img" -t floppy -ro # CD release image # mount d "D:\Games\Dos\1942 Pacific Air War\cd\paw.iso" -t cdrom # PAW Gold CD release # mount d "D:\Games\Dos\1942 Pacific Air War\cd" -t cdrom mount c "D:\Games\Dos\1942 Pacific Air War\hdd" mixer master 100 /noshow c: # Non-gold editions # cd \mps\1942 # jemmex.exe frame=e000 load # cd \mps # call 1942.bat # exit # Gold edition running update v1.5b # cd \mps\pawgold # jemmex.exe frame=e000 load # 1942.exe # exit The following zip file contains this example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown. The cpu_cycle setting of 20000 is suggested to provide quicker installation. It is equivalent to a 486DX 33+ Mhz machine. The game runs with the default cpu_cycles_protected setting at 60000. cycleup/down settings are changed to values rather than percentages. Voodoo emulation isn't required and is disabled. The mixer settings are a personal preference but a light chorus may be more suitable for aircraft engine sounds. PAW supports a wide variety of MIDI sound devices including Roland MIDI and general MIDI devices. Sound Blaster is also another option for music. The default Sound Blaster settings are appropriate for Sound Blaster music and digital sounds. Multiple general MIDI devices are configured in the [mt32], [fluidsynth] and [soundcanvas] sections. A Win10 MIDI synth can also be used with DOSBox Staging (see Compatibility tools). The optimum Roland sound settings use the CM32L device, as described in List of MT-32-compatible computer games. The FluidSynth soundfont is a personal preference. In the above example, Shan SGM Pro v14 is used, an excellent general purpose soundfont. DOSBox Staging v0.83.0-RC1 introduces Sound Canvas support. The Sound Canvas config, like the Roland MIDI config, requires a model to be selected and a folder containing the Sound Canvas ROMs to be specified. The MIDI section specifies a Win10 MIDI synth. This can be changed to your preferred MIDI device: mt32, fluidsynth or soundcanvas. Alternatively a PAW launcher is available to allow selection of a DOSBox MIDI device within DOSBox (see PAW Launcher), allowing multiple MIDI devices to be tried before selecting your preferred MIDI device and setting it in the config as a default. The midiconfig setting is used to select a Win10 MIDI synth if there is more than one synth available. The joystick settings are a personal preference and suitable for my joystick hardware. A ch joystick type allows the joystick hat to be used in-game. The [dos] settings are recommended in the DOSBox Staging wiki, Game issues for 1942: The Pacific Air War. The autoexec mount settings are examples only, demonstrating how to mount multiple floppy disk images or a cd image. The mixer setting restores the master volume to 100%. The Jemm memory manager is loaded using recommended options from the DOSBox Staging wiki, Game issues for 1942: The Pacific Air War. The game is started using the batch (.bat) file created by the installer of most PAW releases. This can be replaced with a PAW Launcher menu Compatibility tools The following compatibility tools are employed to ensure PAW runs without issues in the DOSBox Staging emulator. Jemm Expanded Memory Manager (EMM) When run in the DOSBox Staging emulator, PAW requires the use of the Jemm Expanded Memory Manager. WIthout this memory manager sound does not work properly. Jemm is freely available from the Jemm GitHub repository under Releases. The recommended version to use is the latest v5.86 version. The digital edition of PAW already includes an earlier Jemm expanded memory manager. Installation Jemm should be obtained before running the PAW installer. For floppy disk based releases, once the base game is installed, Jemm should be added using the instructions below. The scenarios expansion and patches can then be installed. For CD based releases once the CD based installer has complete, Jemm should be added using the instructions below. Patches can then be installed. Once downloaded the contents of the zip archive can be extracted to a folder in Win10, e.g. D:\Games\DOS\1942 Pacific Air War\patch\jemm The jemmex.exe file should be copied into the game installation folder, this can be done in Win10: # Game installation folder in Win10 D:\Games\DOS\1942 Pacific Air War\hdd\MPS\1942 # And in DOSBox C:\MPS\1942 Add the following lines to the [autoexec] section of the DOSBox Staging config, after switching to the c: drive: [autoexec] ... c: cd \mps\1942 jemmex.exe frame=e000 load ... This changes to the DOSBox folder with the jemmex.exe file and loads it into memory at memory location E000. Lower memory addresses are already used by DOSBox Staging. Gold edition installation The Gold edition uses a slightly different default installation folder. The jemmex.exe file should be copied into the game installation folder, this can be done in Win10: # Game installation folder in Win10 D:\Games\DOS\1942 Pacific Air War\hdd\MPS\PAWGOLD # And in DOSBox C:\MPS\PAWGOLD Add the following lines to the [autoexec] section of the DOSBox Staging config, after switching to the c: drive: [autoexec] ... c: cd \mps\pawgold jemmex.exe frame=e000 load ... Digital edition installation The digital edition already includes an older version of the Jemm expanded memory manager. To use the older included version, only the following line needs to be added to the [autoexec] section of the DOSBox Staging config, after switching to the c: drive: [autoexec] ... c: jemm578B\jemmex.exe frame=e000 load ... To use the latest version, he jemmex.exe file should be copied into the game installation folder, this can be done in Win10: # Digital edition game installation folder in Win10 D:\Program Files (x86)\GOG Galaxy\Games\1942 The Pacific Air War # And in DOSBox C:\ Add the following lines to the [autoexec] section of the DOSBox Staging config, after switching to the c: drive: [autoexec] ... c: jemmex.exe frame=e000 load ... VirtualMIDISynth and MIDIMapper These are optional MIDI tools that can be used by DOSBox Staging and PAW, as General MIDI (GM) is supported as a PAW music option. The built in features of DOSBox Staging can do the job of these tools but they may make things easier for those who wish to try out multiple soundfonts (VirtualMIDISynth) or switch between different Win10/11 MIDI synths (MIDIMapper). For a further discussion on using these tools with the latest DOSBox Staging, see DOSBox Staging and MIDI. Installation 1942: The Pacific Air War floppy retail releases This section is applicable to 1942: The Pacific Air War with or without the Scenarios expansion. Note: PAW and PAW expansion disk images should be named so they can be distinguished from each other, as shown in the below example. Example mount commands for floppy images, to add to the [autosec] section of the DOSBox config, are shown below: [autoexec] ... # Base game # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\paw*.img" -t floppy # Scenarios expansion # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\scen*.img" -t floppy ... As both PAW and PAW Scenarios use multiple floppy disk images the *.img wildcard is used to mount a set of floppy images. Only one set of floppy images should be mounted at once, either paw*.img (6 base game installation floppy images) or scen*.img (3 Scenario expansion floppy images) depending on the step of the installation process. Install 1942: The Pacific Air War The installation process is straightforward, the gallery below shows each step required. Ensure the PAW disk images are mounted as the A: drive, the line below should be the only uncommented/enabled A: mount n the DOSBox config. mount a "D:\Games\Dos\1942 Pacific Air War\fdd\paw*.img" -t floppy Start DOSBox with this config and run the installer from the first disk/image: A:\> install.exe Only a single music & sound card can be selected with the PAW base game, so selecting SoundBlaster Pro is a good choice at this stage. Install Jemm Use the Jemm installation instructions to add Jemm and change the DOSBox config. Restart DOSBox. Configure 1942: The Pacific Air War Note: It may seem odd to configure PAW at this stage, however, the Scenarios expansion and update patch require a complete in-game configuration before the installers will run. Change to the MPS folder and run the game from the batch file to start the configuration: C:\> cd \mps C:\MPS> 1942.bat Once the intro movie has completed the configuration will start immediately, the steps are described in In-game configuration. Install 1942: The Pacific Air War Scenarios (optional) For those wishing to install the PAW Scenarios expansion, the installation process is straightforward, the gallery below shows each step required. Ensure the PAW Scenario disk images are mounted as the A: drive, the line below should be the only uncommented/enabled A: mount n the DOSBox config. mount a "D:\Games\Dos\1942 Pacific Air War\fdd\scen*.img" -t floppy Start DOSBox with this config and run the installer from the first disk/image: A:\> install.exe Note: the above examples demonstrates switching to a MIDI music device, however you may also wish to switch the digital sound device to the Sound Blaster 16. The digital sound parameters should be set to the DOSBox Sound Blaster defaults of: Address: 220 h IRQ: 7 DRQ: 1 Music and digital sound options can be re-configured multiple times by running the installer from the game installation folder, e.g. C:\> cd \mps\1942 C:\MPS\1942> install.exe Hit Esc to skip past the release notes and select Setup Sound. After re-configuring sound devices don't forget to Save Setup. 1942: The Pacific Air War CD compilation This section is applicable to 1942: The Pacific Air War CD compilation releases. Example mount commands for a cd image, to add to the [autosec] section of the DOSBox config, is shown below: [autoexec] ... # CD release mount d "D:\Games\Dos\1942 Pacific Air War\fdd\paw.iso" -t cdrom ... Install 1942: The Pacific Air War The process of installing the CD release is identical to the floppy version with an identical installer app. See Install 1942: The Pacific Air War. The installer app installs the base game plus expansion pre-patched to version v1.4. Install Jemm Use the Jemm installation instructions to add Jemm and change the DOSBox config. Restart DOSBox. Setup 1942: The Pacific Air War The installer app adds an additional setup app (setup.exe) which is identical to the expansion installer. The following commands run the setup app from the PAW installation folder: C:\> cd \mps\1942 C:\MPS\1942> setup.exe The steps to setup music and digital sound devices are identical to the steps used in the expansion installer, as described in Install 1942: The Pacific Air War Scenarios (optional). The Install Game option of the setup app should not be used. The expansion having already been installed and patched by the CD installer app. Music and digital sound options can be re-configured multiple times by running the setup app from the PAW installation folder. Configure 1942: The Pacific Air War The steps to configure a PAW CD release are identical to a floppy disk based release and are described in In-game configuration. 1942: The Pacific Air War Gold edition This section is applicable to 1942: The Pacific Air War Gold edition only. It is recommended to use two DOSBox Staging configs: A config to run the PAW game within DOSBox. A config to run Windows apps within Windows for Workgroups within DOSBox. The PAW game requires a config disabling extended/expanded memory and upper memory blocks in the [dos] section and uses the Jemm expanded memory manager instead. The PAW Windows config below continues to use the extended/expanded memory and upper memory blocks provided by DOSBox Staging. Both configs should use the same DOSBox emulated hard disk folder (hdd). The notes on obtaining and installing Windows for Workgroups are identical to those in the Fleet Defender: Defending in DOSBox guide. They are repeated below for convenience. Obtaining 16-bit Windows This requires a 16-bit Windows version which includes Windows 3.1, WIndows 3.11 or Windows for Workgroups 3.11. None of these products are available for purchase, but can be obtained from WinWorld. The recommended version is Windows for Workgroups 3.11 OEM. This is distributed as a zip archive containing multiple floppy disk images. It is recommended to keep a copy in the win game management folder. Installing Windows for Workgroups To install Windows for Workgroups in DOSBox Staging, there are some excellent Windows 3.1x installation instructions to be found on the DOSBox Staging wiki. Credit and thanks go to MasterO2 for these excellent instructions. Rather than repeating the already clear and precise instructions, this part of the guide will cover some additional notes to be used in conjunction with these instructions. Note: The instructions use a smaller/simpler DOSBox Staging config to install Windows and then builds on this simple config to add sound/MIDI etc. It's recommended to use this simple Windows install config and then switch to the config shown in DOSBox Staging config (1942: The Pacific Air War Gold), after Windows is installed. Note: The zip file containing the Windows disk images was saved in the win folder for safekeeping. The disk image contents of this zip file (eg. disk1.img, disk2.img, etc...) were extracted and stored in the fdd folder. Note: The instruction's DOSBox config file was supplemented with mount and imgmount commands below. As there are multiple disk images in the fdd folder, the wildcard *.img was used, as a convenience, to mount them all. The first disk image will be accessible from the A: drive. Ctrl-F4 switches to the next disk image. If accessing the last disk image, Ctrl-F4 will return to the first disk image. [autoexec] mount a "D:\Games\Dos\1942 Pacific Air War\fdd\*.img" -t floppy mount c "D:\Games\Dos\1942 Pacific Air War\hdd" Note: The instructions refer to creating DRIVERS and INSTALL folders in a win31 folder. Instead the win31 folder is replaced with our hdd folder. So the DRIVERS and INSTALL folders are created in our hdd folder. So: In DOSBox Staging we see: C:\INSTALL C:\DRIVERS In Win10/11 we see (as an example): D:\Games\Dos\1942 Pacific Air War\hdd\INSTALL D:\Games\Dos\1942 Pacific Air War\hdd\DRIVERS Note: The instructions refer to Windows 3.0 installation instructions, to copy the disk image contents to the INSTALL folder (using DOSBox Staging). As all of the disk images are mounted already, the same copy command (below) is used to copy the disk contents to the INSTALL folder (using DOSBox Staging). Then use Ctrl-F4 to access the next disk and use the same copy command again, until the file contents of each disk have been copied. COPY A:\*.* C:\INSTALL Note: The recommended display drivers and SoundBlaster 16 drivers were used, following the instructions provided. The zip files containing the drivers were placed in the win folder for safekeeping. The contents of the zip files were stored in an S3 folder (for the display drivers) and an SB16 folder (for the SoundBlaster 16 drivers), within the DRIVERS folder, so: In DOSBox Staging we see: C:\DRIVERS\S3 C:\DRIVERS\SB16 In Win10/11 we see (as an example): D:\Games\Dos\1942 Pacific Air War\hdd\DRIVERS\S3 D:\Games\Dos\1942 Pacific Air War\hdd\DRIVERS\SB16 Note: The recommended resolution to use for the display driver is 640x480. This may seem low but is optimum for the video app as it allows the DOSBox window to be filled (if DOSBox is run in a window) or fullscreen (if run in fullscreen). At higher resolutions the video app is run in a 'Windows' window. At very high resolutions (e.g. 1600x1200) it becomes a very small window making it harder to navigate or read text. However this is really down to a personal preference. Note: Although I used the instructions to set up CD Audio in Windows, this was unnecessary for PAW. Note: The printing and networking sections of the guide can be ignored as those features aren't required by PAW. DOSBox Staging config (Windows apps only) The final DOSBox Staging config to use once Windows for Workgroups is successfully installed, is a combination of the earlier DOSBox Staging config with the following additional settings applied. Note: This is an additional DOSBox Staging config (used to run the PAW Windows apps), to be used in conjunction with the earlier config (used to run the PAW game). Both configs should use the same DOSBox emulated hard disk folder (hdd). The Windows app config is based on the PAW game config but with sections replaced with those below, i.e. the [cpu] section in the earlier config is replaced with the [cpu] section below. # This is the configuration file for 1942: The Pacific Air War Gold. # This config supports 16-bit Windows. [dosbox] vmemsize = 4 [cpu] cputype = pentium cpu_cycles = 40000 cycleup = 500 cycledown = 500 [mouse] builtin_dos_mouse_driver_options = immediate [autoexec] @echo off # Unmount any existing c: drive mount -u c # C: drive with Windows for Workgroups 3.11 and cd folder mount c "D:\Games\Dos\1942 Pacific Air War\hdd" mount d "D:\Games\Dos\1942 Pacific Air War\cd" -t cdrom set path=%path%;c:\windows; c: # win # exit Note: The [dos] section is omitted to use default settings. The [dos] setting from the game config should not be used. The following zip file contains the complete example DOSBox Staging config. It should be changed to match your hardware and personal preferences. 1942: The Pacific Air War Gold installation preparation As was briefly mentioned, the Gold edition contains files on the CD which do not conform to the ISO9660 filesystem standard (those with a $00 file extension). When ripping a Gold edition CD into an image it is preferable to use the 'ISO9660 with Joliet extensions' filesystem which will retain the $00 extension. Files on the CD/image with the extension $00 will be interpreted as _00 by DOSBox Staging, which only supports the CD ISO9660 filesystem standard. During installation this will cause the Gold installer app to fail. This is an issue for the Gold edition only, other CD compilation releases extract files from archives during the installation process, retaining the correct file extension. The solution is to copy the contents of the Gold CD/image into a folder and mount the folder as a CD to retain the correct extension. The steps to take are: Mount the PAW Gold CD/image in Win10/11. Copy the contents of the CD/image into a suitable cd folder, e.g. D:\Games\DOS\1942 Pacific Air War\cd Unmount/eject the image in Win10/11. Mount the CD folder as a CD in the DOSBox config: [autoexec] ... mount d "D:\Games\Dos\1942 Pacific Air War\cd" -t cdrom ... 1942: The Pacific Air War Gold installation Start Windows for Workgroups (WfW) from within DOSBox and use the File Manager to open the CD and run the installer (setup,exe). The gallery below shows the steps to install the game: Configuring 1942: The Pacific Air War Gold Immediately following installation, configuration will begin. The gallery below shows the steps to configure the game: Install Jemm Use the Jemm installation instructions to add Jemm and change the PAW game DOSBox config only. Restart DOSBox. 1942: The Pacific Air War digital release Digital releases should be installed using the appropriate digital platform client, or any standalone install packages available from the digital platform, e.g. the gog.com offline installer. This process assumes the installation folder used will be the one created by the digital platform client or offline installer. Switching to DOSBox Staging The [autoexec] section of the PAW game DOSBox config is changed as shown below: [autoexec] @echo off mount c "D:\Program Files (x86)\GOG Galaxy\Games\1942 The Pacific Air War" # mount c "D:\Program Files (x86)\GOG Galaxy\Games\1942 The Pacific Air War\cloud_saves" -t overlay mixer master 100 /noshow c: jemm578B\jemmex.exe frame=e000 load 1942.exe A gog.com digital release provides a cloud based saving facility, it does this by providing an overlay mount in the digital release DOSBox config. This mount is recreated in the DOSBox Staging config, however it remains untested and is not guaranteed to work. The gog.com Galaxy client may need to be running. Upgrading Jemm (optional) The digital release uses Jemm v5.78, the latest version is v5.86. Optional: Use the Jemm digital edition instructions to add the latest version of Jemm and change the DOSBox game config. Patching Showing the version number The earlier patching strategies indicate the required patches. Running in DOSBox means patches for specific legacy hardware or smaller install sizes can be skipped. As patches require a particular version, to check the version, run the game and at the main menu, use Alt + V to display the current version (see screenshot). 1942: Pacific Air War Version 1.4 Update This patch is applicable to: 1942: The Pacific Air War floppy release at Ver 1.0. 1942: The Pacific Air War floppy release with Scenario expansion at Scenario Ver 1.0. To apply the patch: Ensure the mount command for the floppy disk images are commented/disabled, otherwise the installer will fail: # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\paw*.img" -t floppy -ro # mount a "D:\Games\Dos\1942 Pacific Air War\fdd\scen*.img" -t floppy -ro In Win10/11, if the contents of the patch zip file (paw_v14a.zip) are additional zip files, extract them to a temp folder, e.g. D:\Games\DOS\1942 Pacific Air War\patch\patch_v14 In Win 10/11 extract the contents of these additional zip files to a patch folder (paw_v14) in the DOSBox hdd folder, e.g. # In Win10/11 D:\Games\DOS\1942 Pacific Air War\hdd\paw_v14 # In DOSBox C:\paw_v14 In DOSBox, change to the paw_v14 folder and run the patch: C:\> cd paw_v14 C:\PAW_V14> install.bat If the base game or Scenario expansion installer starts, then the A: drive mount commands were not disabled. Remove the contents of the paw_v14 folder and extract the patch contents to this folder again. Disable the mount commands and restart DOSBox. The remaining steps are shown in the gallery below: The installation process for Update V1.4 is nearly identical to the Scenario expansion installation process. 1942: Pacific Air War Version 1.5b Update This patch is applicable to: 1942: The Pacific Air War Gold edition at Scenario Ver 1.0. 1942: The Pacific Air War with/without Scenario expansion and CD compilation releases at Update Ver 1.4. To apply the patch: In Win10/11, extract the contents of the patch zip file to a folder in the game management patch folder. Optional: You may wish to take a backup of the original 1942.exe file. In Win10/11, copy the files: 1942.exe and paw15b.txt to the game installation folde, replacing any files as required: # In Win10/11 one of these folders: D:\Games\DOS\1942 Pacific Air War\hdd\MPS\1942 D:\Games\DOS\1942 Pacific Air War\hdd\MPS\PAWGOLD # In DOSBox it becomes one of these folders C:\MPS\1942 C:\MPS\PAWGOLD Start DOSBox and run the game. At the main menu use Alt + V to check the version: Update version 1.5b Sound options PAW supports a wide variety of digital sound and music options. The PAW Launcher can swap between MIDI devices during a DOSBox session, and coupled with VirtualMIDISynth allows switching between soundfonts 'on-the-fly'. However once a preference has been settled on, you may wish to make this the default without having to choose the preferred sound/music devices each time. When reconfiguring music/sound devices the following apps should be used: Floppy release with/without expansion,from the game installation folder: install.exe. 1942: The Pacific Air War Gold edition, from Windows for Workgroups, run the Sound Card Configuration app from the PAW program group. CD release, from the game installation folder: setup.exe. Digital edition, from the game installation folder: install.exe. Alternatively run the setup option from the PAW Launcher. Sound Blaster Can be selected for music and sound. The default DOSBox config Sound Blaster settings are Ideal. Music/sound should be set in the appropriate PAW app to Sound Blaster 16. Sound Blaster settings: Address: 220h IRQ: 7 DRQ: 1 Roland sound Roland devices can be selected for music only. Settings for all Roland devices: Address: 330h IRQ: N/A (leave at 2 if set) CM32-L The DOSBox configs use the optimum device model: cm32l. This is noted in List of MT-32-compatible computer games. The DOSBox configs should be changed as follows: [midi] mididevice = mt32 Music should be set in the appropriate PAW app to: Roland LAPC-1/CM32-L. MT-32 To use an MT-32, the DOSBox configs should be changed as follows: [mt32] model = mt32_new [midi] mididevice = mt32 The preferred model: mt32_new is noted in List of MT-32-compatible computer games. Music should be set in the appropriate PAW app to: Roland MT-32. Sound Canvas The DOSBox configs specify a suitable Sound Canvas model: sc55. The DOSBox configs should be changed as follows: [midi] mididevice = soundcanvas Music should be set in the appropriate PAW app to Roland RAP-10 or General MIDI via MPU-401. The original audio hardware for PAW was the SC-55, as noted in List of MT-32-compatible computer games. FluidSynth The FluidSynth device is selected for music only. The DOSBox configs specify an example soundfont and soundfont folder, these should be changed to your own preferred soundfont and valid soundfont folder, e.g. [fluidsynth] soundfont = "Shan SGM Pro 14.SF2" soundfont_dir = "D:\Midi\Soundfonts" [midi] mididevice = fluidsynth Music should be set in the appropriate PAW app to General MIDI via MPU-401. Settings: Address: 330h IRQ: N/A (leave at 2 if set) External MIDI devices External MIDI devices are selected for music only. The following commands lists all internal MIDI devices, FluidSynth soundfonts and external MIDI synths in WIn10/11: C:\> mixer /listmidi In the last Win32 section, external MIDI devices are listed with an id and description. This id is used by the midiconfig setting, e.g. Win32: 0 - "CoolSoft MIDIMapper" 1 - "Microsoft GS Wavetable Synth" 2 - "VirtualMIDISynth" The DOSBox configs should be changed as follows, e.g. for VirtualMIDISynth: [midi] mididevice = port midiconfig = 2 Music should be set in the appropriate PAW app to General MIDI via MPU-401. Settings: Address: 330h IRQ: N/A (leave at 2 if set) Running To automatically run the game the following commands can be added to the PAW game DOSBox config, at the end of the [autoexec] section:. Floppy releases with/without the expansion: CD releases: [autoexec] ... cd \mps call 1942.bat exit Digital release: [autoexec] ... 1942.exe exit Gold edition, PAW game config: [autoexec] ... cd \mps\pawgold 1942.exe exit Gold edition, PAW Windows apps config: [autoexec] ... win exit In-game configuration The in-game configuration steps are shown in the gallery below: PAW Launcher This is a batch file menu launcher (pawmenu.bat) that performs a number of functions: Start the game. Run the install/setup app to reconfigure music/sound settings. Run Windows (if installed). View the various release notes. Switch to a different DOSBox MIDI device (MT32, FluidSynth or Sound Canvas). Switch to an external (Port) MIDI device (e.g. VirtualMIDISynth, MIDIMapper). Return to the DOSBox command prompt. Close DOSBox. This launcher should be compatible with floppy releases with/without the expansion, Gold edition, CD compilation editions and digital edition. The launcher relies on the various releases being installed to their default folders. Not all options are valid for all releases, invalid options are not shown in the menu. Switching MIDI devices allows trying out various MIDI options to find a preference. Installing Download the launcher below: In Win10./11, extract the contents to the game installation folder: # In Win10/11: D:\Games\DOS\1942 Pacific Air War\hdd # In DOSBox this becomes: C:\ Change the PAW game DOSBox config as shown: From [autoexec] ... # Non-gold editions cd \mps call 1942.bat exit # Gold edition update v1.5b cd \mps\pawgold 1942.exe exit To [autoexec] ... # Non-gold editions cd \ call pawmenu.bat # Gold edition update v1.5b cd \ call pawmenu.bat Note: When using the Gold edition do not run Windows using the PAW game config. Gold edition Windows app config To use the launcher with the PAW Windows apps DOSBox config used by the Gold edition, change the config as shown (this allows trying MIDI options in WIndows): From [autoexec] ... c: win exit To [autoexec] ... c: call pawmenu.bat Note: Do not run the PAW game using the PAW Windows apps config.. Documents The following documents are available for PAW: Game Player's Guide, pdf download. Old-Games.RU, 1942: The Pacific Air War, files. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Pilot's Handbook, pdf download. Old-Games.RU, 1942: The Pacific Air War, files. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Technical Supplement, pdf download. Old-Games.RU, 1942: The Pacific Air War, files. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Scenario Instruction Manual, pdf download. Old-Games.RU, 1942: The Pacific Air War, files. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Scenario Technical Supplement, pdf download. Old-Games.RU, 1942: The Pacific Air War, files. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Key Reference Card, DOS Days, 1942: The Pacific Air War, Keys, png image. Old-Games.RU, 1942: The Pacific Air War, files, pdf download. replacementdocs, Manual Download, PC (Dos/Windows), page 1. Gold & digital edition The Gold and digital editions use a single manual which combines: Technical Supplement. Game Player's Guide. Pilot's Handbook. Scenario Technical Supplement. Scenario Instruction Manual. Key Reference Card. Gold edition Gold edition manual, pdf download. DOS Days, 1942: The Pacific Air War, Supporting Documents. Internet Archive, 1942: The Pacific Air War Gold Manual. Steam, 1942: The Pacific Air War, View the manual. Digital edition Manual, pdf. Game installation folder. Key Reference Card, pdf. Game installation folder. Example videos 1942: The Pacific Air War training missions Gold edition Finally... Credit and huge thanks go to: DOS Days, Internet Archive and Old-Games.RU for hosting documents and patches. The Patches Scrolls for hosting patches. VOGONS for PAW information on the VOGONS wiki. John Novak and the rest of the DOSBox Staging team for DOSBox Staging and DOSBox Staging wiki. CoolSoft and the developers of VirtualMIDISynth and MIDIMapper. Baron-von-Riedesel for Jemm. David Shan for the Shan SGM Pro 14 soundfont. Good hunting!

VirtualMIDISynth and MIDIMapper are optional MIDI tools that can be used by DOSBox Staging and games supporting MIDI music. However with the latest config changes in DOSBox Staging v0.83.0-RC1 it may be worth taking another look at DOSBox MIDI both built-in and external synths in Win10/11. Further information on obtaining and installing these tools can be found in VirtualMIDISynth and MIDIMapper. They are not required and existing DOSBox facilities can do the job but these tools may prove more convenient. VirtualMIDISynth is a Win10/11 software MIDI synth that supports soundfonts. It does the same job as FluidSynth built into DOSBox Staging (which also supports soundfonts). However, with VirtualMIDISynth the soundfont can be changed 'on-the-fly' as the game is running allowing many soundfonts to be tried and tested. Changing soundfonts with fluidsynth requires shutting down DOSBox changing the soundfont in the config and restarting DOSBox. MIDIMapper is a Win10/11 MIDI synth selector. It can be used to select the default Microsoft Synth, VirtualMIDISynth or another MIDI synth that may be installed in Win10/11 (e.g. a Yamaha synth). This is another optional tool as the DOSBox config and DOSBox commands can be used to send MIDI music to a specific Win10/11 synth. Alternatively DOSBox can sent MIDI music to the MIDIMapper and let it decide the Win10/11 synth that should be used. The following example demonstrates how the same result can be achieved using the different tools: DOSBox is configured to send MIDI music to the built-in FluidSynth. FluidSynth is using soundfont X. DOSBox is configured to send MIDI music to VirtualMIDISynth. VirtualMIDISynth is using soundfont X. DOSBox is configured to send MIDI music to MIDIMapper. MIDIMapper is configured to send MIDI music to VirtualMIDISynth. VirtualMIDISynth is using soundfont X. Example DOSBox config For the purposes of this article we'll assume there is an example DOSBox config with MT32, FluidSynth and Sound Canvas components configured, as shown in this config: [mt32] model = cm32l romdir = "D:\Midi\Versioned" [fluidsynth] soundfont = "Shan SGM Pro 14.SF2" soundfont_dir = "D:\Midi\Soundfonts" [soundcanvas] soundcanvas_model = sc55 soundcanvas_rom_dir = "D:\Midi\soundcanvas\ROMs" [midi] mididevice = mt32 midiconfig = 0 Finding MIDI components We can find a list of MIDI components configured in DOSBox by running the following DOSBox command: C:\> mixer /listmidi From this we get the following pages of results: The mt32 section shows the valid Roland devices available from the Roland ROMs found in the Roland ROM path. The the mt32 section we can see an active CM32L device (in green text). This is the device set in the config file. The soundcanvas section shows the valid Sound Canvas devices available from the Sound Canvas ROMs folder. The fluidsynth section shows all of the soundfonts discovered. The win32 sections shows external (to DOSBox Staging) MIDI devices in Win10/11. Device 0 is the MIDIMapper device, a MIDI synth selector. Device 1 is the default Microsoft GS Wavetable Synth always present in Win10/11. Device 2 is VirtualMIDISynth. Using DOSBox Staging MIDI components The [midi] section of the DOSBox Staging config determines the built-in component that will handle MIDI music. Some examples: [midi] mididevice = mt32 mididevice = fluidsynth mididevice = soundcanvas The midiconfig setting has no effect when using a built-in component. The Roland MT32 option is strictly speaking not a General MIDI (GM) device but a General Standard (GS) device. General Standard is General MIDI but with a lot of propriety Roland extras added. The difference in General MIDI (GM) and General Standard (GS) devices is why there is often a Roland sound (MT32, CM32L or LAPC-1) option and a General MIDI option when installing or configuring games. Each option has its own section in the DOSBox config for configuring the device, e.g, [mt32], [fluidsynth] or [soundcanvas]. Using external MIDI components By external we mean external to DOSBox Staging, so not an internal built-in DOSBox component. The [midi] section of the DOSBox Staging config allows the use of external MIDI components with: [midi] mididevice = port Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi mididevice=port The mixer /listmidi command has provided a list of Win10/11 MIDI devices: Device 0: MIDIMapper. Device 1: Microsoft GS Wavetable Synth Device 2: VirtualMIDISynth We can choose a synth to use directly with the midiconfig setting, the midiconfig setting matching the device to use, e.g. to use VirtualMIDISynth: [midi] mididevice = port midiconfig = 2 Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi midiconfig=2 We don't have to choose a MIDI synth, we can select the MIDIMapper and let it decide which Win10/11 MIDI synth should be used. To use the MIDIMapper: [midi] mididevice = port midiconfig = 0 Or the following DOSBox command can be run from within DOSBox: C:\> config -set midi mididevice=port C:\> config -set midi midiconfig=0 Finally... Credit and thanks go to: The CoolSoft developers of VirtualMIDISynth and MIDIMapper. John Novak and the rest of the DOSBox Staging team. Good hunting!

A guide to running the classic space sim Frontier Elite II (FE2) on modern hardware with DOSBox Staging and natively in Win10. Frontier: Elite II marked a significant departure from the existing Elite universe. The game-like space flight controls are replaced with Newtonian physics. The species making up GalCorp are replaced with a simulation of the galaxy populated by the human only Federation and Empire superpowers. There is no plot to follow, so you have the freedom to become a trader, miner, pirate or a freelance agent for the Federation or Empire, some or all of the above! Note: This article is only covering Frontier: Elite II, the sequel Frontier: First Encounters is not covered. Strategy The DOS version will run in the latest version of the DOSBox Staging emulator (v0.83.0-RC1 at the time of writing). The Windows port of FE2 is glFrontier, it does not require the DOS version to run. Version & patch history Initial UK release (October 1993) The initial UK release was supplied on 1 or 2 x 3.5" Double Density (DD) floppy disks. The first disk containing the game and installer and the optional second disk containing 5 alternate starting scenarios. This was considered a rushed release and the game contains a number of bugs including: Passenger bug. Wormhole bug. Bribe bug. ELITE bug. Mining bug. Imperial ship bug. Cemiess negative price bug. Despite these issues some FE2 veterans still consider this to be the optimum version as it was believed the wormhole bug enhanced the game. This is not a recommended version, as later versions have most of these bugs fixed. Most full priced retail version included a manual, quickstart guide, a gazetteer (a list of notable systems) used in conjunction with the systems map and 'Stories of life on the frontier', a collection of short stories set in the FE2 galaxy. Mining bug patch (October 1993) A patch created by Steve Critchlow that fixed the mining bug that would cause a crash after leaving an unattended MB4 mining machine in a system. This is a file replacement patch, once downloaded the zip archive is extracted into the game folder replacing a single file. This patch is only recommended for the initial UK release. This patch is available from: First Encounters (courtesy of the Wayback Machine). Frontierverse. Internet Archive. CD release (March 1994) The CD release has most bugs fixed, with only the bribe bug remaining. Distributed on a single CD. This version included all the FE2 documentation. This is a recommended version. International release (August 1994) The worldwide release has most bugs fixed, with only the bribe bug remaining. Distributed on 1 or 2 x 3.5" Double Density (DD) floppy disks. This version included all the FE2 documentation. This is a recommended version. Digital release (June 2001) Also known as the shareware release, it was distributed as a zip archive. This was an official distribution via the Elite Club website. This version is fully patched and includes the copy protection codes. This is a recommended version and probably the easiest to obtain. This version does not include complete documentation, however it is complemented with a version of the manual in html format, and a separate copy protection document, available from Elite Club. This version can be obtained from: Elite Club (game, manual and copy protection, courtesy of the Wayback Machine). FrontierAstro. Frontierverse. Life on the Frontier (game, manual and copy protection). Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy 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 staging compatible .ima or .img image format. The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd. Game management It is recommended to use a DOSBox game management strategy or similar strategy you may have developed. The DOS game folder is: D:\Games\DOS\Frontier Elite II The recommended game management folders for the DOS version are: cd - for any cd images. fdd - for any floppy images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents.. The Windows port, glFrontier has an installation folder, and a separate setup folder as shown below. The setup folder is used to store any setup files, e.g. HOTAS config or docs. You may wish to try a similar setup: D:\Games\Win\glFrontier D:\Games\Win\glFrontier setup HOTAS config Only the Joystick is supported by the DOS version. 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 2 axes. When using a physical controller with 4 axes or less, the game should be able to correctly identify the 2 joystick x and y 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 controller is detected by DOSBox. [6][7][8]. The physical axes to Windows axes were configured as follows: Physical axis Stick & throttle Joystick x-axis DX_X_AXIS Joystick y-axis DX_Y_AXIS Note: There is no HOTAS config for glFrontier, discussed below. DOSBox config This is using a configuration compatible with DOSBox Staging v0.83.0-RC1. [cpu] core = simple cpu_cycles = 25000 cycleup = 500 cycledown = 500 [voodoo] voodoo = off [mixer] reverb = small chorus = light [mt32] model = cm32l romdir = "D:\Midi\Versioned" [midi] mididevice = mt32 [joystick] joysticktype = 2axis timed = off swap34 = on deadzone = 0 [dos] xms = off [autoexec] @echo off # mount a "D:\Games\DOS\Frontier Elite II\fdd\*.img" -t floppy mount c "D:\Games\DOS\Frontier Elite II\hdd" # mount d "D:\Games\DOS\Frontier Elite II\cd\frontier.iso" -t cdrom mixer master 100 /noshow c: cd frontier autotype -w 1 y 1 call frontier.bat exit The following zip file contains an example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown above. The cpu is set to simple for increased compatibility. It is suggested by fan sites and an earlier DOSBox guide to set cpu_cycles to at least 20000. To prevent any speed issues this has been increased slightly to 25000 cycles. Voodoo emulation isn't required and is disabled. The mixer and joystick settings are a personal preference and suitable for my joystick hardware (see HOTAS config). The game supports Roland or Adlib/Sound Blaster sound. The default Sound Blaster settings are appropriate. The optimum Roland sound settings use the CM32L device as described in List of MT-32-compatible computer games. The game requires EMS memory and requires XMS memory to be disabled, as described in the DOSBox Staging wiki, Game does not run properly or at all because EMS is not set. EMS is enabled by default. XMS must be disabled in the [dos] section. The autoexec has example mount commands for mounting installation floppy disk images, a hard disk folder and a cd image of the game. As there are multiple installation floppies a wildcard is used to mount all floppy disk images. As the shareware version of the game is used, the autotype commands automates the config menu selection when the game is run. After waiting 1 second, y accepts the shareware agreement and 1 selects Roland CM32L sound (2 could be used to select Adlib/Sound Blaster sound). Installation Retail floppy/CD The retail floppy/CD images should be installed using DOSBox. The first installation floppy and CD has an installer utility to copy files to an appropriate hard disk folder. The install utility is run with: install c Where c is the emulated DOSBox hard disk. The CD install requires an additional language selection during installation. Shareware The shareware version can be downloaded and the contents extracted using Win10/11. The extracted files and folders should then be copied into the DOSBox hard disk folder. Patching Only the initial UK release requires patching, however using an alternative pre-patched release is preferrable. If you wish to use the patch on the initial UK version: Download the patch zip archive and extract the contents, which should be a single file. Copy this into the appropriate FE2 installation folder replacing the existing file. Running & configuration The cd and floppy version is run from DOSBox with the following command: C:\FRONTIER> frontier.exe The digital/shareware version is run from DOSBox with the following batch file: C:\FRONTIER> frontier.bat The digital/shareware version requires confirmation of the shareware licence by selecting Yes. All version require a sound selection, there is a choice of: 1. Roland CM32L sound board. 2. Adlib / SoundBlaster compatible sound board. 3. PC internal speaker. 4. No sound. It is recommended to select 1 or 2, whichever is preferred. Autotype The autotype command in the DOSBox config assumes the shareware/digital version is used and automates the shareware licence confirmation and selection of Roland CM32L sound. Quitting Ctrl-C quits the game. Documentation The following documents are available digitally: Original retail documents Manual, pdf download. Internet Archive, Frontier Elite II Manual. The Gazetteer, pdf download. Internet Archive, Elite II Frontier The Gazetteer PC. Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, The Gazeteer. Quick start card, pdf download. Internet Archive, Frontier Elite II Quick Start Card. Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Misc, FE2 Quick Reference Card (PC). Stories of Life on the Frontier, pdf download Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Stories of Life on the Frontier. Galaxy map, jpg image Life on the Frontier, Frontier Universe Fiction, Frontier: Elite 2, Misc, FE2 Galaxy Map. Digital/shareware documents Manual, zip download. Elite Club, Downloads, FRONTIER: ELITE II - Manual (HTML format). Life on the Frontier, Downloads, FE2 Manual Copy protection codes, txt download. Elite Club, Downloads, FRONTIER: ELITE II - Copy protection codes. Strategy guides & FAQs The Secrets of Frontier Elite, Tony Dillon, pdf/rar download Internet Archive, Frontier Elite 2 Guide PDF. FRONTIER (ELITE II) Game Info, compiled by Christoph Tietz, txt download. Jades (Wayback Machine), Frontier FAQ. Tutorials Frontier Fundamentals, JimPlaysGames, YouTube video tutorial series. Mods Most mods are of the save game variety allowing an advantageous starting position, or cheat based mod, increasing funds or changing game parameters (reducing space requirements of equipment, etc). One notable exception is the control mod, which adds manual control of left/right lateral thrusters and top/bottom thrusters. This allows for manoeuvres including a vertical takeoff from a planet spaceport or circle strafing an enemy during combat. Created by Andrea Villa, this enhancement to FE2 is available from: FrontierVerse, Control mod. Further information The following sites provide additional information on FE2 as well as patches, mods and utilities to enhance gameplay.: FrontierAstro. First Encounters (courtesy of the Wayback Machine). Frontierverse. Life on the Frontier. glFrontier Created by Tom Morton, glFrontier is a highly re-engineered/reverse engineered Windows port of the Atari ST version of the game. It utilizes code from the Hatari emulator and the SDL library, to support OpenGL graphics. As it is based on the Atari ST version there are no textures giving the game a very 'clean' look. glFrontier @ 1920x1080 glFrontier does suffer from significant glitches and issues and it is left to personal preference as to whether glFrontier or the DOS version of FE2 is used. There are currently three glFrontier releases: The original glFrontier by Tim Morton. A later Win32 release, GLFrontier-win32 from Kochise. The GLFrontier-Extended from Brett Wilson that adds Android support and touch screen controls. As glFrontier is reversed engineered from the Atari ST version, the DOS version is not required to run glFrontier. Obtaining The original glFrontier can be obtained from the following sites: GLFrontier Project Page (courtesy of the Wayback Machine). FrontierAstro. SpaceSimCentral (requires registration). The Win32 release, GLFrontier-win32 can be obtained from: The GLFrontier-win32 GitHub repository. GLFrontier-Extended can be obtained from: The GLFrontier-Extended GitHub repository. Running The original glFrontier will often fail to setup the window or screen resolution properly resulting in an immediate crash. The game may need to be restarted multiple times until it is successful and the intro movie begins. GLFrontier-win32 and GLFrontier-Extended seem to employ a more robust setup that fails less often. GLFrontier-win32 seems to have particular problems with saving progress. At present compatibility options don't seem to solve this problem. Command line options The following command line options are supported across all versions: Usage: frontier [options] Where options are: --help or -h Print this help text and exit. --fullscreen or -f Try to use fullscreen mode. --nosound Disable sound (faster!). --size w h Start at specified window size. Note: the usage should state: glfrontier [options] Additional in-game commands These are glFrontier commands only: F11 Toggle fullscreen. Ctrl-E Toggle hardware GL / original software renderers. Ctrl-M Toggle mouse grabbing. F Toggles some debug info & fps readout. Ctrl-Q Quits the game. Joystick issues According to the code in the glFrontier project, there doesn't seem to be any support for joystick or HOTAS devices despite the Joystick control option present in the in-game options menu. Example video Example video showing the digital/shareware version of FE2 with joystick support and the Control mod applied. glFrontier @ 1920 x 1080 Finally... Credit and thanks for the FE2 information goes to: Frontier Developments for the digital/shareware release of FE2 and supporting documents. George Hooper for the First Encounters fan site. Robin Sharrock for the Frontierverse fan site. The creator/maintainer of the FrontierAstro fan site. The creator/maintainer of the 'Life on the Frontier' fan site for info and hosting documents. The Internet Archive for hosting patches, documents and the Wayback Machine. The DOSBox Staging wiki maintainers for FE2 game issues and solutions. Tony Dillon for The Secrets of Frontier Elite. Christoph Tietz for compiling the FE2 FAQ and the Jades fan site for hosting it. JimPlaysGames for the Frontier Fundamentals video series. Andrea Villa for the Control mod. Credit and thanks for the glFrontier information goes to: Tom Morton for glFrontier. Kochise for GLFrontier-win32. Brett Wilson for GLFrontier-Extended. FrontierAstro and SpaceSimCentral for hosting glFrontier. Good hunting/trading/mining/piracy!

A guide to running the Rowen & Spectrum Holobyte developed, 1990 sim, Flight of the Intruder in DOSBox Staging. Based on the book and film of the same name, Flight of the Intruder (FotI) is a sim of the naval carrier aircraft F-4 Phantom II and A-6 Intruder based in the Vietnam theater during the war. In 1990 there was little to choose from graphics-wise between the Amiga and PC, with the introduction of VGA although the Amiga still retains superior sound. As a DOS only sim DOSBox Staging is used. This game was considered the spiritual successor to the original Falcon (from Spectrum Holobyte) before the release of Falcon 3.0. Version & patch history The versions and patches released for FotI are listed below. Initial release The initial release was in July 1990 and distributed on 3 x 5.25" floppy or 3 x 3.5" floppy disks. There is no version listed for the game in the credits but is believed to be version 1.0, given the subsequent version numbering. The first disk is used to install/run with CGA graphics, while the remaining two disks are used to install the EGA/VGA version. Version 1.1 A re-release occurred in August 1990 and was again distributed on 3 x 5.25" or 3 x 3.5" floppy disks. The version is listed at the end of the credits. Like the initial release the first disk is the CGA version while the remaining two disks allow the EGA/CGA version to be installed. There are no release notes accompanying this version. Update disk (version 1.2) An update disk was released in December 1990 on a single 3.5" floppy, which updated the game to version 1.2. The version is listed at the end of the credits. The update was applicable to the EGA and VGA versions. There were no release notes accompanying the update disk. This is a recommended update for versions 1.0 and 1.1. Version 1.2 Releases occurred throughout the 1990's with version 1.2 release on cd-rom in May 1995. The minimum spec also being raised a 386 processor and VGA graphics only. The game is first run from the cd, with the game installed to the hard disk as part of running the game. The game can be played later from the cd-rom or hard disk. The version is listed at the end of the credits and there are no release notes detailing changes or enhancements. Digital release The game was re-released digitally on the gog.com platform in 2024. The digital edition uses version 1.2. Retail media Due to the age or the media and the drives required to read the media, it is recommended to rip floppy 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 staging compatible .ima or .img image format. The cd-rom can be ripped to a data only .iso image format as there is no cd audio on the cd. A digital edition of the game is available on gog.com. Game management It is recommended to use my DOSBox game management strategy or similar strategy you may have developed. The recommended game management folders for the DOS version are: cd - for any cd images. fdd - for any floppy images. hdd - the folder use as the emulated DOSBox hard disk conf - to store DOSBox and HOTAS configuration files. docs - for documents.. HOTAS config Joystick, throttle and rudder pedals are supported. The game supports either a stick and throttle scheme or a stick, throttle and rudder scheme. 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 controller is detected by DOSBox. [6][7][8]. The physical axes to Windows axes were configured as follows: Physical axis Stick & throttle Stick, throttle & rudder Joystick x-axis DX_X_AXIS DX_X_AXIS Joystick y-axis DX_Y_AXIS DX_Y_AXIS Throttle DX_Z_AXIS DX_Z_AXIS Rudder N/A DX_XROT_AXIS DOSBox config The DOS version is configured to run under the latest released DOSBox Staging version, v0.83.0-RC1 (at time of writing). [dosbox] vmem_delay = 500 [cpu] core = simple cycleup = 100 cycledown = 100 [voodoo] voodoo = off [mixer] reverb = small chorus = light [sblaster] sbtype = none oplmode = opl2 [joystick] joysticktype = 4axis timed = false swap34 = true deadzone = 0 [autoexec] @echo off # mount a "D:\Games\DOS\FLight of the Intruder\fdd\disk*.img" -t floppy mount c "D:\Games\DOS\FLight of the Intruder\hdd2" mount d "D:\Games\DOS\FLight of the Intruder\cd\intruder.iso" -t cdrom mixer opl 1000 /noshow mixer master 100 /noshow d: intruder.exe pause exit The following zip file contains an example DOSBox Staging config. It should be changed to match your hardware and personal preferences. Due to the revised defaults with this DOSBox version, most settings are now personal preference or optimal settings, such as sound or joystick settings. Only those settings that differ from the DOSBox Stagiing v0.83.0-RC1 default config are shown. The vmem_delay is set to improve the timing issues within the sim. The credits scroll too quickly without this setting, with it the sim is slowed to a better pace. The cpu is set to simple as it is optimised for, and provides better compatibility with older real mode games. Voodoo emulation isn't required and is disabled. The Sound Blaster settings emulate an AdLib Music Synthesizer Card as described in the DOSBox Staging wiki Sound cards. The mixer and joystick settings are a personal preference and suitable for my joystick hardware. The autoexec has example mount commands for mounting installation floppy disk images, a hard disk folder and a cd image of the game. The Adlib sound is extremely quiet in-game, possibly due to the game expecting the Adlib audio to be played through amplified speakers (according to the FotI manual). In order to hear the Adlib audio, the master volume is restored to 100% and the OPL volume is increased to 1000%. Note: It is recommended to increase this volume in increments from 100% until a suitable OPL volume is found, to prevent a volume that may damage speakers. In this example config the cd version of the game is run. Floppy release The floppy release includes the CGA, EGA and VGA versions of the game. The CGA is run/installed from a single disk. The EGA/VGA versions are installed from the remaining two disks. Installation and patching are dependent on version. Installation The CGA version is installed onto a hard disk by copying the contents of the CGA disk into a suitable hard disk folder. The EGA and VGA versions must be installed from the remaining two floppy using the DOS installer app (install.exe). Patching Only the EGA and VGA versions can be patched to version 1.2. The patch was distributed as a separate floppy update disk. The image of this disk should be mounted in DOSBox and the update utility (update.exe) run from within DOSBox. Running The game is run from the installation folder (the default is intruder) with: C:\INTRUDER> intruder.bat CD release CD menu The CD release uses a unique combined installation and running process. When the game is first run from the cd, it installs on the hard disk, before running the game. When subsequently run from the CD, the hard is checked for the game folder and files and if they exists the game is run. This means the game can be run from the CD or directly from the hard disk folder created by the installation process. To run the game from the cd: D:\> intruder.exe And directly from the hard disk: C:\INTRUDER> intruder.bat Configuration All configuration is performed in-game. THe sound source can be selected from the File menu and the optimum setting is Adlib. The Control menu allows the selection of graphics, sound and control settings as shown below: Documentation Theater map The following documents are available for this sim in pdf format: Manual. Special installation instructions and addendum. Quick reference (keyboard command & cockpit layout). Map. They should be obtained as they are essential to use the sim, which differs significantly from modern aircraft sims. Example Video Finally... Credit and thanks to John Novak and the rest of the DOSBox Staging team. Good hunting!

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 (G-Z), however important changes are repeated below. 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!