|
|
|
|
|
|
|
|
|
Re: Everythings perfect. But Eclipse installer can't install it for a reason that it can't find the [message #1816841 is a reply to message #1816837] |
Fri, 08 November 2019 06:35 |
Ed Merks Messages: 33258 Registered: July 2009 |
Senior Member |
|
|
Looking at the C code of the latest version, this result seems almost impossible.
You're sure that Downloads contains just one version if eclipse-inst-win64.exe? Whenever I download a new version (with Firefox), I end up with a numbered version. E.g., my most recent download is eclipse-inst-win64(43).exe. So you're sure your Downloads doesn't contain a whole whack of such numbered versions such that you're not actually testing on the command line the most recently download version?
If you're sure you're testing the most recently downloaded version from the link I gave, will you be willing to help further, i.e., if I add more debug trace statements, to figure out where things are going wrong?
Because currently what you are describing suggests that the code doesn't just crash, but it really gets to the point of opening the browser link. So the code must have looked for javaw.exe in every folder on the PATH, and must of found none because there's no trace output from it testing any of JVMs, which also suggests that JAVA_HOME and the registry also did not find any folders to test. To understand why that's the happening, I'd really need more debug tracing, e.g., printing out every folder on the PATH that is tested for the presence of javaw.exe.
The native executable did change 2019-04 so it's possible that something newer is not working well for you... Mostly the support was for adding command line processing support and I changed the way command lines are launched to properly support "wide characters" to ensure that the command line can specify arbitrary unicode characters and that those arrive properly in the Java application...
Do you the default encoding on your OS?
I looked at this to see how that can be determined:
https://superuser.com/questions/670197/finding-out-the-default-character-encoding-in-windows
So I ran PowerShell and executed that:Quote:Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\merks> [System.Text.Encoding]::Default
IsSingleByte : True
BodyName : iso-8859-1
EncodingName : Western European (Windows)
HeaderName : Windows-1252
WebName : Windows-1252
WindowsCodePage : 1252
IsBrowserDisplay : True
IsBrowserSave : True
IsMailNewsDisplay : True
IsMailNewsSave : True
EncoderFallback : System.Text.InternalEncoderBestFitFallback
DecoderFallback : System.Text.InternalDecoderBestFitFallback
IsReadOnly : True
CodePage : 1252
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.09102 seconds