Navy Strike: Staging a strategic strike

Navy Strike, or using the full title, Navy Strike: Task Force Command is a mixture of flight sim and strategy game allowing the command of a carrier task force whilst allowing individual missions to be flown in the F/A-18E Hornet, a navalised F-22 Raptor or the A X which seems to be a fictional navalised F-117A Nighthawk. It was also released as Carrier Strike Force.
The game was developed by Rowan and published by Empire Interactive like many of the Rowan sims and seems to use a similar engine as Air Power: Battle in the Skies, released a little later in 1995, again combining flight sim with an overarching strategy component.
At release it received fair to middling reviews and during the heyday of flight sims, soon disappeared off many potential fans radars.
Contents
Strategy
This guide will cover running the game as well as possible under the latest version of DOSBox Staging (version 0.83.0 at time of writing). This includes sound options, HOTAS controls and the notoriously tricky SVGA DOS drivers included with the game.
Version and patch history
The following is an incomplete version and patch history pieced together from various sources usually without a secondary reference, due to the limited information available. Information in this section may be incorrect or liable to change.
Each release of Navy Strike used the same build with a compiled date of 16/10/95 18:34:24, and the release notes of each release are dated, 17 Oct 95. From this we can conclude the game build remained the same across all releases although some components would be replaced by a patch.

Navy Strike (initial release, October 1995)
The initial release by Rowan, was published by Empire Interactive around October 1995. It was distributed on a single CD-ROM. Although unconfirmed it is believed this release was on a mixed mode CD-ROM featuring game data and CD audio tracks providing dynamic music.
The documentation included the manual, technical supplement and key reference guide. This release is not believed to be available on any of the digital platforms.
Graphics driver update (January 1996)
The one and only believed to be official patch was released around January 1996. It is a file replacement patch for DOS SVGA VESA graphics card drivers. It is believed this patch is only applicable to the initial release. This patch seems to be incompatible with later releases and partially with DOSBox Staging.
This patch is available from:
Internet Archive, Navy Strike Update (new video drivers).
Internet Archive, Score 27 CD-ROM (1996-03).
Old-Games.RU, Games, Navy Strike, Navy Strike - files.
Patch notes
This patch requires some explanation as its use isn't clear due to a lack of release notes.
The Navy Strike installer copies the graphics drivers from the rowan folder on the CD-ROM into an identical rowan folder under the Navy Strike hard disk installation folder (e.g. c:\strike\rowan). These drivers are used by the svgaset.exe utility. The svgaset utility is used by the installer to initially select the DOS SVGA graphics drivers and can be used to reselect drivers later.
The svgatest utility copies the driver files from the rowan folder, creating another copy of graphics drivers in the installation folder (e.g c:\strike). These drivers are used by the svgatest.bat, svgavesa.exe and svgademo.exe utilities to reselect DOS SVGA graphics drivers.
So there are two mechanisms that can be used to select/change DOS SVGA graphics drivers, svgaset and svgatest.
Both utilities scan their chosen folder for s3d and svc files to build driver lists to choose from. The patch replaces some files and adds further s3d and svc files to the installation folder (c:\strike) only. The patch includes new versions of svgatest.bat, svgavesa.exe and svgademo.exe.
Therefore after applying the patch, svgatest is run to reselect new drivers and use them in the game. If the new drivers fail, svgaset can be used to reselect the original drivers from the unmodified rowan folder (c:\strike\rowan).
In DOSBox Staging, svgatest can successfully update the drivers but fails to display the test image, without a small fix for svgademo, while svgaset works normally.

