Specifying JRE 5

From RifidiWiki

Jump to: navigation, search

Some users may notice that Rifidi Designer or Rifidi Tag Streamer may not work correctly on their computer. This problem may exist because the user is running a version of the Java Runtime Environment (JRE) that is not JRE 5. To check for this problem:

  1. Go To Start -> Run
  2. Type 'cmd'
  3. At the command line type 'java -version'

If your version of java is anything other than 1.5 (or minor versions of 1.5, such as 1.5.0_12), The Rifidi product may not run correctly.

If your version is less than 1.5 (or you don't have JRE installed):

  1. Go to http://java.sun.com/javase/downloads/index_jdk5.jsp
  2. Download JRE 5.0 update 14.

If your version is greater than 1.5 (such as 1.6):

  1. Check to see if you already have 1.5 installed
    1. Go to Start -> C:
    2. Navigate to C:\Program Files\Java

If you see a directory that starts with 'jre1.5' or 'jdk1.5', then you have the correct JRE installed, it is just not your default JRE.

If you don't have it installed please follow the instructions above to install it.

If you do have the correct JRE install, but another version is the default version, you have two options.

  1. Uninstall the other version. Often, JRE 6 will override JRE 5. You can uninstall JRE 6 through the add/remove programs function in windows
  2. You can specify the path to the JRE that you want to use via the command line when you start up a Rifidi Product. To do this:
    1. Open up a command prompt
    2. Navigate to the directory that directory where the Rifidi product is installed.
    3. Open the Rifidi product with a command such as:
      'RifidiStreamer.exe -vm "c:\Program Files\Java\jre1.5.0_14\bin\javaw.exe'

Note that this command should change depending on the path to the correct javaw.exe file. Also, if you have already tried to run the program (either tag streamer or designer) via double cliking on the shortcut and ran into the jre-6 problem, you may need to uninstall streamer or designer and reinstall it for this workaround to run.

Personal tools