A couple of 3.5.1 problems

[Matt Korth]

It kind of sucks that the first post I'm making is about problems, since I've been using jGnash for... a very long time now, if my account registers are to be believed (I've removed old details because I don't need them anymore, but I do have a "2002 Summary Entry" in there).

Anyway...

I'm running on Windows 10, with the Zulu implementation of OpenJDK 13.

openjdk 13.0.2 2020-01-14
OpenJDK Runtime Environment Zulu13.29+9-CA (build 13.0.2+6-MTS)
OpenJDK 64-Bit Server VM Zulu13.29+9-CA (build 13.0.2+6-MTS, mixed mode, sharing)

JAVA_HOME has been set accordingly (to "C:\Program Files\Zulu\zulu-13\"), and "C:\Program Files\Zulu\zulu-13\bin" has been added to PATH.

Unfortunately, I seem to be experiencing the exact problems described by another user in this thread: I can't get jGnash to launch by double-clicking on jGnash.exe.  The only difference I could see is that I can't run 3.4.0 either - I have to go all the way back to 3.2.0 to be able to start jGnash.

I did find that Alfred Mühlleitner's idea of running Bootloader.bat worked, though.

Any help is appreciated, thanks.

--Matt.

[Craig Cavanaugh]

Matt,

I just tested the Zulu 13 implementation using the .msi installer and set the env variables and everything is working as expected for me.

However, I do not have the trailing "\" for JAVA_HOME.  Mine looks like "C:\Program Files\Zulu\zulu-13"

If that does not work, Adopt OpenJDK may behave better.  When installing, make sure the option to overwrite the reg keys is enabled.  The manual details how to do it.

Thanks,

Craig

[Matt Korth]

That seems to have done the trick.  I'm not sure why Zulu decided to stop working (and as far as I can tell, ONLY for jGnash), but oh well...

Thanks.

--Matt.

[Craig Cavanaugh]

The change in PATH or Adopt OpenJDK?

Looking for insight for making the launcher more robust...

Thanks,

Craig

[Matt Korth]

Adopt OpenJDK.  Sorry, should have said.  The change to PATH did nothing, so far as I could tell.

[Craig Cavanaugh]

Thanks!