Just noticed that DBGL v0.98 seems to have trouble opening game packages created with 0.99. It's understandable, but I wonder if there's any easy fix for this. I'd like to keep trading packages between my desktop (Windows 10 and DBGL v0.99) and my laptop (Windows 7 and therefore DBGL v0.98).
Not sure what's going on there, but you should be able to use DBGL0.99 on Win7 using lib/swtwin64.jar from 0.98 as explained here.
Swapping floppies only works in DOSBox SVNs or DOSBox forks. You need to mount all of them as A: and floppy, then press CTRL+F4 during emulation to change between them.
EDIT: Before installing the game, the Mounting tab should look like this:
I'm having a spot of bother with DBGL 0.99 and DOSBox Staging 0.82.0.
I can create a game profile successfully with DOSBox Staging 0.82.0 set as default, and the game will run. However DBGL will hang if I then try to edit the profile I just created.
I normally use DOSBox ECE, and my ECE game profiles run and edit just fine, but there are a few games like "Spellicopter" that need Staging to run correctly. I've resorted to editing the profile conf file directly for these few profiles.
For the record, here is my DOSBox Staging config:
Attached is my database.log where I add the new game profile, save it and test run the game, then edit the profile and change the machine type to cga. At the point of clicking OK to save the edited profile, DBGL hangs and I need to force close the app.
Here's another small update to fix the problem mentioned by dosdog, above. Also fixed is a minor issue related to DOSBox-X 2024.10.01 and 2024.12.04 detection.
I'm having a few issues with the 0.100beta2 build, myself. I'm on Arch Linux and using a DOSBox Staging portable build, and it's the only DOSBox version I have set up. This is how I've got that set up:
I can set up games just fine with a couple big caveats:
- For me, under 'Add Profile' everything from "DOS" down is grayed out except for things I've changed in the global config for the set up DOSBox. This means I'm stuck manually editing configs to change anything beyond an applied template.
- The "Add Game Wizard" button instacrashes DBGL. It did this for me before 0.99, as well. The crash output is:
1Exception in thread "main" java.lang.IllegalArgumentException: Argument cannot be null 2 at org.eclipse.swt.SWT.error(SWT.java:4903) 3 at org.eclipse.swt.SWT.error(SWT.java:4837) 4 at org.eclipse.swt.SWT.error(SWT.java:4808) 5 at org.eclipse.swt.widgets.Widget.error(Widget.java:597) 6 at org.eclipse.swt.widgets.Combo.setText(Combo.java:2560) 7 at org.dbgl.gui.dialog.wizard.AddGameWizardDialog.updateControlsByProfile(AddGameWizardDialog.java:386) 8 at org.dbgl.gui.dialog.wizard.AddGameWizardDialog.onShellCreated(AddGameWizardDialog.java:327) 9 at org.dbgl.gui.abstractdialog.BaseDialog.open(BaseDialog.java:112) 10 at org.dbgl.gui.dialog.MainWindow$18.widgetSelected(MainWindow.java:526) 11 at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:265) 12 at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:91) 13 at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5855) 14 at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1617) 15 at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5065) 16 at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4517) 17 at org.dbgl.gui.abstractdialog.BaseDialog.open(BaseDialog.java:120) 18 at org.dbgl.gui.Launcher.main(Launcher.java:55)
Now for the positive: The new support for forks is very much appreciated, and has me excited to use DBGL again! Thanks for everything you do. 😄
Thanks for the heads-up, ColetteDiskette. The crash you mention should be fixed in beta3.
Both issues are most likely related, though. I suspect something is wrong with the config file "colette-base.conf" that you have configured, can you please share it (via PM) ?
dbgl-user, DBGL can be made portable by editing the dbgl startup script, and changing -Ddbgl.data.userhome=true to -Ddbgl.data.userhome=false .
Oh, I just tested that new build and can confirm that the Add Game Wizard at least doesn't instacrash for me now. I'll get around to setting up something pretty soon, but I at least wanted to report back with that for now. 😄
Thank you ColetteDiskette; I see what you did here.
The DOSBox config file should actually remain untouched, with all the original default values, for DBGL to work properly. That is to say, you should at least keep all sections and items in there, as it is the only thing DBGL can use to check for supported features. You can make changes to the default values in the conf if you want, but it is recommended to use a DBGL Template if you'd want to deviate from the defaults. Also, if you want, you can make that Template 'default' so it is automatically applied to any new profile.
Thus, the reason that
everything from "DOS" down is grayed out
is because all these sections are missing in your dosbox conf.
Note that you can simply enter a new filename in the "Config file" input field, and DBGL will suggest to create that clean config file for you, automatically.
Last edited by rcblanke on 2025-01-02, 20:58. Edited 1 time in total.
dbgl-user, to make a minimal portable JRE, you need to install JDK 17 or newer. I would recommend openJDK21 (apt install openjdk-21-jdk). You will also need jlink (apt install openjdk-21-jdk-headless).
This should make the Java dependency portable. Please keep in mind, that you will want to place the DOSBox version(s) that you use, also in the DBGL folder. That way, you can reference them using relative paths, as to also have that portable.
Oh! Yeah, when it said 'config file' I didn't realize it was asking for a stock config for the purpose of knowing what in the world to do with all these forks. I already had a setup with a global config and just kind of plugged it in as an assumption on my part. It makes sense to me now. I appreciate it!
since the new 0.99 version, I'm unable to start the app on macOS Sonoma 14.7.2
The icon jumps up for 1 seconds and then closes immediately.
This is the log I got:
1Thomas@Thomas-Mac-mini ~ % /Applications/Spiele/DBGL.app/Contents/MacOS/dbgl ; exit; 2Launching DBGL using 64-Bit VM 18.0.2 on Mac OS X v14.7.2x86_64, HSQL Database Engine 2.7.3, SWT v4966cocoa 3Exception in thread "main" java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: 4 no swt-cocoa-4966r5 in java.library.path: /Users/Thomas/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. 5 no swt-cocoa in java.library.path: /Users/Thomas/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. 6 no swt in java.library.path: /Users/Thomas/Library/Java/Extensions:/Library/Java/Extensions:/Network/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:. 7 Can't load library: /Users/Thomas/.swt/lib/macosx/x86_64/libswt-cocoa-4966r5.jnilib 8 Can't load library: /Users/Thomas/.swt/lib/macosx/x86_64/libswt-cocoa.jnilib 9 Can't load library: /Users/Thomas/.swt/lib/macosx/x86_64/libswt.jnilib 10 Can't load library: /Users/Thomas/.swt/lib/macosx/x86_64/libswt-cocoa-4966r5.jnilib 11 12 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:345) 13 at org.eclipse.swt.internal.Library.loadLibrary(Library.java:254) 14 at org.eclipse.swt.internal.C.<clinit>(C.java:19) 15 at org.eclipse.swt.widgets.Display.<clinit>(Display.java:110) 16 at org.dbgl.gui.Launcher.main(Launcher.java:51)
It doesn't matter rather I'm using the x86 or arm version.