FAQ: JBuilder Foundation Installation
Category: Install
Platform: Linux, Solaris, Windows NT
Date: January, 2000

JBuilder Foundation Installation FAQ

Please visit the JBuilder newsgroups at http://www.borland.com/newsgroups for more information about JBuilder Foundation installation issues.

JBInstall_01: What's the difference between JBuilder Standard and JBuilder Foundation?

JBInstall_02: When will the Professional and Enterprise versions be available?

JBInstall_03: Why can't I use my JBuilder libraries with JBuilder Foundation?

JBInstall_04: What distributions of Linux will JBuilder Foundation run on?

JBInstall_05: What problems are there running JBuilder Foundation on Windows 9x?

JBInstall_06: When I try to install JBuilder Foundation on my Linux machine, I get an error stating that I have insufficient disk space. Why is this?

JBInstall_07: When I try to install JBuilder Foundation on my Linux machine (after installing JDK 1.2.2), the installer doesn't find my JVM. The JDK is on my PATH. Why is this?

JBInstall_08: When I try to install JBuilder Foundation on my Solaris machine the installer fails (exits or locks up). Why is this?

JBInstall_09: When I try to install JBuilder Foundation on my Linux machine the installer fails (exits or locks up). Why is this?

JBInstall_01: What's the difference between JBuilder Standard and JBuilder Foundation?

• JavaBeans Component Library (JBCL)
• JDK switching
• Deployment Wizard
• Classes with tracing disabled view (debugger)
• Execution log (debugger)
• Dialog Wizard
• Frame Wizard
• Panel Wizard
• Implement Interface Wizard
• Override Methods Wizard
• Printed documentation

JBInstall_02: When will the Professional and Enterprise versions be available?

They are available now! You can order them directly from Borland at:

http://shop.borland.com

JBInstall_03: Why can't I use my JBuilder libraries with JBuilder Foundation?

The Inprise/Borland value-added libraries, such as DataExpress and JDataStore, are available with JBuilder 3.5 Professional and Enterprise.

JBInstall_04: What distributions of Linux will JBuilder Foundation run on?

JBuilder Foundation has been tested on RedHat Linux 6.x and Mandrake Linux 6.x. It should run on any distribution, provided that the distribution can fully run the JDK 1.2.2 as released by Sun and Inprise. Tests with the current version of Corel Linux and Debian showed incompatibilities caused by an older version of glibc. JDK 1.2.2 requires glibc 2.1.1 or higher to run correctly. Your Linux distribution will also need kernel version 2.2.5 or above. For more information on system requirements, please see:

http://www.borland.com/jbuilder/productinfo/sysreq.html

JBInstall_05: What problems are there running JBuilder Foundation on Windows 9x?

We are aware of two problems running under Windows 9x:

• Out of environment space error message
• Graphical glitches

Out of environment space error message

When you first launch JBuilder Foundation from the DOS prompt under Windows 95 or 98 you may see the message: Out of environment space. JBuilder stops loading.

When this message is displayed, the command session (DOS) prompt has filled the small amount of memory reserved for storing environment settings like PATH and CLASSPATH, etc. On Windows 9x, the command prompt defaults to a setting of Auto, which means that very little memory is reserved. To change this amount:

1. Open the DOS prompt.
2. Click the DOS prompt icon in the upper left of the command prompt window.
   The DOS prompt menu commands are displayed.
3. Choose Properties to display the Properties dialog box.
4. Choose the Memory tab.
5. Set the Initial Environment memory to 4096.
6. Click OK.
7. Type exit to close the DOS session.
   The change does not take effect until you restart the DOS session.

Graphical glitches

Graphical glitches are visible on some machines running Windows 95 or 98. If you see graphical problems, look at the following Developer Support FAQ for more information and possible workarounds: http://community.borland.com/article/1,1410,19677,00.html.

If the above link does not work then you can also find the article by searching for "jbuilder" and "painting".

If the solutions suggested in the FAQ do not solve your problem, try this workaround:

For JBuilder Foundation v. 3.1:

