top of page

M1 Tank Platoon: Getting the DOSBox hull down


The classic M1 Tank Platoon
The classic M1 Tank Platoon

This is my guide to getting M1 Tank Platoon (M1TP) running under DOSBox Staging. Before beginning it's worth noting that getting M1 Tank Platoon running DOSBox takes quite the effort, there are a lot of mis-steps that are easy to make, it's far too easy to get the patching wrong or miss DOSBox configuration settings and break the installation or fall foul of the copy protection.



Hopefully this guide will help you avoid these pitfalls and get a working installation running under DOSBox Staging.


Importance of versions


Setup options and version number
Setup options and version number

It's vitally important to know which version of M1TP you have as it will determine the patches you need to apply. Unfortunately you may not know this until until you either change some obscure DOSBox options and run it in a vanilla state or apply the Pentium update patch before you run it!


The version is shown on the setup options screen as shown.




There are two versions you're like likely to come across the initial release version v449.01 and a later v449.02. I believe v449.02 includes the Firing patch, Adlib patch and Roland patch. Version 449.02 is the preferred version as it requires less patching.


All the releases encountered so far, have been distributed by floppy disk image. They may be distributed as either 2 x 720k 3.5" disk images or 3 x 360k 5.25" disk images, but there may be others. I actually have the big box game but still use floppy disk images to save wear and tear on the disks.


Game folders


I use my DOSBox game folder scheme described in DOSBox game management. So in my case I have a D:\games\dos\M1 Tank Platoon folder with the following sub folders:


  • conf (DOSBox Staging configuration file).

  • docs (manuals, other docs, etc.)

  • fdd (floppy disk drive, for the floppy images)

  • hdd (hard disk drive, folder used by DOSBox to emulate a C: drive)

  • patches (folder to keep the zipped patches)

  • images (folder to keep the zipped floppy images)


A cd folder isn't required as we won't be using a cd image. As I was testing both versions I used fdd and hdd for v449.01 and fdd2 and hdd2 for v449.02, but you'll only need a single fdd and hdd folder.


Command line options


M1TP supports a number of command line options. The following is taken from the technical supplement:


  • /J Joystick will be used

  • /NJ No Joystick is used

  • /GE Graphics are EGA 16-color

  • /GM Graphics are MCGA or VGA 256-color

  • /GC Graphics are CGA 4-color

  • /GT Graphics are Tandy 1000 16-color

  • /GH Graphics are Hercules monochrome


  • /AI Audio (sound) is IBM (emulated PC speaker)

  • /AT Audio (sound) is Tandy 1000

  • /AA Audio (sound) is AdLib (emulated Soundblaster)

  • /AN Audio (sound) is off (No sounds)


  • /D0 Detail level is low

  • /D1 Detail level is high


  • /O Options are the same as last game (see below)

  • /T Title screens are disabled (see below)


Note, v449.02 has the Roland sound driver, but there is no command line option for it. The v449.01 version has the Roland sound driver added by patch (see Patching versions below).


The /O and /T options are best described by the technical supplement:

Options Repeat (/O): Every time you start the simulation saves a file titled “OPTS” that records your parameters (including joystick information). The /O parameter reads those saved parameters from the OPTS file. The option doesn’t work the first time, or when loading from an original disk.
Title Screens (/T): This option parameter disables the title sequence and music. Initially you must use it with /O; that is, “TANK /O /T”. Thereafter it becomes part of the options repeat (/O) parameter.

If you haven't played for a little while, you may wish to skip 'Options Repeat' if you wish to recalibrate your joystick.


DOSBox Staging setup


The DOSBox Staging video and rendering setup defaults provide a solid set of options that don't need to be tweaked for a really good gaming experience. You may find the 'out of the box' settings never need to be changed.


Running vanilla versions (not recommended)


If you wish to discover the version of M1TP you have, it's recommended to install M1TP then apply the Pentium update patch before running. It's not recommended to use the settings described below. If you are dead-set on the vanilla experience then there are some additional DOSBox settings to be aware of that normally aren't used.


CPU setup


M1TP is one of the few games to require the use of the 386_prefetch CPU type. Failure to select this option for a vanilla install will result in the game hanging. As we have to use the 386_prefetch CPU we must also use the normal core as it is the only core which supports this. Both of these options are in the cpu section of the config.


[dosbox] setup


