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.
I tried to install the Netbeans IDE version 4.0 beta on an AMD Opteron running Solaris 10 (build 2004-08-05) and java version 1.5.0-beta3-b57 and got the following output: InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... .................The wizard cannot continue because of the following error: could not load wizard tree specified in /wizard.inf (106) Tried the workaround described in bug 26965 (Crash "... /wizard.inf (104)") but could not find jre/lib/endorsed; also the number in the message differs. That bug is for Windows OS, so possibly the workaround differs. Tried downloading and extracting netbeans-4_0-beta.tar.gz as another workaround. Running /netbeans-install-directory/bin/netbeans as directed in README.html hung at the final "eval" in the script with the netbeans_jdkhome variable unset. Tried setting netbeans_jdkhome on the command line: ; cd NetBeans4.0b/netbeans/bin ; netbeans_jdkhome=/usr/java ./netbeans :-) That finally worked! (I clicked No when asked if I wanted to import settings from previous 3.6 installation).
Please try to run with -is:log <log file name>. It will create log from native launcher. Please also try -is:javaconsole. It will output debug log from installer. It could provide us with more detail info what goes wrong.
Please report problem with NetBeans start up script as separate issue.
Created attachment 17536 [details] logfile produced by installer using -is:log option
-is:javaconsole produced no additional output
Startup script issue moved to bug 48802.
It might be duplicate of regression in JDK 1.4.2_06 b02. It is filed in Bugtraq/Bugster as issue #5108664. It causes exactly the same problem. (Though in our latest Solaris 10 build 68 installation I did not find JDK 1.4.2_06. Default JDK is: $ java -version java version "1.5.0_01-ea" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-ea-b02) Java HotSpot(TM) Client VM (build 1.5.0_01-ea-b02, mixed mode, sharing) $ whereis java java: /usr/bin/java Please check/verify this. Thanks. If you want I can send you simple test installer (about 2MB) to test it. It is also attached in issue given above. Let me know. Test is simple installer created using InstallShield wizard.
I downloaded and extracted the attachment and ran it as directed: java -Dis.debug=1 -jar TestInstaller.jar This successfully launched InstallShield, which successfully completed all steps including Finish. However, I still have the same problem with the NetBeans installer: : tomee@cabochon[49]; uname -a SunOS cabochon 5.10 s10_71 i86pc i386 i86pc : tomee@cabochon[47]; java -version java version "1.5.0_01" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_01-b05) Java HotSpot(TM) Server VM (build 1.5.0_01-b05, mixed mode) : tomee@cabochon[48]; ./netbeans-4_0-rc1-solaris-intel.bin InstallShield Wizard Initializing InstallShield Wizard... Searching for Java(tm) Virtual Machine... ...............The wizard cannot continue because of the following error: could not load wizard tree specified in /wizard.inf (106)
Installer native launcher uses its own way how to locate JVM to run on. It first looks for JDK 1.4.2_X. This problem happens with JDK 1.4.2_06 build 02. You must have this JDK somewhere on your system installed. I highly recommend to upgrade it to build 03. You can use command line option -is:javahome <path to JDK dir> and point it to JDK 1.5.0. If you use -is:log <log file> you will get output from native launcher which contains info from JVM search and it also gives info which JVM is used to run installer. Some build of Solaris 10 contains JD 1.4.2_06 build 02 with this problem. If you use Test.jar and run java it uses another JVM not JDK 1.4.2_06 installed on system.
Thanks! Installation worked when I ran netbeans-4_0-rc1-solaris-intel.bin \ -is:javahome /usr/jdk/instances/jdk1.5.0
*** Issue 52590 has been marked as a duplicate of this issue. ***
*** Issue 52730 has been marked as a duplicate of this issue. ***
*** Issue 54293 has been marked as a duplicate of this issue. ***