openMSX Launcher 1.9

Page 2/2
1 |

By oelsha

Rookie (32)

oelsha's picture

20-11-2017, 22:49

Hi DamnedAngel,

If you feel comfortable making modifications to the Registry, here's a description of the keys that I found on two separate machines running Windows 10:

Under:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment
add key name CurrentVersion with value 1.8.

and Under:
HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.8
add key name JavaHome with value location of the JRE
Location will be something like C:\Program Files\Java\jre1.8.0_151

I wouldn't recommend to make changes to the Registry, but it's up to you. I'll try to work on making the executable take an optional argument to be the location of the JRE hopefully this week. That would be the fastest fix for now.

By oelsha

Rookie (32)

oelsha's picture

23-11-2017, 03:21

@DamnedAngel

I modified the Windows executable to take an optional JRE location to be used instead of the registry lookup. If no location is provided, the registry mechanism will be used as before.
You can download the new build of the executable from here
Please give it a try and let me if it works. I will then add a link to it on the MSX Launchers site when I get your confirmation.
In order to pass the JRE location as an option, create a shortcut for the executable and edit its target to pass the JRE location. Make sure you add the location without double quotes (i.e. C:\Program Files\Java\jre1.8.0_151\bin\java.exe).

By DamnedAngel

Master (143)

DamnedAngel's picture

23-11-2017, 18:17

Hi oelsha,

I am sorry for the delay. I've been too busy these days and that kept me from trying your suggestions.

I intend to, during the upcoming weekend, try both registry hacking and the new executable, in order to give you the feedback. Both solutions working, of course I would rollback the registry editing and maintain the executable solution, but still I owe you responses for your so kind attention to my case.

Thanks for putting your efforts into making the tool even better.

best!

By DamnedAngel

Master (143)

DamnedAngel's picture

27-11-2017, 02:23

Hi oelsha,

Let's go for the results:

Registry Hacking
Adding the keys and values to the registry as you mentioned did not work - however, the error message changed to "Could not start openMSX Launcher". By your example on how to use your new executable, however, I found that the JavaHome you mentioned was not the java executable folder, but the folder which contained a "bin" folder, which contained the JRE. That meant that your launcher was probably adding a "bin" subdirectory to the JavaHome dir you fetched from Registry. My setup did not have such "bin" folder, so I added it under my javahome dir (which, BTW, is "C:\ProgramData\Oracle\Java\javapath" - don't ask, I don't know why), and copied java.exe to this dir. After that, the launcher worked (both older and newer version).

New executable
With proper registry keys, it worked right away, with no parameters, just like the older version. Without the Registry Keys, it failed as the older version too. With the proper path parameter, however, it worked like a charm - even without the registry keys. Thanks a lot for that!!!!

Please let me know if that info is what you expected. I will be happy to provide you with any additional data about my setup or about further tests in case you need them.

best regards!

By oelsha

Rookie (32)

oelsha's picture

27-11-2017, 05:18

@DamnedAngel

Thanks for doing the testing. For the Registry hacking, I don't know why your installed JRE doesn't have the expected Registry keys or why it gets installed in a different location. I have to look into that.
As for the new executable, I am glad it worked. I am going to put it up on the site for others to use in case they run into this issue.

Thanks again DamnedAngel and let me know if you encounter other issues.

Page 2/2
1 |