How can I install the JBuilder 3.5 Documentation, Professional, or Enterprise add-on under Windows NT or Windows 9x? The installer stops at the "Configuring Your Application" screen or will not launch.

This happens because the JBuilder Foundation add-on installers need to verify that you have JBuilder installed on your machine. If the installer runs on a JDK that does not include the classes that allow this, the installer will not be able to verify this and will appear to "lock".

To verify which JDK the installer is using, run "install.exe" and when the first progress bar is approaching 100%, hold the CTRL key down until it passes 100% and "Command Prompt"/"Dos Box" (console) opens. This will launch the installer in debug mode and allow it to provide debug output to the spawned console window.

When the installer has loaded the first "splash" screen, which allows you to pick your language, check the console window. You should see some output like this:

java.version       = <JDK version>
java.vendor        = <JDK Vendor>
java.home          = <Path to the Java or JRE executable>
...etc...

If java.version is anything other than "1.2.2" the installers will not work correctly.

If java.vendor is anything other than "Sun Microsystems Inc." the you are using an unsupported version of JDK 1.2.2.

If java.home is anything other than the path to the "jre" executable that was installed with JBuilder Foundation then the installer may not work.

If you find that you are not using the Sun JRE 1.2.2 that comes with JBuilder you can try the following solutions to make the installers work:

Re-Install JBuilder 3.5 Foundation:

This will help assure that you do not have a corrupt install. Be sure to follow these steps when doing so:

1. Back up your project files, if any.
2. Uninstall JBuilder by deleting the JBuilder directory
3. Delete the .jBuilder directory from your "home" directory.
4. Reboot the computer.
5. Disable any unnecessary applications that are running, including Netzip, Real Player, virus checkers, etc.
6. Re-install JBuilder Foundation.

Add the JRE executable to the System Path:

First, determine where the "bin" directory from the JRE that was installed with JBuilder is located. For example, if you installed to "C:\JBuilder35" then the JRE will be in "C:\JBuilder35\jdk1.2.2\jre\bin".

Open a console and type "set path=<Path to JRE bin directory>". For example, using the above mentioned path, type "set path=C:\JBuilder35\jdk1.2.2\jre\bin".

From this console navigate to the directory that contains the JBuilder "install.exe" file you would like to run. Run the install in debug mode again and check to see if it is using the JRE that you just added to the path. If it is using the correct JRE, proceed with the install.

Remove JDK references from the registry:

WARNING: Do not attempt the following steps if you are unfamiliar with editing the registry. Borland takes no responsibility for mistakes made or consequences from following these steps.

The idea here is to remove any conflicting JDK references from the registry so that the installer can find the correct JDK.

From the Start menu, select "Run..." and type in "regedit". Note for Windows NT users: do NOT use Regedit32.

Press F3 and, in the Search dialog that opens, type in JavaSoft. Regedit should stop on the key "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft". With this key selected, click the "Registry" menu and select "Export Registry File...". Be sure the "Export range" is set to "Selected Branch" and save the key to a file that you can remember.

Expand the JavaSoft Branch and Delete the following keys, if they are present:

• HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in
• HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Development Kit

Expand the "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment" key. If there are any keys below this one that are not "1.2" delete them.

Select the "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment\1.2" key and check the entry for "JavaHome". If this does not point to the JRE directory that was installed with JBuilder 3.5, you need to change it so that it does. If you change this value then you will need to change the "RuntimeLib" value as well. The appropriate path should be apparent.

Continue searching for "JavaSoft" just to be sure that there are no other keys besides "HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft". If you find more, modify them as above.

When done, exit regedit and restart the computer.

Run the install in debug mode again and check to see if it is using the JRE installed with JBuilder. If it is using the correct JRE, proceed with the install.

When the installer is finished (or if it still fails), you can restore the old registry settings by double-clicking the registry file(s) you exported.

The installer still fails:

We are still investigating install problems with JBuilder 3.5 and could use your help. We will need the debug output from the installer if you would like to help. Here are the steps to get the complete debug output (for Windows NT users only):

1. Launch the installer in debug mode and quickly press the PAUSE key when the console starts. If any output scrolls past, please try this step again.
2. Click the MS-DOS icon in the upper, left-hand corner of the console and select "Properties".
3. Select the "Layout" tab.
4. In the "Screen Buffer Size" section, set the "Height" to something like 500 lines.
5. Click OK and OK again on the pop-up dialog.
6. Press the ENTER key to allow the install to continue.
7. When the install stops/locks, go the console and click the MS-DOS icon again.
8. Select "Edit" and then "Mark".
9. Highlight all text in the console.
10. Open the MS-DOS icon menu again and do "Edit | Copy".
11. Paste the contents to a text file and save. You may exit/kill the installer at this time.

Now that you have the debug output in a file you need to get it to us. The best way to do this would be to open a Web Install Support case at:

http://pso.inprise.com/devsupport/

In the case notes, let us know that you have a debug output file to send to us. Do NOT paste the debug output into the case notes as it may be too large and could get lost.