Navy Strike (The White Label budget release, September 1996)
The first budget release was published by Virgin Interactive Entertainment (VIE) on 'The White Label' budget catalogue around September 1996. It was distributed on a single CD-ROM. Unfortunately this seems to have been a data only CD-ROM without the CD music present on the original release.
There seem to have been regional differences in this release with the European release featuring lower quality black and white pdf documents of the manual and separate technical supplement. The US release has a single combined technical supplement and manual but is a higher quality colour pdf document.
It is believed the patch is already integrated into this release given the release date and the svgatest utility makes reference to the VIE helpline when manually selecting a driver, suggesting the utility has been updated for the release.
Navy Strike (The White Label budget re-release, December 1996)
A budget re-release from VIE on The White Label occurred in December 1996. It was distributed on a single data only CD-ROM without CD music. This release has a single combined technical supplement and manual using the higher quality colour pdf document.
It is believed the patch is already integrated into this release given the release date and the svgatest utility continues to make reference to the VIE helpline.

Navy Strike (Steam digital edition, October 2021)
The Steam platform digital edition was released in October 2021 by Strategy First, to a certain degree of controversy. The release seems to be based on one of The White Label budget releases with the CD music missing. In addition it seems to use a sub-optimal DOSBox configuration.
The release uses the lower quality black and white pdf documents for the manual and technical supplement. This edition is available from:
Steam, All Games, Action Games, Navy Strike.
Navy Strike (Zoom digital edition, March 2023)
The Zoom platform digital edition was released in March 2023 by Strategy First. The details of this release aren't known, but given it is released by the same publisher, Strategy First, responsible for the Steam release, it is assumed to be identical to the Steam digital edition. This edition is available from:
Zoom Platform, Navy Strike.
Documents
The manual and technical supplement are included on the CD with The White Label releases. None of the releases include the Key Guide.
Those with the lower quality black and white pdf documents may consider it necessary to obtain the combined colour technical supplement and manual. It makes a stark difference, as shown below:
Black and white pdf Technical Supplement. Colour pdf Technical Supplement.
The combined colour documents are available digitally:
Technical Supplement/Manual (pdf document, download).
Old-Games.RU, Games, Navy Strike, Navy Strike - files.
The separate black and white documents are available digitally:
Manual (pdf document, download).
Steam, All Games, Action Games, Navy Strike, View the manual.
Technical Supplement (pdf document, download).
Steam, All Games, Action Games, Navy Strike, View the quick reference.
Preparation
This section covers tasks prior to configuring DOSBox or installing the game.
Retail media
Due to the age of the media and the drives required to read the media, it is recommended to rip CD-ROM media to image files, to save wear and tear on media and the mechanical drives.
The initial release on a mixed mode CD-ROM featuring CD music should be ripped to a bin/cue image pair to preserve the music tracks.
Later releases can be ripped to a data only iso image format as there is no CD audio on the CD-ROM.
Game management
It is recommended to use a game management strategy or similar strategy you may have adopted. The recommended game management folders are:
cd - for cd images.
hdd - the folder used as the emulated DOSBox hard disk.
conf - to store DOSBox and HOTAS configuration files.
docs - for documents.
patch - to store any patches.
These management folders are placed in the following game folder (as an example), and used in the rest of the guide:
D:\Games\DOS\Navy StrikeDOSBox
This guide assumes the latest version of DOSBox Staging v0.83.0 has been installed, is fully working and has been run at least once to create a default configuration file. It is also assumed only a single copy of DOSBox Staging is installed, with each game using DOSBox having its own configuration file (containing only settings differing from the default configuration file).
Config
This DOSBox config is based on earlier DOSBox configs found for Navy Strike from a variety of sources coupled with the later Air Power: Battle in the Skies config as both games use a very similar engine.
# DOSBox Staging config for Navy Strike: Task Force Command
[sdl]
fullscreen = on
[dosbox]
memsize = 31
[cpu]
cpu_cycles = 62500
cpu_cycles_protected = auto
cycleup = 500
cycledown = 500
[voodoo]
voodoo = off
[mixer]
reverb = small
chorus = light
[mt32]
model = cm32l
romdir = "D:\Midi\Versioned"
[midi]
mididevice = mt32
[joystick]
joysticktype = ch
timed = on
swap34 = on
deadzone = 0
[autoexec]
@echo off
# Example hdd mount
mount c "D:\Games\dos\Navy Strike\hdd"
# Example cd mounts
# mount d "D:\Games\dos\Navy Strike\cd\Navy Strike.cue" -t cdrom
# mount d "D:\Games\dos\Navy Strike\cd\Navy Strike.iso" -t cdrom
c:
# Starting the game
# cd strike
# strike
# exit
# Starting the launcher menu
# call navymenu.batThis config can be found in the following GitHub repository: DarkenedRoom/dosbox-staging-configs/Navy Strike/NavyStrike-staging.conf.
The [dosbox] memsize is increased to 31MB similar to the Air Power config.
In the [cpu] section cpu_cycles and cpu_cycles_protected are changed to 62500 cycles, identical to the Air Power config.
In the [voodoo] section, emulation isn't required and is disabled.
The [mixer] settings are an example and can be changed to a personal preference, however a small reverb and light chorus may be more suited to constant engine noise while in flight.
Navy Strike supports Roland MT-32 type devices. The recommended model, cm32l, is taken from the VOGONS wiki article, List of MT-32-compatible computer games. The [midi] section is configured to use the MT-32 MIDI device.
The [joystick] section has the joysticktype set to ch as the game supports the CH Flightstick Pro. This game also seems to benefit substantially by having timed intervals enabled rather than disabled. The swap34 setting and deadzone are examples appropriate for my controllers and personal preference, you may wish to adjust it.
The [autoexec] section has example hard disk and CD-ROM mount commands. There are examples for running the game from the DOS session or using the navymenu launcher tool.
Tools
A Navy Strike launcher menu (navymenu.bat) has been created to simplify the following tasks:

