On Thu, Aug 31, 2023 at 09:21:40PM +0100, Michael wrote > > Do both machines have alsa built the same way and working?
I don't know. From the looks of it, probably not. > > Does it work without error if you specify it on the CLI? CLI doesn't make a difference. > > SDL_AUDIODRIVER=alsa /usr/bin/dosbox That changes the error message... [waltdnes][~] SDL_AUDIODRIVER=alsa /usr/bin/dosbox DOSBox version 0.74-3 Copyright 2002-2019 DOSBox Team, published under GNU GPL. --- Exit to error: Can't init SDL Audio target 'alsa' not available Later... that very same evening... After some spelunking I noticed that I had libsdl and libsdl2 flagged with "-alsa" in package.use on the non-working machine (don't know why), and "alsa" on the working machine. Changing the flags to "alsa" and updating world with "--changed-use" fixed things on the non-working machine. Thanks for everybody's help. -- I've seen things, you people wouldn't believe; Gopher, Netscape with frames, the first Browser Wars. Searching for pages with AltaVista, pop-up windows self-replicating, trying to uninstall RealPlayer. All those moments, will be lost in time like tears in rain... time to die.
