A guide to setting up and playing Privateer 2: The Darkening, the sequel (in name if not setting) to Wing Commander: Privateer. This guide covers installation, patching and first run in DOSBox Staging, followed by running natively in Windows 10.
This guide will cover the installation and patching of the original DOS version of the game in DOSBox. Then we'll take this DOSBox installation folder, install additional components and patches to turn it into a modern Windows 10 compatible version of Privateer 2.
Versions & patches
A list of the various commercial releases of Privateer 2 and the patches used to update them. Each release will be covered but not each patch, as many of the later patches have been superseded by the latest enhancement pack.
The only patches that will be recommended are:
Latest official patch v17.0e.
Midi driver fix.
Privateer 2 Enhancement Patch.
For impressive amounts of information on Privateer 2, including a number of additional patches that aren't strictly required, but may be useful for some, check out the Privateer 2 pages of the Wing Commander Combat Information Centre (CIC).
Privateer 2: The Darkening (DOS)
The original base game, developed by EA Manchester and published by Electronic Arts in 1996 for DOS, distributed on 3 cds. This release is v16.0 (named Commercial).
Latest official patch v17.0e
The latest official patch which upgraded the version to v17.0e (named Buffalo Wings). The patch provided a number of bug fixes and a few enhancements (an invulnerability option, native support for some joysticks of the day, some additional key commands, etc.). It was released around Jan 1997.
This is a recommended patch for any DOS version not already at v17.0e. It can be found at the Wing Commander CIC, Privateer 2 Patch page.
Midi driver fix
This is a file replacement fix of the midi driver file, MPU401.MDI. The driver file is padded with zeros to increase the file size, from 2kb to 17kb, making it the same size as other midi driver files on the cd. This increases compatibility with DOSBox Staging and reduces crashes in movies.
This fix was developed by VOGONS member ripsaw8080 to help prevent general midi crashes in another game, in this post. The same method was employed by VOGONS member kingjoma_za to reduce general midi crashes in Privateer 2 in this post. Big thank you to both for finding and developing this fix.
This is a recommended patch for any DOS version with a small 2kb MPU401.MDI file. This file replacement fix can be found in this VOGONS post.
Privateer 2: The Darkening Deluxe (DOS Edition)
This was a compilation of the complete Wing Commander: Privateer and Privateer 2: The Darkening (DOS). Released by Electronics Arts in 1996.
It's not known if this version is already patched to v17.0e, but it would probably benefit from the the midi driver fix.
Privateer 2: The Darkening Deluxe (Windows 95 Edition)
A re-release of Privateer 2 as a native Windows 95 game by Electronic Arts in 1997. The release included some limited edition goodies. This version is already patched to v17.0e, but it may benefit from the midi driver fix, if MPU401.MDI is still used in this release.
Privateer 2: The Darkening (GOG Edition)
The GOG re-release of a v17.0e patched DOS version of Privateer 2 running under DOSBox emulation. Released in 2013 by GOG, this release includes, manuals, key references, the strategy guide and other goodies. This is probably the most common version today, due to ease of availability.
This may benefit from the midi driver fix, if it still uses a small 2kb MPU401.MDI file.
Privateer 2 Enhancement Patch
Developed by HCl the Privateer 2 Enhancement Patch is the only patch needed by Windows 95 and GOG Editions to allow Privateer 2 to be played natively under Windows 10 (and is compatible with DOS editions). The patch features a new executable and setup options, DirectX graphics and sound wrapper. A huge thank you to HCl for some excellent work.
The patch can be found at the Wing Commander CIC. The patch is now into its third released version, p2_patch_test3.zip.
Strategy
I'll be using an original retail version converted into cd images. The installation strategy will be a fresh install from cd, of Privateer 2 in DOSBox Staging. The install will then be patched with latest official patch and midi driver fix.
The game is then started and played until spaceflight. This ensures the HOTAS controller is configured and calibrated and the in-flight options work. Without this DOSBox install and initial spaceflight the in-flight options page is never accessible in Windows 10 and the game fails and crashes out with an error.
For those with the Windows 95 or GOG editions, it may be sufficient to run the game once to ensure any required config files are created.
The Privateer 2 installation folder is copied to an appropriate location, the contents of the cds applied and finally the Privateer 2 Enhancement Patch is applied. The game is then available to play natively under Windows 10.
HOTAS Config
If your HOTAS controller(s) use 4 axes or less, then this won't apply. If you have more than 4 axes then you'll need to use profiling software to create a virtual controller limited to 4 axes. A 4 axes joystick/controller is one DOSBox is able to use. I also found that the version of Privateer 2 that runs natively in Windows 10, also prefers a 4 axes controller, so the HOTAS config was used for both DOSBox and Privateer 2 natively in Windows 10.
The 4 axes controller mapping will depend on your particular setup, but for reference this is one I created in TM TARGET profiling software:
Physical Axis | Windows Axis |
Joystick x-axis | DX_X_AXIS |
Joystick y-axis | DX_Y_AXIS |
Throttle | DX_Z_AXIS |
Rudder pedals | DX_XROT_AXIS |
Privateer 2 only uses the joystick and throttle axes.
DOSBox Staging
The purpose of using DOSBox is to create a Privateer 2 DOS install and then run the game to ensure any and all required config files are created. The DOSBox settings aren't required to be optimal just usable.
DOSBox Staging config
This DOSBox Staging config, just shows the differences from the default DOSBox Staging config and any settings of particular interest.
[dosbox]
memsize = 64
[cpu]
cycles = auto
cycleup = 1000
cycledown = 1000
[midi]
mididevice = fluidsynth
[fluidsynth]
soundfont = "D:\Midi\Soundfonts\FluidR3_GM_GS.sf2"
[joystick]
joysticktype = 4axis
timed = true
swap34 = true
deadzone = 0
mount c "D:\Games\Dos\Privateer 2\hdd"
imgmount d "D:\Games\Dos\Privateer 2\cd\*.iso" -t cdrom
c:The memsize setting needs to be increased from the default 16 for Privateer 2 to run.
The CPU setting is left as auto, although cycleup/down will allow it to change in sensible increments if needed.
We want a midi device so general midi can be chosen as the music option.
Fluidsynth is configured with a soundfont.
The joystick settings are suitable for my particular HOTAS config, you may need to tweak them for your setup.
I'm using my DOSBox game management strategy, so there is a 'D:\Games\Dos\Privateer 2' folder which holds everything related to the game, with the 'hdd' subfolder acting as the DOSBox emulated C: drive.
All the cd images are kept in the 'cd' subfolder, they are all mounted with the imgmount command and the *.iso wildcard for convenience.
Installing & configuring Privateer 2 in DOSBox
Use the DOS installer and config app, install.exe on cd 1 of the 3 cds (or cd images).
The options should be set as shown. The sound card and music card can be autodetected and tested during the install process.
The default directory isn't changed.
Control is switched to Joystick/Throttle, although Joystick may be a more appropriate option, depending on your setup.
Once selected the game should install in DOSBox without issue.
Once installation has complete successfully, the latest official patch should be downloaded and extracted to the Privateer 2 installation folder. The patch should then be run from within DOSBox to patch the game to v17.0e.
Once the patch is installed, the midi driver fix should be downloaded and extracted to the Privateer 2 installation folder replacing the existing MPU401.MDI file.
That concludes the installation and patching of the DOS edition of Privateer 2.
Running in DOSBox
The DOS edition of game is run once in DOSBox to ensure all the required config files are created. Once the game has started playing intro movies:
Hit Esc to skip past all the intro movies, there are about 15 mins worth.
Once you reach a choice, select either choice.
Continue skipping past movies, leave the bar and head to Customs.
Use the booth system to buy a ship.
Leave Hermes, the first time in spaceflight you may be required to calibrate the joystick/throttle.
Once calibrated and the joystick/throttle is working as expected, quit the game.
Other editions of the game should be run once to ensure appropriate config files are created.
Windows 10
Here are the steps to create and run a native Windows 10 compatible version of Privateer 2. It will applicable to any of the DOS, Windows 95 or GOG editions.
Installing
Everything is done in Windows 10, DOSBox is no longer needed going forward.
The first step is to take the existing Privateer 2 installation folder and copy it to a shorter path without spaces/non-standard characters. The game can be a bit temperamental with longer folder paths. So in my case we copy the 'D:\Games\Dos\Privateer 2\hdd\DARK' folder to the D:\ drive creating a 'D:\DARK' folder.
Mount each cd (or cd image) and copy all the contents of each cd into the installation folder, in my case I'd be copying into the 'D:\DARK' folder. Existing files from earlier cds can be overwritten and replaced with files from later cds. Once the contents of all 3 cds have been copied, this step is complete.
Patching
Download and extract the Privateer 2 Enhancement Patch into the Privateer 2 installation folder. In my case this was 'D:\DARK'. That's all that is required, the patch is installed!
Configuring
The Privateer 2 Enhancement Patch assumes the Privateer 2 installation folder exists on the C: drive. Since my folder exists on D: drive, a text editor can be used to change the first two settings in the DARK.FIX file from:
C:.
C:.to:
D:.
D:.The darkfix_setup.exe patch config utility should be run to make any changes necessary, then save and exit.
Running
To run the game, the new executable provided by the patch, DARKFIX.EXE should be used instead of the previous game executable.
Good hunting!
Comentarios