Running the game.
Running the graphics driver setup with svgaset.
Fixing and running the graphics driver setup with svgatest.
Running the graphics and sound setup.
Viewing the release notes.
Viewing the free memory release notes.
Save file backup and restore.
Reset settings.
Returning to the DOSBox DOS prompt.
Quitting DOSBox.
The Navy Strike launcher menu can be found in the following GitHub repository:
DarkenedRoom/dosbox-staging-configs/Navy Strike/NAVYMENU.BAT.
It should be extracted into the hdd folder. e.g.
D:\Games\DOS\Navy Strike\hdd (in Win10/11 becomes)
C:\ (in DOSBox)Sound
Navy Strike supports Sound Blaster digital sound and Sound Blaster or Roland music. Despite claims of additional support, these are the two DOSBox and Navy Strike supported devices.
Sound Blaster
The default Sound Blaster settings set in the default DOSBox config are appropriate for Sound Blaster digital sound and music, however the following settings may be useful to refer to when configuring the game:
S.B. port No.: Port 220 (default).
S.B. DMA Int.: IRQ 7 (default).
S.B. DMA Chan.: 1 (default).
Configuration is covered in Graphics and sound config with strike.
Roland
Navy Strike supports Roland music The Roland MT-32 model is set to cm32l, as recommended by the List of MT-32-compatible computer games. Configuration is covered in Graphics and sound config with strike.
Controls
The following section covers joystick/HOTAS setup.
HOTAS config
Joystick, throttle and rudder pedals are supported. Configuring axes may not be required if your HOTAS has 4 axes or less. When using a combination of devices totaling more than 4 axes, a virtual controller can be configured (with vendor software or Joystick Gremlin), limited to 4 axes.
For those using controllers from multiple vendors, the vJoy/Joystick Gremlin combination may be required instead of vendor specific HOTAS profile software. You may also have to use HidHide as a device firewall, to hide your real controllers, so only the vJoy virtual controllers are detected by Navy Strike. [6][7][8].
The physical axes to Windows axes were configured as follows:
Physical axis | Windows axis |
Joystick x-axis | DX_X_AXIS |
Joystick y-axis | DX_Y_AXIS |
Throttle | DX_Z_AXIS |
Rudder | DX_XROT_AXIS |
The following DOSBox config settings are suggested, depending on controller hardware:
[joystick]
joysticktype = ch
timed = onNavy Strike supports the CH Flightstick Pro so the ch joysticktype is used. Many may find the default hat buttons unintuitive, as they are used to control afterburner and airbrake rather than views.
The subjective joystick 'feel' seems substantially improved by enabling timed intervals and allows the in-game calibration to work without issue. When timed intervals are disabled the in-game calibration will warn of poor calibration results.
The appropriate in-game joystick is covered by In-game configuration.
Installation
The installation app on the mounted CD/image is run with:
D:\> install.batThe following gallery shows the installation steps:
Select a destination folder, the default is recommended. Selecting graphics options, a complete install is recommended. Copying files. Installation is complete but DOS SVGA drivers need to be chosen.
Once the installation is complete, an SVGA graphics driver must be chosen by clicking on the SVGA Drivers button, rather than OK. For further details on choosing an SVGA driver see Graphics driver config with svgaset.
Config
As mentioned earlier there are two mechanisms for choosing SVGA drivers, svgaset and svgatest. Then there is a separate graphics and sound options configuration utility accessed through the game executable, strike.exe. Finally there are the in-game options, also used to calibrate controllers.
So there are comprehensive and often confusing options to work through to get the game working optimally.
For those curious as to why the ET4000 machine type is not used (as in Air Power). This machine type (svga_et4000) and SVGA graphics driver (ET4000) work, However, a thin transparent horizontal band bisects the HUD screen allowing the background to leak through.
Graphics driver configuration with svgaset
svgaset is used by the installer and can be run at any time after installation from within DOSBox with the command:
C:\STRIKE> svgaset.exeThe following gallery shows the configuration steps, starting from where installation left off:
Click on SVGA Drivers to begin driver selection.
When choosing a SVGA graphics driver manually the following options will work with the DOSBox Staging machine type svga_s3:
AVANCE.
MACH32.
Graphics driver configuration with svgatest
svgatest can be run at any time after installation from within DOSBox with the command:
C:\STRIKE> svgatest.batAfter installation svgatest can successfully set the SVGA driver, but fails to display the test image used by svgademo.exe without a manual fix.
To apply the manual fix:
From DOSBox, copy the notgamed.dir file from the CD-ROM into the Navy Strike installation folder with the command:
C:\> copy d:\ns\root\notgamed.dir c:\strikeThe following gallery shows the configuration steps
When using the svga_s3 machine type the Q) MACH32 or W) AVANCE option should be chosen. SVGA drivers are copied to the appropriate folder. svgademo.exe displays the SVGA title page. Confirmation message.
When choosing a SVGA graphics driver, the following options will work with the DOSBox Staging machine type svga_s3:
Q) MACH32.
W) AVANCE.
Running
When running the game for the first time the configuration file (strike.cfg) is not present causing the graphics and sound configuration to run and create this config file.
Once the config file is present, the following command runs the game, from the Navy Strike installation folder:
C:\STRIKE> strike.exeThe graphics and sound configuration can be run at any time within DOSBox from the Navy Strike installation folder, with the command:
C:\STRIKE> strike.exe ?Graphics and sound configuration with strike
The following gallery shows the configuration steps
Selecting a resolution option, SVGA recommended.
When presented with all the selected options, the Sound Blaster settings should be checked against the Sound Blaster default settings above.
In-game configuration
The following gallery shows the in-game configuration and calibration steps for a 4-axis HOTAS, stick, throttle and pedals using a CH Flightstick Pro joystick type:
In-game configuration options.
To re-calibrate existing controllers, select the Recalibrate option from Control Type. Once calibration is complete the main menu is displayed.
Example video
Finally...
Credit and thanks go to:
The Internet Archive for hosting the Navy Strike patch and Score magazine cover CDs.
Old-Games.RU for hosting the Navy Strike patch and colour documents.
Steam for hosting the Navy Strike black and white documents.
Various VOGONS forum members, Internet Archive uploaders and maintainers of various other sites that provided snippets of information that went into this guide.
Good hunting!



Thanks to you, I managed to get this game running on Windows 11 and 10.👍