Closed niclashoyer closed 1 year ago
I think this core has been discontinued and replaced with DOSBox-SVN (https://github.com/libretro/dosbox-svn).
Note to self that I'd still like to look at doing something with this.
I think this core has been discontinued and replaced with DOSBox-SVN (https://github.com/libretro/dosbox-svn).
Someone really should clarify the states of DOSbox ports (perhaps archiving the obsolete ones and linking to the suggested replacement(s) in the README). You have this, DOSbox Core, DOSbox SVN, and DOSbox Pure.
The advantage of this one is that it's tried and true, without a bunch of changes that may or may not break something. DOSbox Pure has the advantage of being able to read ZIP files and having releases (it may just be me, but I like to only use stable releases when possible).
This is my quick "fix" for #92. I don't know if
chdir
is the best solution at this point. I would prefer a config option instead of changing the current working directory for the whole process.This is needed if one is loading a
dosbox.conf
configuration file directly. Without this patch the following would not be possible:My concrete use case is mounting the current directory as a cdrom image (which is not directly possible when calling the
EXE
):It is even possible to start Win 3.11 games using this technique. Just place a shared installed Win 3.11 directory in the parent path. Then: