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.

Bug 52730 - Installer fails to launch on JDS
Summary: Installer fails to launch on JDS
Status: CLOSED DUPLICATE of bug 48633
Alias: None
Product: installer
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: mslama
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-21 12:00 UTC by Roman Strobl
Modified: 2006-03-24 13:06 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roman Strobl 2004-12-21 12:00:48 UTC
[Netbeans 200412210916; JDS R3; JDK 1.5.0_01]

When I launch installer on JDS I get following
text on command line:

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)

This error occurs in latest builds. The last build
which I can install is 200412141900, all newer
produce this message.

I have also tried to install Netbeans from the jar
and that works fine, there's no error there.
Comment 1 mslama 2004-12-21 12:26:39 UTC
As usual. It is known issue of JDK 1.4.2_06 build 02. Update to build
03. Installer first searches for JDK 1.4.X.

*** This issue has been marked as a duplicate of 48633 ***
Comment 2 mslama 2004-12-21 12:27:54 UTC
Try with -is:log <log file> to find out what JVM is found by native
launcher.
Comment 3 Roman Strobl 2004-12-21 13:59:19 UTC
Yes, you're right, upgrade to b03 helped. Note that version
1.4.2_06-ea-b01 is default in JDS R3 so JDS users will get into this
kind of trouble. The strange thing is that the problem occurred only
for builds newer than 200412141900, earlier there was no problem.
Verified.
Comment 4 mslama 2004-12-21 14:05:14 UTC
It might be caused by recent changes in installers: I made JVM
resolution for all installers/uninstallers the same. First JDK 1.4.X
is searched by native launcher.