From Blood Wiki
Jump to: navigation, search

This article is a guide to installing both Blood and Blood II on various systems.


Blood setup utility

Blood was developed to run on computers using MS DOS; on those systems if you have a Blood CD-ROM then you can just put the disc into your drive and run the install program. Afterwards you can configure the game to run properly on your hardware, such as setting up sound and graphical settings, through the game's setup utility. Blood can also work with more modern versions of DOS, the most major being the free software version known as FreeDOS.

Blood can also be ran on some older versions of the modern Microsoft Windows operating system without too much trouble. This can be done with the included MS DOS Prompt. Support for MS DOS applications was maintained through Windows 95, Windows 98, Windows ME, and limitedly in Windows XP. Since most modern versions of Windows have lost nearly all of their old DOS support (most notably in the versions based on NT rather than the old 1.0/95 code bases) the need for third party created DOS compatibility environments such as DOSBox has increased.

This also applies to Windows-like operating systems such as the free software ReactOS. Unix-like systems such as GNU/Linux and macOS have never had any kind of native MS DOS support unlike Windows and as such have always required the use of a DOS compatibility environment such as DOSBox to run Blood. The version of Blood comes with DOSBox configured and ready to install and is recommended for Windows and GNU/Linux users. Some mods such as Bloody Pulp Fiction also try to make using them through DOSBox easier, although this can hinder installing them on different operating systems other than Windows.

Blood remakes or homage games such as Transfusion, Q3 BloodBath, Blood TC, ZBlood, BloodCM and The Flesh Game do run on modern Windows and Unix-like systems. Limited GNU/Linux installation tips, as well as other applicable running notes, for Transfusion can be found here, while advice for loading ZBlood and BloodCM can be found in their articles.

Using DOSBox with Blood[edit]

Blood through DOSBox on Arch Linux with Blackbox

The following explains how to set up your own custom configuration of DOSBox for Blood, assuming you are not using the one supplied by

The simplest and most universal way of launching Blood on GNU/Linux is to load a terminal and then launch DOSBox with the supplied path to your Blood executable. For example, one could type dosbox /path/to/Blood.exe to launch Blood, with the final path listed being changed to the location of the Blood executable on your system as appropriate. One can also make a launcher or shell script to help automate this process.

Custom Configuration[edit]
A custom DOSBox configuration file optimized for use with Blood

For best performance it is recommended that you increase the amount of memory allowed to emulated programs running inside DOSBox as Blood will request more memory than it by default is willing to give. To do this, load up the DOSBox configuration file (found in your "~/.dosbox" directory on GNU/Linux systems) using your preferred text editor and increase the "memsize" value to 64, the maximum that DOSBox will allow. Some other game titles may dislike the raising of this value however, so keep this in mind.

One can also change the "cycles" value to max to ensure that DOSBox takes full advantage of a computer's CPU power, something which can be especially useful on computers with two or more CPU cores. Changing the "core" value to dynamic can also help ensure good performance.

Changing the SDL output setting to the value opengl may help with potential screen corruptions, as well as allow DOSBox to be captured in game recording solutions that involve the capturing of the OpenGL frame-buffer, such as Fraps and SimpleScreenRecorder.

If you do not want these changes to apply globally you can also make a separate DOSBox configuration file by copying your current file and then launching Blood with this distinct configuration file specified, such as by using the dosbox /path/to/blood.exe -conf /path/to/blood.conf command on GNU/Linux, with the final path listed being changed to the location of the alternative configuration file on your system as appropriate.

Deleting the old DOSBox provided configuration file will restore everything back to the defaults unless a custom configuration file is further specified.

Mounting the CD-ROM[edit]

If you have access to the Blood CD-ROM disk you may wish to mount it in order to play CD music tracks and videos. This can be accomplished from inside DOSBox by mounting the D drive as being the CD-ROM mount point. On GNU/Linux systems use the mount d -t cdrom /media/cdrom command, with the final path listed being changed to the mount point of the CD-ROM on your system as appropriate.

If you have ripped your Blood CD-ROM into an Audio CD Cue sheet you can also mount that file within DOSBox with the imgmount d -t iso /path/to/Blood.cue command on GNU/Linux, with the final path listed being changed to the location of the CD-ROM image on your system (without spaces) as appropriate. Windows and macOS users can do the same by supplying their own file paths.

These commands can then be added to the "autoexec" portion of your chosen DOSBox configuration file to have them be entered automatically on start up.

Note: The current stable version of DOSBox, version 0.74, does not loop Blood's CD Audio tracks nor does it support the CD Audio menu volume control. These problems have been fixed upstream in development versions of DOSBox provided through Subversion, but have yet to land in a stable release.

Tricks and Hacks[edit]

A Custom Launcher
Runtime error 200 at 04CE:0091[edit]

