Linux, Dark Places, and Nehahra- .wav talking files issue

[Nessonic]

I am trying to watch the Seal of Nehahra using this setup. Normally I can get quake to run fine, even mods etc. I use ./quake -nehahra and that loads up. I can play the mod fine, and load up demos. However, once I play the demos (movie) console starts showing up errors that it first cannot find theme13.wav and etc. This I didn't notice until later (other background music still played fine, so I didn't noticce I was missing anything). However, once people's mouths were moving and I was hearing no voices...I checked console, and it had failed to load any .wavs. I go into the SOUND folder and play them, sure enough they're the sound speech files.

Any help here? Dark Places doesn't have a forum, and I don't want to bother Lord Havoc with an email like this. Thanks

[leopold]

I watched the the movie with darkplaces on Ubuntu 10.4 or something. I remember that I had to rename the .dem files though. I think it was uppercase for the demo names and lower for the .dem extension (@work atm, can't check).
Double check your installation, it can be done You may have to rename some files from upper to lower case since Linux is case sensitive while last century's windows was not

[Nessonic]

I just checked, and they're all lowercase

Also, I forgot to mention that those themexx.wav files say they are unable to be found (they're there) yet the talking wav's say unable to load. If that makes any difference.

[leopold]

hmm. I just looked at my install and I had to symlink the SOUND dir to sound:
$ ln -s SOUND sound
That may help to find darkplaces the right sound files, lower or upper case (nehara may be inconsistent).
Look carefully at the error messages. They may give you the hint (like uppercase/lowercase in the complete search path).

[Spirit]

try: strace -e trace=file ./yourdpexecutable

That will tell you what files it is trying to access.

[Nessonic]

Well, Spirit I tried that and came up with a huge list. The only Nehahra files it couldn't find (I think) were modinfo.txts. This is a bit far out of my league, I can think.

Also, I tried throwing that $ line into the command line while loading it. Not even sure if I was doing that right, but it still didn't work.

[leopold]

hehe, no, the $ sign should indicate that you type 'ln -s SOUND sound' from the command line Sorry for that confusion
so, open a terminal, cd to the movie dir and type:
ln -s SOUND sound

GL

[Nessonic]

That worked! Now I'll just have to find the time to watch the whole thing...

Many thanks appreciated, quakeone has always came through