I have a suspicion that the copy protection employed by M1TP will result in the TANK.COM executable writing data back to itself. DOSBox will detect this and generate a 'Corrupt MCB chain' error before terminating. To avoid this in the dosbox section of the config, the mcb_fault_strategy must be set to allow.


Example config


An example config suitable for running a vanilla M1TP installation has these additional config settings:

[dosbox]
mcb_fault_strategy = allow

[cpu]
core      = normal
cputype   = 386_prefetch

CPU setup


This is my subjective opinion so your experiences may differ. The CPU settings are often overlooked and get left on auto, I know I normally did but I've recently discovered that the CPU settings may affect the gaming experience. In short, I think the simple core may be underused (but optimised) for older games not requiring protected mode, M1TP being one such game.


If you have problems with the simple core, you can always switch back to an auto or normal core.


You may wish to increase CPU cycles and control speed through the battle speed gameplay option (see Running below).


Midi setup


For a discussion on midi setup see DOSBox midi. For DOSBox Staging the versioned MT-32 roms are used. M1TP v449.01 with the Roland patch or v449.02 work well with the CM32L and MT32 new roms, so leaving the MT32 model, (in the mt32 section) as auto will default to CM32L roms.


Controller Setup


For an in-depth look at modern HOTAS controller configuration for retro flight sims, take a look at my series of posts, Controllers and retro sims.


M1TP only uses 2 controller axes, the joystick x-axis and y-axis. No throttle or rudder axis is needed. Those with a HOTAS with an integrated throttle/rudder axes should be fine. I didn't need a TARGET profile to use my joystick, the game calibration found it and it doesn't make much sense to have a throttle or rudder axis for this sim.


My example config


This is my example config with the changes/options most likely to change from the DOSBox Staging default.

[sdl]
fullscreen          = false
fullresolution      = desktop
windowresolution    = default
viewport_resolution = fit

[render]
aspect			= true
glshader			= crt-auto
integer_scaling		= vertical

[cpu]
core		= simple
cputype	= auto
cycles	= fixed 3000
cycleup	= 100
cycledown	= 100

[midi]
mididevice	= mt32

[mt32]
model	= auto
romdir	= "D:\Midi\Versioned"		# your dir may differ

[joystick]
joysticktype	= 4axis
timed		= true
deadzone		= 0					# my preference

[autoexec]

# v449.01
# imgmount a "D:\Games\Dos\M1 Tank Platoon\fdd\disk1.img" "D:\Games\Dos\M1 Tank Platoon\fdd\disk2.img" "D:\Games\Dos\M1 Tank Platoon\fdd\disk3.img" -t floppy -ro
# mount c "D:\Games\Dos\M1 Tank Platoon\hdd"

# v449.02
imgmount a "D:\Games\Dos\M1 Tank Platoon\fdd2\disk1.img" "D:\Games\Dos\M1 Tank Platoon\fdd2\disk2.img" -t floppy -ro
mount c "D:\Games\Dos\M1 Tank Platoon\hdd2"

c:
# call tank.bat
call m1tpmenu.bat

Installation


Installation is straightforward, locate the INSTALL.EXE utility on the first disk and run it. Specify the C: drive and installation will begin. If you are using multiple floppy images, the install utility will ask you to switch disks. In DOSBox Staging <Ctrl> <F4> will switch to the next disk in the imgmount list.


Patching versions


All patches were originally on the MicroProse FTP site, now no longer available on the internet. An archived version of ftp.microprose.com exists at the Internet Archive which is where these patches were sourced from.


Recommended v449.01 patches:

  • Pentium update patch

  • Firing patch

  • Adlib patch

  • Roland patch


Recommended v449.02 patches:

  • Pentium update patch


Pentium update patch (P5UPD.ZIP)


This patch is strongly recommended for both v449.01 and v449.02. It provides compatibility fixes for Pentium class machines. It also seems to remove copy protection from M1TP. Once this patch is installed it should be easier to run in DOSBox.


Firing patch (M1FIRE.ZIP)


This patch is recommended for v449.01 and will break v449.02 by generating a request to supply the key disk. From the MicroProse FTP archive:

This is a Zip File containing a fix for the continuous firing encountered with Version .01 on certain clones. Unzip and copy the file to your TANK Directory.

Adlib patch (486SND.ZIP)