If you have a CPU faster than 200 MHz Cryptic Passage may give a runtime error message when you try to play it. This can be solved using TPPatch:

  • Download TPPatch
  • Extract tppatch.exe into your Blood directory
  • From a DOS Prompt type: TPPATCH.EXE CRYPTIC.EXE

Alternatively you can download an already patched executable from DeathMask.

Custom Launchers[edit]

For those using the version of One Unit: Whole Blood on GNU/Linux, the following links provide both a custom command-line game launcher using BASH and a graphical launcher using Zenity. The executable shell scripts must be placed inside the Blood directory.

For Windows systems there also exists a launcher program created by McTecman that also includes a considerable amount of extra fan made content.

Blood II[edit]

The Blood II installer running through WINE

Blood II was developed to run on Microsoft Windows and as such it can be installed and ran quite easily on Windows 9x systems. Simply pop in the Blood II CD-ROM and run the installation, afterwards the game should run. Minor configuration might be necessary, and there has been some issues on later versions of Windows since 2000 and XP. For example, typically to get music to work in XP or above you need to download a separate third party music patch. The version has these issues corrected and is recommended for purchase, shipping with fully working music as well as removing the requirement of having the Blood II CD-ROM in your drive.

Although Blood II is a Windows application, it can be run on Unix-like systems such as GNU/Linux and macOS using WINE. A version of LithTech and thus later Blood II for GNU/Linux and potentially other Unix-like systems was being attempted by Jeremy "Loki" Blackman back in 1998, although it sadly was never released. Blood homage or remake games such as Transfusion, Q3 BloodBath, and The Flesh Game also contain elements from Blood II and can all be ran natively on Unix-like systems.

Using WINE with Blood II[edit]

A custom WINE configuration optimized for use with Blood II
Blood II through WINE on Arch Linux with Blackbox

The simplest and most universal way of launching Blood II is to load a terminal and then launch WINE with the supplied path to your Blood II executable. For example, one could type wine ~/.wine/drive_c/Games/Blood2/Blood2.exe on GNU/Linux to launch Blood II, with the final path listed being changed to the location of the Blood II executable on your system as appropriate. One can also make a launcher or shell script to help automate this process.

Using WINE to run Blood II has never been entirely stable, but a good game experience can be achieved with due effort. The effectiveness of of using WINE to run Blood II has varied from version to version of WINE, as unfortunately the need to provide support for a moving target has caused problems for the WINE developers with regards to providing a stable level of support for certain applications.

In the past it was often better to run Blood II using the limited LithTech software renderer as this can bypass the need for simulating hardware acceleration, but for the best graphics experience it is best to try and use WINE's simulation of Direct3D (sadly OpenGL is not available in Blood II as it is in ported versions of Shogo, which would make this process simpler). Recent versions (as of February 2013 and later) seem to be doing well when it comes to running Blood II through WINE, even to the point of supporting online network play. Ironically, as shown in some screamshots, WINE actually adds a feature not present in the Windows release - the ability to play the game windowed. This is due to the WINE desktop feature.

It is best to set Blood II to be launched using Windows 98 compatibility from the winecfg utility (when using the 32-bit version or a 32-bit prefix) as this ensures that the music will work without the need of any additional third-party patches. Players using the version need not concern themselves with this problem as their version will already be patched, but should still set the compatibility mode setting for best results.

Tricks and Hacks[edit]

Shogo with Blood II models running on GNU/Linux

dgVoodoo 2[edit]

dgVoodoo 2 is a wrapper for old graphics APIs to make them work through Direct3D 11 and provide a better experience on modern systems.

  • Download the latest version of dgVoodoo 2
  • Extract the directory from the archive to any location
  • Run dgVoodooSetup.exe
  • Click the DirectX tab and unselect dgVoodoo Watermark
  • Click Apply and click OK to close the program
  • In a file manager go to the dgVoodoo2 directory and proceed to the MS folder
  • Copy D3DImm.dll and DDraw.dll to your Blood II directory.

You may experience issues with a resolution height of over 1000 pixels. This can be solved by applying this separate fan patch.

Blood II through Shogo[edit]

Content from Blood II can quite easily be imputed into the Shogo: MAD ports to GNU/Linux, MacOS, and AmigaOS systems. While there has been no implementation to run the game proper through Shogo, one can get a taste of Blood II on other platforms this way. There is no known reason why, with due effort, a port for Blood II could not theoretically be built through Shogo, in a similar vein as the Unreal port made using the Unix-like executable for Unreal Tournament or the port of Star Trek: Voyager - Elite Force Holomatch using the ioquake3 source port for Quake III Arena and id Tech 3 in general. A guide to installing the Shogo Unix-like port can be found here.

External Links[edit]