-   Linux - Software (
-   -   Doomsday/jDoom (

Makaelin 08-27-2004 05:31 PM

I'm using Slackware 10.0, and Doomsday ( seems to have compiled fine. However, I've had no luck getting it to run whatsoever. Anyone out there that has gotten it running well mind giving a quick step list of how they went about it?

XavierP 08-27-2004 05:48 PM

These are the docs provided by the site itself. You don't tell us what's not working, what errors you get or what you have done to install it.

Makaelin 08-27-2004 05:53 PM

I've read the documentation. I've compiled it and attempted to run it via the instructions in the README, but it gives me a message in the terminal that says INIT ABORTED. I'll post the complete message below.

I did a search here and there wasn't really any posts about running the game, only compiling it. All I was curious about is if someone that is actively running it would mind giving the steps they used after compiling to do so, as Doomsday's documentation for Linux is extremely lacking.

Sorry, I should've made my post more clear as to what I was getting at. This isn't a desperate plea for help on fixing my install (I've got other Doom ports, of course), just a curiousity of how it has worked for others after compiling.

The README is the only document I've found that talks about actually running the program. That section is as follows:



These instructions apply to the Linux version of Doomsday.

The default location for the doomsday executable is /usr/local/bin,
but that can be changed by providing your own prefix for the configure
script (see Build/COMPILING).

I recommend creating your own startup scripts for jDoom, jHeretic and
jHexen. In them, you can specify any command line options you wish to
use. Below is a simple example.

/usr/local/bin/doomsday -game jdoom -file ~/wads/doom.wad \
-userdir ~/doomsday/jdoom

Before running this script you will need to create the runtime
directory ~/doomsday/jdoom. All savegame files, message logs and
other such files will be stored in this directory.
Their example didn't work for me, and produced the following:


LoadPlugin: /usr/local/lib/libdpdehread
LoadPlugin: /usr/local/lib/libdpmapload
Con_Init: Initializing the console.
SW_Init: Startup message window opened.
Executable: Version 1.8.1 Aug 27 2004 (DGL).
Memory zone: 32.0 Mb.
Parsing configuration files.
W_Init: Init WADfiles.
--- No IWAD has been specified! Important data might be missing. Are you sure you want to continue?
**ERROR** Executable: Version 1.8.1 Aug 27 2004 (DGL).
Memory zone: 32.0 Mb.
Parsing configuration files.
W_Init: Init WADfiles.

W_CheckIWAD: Init aborted.
The designer mentions that the "No IWAD has been specified!" message is to be expected in one of his posts on their website.

All times are GMT -5. The time now is 04:32 AM.