This patch is recommended for v449.01 only. It may work on v449.02 but it will corrupt the Adlib menu option on the setup audio menu. I believe this may already be integrated into v449.02, judging from the file timestamps on v449.02 and the patch contents. From the patch README.TXT:

The AdLib drivers (for AdLib, Sound Blaster, Pro Audio Spectrum, Covox and compatibles) of some of our older games have had problems with newer fast computers, especially 486/66s. This file contains a number of updated sound drivers that should work fine on all fast machines.

Roland patch (MPSROL.ZIP)


Version 449.01 sound menu
Option 1 would enable Roland sound

This patch is recommended for v449.01 and isn't required for v449.02, having the Roland sound driver already built in. From the MicroProse FTP archive:

This file contains Roland MT-32/LAPC-1/CM-32L drivers for the following older MPS games: F19 Stealth Fighter, F15 Strike Eagle II, Red Storm Rising, Knights of the Sky, Lightspeed, M1 Tank Platoon. See the readme file in the zip for installation info.

To install this patch on v449.01 you must replace an existing sound driver, so the RSOUND.TNK file must be renamed to either ASOUND.TNK, ISOUND.TNK, NSOUND.TNK or TSOUND.TNK. My recommendation would be to replace either the ISOUND (IBM PC speaker) or TSOUND (Tandy) driver. You would then select the option replaced by the Roland sound driver in the M1TP setup menu.


'No key disk' patches (M1NOKEY.ZIP and MPSKEY.ZIP)


These patches are not recommended, preference given instead to the Pentium update patch. However if you are dead-set on a vanilla experience or aim to run M1TP on period correct hardware you may wish to use them.


MPSKEY.ZIP contains multiple patches for a variety of MicroProse sims including M1TP while M1NOKEY.ZIP is a patch for M1TP only.


Enhancements


The Desert scenery patch came from an archived version of ftp.microprose.com at the Internet Archive.


Desert scenery (M1DESERT.ZIP)


This patch allows you to choose between Europe and desert scenery. It is compatible with both version v449.01 and v449.02. From the MicroProse FTP archive:

This is a Zip File containing the files required to change the VGA Color Palette of M1 from Europe to Desert. Unzip the files to the TANK Directory and Type "Runme".

This is an optional patch, which is down to personal preference.


Start-up menu


My M1TP menu
m1tpmenu.bat

I've created a start-up menu, very heavily influenced (if not downright copied in places!) by the work damson did for F-19 Stealth Fighter.


It provides options for choosing the Europe/Desert scenery, running M1TP, running with existing options, running with existing options and skipping the intro, backup and restore of the roster.




Usage: Unzip into the TANK installation folder and run M1TPMENU.BAT


M1TPMENU
.zip
Download ZIP • 1KB

Documents


M1TP has an extensive manual and you need this to play effectively. The technical supplement provides a useful summary of options and commands. They are available online but probably require a bit of work to hunt down.


I keep these docs in my D:\games\dos\M1 Tank Platoon\docs folder and then place a shortcut to this docs folder on my desktop when playing. That way if I need to consult any docs, I can pause M1TP, switch from fullscreen to window, open the docs folder shortcut and check out any docs without having to hunt around for them.


Running


Battle Speed


You may wish to experiment with increasing cycles while employing the battle speed option to slow gameplay. However, adjusting cycles while using a joystick will negatively affect the joystick calibration.


The battle speed is best described by the Technical Supplement:

M1 Tank Platoon has five internal speeds, from Level 0 to Level 4. From your standpoint as a player, lower levels accelerate the game, while higher levels slow things down.
When you toggle in and out of accelerated time (“Alt a”) the speed level is displayed. Accelerated time goes to the next lower Level than normal time. However, on 8086 and 8088 machines where Level 0 is “normal” time, accelerated time has no effect (because there’s no Level -1).
You can manually adjust the speed Level using the Insert key. On some machines you may find the simulation runs too fast. If so, use this key to change the speed to the next higher Level, which slows things down.
You can return to the standard Levels by toggling Alt a between normal and accelerated speed, ending up with the normal speed setting once more.

Finally


Hopefully you have setup DOSBox Staging, installed and patched M1TP and it's working. If not check the steps you went through in this guide, it's easy to miss a step or mis-configure something. Remember the patches are very version specific so only use the patches recommended for your version.


Good Hunting!




bottom of page