First, verify that you do not have any of the following problems:

1. You are running Solaris 2.5 (5.5) or earlier. JBuilder Foundation requires JDK 1.2.2 to run, and JDK 1.2.2 requires Solaris version 2.6 (5.6) or newer. Please see the JBuilder Foundation System Requirements page for more information.
   
   
2. You do not have enough space in your system's temp directory (usually named "/tmp"). The JBuilder Foundation installer for Solaris incorrectly calculates the necessary space needed in the temp directory for unpacking the product (it ignores the size of the bundled JDK). As such the installer does not report the correct amount of required space to the user. You will need approximately 100MB of space in your temp directory when installing JBuilder on Solaris. Also note that the installer will leave files behind in the temp directory when it finishes. You should delete these files as they can take up quite a bit of space and may prevent other installs from completing
   
   
3. You do not have the JDK on your system path. This will affect all of the installers except Foundation (because it includes the JDK) and the OpenTools documentation (because it is just an archive). The installers affected need a JDK to run on. Just add the "bin" directory of the JDK that was installed with JBuilder 3.5 Foundation to the path and be sure it is exported to the shell that will run the installer. For example (using sh):

   # PATH=/usr/local/jbuilder35/jdk1.2.2/bin:$PATH
   # export PATH
   # sh ./install.bin 
   

   You may alternatively specify the location of the JDK in the command line. For example (again, using sh):

   # sh ./install.bin LAX_VM /usr/local/jbuilder35/jdk1.2.2/bin/java
   

   
   
   
4. You are installing with a username that is longer than 8 characters (which is not strictly legal on Solaris). The JBuilder 3.5 installer attempts to check the file size of the install archive via "ls -l". If your username is longer than 8 characters then the "ls" output will be incorrect, for example:

   % ls -l /foo.zip
-rw-rw-r-- 1 longusernstaff 7401765 Sep 5 15:10 /foo.zip

   This causes the installer to see "Sep" instead of "7401765".

   To workaround this, install as root.
   
   

5. You have file systems mounted that causes your "df" output to break over more than one line, for example:

   Filesystem           1k-blocks      Used Available Use% Mounted on
   /dir1/dir2/AppDisk.img
                           629199    433636    163063  73% /usr/opt
   

   This may cause the installer to fail. You should temporarily unmount these items to workaround this.

If you can verify that you don't have any of the above problems, please follow the steps below:

NOTE: These instructions assume that you are logged in as "root" and are using "sh" for your shell. Be sure to adjust the commands for your shell, if different.

We are still investigating install problems with JBuilder 3.5 and could use your help. If you would like to help, we will need the debug output from running the installer on your machine. Here are the steps to get the complete debug output:

1. Open a console.
2. Create an environment variable named "LAX_DEBUG" and set it to true. For example:

   # LAX_DEBUG=true

3. Export "LAX_DEBUG" so that other shells can use it. For example:

   # export LAX_DEBUG

4. Run the installer. Observe the debug output that will be printed to your console window.
5. Copy ALL of this output.
6. Paste the contents to a text file and save. You may exit/kill the installer at this time if it has not already exited.

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

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

Let us know in the case notes 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/cut-off.