JBuilder 2005 Troubleshooting

Please read these instructions entirely before installing JBuilder 2005.

• Installing JBuilder 2005.
• Registering JBuilder 2005.

For additional information on

• configuring and using JBuilder 2005, please see the Release Notes.
• new features available in JBuilder 2005, see "What's New in JBuilder 2005".

Installing JBuilder

General

If the installation can be performed successfully on another machine (with the same OS platform), the resulting installation directory can be copied from one machine to another. This can be the easiest way to workaround installation problems, but is only useful when other machines on a network are available.

Error -1 when starting the installation program from a CD-ROM

This error occurs when the CD-ROM driver is having trouble reading from the CD. In this case, try copying the contents of the CD into a temporary directory on your hard drive and then launch the installer from that location. If the files cannot be copied from the CD-ROM to the hard drive because of read errors (e.g. error -1, read errors, etc.), check the CD for scratches. If the CD is visibly damaged, please call disk replacement to be issued new media by calling 831-461-9190.

If the contents of the CD-ROM still cannot be copied to the hard drive, an alternative is to simply download and install the appropriate trial version of JBuilder. The trial product will be converted to a full product by using your serial number during registration. Make sure that you choose the download that matches the license (e.g a serial number for Developer will NOT activate the Enterprise Trial). The Trial downloads may be accessed from the following location:

http://borland.com/products/downloads/download_jbuilder.html

In this case, make sure to download and install any supplementary files on the same page as the main download (e.g documentation, samples, extras).

The main installation program does not launch when the CD-ROM is inserted

To eliminate possible conflicts with other third-party software, disable anti-virus software (e.g. stop the service), exit out of any other currently running software, and then retest the installation.

In Windows XP, you can automatically do this using the msconfig.exe tool to restart your system in a diagnostic mode that prevent third-party services from starting up. To do this

1. Choose Start|Run.
2. Enter msconfig and click OK.
3. Under the General tab, select Diagnostic Startup and click OK.
4. Restart your system and start the JBuilder installation program again.

After successfully installing JBuilder, repeat these steps, changing Diagnostic Startup to your usual Startup mode.

Nothing happens after the installation program is started

If the main installation program does not automatically launch when the CD is inserted in to the CD-ROM drive:

1. Navigate to the CD-ROM drive.
2. Navigate to the Disk1\InstData\<platform>\VM\ directory.
3. Double-click on the installation executable (install.exe or install.bin in most cases).

The installation programs seems to start, but then freezes at the splash screen

To troubleshoot installation graphics driver issues, try the following:

• First, visit the website of the manufacturer of the graphics card to download and install the latest driver.
• Windows 2000/XP: If the issue is not resolved, try turning down the graphics card acceleration. To do this:
  1. Right-click on the desktop.
  2. Choose Properties|Settings|Advanced|Troubleshoot.
  3. Set the Hardware acceleration to None.
  4. Start the JBuilder installation program again.

Installing JBuilder as "root" (Linux or Solaris)

This note applies if you are installing JBuilder as a super-user through the "su" command or a different user from the one who started the X server process.

XWindows has security restrictions that can cause a GUI application to fail if running the application as a different user than the one logged in. One such case is when you open a terminal window and use the "su" command to become "root". The error message issued is usually 'Xlib: connection to ":0.0" refused by server'. This is a security feature, not a bug. To avoid this problem, open a terminal window and type the following commands:

xhost +localhost
export DISPLAY=yourmachinename:0.0

This command notifies XWindows that any user on your machine is authorized to use your display. After the installation you can run the command:

xhost -localhost

to reset the value to the default.

On Linux, another possible side effect of this is that you will get an icon for JBuilder 2005 installed on your desktop that does not work when selected. To fix this:

1. Log back in as root using the "su" command.
2. Copy the link created for the icon to your local desktop.

Insufficient available disk space reported with NFS volumes mounted (Solaris)

If you have any NFS volumes 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 installation, disable NFS before installing JBuilder, then re-enable it after the installation has successfully completed.

The installation progress bar stays near the end for a very long time (Linux)

In most cases, the installation will complete successfully after waiting for a while.

Running JBuilder

JBuilder hangs on startup or locks up at the splash screen

There are several possible causes for this problem. The most common are related to issues with your graphics driver.

To troubleshoot installation graphics driver issues, try the following:

• First, visit the website of the manufacturer of the graphics card to download and install the latest driver.
• Windows 2000/XP: If the issue is not resolved, try turning down the graphics card acceleration. To do this:
  1. Right-click on the desktop.
  2. Choose Properties|Settings|Advanced|Troubleshoot.
  3. Set the Hardware acceleration to None.
  4. Start the JBuilder installation program again.
• Try reducing the resolution and/or color depth. Many high-end graphics adapters have high-resolution modes that can cause some aspects of Java to experience difficulties.
• With certain video adapters you may experience some screen painting problems or crashes when running JBuilder. If this happens, try to uncomment a couple of lines in your /JBuilder/bin/jdk.config file:

  vmparam -Dsun.java2d.ddoffscreen=false
  #vmparam -Dsun.java2d.noddraw
  #vmparam -Dsun.java2d.d3d=false
  

  To uncomment the setting, remove the # symbol preceding the lines and try to run JBuilder again to see if the behavior improves.

If this fails to correct the problem, try one of the other troubleshooting suggestions described in the following sections.

JBuilder throws java.lang.NoClassDefFoundException or java.lang.Object for java.lang.NoSuchMethodError

This behavior might occur if a third-party JAR was placed in your JBuilder\lib or JBuilder\jdk\lib directory. This should rarely be necessary. Third-party JAR files should be placed in your JBuilder\lib\ext directory. There is only one sure way to resolve a corrupted JDK installation: Uninstall and then reinstall your JBuilder product. Make sure that you manually delete any residual files left over before you re-install JBuilder.

Exceptions are reported related to a third-party OpenTool

JBuilder has a plug-in mechanism, and the plug-ins that you can add to JBuilder are called OpenTools. There are a number of third-party OpenTools that typically come in the form of a JAR file and usually get installed to your JBuilder\lib\ext directory. Some OpenTools have been written for older versions of JBuilder and can cause your current version of JBuilder to fail to start. If you are having trouble getting JBuilder to launch, remove any OpenTools and re-start JBuilder.

JBuilder does not start or behaves strangely

There are some rare times that some unexplainable behaviors occur in JBuilder or it inexplicably will not start when it was working fine previously. One possible fix is to clear out your existing user settings so that new default ones will be used. To do this, delete the .jbuilder2005 and .primetimex directories in your "user home" directory. New default ones will be created the next time you launch JBuilder.

Warning: You should make a backup copy of these directories in case you want to borrow some of your previous settings, as you will lose all of them by performing this fix.

JBuilder runs slowly or is not painting correctly

If you are receiving out of memory error messages or exceptions, you need to increase the amount of available memory. Although JBuilder has minimum and preferred memory specifications listed you need to take into account that your operating system, other applications, and the application that you are developing take memory as well. The simple solution is to add more physical RAM to your machine.