1. Open jbuilder.bat in a text editor, such as Notepad. The jbuilder.bat file is located in the bin directory of your JBuilder installation.
2. Find the line near the top of the file that starts with:
   set vmargs=
3. Add the following option after the = sign:
   -Dsun.java2d.noddraw
   Do not insert a blank space after the = sign.
4. Save the file.

For JBuilder Foundation v. 3.5:

1. Open jbuilder.config in a text editor, such as Notepad. The jbuilder.config file is located in the bin directory of your JBuilder installation.
2. Add a line like this to the file:
   vmparam -Dsun.java2d.noddraw
3. Save the file.

JBInstall_06: When I try to install JBuilder Foundation on my Linux machine, I get an error stating that I have insufficient disk space. Why is this?

If you have non-local file systems mounted, the installation may fail with an error reporting insufficient available disk space. If you encounter this error and are certain that you have enough disk space available for the installation, unmount NFS and SMB shares, install JBuilder, then re-mount the shares after the installation has successfully completed.

This error message can also occur if available disk space information, as reported to the installer from df, is split over two lines.

Some example df output follows:

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

With the information split over two lines, the install procedure cannot retrieve the available space from the df output. If you rename the disk so the df output is on a single line and the install should complete.

JBInstall_07: When I try to install JBuilder Foundation on my Linux machine (after installing JDK 1.2.2), the installer doesn't find my JVM. The JDK is on my PATH. Why is this?

First, make sure that the entry on your PATH points to the bin directory of the JDK, i.e. /usr/local/jdk1.2.2/bin. If you only set the PATH to something like /usr/local/jdk1.2.2, the installer will not work.

In addition, you need to export your PATH. When you run the JBuilder Foundation installer, you are spawning a new shell. This new shell must have access to your PATH variable so that the installer can find the VM. In order for the new shell to access variables from its "parent" shell, you have to export those variables.

To export the PATH, enter this command before running the installer:

export PATH=/usr/local/jdk1.2.2/bin:$PATH

You can make the path to the JDK shorter by creating a symbolic link to it:

ln -s /usr/local/jdk1.2.2/jdk
export PATH=/jdk/bin:$PATH

Note: Symbolic links to the JDK directory will work, but symbolic links to the JDK bin directory or the java executable itself won't work.

You can also try passing the location of the Java VM on the command line:

sh install.bin LAX_VM <path_to_VM>

JBInstall_08: When I try to install JBuilder Foundation on my Solaris machine the installer fails (exits or locks up). Why is this?

We have found three possible reasons for this:

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.
3. Install Anywhere seems to have problems running under JDK 1.2.2 on some machines. We suggest that you try to install JBuilder using a 1.1.x JDK or JRE. Note that you will still need to have JDK 1.2.2 installed to run JBuilder. You can find more information about 1.1.x JDK's/JRE's for Solaris here:

   Sun's 1.1.x JRE page
   Sun's 1.1.x JDK page

   NOTE: This workaround will allow you to install and use JBuilder 3.5 Foundation, but the Professional, Enterprise, Documentation and JDataStore installers will not work with JDK/JRE 1.1.x becuase they do not include the classes from java.lang.jar.

JBInstall_09: When I try to install JBuilder Foundation on my Linux machine the installer fails (exits or locks up). Why is this?

We have found two possible reasons for this (assuming that you already meet the System Requirements):

1. If your display color depth is set to 16-bit color (65536 colors) you should try changing this to another setting. Any setting besides 16-bit color seems to help (as long as your video card and X-Server support it).
2. Install Anywhere seems to have problems running under JDK 1.2.2 on some machines. We suggest that you try to install JBuilder using a 1.1.x JDK or JRE. Note that you will still need to have JDK 1.2.2 installed to run JBuilder. You can find more information about 1.1.x JDK's/JRE's for Linux here:

   Blackdown.org's Java ports page

   NOTE: This workaround will allow you to install and use JBuilder 3.5 Foundation, but the Professional, Enterprise, Documentation and JDataStore installers will not work with JDK/JRE 1.1.x becuase they do not include the classes from java.lang.jar.