Skip to main content

Doom for Modern Linux

DOOM was released in 1993 and is considered a pioneer in 3D gaming. Previous games from id Software were 2D.

While the original game might be playable in DosBox, There are more modern ports with greater stability and wide platform support. One of the ports, prboom, is available for Mageia6 (and MS-Windows and many other platforms). Based on the release of the original source code; it uses the SDl library.

prboom is one of those rare Linux things that has been fixed enough that everything works. It offers a true-to-the-original gameplay rather than updating the game with modern features like ZDoom, EDGE, and Eternity Engine. prboom emulates the games engines from the different versions of DOOM; it is also compatible with the demo version of DOOM.

$ sudo urpmi prboom 

installs the game in  /usr/games and run the first time with no arguments creates .prboom in your home directory, which is where you will place your *.wad files (referred to as IWADs.

Mageia6 also provides the man freedoom wads in the freedoom package and installs them at

/usr/share/games/doom/freedoom1.wad
/usr/share/games/doom/freedoom2.wad

To install the freedoom IWADS,

$ sudo urpmi freedoom

The freedoom Docs are worth a read and can be found in /usr/share/doc/freedoom/README.html 

So, in answer to the classic meme "Can it run Doom?", launch the first game:

$ prboom -iwad /usr/share/games/doom/freedoom1.wad

Yes, this was considered groundbreaking in 1993, but you can see who far 3D gaming has progressed in 24 years.

The ArchLinux Wiki has excellent instructions on how to configure and launch prboom.

Graphical Frontend for DOOM

Mageia does not provide a graphical frontend for launching Doom games. There is one available from enyo-doom, Doomseeker, Super Shotgun Launcher, qzdl, and DoomLauncher.

I chose to use DoomLauncher (download) . As a java jar, it should work cross-platform. Placing it in ~/bin/, I wrote a script simply named doom to launch it (and don't forget to chmod +x.)
#!/bin/sh# launch DoomLauncherjava -jar ~/bin/DoomLauncher.jar
Once running, initial configuration is not obvious at first.


Begin by clicking on Engine: ...  and select the path to prboom. You can install multiple different game engines if you desire.

Next, click on Iwad: ... and select the path to your IWADs.

Once you have selected your game engine and your IWAD, click on Launch to start the game.

NOTE: The GUI does not do well upon your exit from the game. You need to close it and start it again. Otherwise, it appears to work well.

RESOURCES

ArchLinux Wiki

Zandronum Wiki

Playing SDL_mixer games with soundfonts

PrBoom+

 Troubleshooting JAR File Associations for DoomLauncher

Doomworld Wiki




Comments

Popular posts from this blog

DOS4GW.EXE Version 2.01a and Alternative DOS Extenders

DOS4GW.EXE
The TenberryDOS extender DOS4GW.EXE was used by many early DOS games. I still enjoy playing many of these games and DOS4GW.EXE is usable with DOSBox, so they can be played on Linux.

However, the version of DOS4GW.EXE that was included with the game was whatever was current at the time. The most recent version that includes many bugfixes that possibly affected the games when used with DOSBox have been fixed in the latest version, 2.01a.

It's not free at US$49, but you can downloaded it here. Simply substitute it for whatever version of DOS4GW.EXE your game provided and enjoy the bug-fixed goodness. Tenberry also makes a "high-performance" "pro" version of DOS4GW.EXE, but it costs $300. I think that they could sell quite a few of these to hobby users (since, you know, DOS is dead) for US$5.

Open Souce to the Rescue
There are better performing, free and Open Source alternatives available and worth a look.

DPMI Explained
But first, let's understand w…

Fixing a Buggy ACPI BIOS Updated for Windows 8 and Linux Kernel 3.x

In the BIOS, there is a table that configures/determines a number of hardware values for ACPI and your system to use.

One of the features of ACPI is that the values and methods used can be differentiated at boot time depending on what OS you run. Each version of MS Windows has a unique identifier and while Linux can identify as "Linux", the Linux ACPI gurus have decided that Linux will always identify itself as "Windows NT". Even if you force Linux to identify itself as Linux, the Linux ACPI code still lies to the BIOS, except for the computers specifically listed in drivers/acpi/blacklist.

If you are running very new hardware intended for Windows Vista or Windows 8, you might get better performance on ACPI-related issues if you identify, or "spoof", your Linux OS as Vista or Windows 8. This is done by adding the boot-time kernel parameter of acpi_osi="Windows 2006" or "Windows 2012" respectively (and the quotes are necessary). still,…

Mageia

The first release of Mageia 1 is out. You can download it from here and read the release notes here.

If you've used Mandriva Linux, you'll feel right at home with Mageia. Mandriva has always had a reputation of working well for both the novice user and the power user. Installation is typically easy and hardware support is among the best of any distro. The user and administrative tools are comprehensive and easy to use. Of course, under the hood, it's all Linux and all configuration files are plain text files and all a competent administrator needs do is to choose a shell and a text editor.

Mandriva has also been known for excellent default fully-featured configurations of the KDE, GNOME, XFCE and LXDE desktop environments as well as a broad range of available applications. Mageia is no exception in this regard.

For the average user, the changes are mostly cosmetic. The Mageia art, colors and graphics are very well done (and contributed by the Mageia user community). But …