Program Files folder cannot be written and javaw error

[mikeberger]

Program Files folder cannot be written and javaw error

[mikeberger]

The .exe installer is needed to properly install on windows-7 or higher. The installer that I use (IzPack) will take care of running as Administrator when using the .exe version. The .jar installer does not run as Administrator and can't install properly in the default location.

It sounds like IzPack is having trouble finding the JRE.

Do you only have the JDK installed? Did you install the JDK without the optional JRE? Perhaps that is confusing IzPack. Is there a jre folder under the jdk?

[KarlosFanta]

Even though I only installed JDK, i do find a jre7 folder:
C:\Program Files\Java\jre7
containing: readmes and licences and
Folder bin containing 85 files and 3 folders (dtplugin, plugin2, server)
and folder lib containing 27 Folders and 531 files.
but I'm glad that i got the jar to work (with admin via cmd).
On 2014/11/27 06:43 PM, Mike Berger wrote:

The .exe installer is needed to properly install on windows-7 or
higher. The installer that I use (IzPack) will take care of running as
Administrator when using the .exe version. The .jar installer does not
run as Administrator and can't install properly in the default location.

It sounds like IzPack is having trouble finding the JRE.

Do you only have the JDK installed? Did you install the JDK without
the optional JRE? Perhaps that is confusing IzPack. Is there a jre
folder under the jdk?

—
Reply to this email directly or view it on GitHub
#12 (comment).

[mikeberger]

Someone else reported a similar problem. It was caused by Java 8 in that case. I have been unable to create a working .exe installer using IzPack. The .exe created by Izpack cannot find java 8.

I switched to use launch4j to create the installer .exe and it seems to work. The latest installer is here if you want to give it a try: https://github.com/mikeberger/borg_calendar/releases/tag/v1.8.1_beta3

I think that Launch4j is better at finding java than IzPack. So, even if this problem is not due to having java 8 on your machine, perhaps the new launcher will fix it.

[mikeberger]

Hopefully this is fixed in release 1.8.1, which is now available.