nowbotfaq

1. Linux Dosbox
2. Dosbox Download

Please post all questions concerning DOSBox ECE in this thread for now on, so we can keep other threads tidy and on topic!I compiled a build of DOSBox ECE for Linux. Consider it highly experimental, since I only run Linux in a VM, I can't test all the features, because the VM is lacking hardware acceleration. So it would be very nice if someone could run some tests with it. It comes (or should come) with all the features of the Windows build, minus the possibility to select the midi device by name or a part of it. Please download it (link is in my signature), play with it and let me know if something's not working or missing!

Such a frontend would be toolchain- and platform-specific, especially since DOSBox, unlike the 'MAME World', mercifully does not use its own toolchain that is annoyingly redone every couple of months. Most DOSBox patch authors, including myself, provide a compiled Win32 executable of the latest SVN with that particular patch applied, so compilation is not required when just using one particular patch, at least on the Win32 platform.

And when it comes to applying multiple patches, the potential incompatibilities between the several patches cannot be properly sorted out by a frontend anyway, only by a competent human packager.(And if the 'MAME World' is doing something a particular way, my gut reaction is to do avoid doing that at all cost.) Oldbie Posts: 852 Joined: 2005-9-02 @ 02:26. Filipetolhuizen wrote:The Daum build was working fine just until it merged with doxbox-x.A perfect example of why the more minimal approach that ECE currently uses is the way to go. Nothing is stopping you from starting your own fork to add the patches that are important to you.I'd love to. I guess I keep asking everyone else because of my programming skills total lack.It's the most easiest part to further your programming knowledge in a couple of steps.1. Follow the guide on how to compile Dosbox yourself (essentially setting up your own development environment)2. Compile Dosbox from SVN and test that3.

Learn how to apply a simple patch4. Learn how to apply a more advanced patch and deal with errors when it doesn't apply (with a text editor going through the changes - since the patch is a text file and the source code is made up of text files, it is simple looking at it and finding the pattern where the patch should have applied to)5. Learn how to add mor dependeny libraries to your development environment for patches that require those6. Have no more time to actually play since you are always busy with 4. And 5.and dealing with the fallout of the builds you offered for everyone else. Vanilla DOSBox Linux build throws 'error while loading shared libraries: libasound.so.2: cannot open shared object file: No such file or directory'. Libasound2 package was showing as already installed.While trying to run DOSBox ECE under Linux(Ubuntu 16.04 LTS), I'm getting 'error while loading shared libraries: libSDLsound-1.0.so.1: cannot open shared object file: No such file or directory'.

Linux Dosbox

Libsdl-sound1.2 (1.0.3-7build1) was not pre-installed. Even after installation the error doesn't go away.I'm a relatively new linux user. What am I missing?BTW Windows ECE build works flawlessly, thanks heaps. Yes, this seems a bit complicated.

Dosbox Download

It really shouldn't pull in all of the system dlls. Very problematic are the Virtualbox stuff.