In fact, I do this to run AMIDST from a batch file which points to the JRE. It is possible to use the bundled runtime to run other Java programs, which I highly recommend instead of installing Java just to run an installer.
OH, and another thing, when you are on the Optifine download page, if you want to bypass the adware, click on (mirror) My usual advice is to install the latest 64 bit JRE from Your operating system can't access this JRE so it doesn't know what to do with the Optifine. Install the official Oracle JDK/runtime and use that instead.This usually happens with people that haven't installed Java on their machine and are relying on the embedded Java JRE that is in each Minecraft.jar. Install OpenJDK8 and run Minecraft et-al against thatĢ. So I think your best bet would be to either:ġ. Outside of that, the only other fix would be to update the source code for the original programs to take these changes to the Java language into account - But that's blatantly not feasible, unless you're secretly Notch, or working for Microsoft! So an alternative fix might be to download and install the official Oracle JDK/runtime. I also believe that they recommend using the Oracle JDK/runtime to run it too.
I'll try to look into that for you when I get a chance.Īlso: AFAIK Minecraft is built using the official Sun/Oracle Java SDK. It's not something I've ever had to deal with before. I believe it's possible to have multiple versions of the JDK/runtime installed, but offhand - I don't know how you'd go about specifying which JDK/runtime to use for a particular application.
It's also mentioned in JEP261, which is one of the JDK Enhancement Proposals.įrom what I can see, it looks like the only fix/workaround is to install and use OpenJDK8 for Minecraft (and forge/optifine). But I don't fully understand the document, so I'm not entirely sure if this is a bug, or a deliberate "feature". The OP in the thread is attempting to run a java based program in OpenJDK9 and is getting the same error as you.įrom a quick look at the document linked by the only responder to that post (see pages 32 and 33), it appears to be some kind of backwards incompatible changes that were introduced into openJDK9, which affects the main application loader class.
It's a different program, but they are experiencing exactly the same error message. From a quick bit of duckduckgo-fu, I found someone with a similar problem:
0 kommentar(er)
