Back to the Vavoom Forum Archives


Forum

Vavoom-1.24 installation will not run [solved]

Thu, 27 Sep 2007 20:06:21

skyhawk

I tried installing Vavoom-1.24 from source code for the first time 27 September 2007 without success, or more accurately, I tried running Vavoom-1.24 after the installation without success. The program did not run at all. For configuration parameters, I used <./configure --with-SDL --without-openal>. The configuration and installation moved along without any error messages, so <make install> was followed with <make clean>. I want to use the original DOOM demo wad (DOOM1.WAD) to test the installation, which as I recall from my reading is permissible, so I copied it to my /usr/local/share/vavoom folder, containing the following files: [me@mycomputer vavoom]$ ls -l total 4117 drwxr-xr-x 11 root root 1024 Sep 27 11:34 basev/ -rw-r--r-- 1 root root 4196020 Sep 27 11:44 DOOM1.WAD -rw-r--r-- 1 root root 377 Sep 27 11:34 vavoom.png In my /usr/local/bin folder, I have the following files: [me@mycomputer bin]$ ls -l total 18983 -rwxr-xr-x 1 root root 7294509 Sep 26 13:56 dosbox* -rwxr-xr-x 1 root root 177 Sep 27 11:34 vavoom* -rwxr-xr-x 1 root root 187 Sep 27 11:34 vavoom-dedicated* -rwxr-xr-x 1 root root 4335059 Sep 27 11:34 vavoom-dedicated.i686* -rwxr-xr-x 1 root root 7725819 Sep 27 11:34 vavoom.i686* Running <vavoom> at the CLI, gives the following output: Adding ./basev/common/basepak.pk3 Doing C_Shutdown Doing CL_Shutdown Doing SV_Shutdown Doing V_Shutdown Doing T_Shutdown Doing Sys_Shutdown Doing R_ShutdownTexture Doing VCommand::Shutdown Doing VCvar::Shutdown Doing ShutdownMapInfo Doing FL_Shutdown Doing W_Shutdown Doing GLanguage.FreeData Doing VObject::StaticExit Doing VName::StaticExit Doing Z_Shutdown Game mode indeterminate. Running <vavoom.i686> at the CLI, gives slightly different results: Doing C_Shutdown Doing CL_Shutdown Doing SV_Shutdown Doing V_Shutdown Doing T_Shutdown Doing Sys_Shutdown Doing delete GSoundManager Doing R_ShutdownTexture Doing VCommand::Shutdown Doing VCvar::Shutdown Doing ShutdownMapInfo Doing FL_Shutdown Doing W_Shutdown Doing GLanguage.FreeData Doing VObject::StaticExit Doing VName::StaticExit Doing Z_Shutdown W_GetNumForName: pnames not found! The files /usr/local/share/vavoom-dedicated* and /usr/local/share/vavoom-dedicated.i686* each read as follows: #!/bin/sh # Needed to make symlinks/shortcuts work. # the binaries must run with correct working directory cd "/usr/local/share/vavoom" "/usr/local/bin/vavoom.i686" $* exit $? One day prior to my Vavoom-1.24 installation, I did a successful install of DosBox-0.72 from source code. DosBox-0.72 also needs the SDL development libraries, so I am very confident that they are not the cause of any problems. I am running Mandriva 2007.0, kernel 2.6.17-5mdv, on a Compaq Deskpro EN, P3, 933MHz. My Nvidia TNT2 Pro AGP card is set-up to use the OpenGL driver (2D-accelerated mode) provided with my Mandriva distribution. Any advice on what went wrong would be greatly appreciated. I am out of ideas on this one.
Thu, 27 Sep 2007 20:39:23

scen

Why do you mention "Dosbox"? Are you trying to make Vavoom work on Linux, right? So this package isn't needed at all. You must pass the --with-iwaddir=/some/path to configure script, where /some/path is where your WADS are located (they moust be READABLE by the user that launch Vavoom). Finally, you have to launch Vavoom through its "wrapper script", called vavoom (not directly the vavoom executables).
Fri, 28 Sep 2007 05:10:08

spiderman

All my wads are named in all lower case, maybe the upper case wad filename is messing you up? Try renaming it doom1.wad
Fri, 28 Sep 2007 12:58:37

skyhawk

[quote="spiderman":4a2nrb6l]All my wads are named in all lower case, maybe the upper case wad filename is messing you up? Try renaming it doom1.wad Thanks for the reply. Your advice came very close to being absolutely right on-the-money. After a little more thought (about two hours after trying to run the program), I determined that the filename DOOM1.WAD could be the cause of my problem. Sure enough ... I renamed the file to doom.wad and I was back in business. Vavoom-1.24 is now up-and-running. No other changes were necessary. I can now send for my "DOOM Collector's Edition" disc set, and get back everything that I once had on many, many diskettes. Vavoom-1.24 is definitely a beautiful piece of programming work. By the way, for those who are wondering, I installed DosBox to handle MS-DOS programs that cannot be handled by Vavoom-1.24. DosBox also might be useful to extract files from self-executing MS-DOS archives (Mandriva 2007.0 is my only operating system) . For DOOM, Heretic, Hexen, etc. Vavoom-1.24 is my game engine of choice.
Sat, 29 Sep 2007 00:31:32

spiderman

[quote="skyhawk":zevujtbx]Your advice came very close to being absolutely right on-the-money. doom.wad may work, but doom1.wad should probably be used for the shareware episode. doom.wad should be used for the registered wad, and doomu.wad for ultimate doom. [quote="skyhawk":zevujtbx] DosBox also might be useful to extract files from self-executing MS-DOS archives Those self extracting dos archives are almost always pkzipped, and can be opened with anything that can open normal zips, such as linux "unzip" command or gnome's file-roller. However I agree that DosBox is a very good DOS emulator in general, and excellent for old games. Those of you who haven't seen it might be interested in this massive game compatibility list

Back to the Vavoom Forum Archives