The importer can be used by opening a cmd/terminal window in the DBGL folder, and typing:
java -Djava.library.path=lib -cp dbgl.jar exodos.Import
This will show the options available for importing. The only required parameter is the path to an eXoDOS pack, for example:
java -Djava.library.path=lib -cp dbgl.jar exodos.Import c:\exodos
This will import all games from the c:\exodos pack into the current DBGL installation.Please keep in mind that the imported eXoDOS data will require 810 GB of disk space!
The converter works similarly:
java -Djava.library.path=lib -cp dbgl.jar exodos.Convert
This will again show the options available for converting. The only required parameters are the path to an eXoDOS pack,and the directory in which to write the GamePackArchives, for example:
java -Djava.library.path=lib -cp dbgl.jar exodos.Convert c:\exodos c:\tmp
If you go to this website, you'll find a JRE zip.Unzipping the contents of this zip into the DBGL folder, allows for running DBGL without even installing Java. Just edit dbglcons.cmd and change its contents to:jdk8u252-b09-jre\bin\java -Djava.library.path=lib -jar dbgl.jar pause
In order to kickstart your DBGL games collection, please feel free to try out the following game packages. Just download the *.dbgl.zip files, do not extract them. The game pack archives can be imported directly into DBGL using the menu: Profiles Import ...
Simply run ant (website) to build DBGL. This will compile the Java source into dbgl.jar, and copy files around to create the packagesfor the different operating systems in the dist/ subdirectory. Please note that the MacOS package can only be created on an actual Mac because of a dependency on hdiutil.
Prior to bundling all compiled code and static resources into dbgl.jar, the various MessagesBundle files (containing all translations) are compacted (stripped of duplicate entries) using CompactResourceBundles.java . In case entries are missing from a certain bundle, one might use SyncResourceBundles.java to remedy this.
Just extract the DBGL archive to any dir and run the dbgl.bat file. Please note that you MUST have the Java Runtime Environment 1.5 installed, it will not work without the JRE1.5, or with an older version. Moreover, java.exe should be in your path. See
On line 3 of 'dbgl.sh', you should add 'exec ' to the start of the line. This avoids having an unnecessary bash process running in the background, and better informs whatever runs dbgl of what is actually running. Right now, it will think bash is running, not dbgl.
Just a quick heads-up to inform you guys and girls that I have updated the main website at dbgl.org to provide for a better browsing experience on mobile devices. Expect more updates in the coming days.
the last couple of months i was quite busy and had no time to play good old dos games via dbgl. but now i want to start over again. i have an older installation of dbgl v0.93 on my drive which i combined with dosbox ece last year. it's running great, shaders and roland sound are working perfectly. but now i decided to start over again from scratch and downloaded the newest versions of dbgl & dosbox ece.
and here i need to ask for your help please - to use roland sound (or mt32 or cm32l roms) in the older 0.93 version of dbgl i click "edit profile" of any compatible game, after that i click "audio" and under "midi device" i have many choices: alsa - default - coreaudio - coremidi - none - oss - win32 - fluidsynth - mt32 - synth - timidity -> 11 options in total. so i choose "mt32" for wing commander for example and it works.
The problem is I can't seem to locate the startup script. A folder called "dbgl" was created in my /Library folder, but this script doesn't appear to be in there, nor can I locate a ./dbgl hidden folder in my home folder's root or the system root.
To answer your question about the startup script:
Open Finder and browse to Applications. Right click on DBGL.app and choose 'Show Package Contents'. You will find the dbgl startup script in the subdirectory
But please take note that updating older DBGL versions on MacOS can be a bit tricky. Older DBGL versions stored (game) data inside the DBGL.app directory structure. This could mean that whenever you trashed DBGL.app from your Applications list to install a newer version, you could accidentally also have trashed all its (game) data. That's why I opted to use /Library/dbgl for data instead (since DBGL version 0.93). That way, you can safely trash DBGL.app to put a new version in place without touching your data.
08ab062aa8