Dang Thanksgiving week! I'll have to try it when I get back.

Nice to see that you have begun to use the power of XSL (and, I guess, internally generating XML as input to the transformation process). I look forward to the day you can export the game profiles as XML, and import them as well.

MiniMax wrote:

Nice to see that you have begun to use the power of XSL (and, I guess, internally generating XML as input to the transformation process). I look forward to the day you can export the game profiles as XML, and import them as well.

I'll second that. I hope all of the frontends move in this direction.

I'd still like to see a "translateable" D.B.G.L. in the near future. Are there any plans in that direction?

Neville wrote:

I'd still like to see a "translateable" D.B.G.L. in the near future. Are there any plans in that direction?

Yep, just started working on it. I can provide Dutch and Simplified Chinese translations.

Any volunteer translators to provide other languages?

Having wasted a fair amount of time trying to "roll my own" 64bit compile of 0.63 fo DBGL for use under Ubuntu, has anyone managed to get it to work?
0.55 works fine, but I was hoping to keep my windoze and linux DBGLs in synch.

I gave up after 5 hours of banging my head against javac...

I also tried moving the 0.63 dbgl.jar into the 0.55 folder (Ha Ha I know) with no luck?

I suppose what I want to know is, is it actually possible?

cheshirenoir wrote:

I also tried moving the 0.63 dbgl.jar into the 0.55 folder (Ha Ha I know) with no luck?

Ha ha (?) it should work just fine, there is really no need for recompilation 😖 😜
Could you show me the error message when starting it in a console with ./dbgl ?

rcblanke wrote:

Neville wrote:

I'd still like to see a "translateable" D.B.G.L. in the near future. Are there any plans in that direction?

Yep, just started working on it. I can provide Dutch and Simplified Chinese translations.

Any volunteer translators to provide other languages?

Yes, you can count me in for a Spanish translation.

Ha ha (?) it should work just fine, there is really no need for recompilation S-Face Sticking Tongue Out
Could you show me the error message when starting it in a console with ./dbgl ?

Sure!
First, the correct behavior with the original dbgl.jar

1cheshire@Leviathan:~/Downloads/DBGL$ ./dbgl
2startup
3shutdown
4cheshire@Leviathan:~/Downloads/DBGL$ 

and then with the 0.63 dbgl.jar

1cheshire@Leviathan:~/Downloads/DBGL$ ./dbgl
2Exception in thread "main" java.lang.NoClassDefFoundError: SevenZip/Archive/IInArchive
3	at com.db.Database.<clinit>(Database.java:88)
4	at com.gui.MainWindow.open(MainWindow.java:71)
5	at com.gui.MainWindow.main(MainWindow.java:63)
6Caused by: java.lang.ClassNotFoundException: SevenZip.Archive.IInArchive
7	at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
8	at java.security.AccessController.doPrivileged(Native Method)
9	at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
10	at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
11	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
12	at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
13	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320)
14	... 3 more
15cheshire@Leviathan:~/Downloads/DBGL$ 

I'm runnning Sun JRE

