I just build a portable DBGL with some games and DOSBox Staging in order to demonstrate the new Sound Canvas emulation to some friends. However, I noticed I still had to add the "soundcanvas" switch to the "mididevice_staging0810" section in the Dynamic Options. I'm using latest beta, dbgl0100beta17. I'm a bit confused, because right now I can't remember if any stable version of DOSBox Staging has already included the Sound Canvas emulation. Anyway, maybe it's time to start including the option.

The Sound Canvas section on the dosbox-staging.conf file also has a few options, but I don't know if they deserve its own section on the profile editor. Here they are:

[soundcanvas] # soundcanvas_model: The Roland Sound Canvas model to use. # One or more CLAP audio plugins t […]
Show full quote

[soundcanvas]
# soundcanvas_model: The Roland Sound Canvas model to use.
# One or more CLAP audio plugins that implement the supported Sound Canvas
# models must be present in the 'plugins' directory in your DOSBox installation
# or configuration directory. DOSBox searches for the requested model by
# inspecting the plugin descriptions. The lookup for the best model is
# performed in order as listed.
# auto: Pick the best available model (default).
# sc55: Pick the best available original SC-55 model.
# sc55mk2: Pick the best available SC-55mk2 model.
# <version>: Use the exact specified model version (e.g., 'sc55_121').
# Possible values: auto, sc55, sc55_121, sc55_120, sc55_110, sc55_100, sc55_200, sc55mk2, sc55mk2_100, sc55mk2_101.
#
# soundcanvas_filter: Filter for the Roland Sound Canvas audio output:
# on: Filter the output (default).
# off: Don't filter the output.
# <custom>: Custom filter definition; see 'sb_filter' for details.
#

soundcanvas_model = auto
soundcanvas_filter = on

Oh, and 've been thinking about those PC-98 self-booting HD images I talked about earlier. Made me realise there's not an option in DBGL to boot PC harddrive images either. I can see why not, because it's not something one would usually need. Anyway, if there's room in the Mounting tab and the feature is added to any of those systems (PC or PC-98), why not both?

And well, if adding this feature is out of the question, I can always write a BAT file to launch these rare games that need booting from an HD image. There aren't that many .

rcblanke wrote on 2025-10-03, 18:30:

Yes, you can run dbglcons.cmd to keep a debug console open.

Good morning
Do you plan to support DOSBox Pure Unleashed, new version standalone of dosbox pure https://github.com/schellingb/dosbox-pure-unleashed ?

kolderman wrote on 2025-10-03, 20:53:

I get an error:

i get an error minimum windows build version 14393 but currrent is 7601

Maybe there are some left-over temporary SWT files from the 'new' jar. Please try removing (or renaming) the .swt folder in your home directory.

willow wrote on 2025-11-03, 20:44:

Good morning
Do you plan to support DOSBox Pure Unleashed, new version standalone of dosbox pure https://github.com/schellingb/dosbox-pure-unleashed ?

Hi willow; that is quite unlikely, as this particular DOSBox fork seems mostly intended to be used stand-alone, using it's own gui etc. Unless there actually IS a compelling reason to use it with DBGL?

Neville wrote on 2025-10-11, 20:15:

..Oh, and 've been thinking about those PC-98 self-booting HD images I talked about earlier...

For the moment, I'm working on implementing .HDI browsing. More work is underway, but as usual, the last months of the year are the busiest for me - so it might take some time.

Sure, take all the time you need. I also imagine it's not a very urgent or popular feature.

rcblanke wrote on 2025-11-25, 19:08:

willow wrote on 2025-11-03, 20:44:

Good morning
Do you plan to support DOSBox Pure Unleashed, new version standalone of dosbox pure https://github.com/schellingb/dosbox-pure-unleashed ?

Hi willow; that is quite unlikely, as this particular DOSBox fork seems mostly intended to be used stand-alone, using it's own gui etc. Unless there actually IS a compelling reason to use it with DBGL?

Thanks.

Greetings! I've been using DOSBox Game Launcher for a while now, I am an ex-DFend user and found this to be an excellent replacement. Thank you for making this possible!

I am setting up a laptop for a family member, and would like to export some of my games for them. When I try use the export function (Game data + captures) I reach step 2 but can't get past this page, the app reports that "the game directory XYZ is invalid, it must be relative to the dosroot"

I am unsure what this error is saying. The directory does exist. I have tried changing the directory to various other locations to test what works, but not having any luck. What exactly does dosroot refer to? Is that the path that is mounted as the C drive?

Each game has its own directory mounted as C drive, attached are snaps of the mount configuration.

Any advice will be appreciated 😀

1$ java -version
2openjdk version "21.0.9" 2025-10-21
3OpenJDK Runtime Environment (build 21.0.9+10-Debian-1deb13u1)
4OpenJDK 64-Bit Server VM (build 21.0.9+10-Debian-1deb13u1, mixed mode, sharing)

Running DBGL 0.99

Apologies, I solved it.

I used the find command to discover the dosroot location at ~/.local/share/dbgl/dosroot, pointing to that path allows the next export step.

Thanks! 😀

Oh, okay so the exported archive does not contain the game files at all, it contains whatever is in the dosroot directory (which is empty on my setup).

So I guess the export feature won't work for games that mount their drives from paths outside of dosroot?

That is correct wesbat. DBGL will use relative paths only if the target file or directory is located underneath a certain location (in most circumstances, DOSROOT). Locations outside are considered absolute. The reason for this is that by using this logic, one can safely move the DBGL directory to another location without breaking any file or directory locations.

Just a small "bug" I found: if you try to mount an ISO or CUE file stored on a network drive, you get "null" instead of the actual link. I have to mount the folder to a drive letter before DBGL will correctly link to it. Oddly enough it doesn't do this with other folders or files?

Also: if you boot DBGL off the drive via the drive letter (for example N:\DBGL) it will see the folder as \\NASDRIVE\MYDRIVE\DOSGAMES\DBGL - this too used to be different. I mean, it's more correct and not dependant on the mount letter to remain the same but it seems to have some issues working with network links.