This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
After running the 3.5 Beta installer, a progress indicator is displayed indicating it is looking for suitable JDK, then it is hidden and nothing more happens. Environment is: - Win XP Pro, 512MB RAM - JDK 141 and 131 installed (3.4.1 runs ok) Can make my computer available for testing.
Ups I didn't seen this bug. Sorry for late response. I should look what happen on your computer.
It is strange. I saw this problem on your machine but I'm not able to reproduce this bug on my machine. Used jdk - 1.4.1_02-b06 and 1.4.1_01-b01 - but Win2000 not XP .
OK, after jdk1.4.1 reinstall on Ian's machine installer works. Probably we need to add release note that sometimes reinstallation of jdk1.4.1 is necessary.
What is your opinion Patrick?
Proposed relnote: When running on Microsoft Windows systems and JDK version 1.4.1 is installed, the NetBeans IDE installer fails while looking for a suitable JDK version. Workaround: Run the installer again
Oops, I guess the workaround is to reinstall the JDK. Is this the best workaround? Or should we also suggest the user install from the zip file?
In case of Ian's machine reinstallation helps. I think issue's occurence will be low.I propose something like "If installer doesn't start on winXP and jdk1.4.1, try to reinstall your jdk.If it doesn't help use another jdk or download archive"
How about? Description: In some cases, when running on Microsoft Windows XP systems and JDK version 1.4.1 is installed, the NetBeans IDE installer fails while looking for a suitable JDK version. Workaround: Reinstall the JDK software. If the problem persists with that JDK version, try a different JDK version.
I like it.
Yet another dup of issue #30767?
Don't thing so.
Comment from A.R.Butler (sent directly): I also had the install issue described in 32958. I suspect re-installing the jdk may be a read herring. I did re-install but was still suffering the problem. On a whim, I temporarily renamed the environment variable JAVA_HOME to JAVA_HOME1 and the install proceeded correctly. I hope this helps identify the problem. thanks!
George, is this bug still relevant? Related to currently arising issues maybe?
I don't know if this is related to any issues. I took a quick look at the issue descriptions open for the installer and nothing seemed to fit. I think it is no longer relevant.
removing RELNOTE keyword