I know it's awkward but, I wanna give a "second chance" for an old, but 100% functional, notebook.
It's only run Windows XP because its SiS video driver. Its Linux (and FreeBSD) drivers are old and more slow than XP.
I read that dosbox staging has Windows XP support for run but when I tried the 32bit version, it's give that error: "dosbox.exe is not a valid Win32 application".
My Windows XP is updated with all avaliable hotfixes. All Microsoft Visual C++ libraries (2005 to 2017) are installed too.
My notebook is a Acer Aspire 3000:
Binary that I tried:
https://github.com/dosbox-staging/dosbox-staging/releases/download/v0.75.2/dosbox-staging-windows-x86-v0.75.2.zip
Our official builds won't work on Windows XP by default - we don't test it, we won't work on it, sorry. Minimal requirements for CPU for our Windows builds is SSE 4.2; you can try version 0.75.0 - it had SSE support turned OFF and was not bundling VC++ libraries compatible with Win 7 or newer (but I seriously doubt it will work on XP anyway).
I am not sure Microsoft's VC++ 2015 and 2017 libraries are even compatible with Windows XP…
You can try compiling your own version (and it should work… mostly, there are some small issues due to ancient version of C standard library available on Windows XP), but it will be a major chore.
You would need to use MSYS1 (I don't even know where to find it…) and build all dependencies manually. We had one dev who managed to successfully do it (before 0.75.0), but later he switched to using Linux instead.
TL;DR; We "support" Windows XP only in the meaning: you can attempt to build it yourself.
For such an old machine, you should probably stick to DOSBox 0.74-3 - it's based on 10-year old codebase and supports Windows XP (AFAIK, never tested it myself).
@tiagotarifa,
I noticed you're a fellow Linux and shell user in your profile, so if you're up for some command line labour (ie: manually compiling precursor dependencies, then mid-level dependencies, and finally DOSBox Staging's direct dependencies), then the MSYS approach is certainly possible.
Plus, adding such a nightmare fits with our present Halloween / Guy Fawkes holiday theme :bat:
@dreamer mentioned another maintainer managed to do this; and it was indeed a non-trivial, multi-week effort.
You mentioned wanting _to give a "second chance" to an old, but 100% functional, notebook._ Another approach to do this would be installing a modern and supported, but memory-frugal, Linux (or BSD) distribution, such as: https://www.linuxliteos.com/forums/release-announcements/linux-lite-5-2-final-released/
This configuration _is_ supported as a build environment, and it would literally be five commands to get you up-and-running with a build specifically optimized for your Sempron's instruction set:
sudo apt install -y gitcd dosbox-staginggit clone --depth 1 https://github.com/dosbox-staging/dosbox-stagingsudo apt install -y $(./scripts/list-build-dependencies.sh -m apt -c gcc)./scripts/build.sh -c gcc -t release -m nativeUnlike XP, installing a 64-bit Linux would also let you leverage the full 64-bit register space of your CPU, which can often double performance for CPU-bound tasks.
Hey, I forgot about another possibility: cross-compile from Linux to Windows - perhaps it will work on Windows XP.
On Fedora, almost all dependencies we use are provided by Fedora repo (e.g. mingw32-SDL2); use mingw32-configure instead of ./configure and mingw32-make instead of make. I did it once and needed to some some tiny adjustment for icon file or something.
I think this might be the most practical solution here - it's definitely much easier than building on Windows XP.
Thanks guys!
I'll give a try in this weekend, to build the binary for Windows XP using Linux. If it works, I'll post all steps here.
If you can package it into a script, we'd be happy to add it to the existing helper tools in ./contrib
Most helpful comment
Thanks guys!
I'll give a try in this weekend, to build the binary for Windows XP using Linux. If it works, I'll post all steps here.