Installation

<< Documentation Home | TOC | Desktop Shortcut >>

How to Install JMaker1

The short answer

Using JDK 1.6 or higher

• If the jdk is in the C:\JDK folder
• Then the tools are in the C:\JDK\bin folder
• Put the jmaker1 folder in the C:\JDK\jre\classes folder
• You may need to create the C:\JDK\jre\classes folder
• Run JMaker by typing C:\JDK\bin\java jmaker1.JMaker1

Note: Substitute your path for C:\JDK

The long answer

The JMaker1 Installation consists of 2 steps:

Step 1: Extracting the JMaker1 files using jar or another decompression program.
Step 2: Placing the 'jmaker1' files in one of the Java Virtual Machinge (JVM) classpaths for JMaker to operate properly.

Hardware requirements:

JDK 1.x does not require much.

• This is based on our experience. You may have a different opinion and your results may differ

1. JDK 1 - 90 mhz cpu or better (it will just barely run on a i486)
2. JDK2 - 233 mhz cpu or better
3. 64 Meg Ram or more.
4. Less than one megabyte of Hard Drive space required for JMaker1

The current version of the JDK requires more computer power.

Software requirements:

1. JVM ( Java Virtual Machine) to run JMaker1 - this comes with the JDK
2. JDK 1.1.8 or higher for Java development

• Why do you need the JDK?
  • The JDK the programs that you will use to compile the java files and to view applets.

Install

NOTE: Be sure the Java Development Kit (JDK) is correctly installed before installing JMaker.
Do not proceed with the installation of JMaker1 before the JDK is installed and working properly.
For information about downloading and installing the JDK see the Java web pages at java.sun.com.
You may test your JDK installation by successfully compiling and running java programs and by viewing java applets.

JDK install test

If you are not sure if the JDK is installed correctly:

1. At a command prompt go to the /bin folder of your JDK installation
   1. In windows this is something like cd C:\JDK6\bin
   2. In linux (as root) it is something like cd /usr/java/jdk1.6.0_02/bin
2. See what happens when you type "appletviewer", "java" or "javac" at a command prompt?
   • In linux you may need to type something like /usr/java/jdk1.6.0_02/bin/appletviewer or ./appletviewer
   • You will need to modify this if your path is different
3. You should see a list of options. See the examples below
4. If you see something like "unknown command" then the JDK is not correctly installed.

Typing appletviwer at the command prompt:

>appletviewer
Usage: appletviewer <options> url(s)

where <options> include:

The -J option is non-standard and subject to change without notice.

Typing java at the command prompt:

>java
Usage: java [-options] class [args...]

           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

where options include:

                  The default VM is client.

                  A : separated list of directories, JAR archives,
                  and ZIP archives to search for class files.

                  set a system property

                  enable verbose output

                  require the specified version to run

                  include/exclude user private JREs in the version search

                  enable assertions

                  disable assertions

                  enable system assertions

                  disable system assertions

                  load native agent library <libname>, e.g. -agentlib:hprof
                    see also, -agentlib:jdwp=help and -agentlib:hprof=help

                  load native agent library by full pathname

                  load Java programming language agent, see java.lang.instrument

                  show splash screen with specified image

Typing javac at the command prompt:

>javac
Usage: javac <options> <source files>
where possible options include:

Your results may be a bit different, but should be similar

Help - I'm a linux user and

I downloaded and installed the JDK but now I do not know where it is:
You can use the find command:
find / -type f -name appletviewer
If should give a result similar to this:
/usr/java/jdk1.6.0_02/bin/appletviewer

Make a note of the location of the JDK tools (javac, java, jdb, javap, javaw, appletviewer, jar, jarsigner, keytool, javah, native2ascii, policytool, rmic, etc). These are located in the 'bin' folder if the JDK installation.

Note the location of the JDK tools - in this example they are in "C:\jdk2\bin"

The JMaker1 Installation consists of 2 steps:

Step 1: Extracting the JMaker1 files using jar or another decompression program.
Step 2: Placing the 'jmaker1' files in one of the Java Virtual Machinge (JVM) classpaths for JMaker to operate properly.

Step 1 - Extracting the JMaker files

Extracting the JMaker files

Examples of extracting the JMaker Files

Notes:

• You can also extract jmaker1.zip using the jar command - see Extracting above.
• The jmaker1.jar and jmaker1.zip files contain the directory information to create the 'jmaker1' folder.

jmaker1 installation folders

This image shows JMaker in the /jre/classes folder (See Option 3 below)

Step 2: Placing the 'jmaker1' folder in one of the Java Virtual Machinge (JVM) classpaths for JMaker to operate properly.

There are at least 3 ways to get the JVM to find the JMaker1 classes.

How to put the jmaker1 folder in a JVM classpath

JDK 1.2 and higher will look in the jre/classes folder.

• If the jdk is in the C:\JDK folder
• Then the tools are in the C:\JDK\bin folder
• Put the jmaker1 folder in the C:\JDK\jre\classes folder
• You may need to create the C:\JDK\jre\classes folder
• Run JMaker by typing C:\JDK\bin\java jmaker1.JMaker1

Install Check

• Run JMaker1 to check installation.
• From a command prompt type:
• java jmaker1.JMaker1
• or Create a shortcut with "java jmaker1.JMaker1" as the target.

Examples of running the JMaker1 program

Note that the JVM is case sensitive when typing 'jmaker1.JMaker1'.
JMaker1 is packaged in the 'jmaker1' package. This is why 'jmaker1.JMaker1' must be used to run JMaker1.
If JMaker1 does not run then there are 2 possible problems.

Problem 1 'Bad command or file name'

The JDK is not installed correctly. Perhaps the PATH is not set to find the JDK's bin directory.
Solution: Check installation of the JDK. See ' java.sun.com ' for JDK installation help.
In windows this can be done in the autoexec.bat file by adding these 2 lines:
SET JDKHOME=c:\jdk
SET PATH=\bin

In some cases you may need to change
SET PATH=\bin
to:
SET PATH=;\bin

You will know the path is set correctly when you can type 'java' or 'javac' or 'appletviewer' at the command prompt and get a list of options.

• Typing java at the prompt in linux will give something like this:

$ java
Usage: gij [OPTION] ... CLASS [ARGS] ...

          to invoke CLASS.main, or
       gij -jar [OPTION] ... JARFILE [ARGS] ...
          to execute a jar file

Try `gij --help' for more information.

• Typing java at the prompt in windows will give something like this:

C:\>java
Usage: java [-options] class [args...]

           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

where options include:

    -client       to select the "client" VM
    -server       to select the "server" VM
    -hotspot      is a synonym for the "client" VM  [deprecated]
                  The default VM is client.

    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
                  A ; separated list of directories, JAR archives,
                  and ZIP archives to search for class files.

You can also provide the path to the tools as in typing:
c:\jdk\bin\java jmaker1.JMaker1
See option 3 above.

Problem 2 'Can't find class JMaker1'

The JVM cannot find the JMaker folder in a classpath.
Solution: Check the installation instructions above for solutions to this problem.

Repeat the Install Check section until you have solved both problems.

Low-impact installation

JMaker1 installs lightly on your computer.

Installing JMaker1:

1. Does not add any .dll or .exe files to your system
2. Does not make changes to the registry
3. Does not require alteration of the autoexec.bat or any .ini files
4. Does not change any menus or windows

Removing JMaker1

Delete the jmaker1 folder and any shortcuts you may have created.

Installation Notes