1cheshire@Leviathan:~/Downloads/DBGL$ sudo update-alternatives --config java
2
3There are 4 alternatives which provide `java'.
4
5  Selection    Alternative
6-----------------------------------------------
7*         1    /usr/lib/jvm/java-6-sun/jre/bin/java
8          2    /usr/bin/gij-4.2
9          3    /usr/bin/gij-4.3
10 +        4    /usr/lib/jvm/java-gcj/jre/bin/java
11
12Press enter to keep the default[*], or type selection number: 

Any ideas?

What is the value of

$ echo ~

What is the value of

$ echo $JAVA_HOME

What is the value of

$ echo $CLASSPATH

Try

$ /bin/sh -x ./dbgl

Thanks cheshirenoir. It didn't reveal anything, but it did eliminate some possible problems.

How about

$ cd ~/Downloads/DBGL
$ zipinfo -1 lib/J7Zip.jar

Hah! That did it. The library wasn't in the right directory. I moved it in (From a copy I had downloaded of the 32 bit version) and away we go!

So for whoever follows me, here are the instructions:

Download the 0.56 64 bit Linux archive.
Uncompress it somewhere you can find it.
Download the 0.60 32 bit Linux Archive.
Extract JUST the J7Zip.jar and dump it into the lib directory of your DBGL directory
Download the 0.63 JAR and dump it into the DBGL directory, overwriting the current dbgl.jar
Run the dbgl script...

Thanks folks!

Glad you got it working cheshirenoir, and thanks for sharing your findings. For the next release I will (have to) recreate complete packages for the various OSs again, so that should be a lot easier 😀

rcblanke - I downloaded the srcXXX.zip package but I didn't find the dbgl script in there. I had to get the tar.gz package to see the script.

Hi all,

Version 0.64 greets the new year! Let's see what's inside:

* Implemented multi-language support; For the moment, English, Chinese(yzchang), Dutch and Spanish(Neville) translations are completed. You can find the language selection in the 'Settings' dialog.
* Added the possibility to browse inside ISO archives; In the profile editor, simply select the .iso file that contains your game and the executable inside that .iso. DBGL will take care of proper mounting. Many thanks to the people behind Loopy and Apache Commons VFS (skardavnelnate).
* Added IPXNET command support (Metron4).
* Also new is the possibility to export your game-list to another file, such as a plain TXT file, a basic .CSV or a fancy HTML page. If you know how to write xsl files, feel free to create your own export formats. When you put them in the xsl folder, they'll show up in DBGL.
* Added a menu option to clean un-used autocomplete entries for developers, publishers, etc. to reduce database size (skardavnelnate).
* Fixed a regression (since 0.63) in profile duplication; mounting settings got lost in the newly created profile.
* Updated the SWT and HSQLDB libraries.

Windows package only for the moment, Linux and OSX builds will follow soon.

Regards,
Ronald

I had some problems getting DBGL to run on Vista 64, I got the

1Exception in thread "main" java.lang.UnsatisfiedLinkError: no swt-win32-3349 or swt-win32 in swt.library.path, java.library.path or the jar file

error no matter what I did.

The reason for me seemed to be that my default JRE was 64-bit while the SWT library is 32-bit.

I changed the line that starts the game in dbgl.cmd to the following which fixed the problem for me:

1start "DBGL" /B /D<DBGL_PATH> "<JAVA_PATH>\javaw.exe" -Djava.library.path=lib -jar dbgl.jar || pause

What this does is use the 32-bit version of Java to run the game.

First the "DBGL" part sets the title for the console window, and that needs to be done so we can use quotations for the paths. Seems that the first quotated string is used as title, go figure...

The /D<DBGL_PATH> command sets the directory where the command is run in. In my case /DC:\dbgl. There's no space between the /D and the path.

<JAVA_PATH> should point the directory where the 32-bit java is found. For me it was C:\Program Files (x86)\Java\jre6\bin (the 64-bit programs are in Program Files and 32-bit programs in Program Files (x86) on 64-bit Vista).

Not sure if this has been posted before, but it took me a while to realize what the problem was and I thought this might help someone else.

Thanks for sharing your findings, Brain! Narf!

I look forward to the day you can export the game profiles as XML, and import them as well.

I would like to continue working on import/export functionality. But I need more information to make sure that most users won't be disappointed when its done:

So, what is it exactly that you guys and girls want to accomplish by using import/export functionality? Share your games with friends? Being able to share game settings between multiple DBGL instances on the same computer? Maybe something else?

I need to have the various goals for this functionality entirely clear, in order to prevent making mistakes in the beginning of the programming design that might be hard to fix later on.

Regards,
Ronald

Why I want an XML export & import facility in ALL frontends:

• Open format - prevents me from being locked into a specific frontend.
• Open format - will allow me to easily try different frontends.
• Open format - will facilitate creating a shared database of configurations.
• Text format - makes verification and debugging easier.
• XML is extensible - I want to be able to include not only DOSBox configuration data, but also meta-data about the game (title, publisher, developer, year, status, genre, links to web-sites, MD5 checksums, paths to configuration files, paths to save-game files).