|Re: Eclipse IDE 2020‑06 (eclipse-inst-win64.exe) won't install on Win 7 Pro SP1 64-bit OS [message #1830308 is a reply to message #1830293]
||Thu, 23 July 2020 07:15
| Ed Merks
Registered: July 2009
That's strange. The installer's self-extracting executable looks for all the Java installations in the system registry and tests each one's version and bitness (32 versus 64). If it doesn't find a suitable one, it opens a browser page to help you find one to install. So it sounds like that's what happened and then you installed 64 bit version of Java 1.8. It seems the installer now finds that and tries to use it, but then it failed to launch. So I tried extracting exactly the 2u261 version and run the installer with exactly that version:|But that works for me so there's nothing strange or wrong about this latest Java 1.8 update...
"D:\stuff\eclipse-inst-win64.exe" -vm "C:\Program Files\Java\jdk1.8.0_261"
If you run "java -version" from the command line, does that work and print something like this:
"C:\Program Files\Java\jdk1.8.0_261\bin\java.exe" -version
java version "1.8.0_261"
Java(TM) SE Runtime Environment (build 1.8.0_261-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.261-b12, mixed mode)
I'd normally suggest just downloading a package from here:
But that's highly likely to fail the same way for the same reason.
One thing you could try is running
The -vm option only tells the installer explicitly which Java to use; if you don't specify that, it will typically use the one on the PATH, if that's an appropriate version. With the --debug flag, it will tell you what the self-extractor is doing, i.e., where it's putting things and which processes it's launching. When I do that it tells me it's extracting the installer to C:\Users\merks\AppData\Local\Temp\eoi2E94.tmp and then I can look in C:\Users\merks\AppData\Local\Temp\eoi2E94.tmp\configuration\.metadata\.log to see any logged problems that might have caused the launch to fail.
"D:\stuff\eclipse-inst-win64.exe" --debug -vm "C:\Program Files\Java\jdk1.8.0_261"
I'll need the debug information that is printed to the console and the contents of the .log to further diagnose your problem.
Professional Support: https://www.macromodeling.com/
Powered by FUDForum
. Page generated in 0.03546 seconds