Since you are using 0.72, try disabling GUS in the in config-file. Or update to 0.73. Also, try with some fixed low cycles count, like 2000.

Disabling GUS or setting cycles to 2000 didn't change anything.

Then I rebuilt the Fedora 11 source RPM (dosbox-0.73-1.fc11.src.rpm) on my machine (because the binary RPM did not install due to needed Fedora 11 dependencies). With that, I get the following output on the console when starting dosbox:

1DOSBox version 0.73
2Copyright 2002-2009 DOSBox Team, published under GNU GPL.
3---
4ALSA lib pulse.c:272:(pulse_connect) PulseAudio: Unable to connect: Connection refused
5
6CONFIG:Loading primary settings from config file tomb.conf
7"vga" is not a valid value for variable: machine.
8It might now be reset it to default value: svga_s3
9ALSA:Can't subscribe to MIDI port (65:0) nor (17:0)
10MIDI:Opened device:oss

The last 2 lines were there also with dosbox 0.72, but the PulseAudio error is new. Anyway, still no sound (which sounds logical if dosbox cannot connect to PulseAudio).

You're using an old dosbox config file, and (independent of that) pulseaudio fails.

Yes, I just found out that pulseaudio was not running anymore due to my experiments to get the sound working...

Logging out/in fixed that problem.

Will try with a new config file now...

Made a new config file using "CONFIG -writeconf dosbox.conf" and started from that to make my tomb.conf configuration file. I verified that I still have sound in Rama, but for Tomb Raider the result is the same: no sound. Output on console:

1DOSBox version 0.73
2Copyright 2002-2009 DOSBox Team, published under GNU GPL.
3---
4CONFIG:Loading primary settings from config file tomb.conf
5ALSA:Can't subscribe to MIDI port (65:0) nor (17:0)
6MIDI:Opened device:oss

get pmidi
type
pmidi -l
you will get a a few midi ports
add the right one to the midiconfig= line in dosbox.conf

OK, did that:

1$ pmidi -l
2 Port     Client name                       Port name
3 14:0     Midi Through                      Midi Through Port-0

Gives output at start:

1DOSBox version 0.73
2Copyright 2002-2009 DOSBox Team, published under GNU GPL.
3---
4CONFIG:Loading primary settings from config file tomb.conf
5ALSA:Client initialised [14:0]
6MIDI:Opened device:alsa

But still no sound (I kind of expected that, because I got the same midi errors in Rama, where I do have sound).

tomb raider doesn't support MIDI. It has cd audio music.

robertmo wrote:

tomb raider doesn't support MIDI. It has cd audio music.

CD audio? That means verthezp should make a BIN/CUE-image combo and use IMGMOUNT, right?

But I suppose the in-game sounds, like shooting a revolver, have nothing to do with cd audio, but still I don't get them. Probably the videos in between parts of the game would use cd audio, but I'm not even really interested in that.

I have also used imgmount by the way (next to running directly from cd), but just an iso image of the data part of the cd.

Apparently I found the problem.

On an old Windows system, I still had Tomb Raider installed, and there I saw that the installer had copied the TOMB.EXE executable to C:\TOMBRAID along with some other files. On the dosbox in Linux however, C:\TOMBRAID only contained the saved configuration file HMISET.CFG (with the sound configuration that I did manually) after I ran the INSTALL.EXE. I always ran the TOMB.EXE executable from the cd or the mounted isoimage in dosbox.

Once I copied over the proper files, and ran TOMB.EXE from C:\TOMBRAID, sound was there.

I'm not sure why the installer did not install those files properly, but anyway, it works now.

Hm could you please try to reproduce the problem, like doing the exact
installation steps for an empty mounted c-drive and see if it works under
windows but doesn't work under linux?

OK, I understand what happened now...

I had a long time ago already played Tomb Raider under dosbox. But for some reason I had removed the TOMBRAID directory in the mean time, but not the TOMBPATH.TXT file in the C: drive, which contains the path "C:\TOMBRAID". When the install program sees that file, it assumes everything is already installed, and only the sound configuration is retried (and doesn't really work at that time apparently).

On an empty C drive, that doesn't have that TOMBRAID.TXT file, everything works correctly: sound auto-detection works and everything is installed correctly.

Thanks for all the help!

Thanks for reporting back!