VOGONS

Common searches


DOSBox Game Launcher (DOSBox Frontend)

Topic actions

Reply 1920 of 1924, by rfc

User metadata
Rank Newbie
Rank
Newbie

Hi,
I'm trying to get dbgl running (again) on a "portable" installation I have on my NAS which so far I successfully shared between Windows and OSX by mounting it.

I'm facing a problem on OSX Sonoma 14 (Intel) using dbgl 0.97, in that on startup it seems it wants to copy all files to ~/Library/dbgl (which at first I didn't realize because my dosroot is quite big and it wrote "Startup" on the terminal and nothing happened for a looong time).

But I mount the files from the NAS into /Volumes/Data/dbgl and start it from there and want to keep it there, to have my portable installation.

I almost forgot how did I get there, because had to manually copy out the dbgl.jar and libs/ and dosbox binary from the `Dbgl.app/` directory to my mounted installation, so I guess I'm not really dong it the way it's supposed to be.

I tried to find it on https://dbgl.org/ but couldn't, what is the proper procedure to have a portable version of dbgl running on OSX?

Thank you

Reply 1921 of 1924, by rcblanke

User metadata
Rank Oldbie
Rank
Oldbie

Hi rfc,

Thanks for the question. This comes up every once in a while, I'll update the documentation on the website.

By default, DBGL will use ~/Library/dbgl to save its data on a Mac. On Linux it is ~/.local/share/dbgl (as defined in the XDG specification). For Windows machines, on the other hand, all data is stored in the DBGL folder itself (unless it is read-only, then %localappdata%/dbgl is used). Let's call this location the 'DBGL data location'.

Linux and OSX can also use the DBGL folder. On Mac, open DBGL.app/Contents/MacOS/dbgl with a text editor and change -Ddbgl.data.userhome=true to -Ddbgl.data.userhome=false. A similar change is required for Linux in the dbgl startup script. In your case, changing this setting will prevent your DBGL dosroot from being copied from the NAS to your local machine.

So, if you just want to have all DBGL content in a single directory structure, use dbgl.data.userhome=false . This should also work fine if you running it from off the NAS share.

But what if you want to use DBGL with different Operating Systems? This question has come up quite a while ago. Most of the information in that thread is still correct, but to summarize:

  1. Create a directory on your NAS (or USB stick) for DBGL and mount it (with RW permissions); let's say /Volumes/dbgl for Mac, \\mynas\dbgl for Windows or /Media/USBSTICK/dbgl for Linux. Let's call this the 'shared content location'.
  2. Install DBGL on your different OS' and start it once. Please note that for Mac and Linux, you should use dbgl.data.userhome=false !!
  3. After closing DBGL, there will be a settings.conf file in your DBGL folder. Open that file with your favorite text editor and change the 'data' setting. By default, it's set to '.', which means DBGL expects all user-generated content to be in the 'DBGL data location'. Change the value to your 'shared content location', for example data=/Volumes/dbgl
  4. Move the folders captures, db, dosroot, export, profiles, templates and xsl to the 'shared content location'

If you use this solution, you have all your DBGL user-generated content in one place, while maintaining the flexibility to customize your DBGL installation on the various OS systems. For example, you can still use different system environment options (inside DBGL) on each OS. This allows you to set a specific SDL output renderer for each Operation System, for instance.

Please note that this technique has its limitations, especially with regards to DOSBox versions. Because of the fact that you're sharing DOSBox Version settings with multiple operating systems, it is required that you'll have the various DOSBox versions in the correct subdirectories on the local machines. For example, by default a 'DOSBox-0.74-3' folder is expected to exist (on your local machine, inside the DBGL folder) and have (at least) the dosbox executable and dosbox.conf files. When using Windows, DBGL will look for 'DOSBox.exe'. On Mac, 'DOSBox' is expected, and on Linux, 'dosbox'.

Also note that you can start only one instance of DBGL at the same time.

In the end, you can configure and play your DOS games on all systems using one familiar interface, without the need to export and/or import anything.

Please let me know if anything's unclear, or requires a better explanation.

Regards,
Ronald

Reply 1922 of 1924, by rex0

User metadata
Rank Newbie
Rank
Newbie

I'm a noob, just started with DOS games and downloaded DBGL because it seemed user friendly. Though I'm facing a problem regarding shaders.

Aside from those displayed in the "Scaler" dropdown menu in "Official options", where can I find more shaders like CRT etc. and how do I use them? I can't seem to find any info about this either.

I found some shaders here: https://github.com/tyrells/dosbox-svn-shaders

I have downloaded them but unable to use them. I see an "Experimental options" tab in the Display options but everything is greyed out. Another thing is that I'm facing screen tearing in some games. I see "Vsync" in "Experimental options", but again, it's greyed out.

Any help will be really appreciated. Thanks.

Reply 1923 of 1924, by mgtroyas

User metadata
Rank Newbie
Rank
Newbie

Hi, firstly the DOS box build you use must support shaders. Vanilla version does not, but for instance Staging does. In fact on last version they're removing it again because they'll start using some advanced auto-confugured internal shader...