qeX][lenny-, it seems you misunderstood me there. At least that's what I read from your post in which you replied to me.
Let me explain further. There are actually two seperate programs you need.
The first one is the actual daemon which is listening to incoming connections. This one is artsd
. You only need to start it once as a background program, it will then continue running.
But there is another program which is called artsdsp
(careful about the spelling). This is a program which will run another program as a child process (like xmms or your game), intercept the child process' audio output and reroute it to the artsd which is running in the background. artsd will then remix the audio data it gets from artsdsp and send it to the audio card.
Another way to look at artsdsp is that it makes a program (like xmms, game) think that it is accessing the audio card when actually the audio data goes to artsd first. This way you should - in theory - be able to use any program with artsd that wants to access /dev/dsp.
So instead of the normal (direct) path
Program -> Audio card
the audio data will take another way to the audio card which looks like this:
Program -> artsdsp -> artsd -> Audio Card.
The clue is that once artsd is running you can run multiple programs via artsdsp, all whose audio data will be sent to the artsd daemon. The daemon will mix all those sound streams into one before sending it to the sound card. This way you are able to have multiple programs have access to your sound card.
Again, in my example I would execute the following three command lines to listen to music while playing ET:
/opt/kde/bin/artsdsp xmms &
(The & at the end of the line sends the program straight to background in case you didn't know)
I hope I made it more clear and understandable this time. It took me some time as well to understand how exactly this system works.