Recent Changes - Search:

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:

-debug Start the applet viewer in the Java debugger
-encoding <encoding> Specify character encoding used by HTML files
-J<runtime flag> Pass argument to the java interpreter

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:

-d32 use a 32-bit data model if available
-d64 use a 64-bit data model if available
-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.
-D<name>=<value>
                  set a system property
-verbose[:class|gc|jni]
                  enable verbose output
-version print product version and exit
-version:<value>
                  require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
                  include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
                  enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
                  disable assertions
-esa | -enablesystemassertions
                  enable system assertions
-dsa | -disablesystemassertions
                  disable system assertions
-agentlib:<libname>[=<options>]
                  load native agent library <libname>, e.g. -agentlib:hprof
                    see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
                  load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
                  load Java programming language agent, see java.lang.instrument
-splash:<imagepath>
                  show splash screen with specified image
Typing javac at the command prompt:

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

-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are used
-classpath <path> Specify where to find user class files and annotation processors
-cp <path> Specify where to find user class files and annotation processors
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-endorseddirs <dirs> Override location of endorsed standards path
-proc:{none,only} Control whether annotation processing and/or compilation is done.
-processor <class1>[,<class2>,<class3>...]Names of the annotation processors to run; bypasses default discovery process
-processorpath <path> Specify where to find annotation processors
-d <directory> Specify where to place generated class files
-s <directory> Specify where to place generated source files
-implicit:{none,class} Specify whether or not to generate class files for implicitly referenced files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-version Version information
-help Print a synopsis of standard options
-Akey[=value] Options to pass to annotation processors
-X Print a synopsis of nonstandard options
-J<flag> Pass <flag> directly to the runtime system

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
compressed filecommand to extract
jmaker1.jar or jmaker1.zipjar xf jmaker1.jar
jmaker1.zipuse a zip program like WinZip or use jar xf jmaker1.zip
jmaker1.zipYou may be able to right-click the file and choose "extract all" or a similar command
Examples of extracting the JMaker Files

JDK location

  1. Desired JMaker installation
  2. location of jmaker1.jar and
  3. current working directory

Command

c:\jdk

c:\jdk\jre\classes

c:\jdk\bin\jar xf jmaker1.jar

c:\jdk1.3

c:\jdk1.3\jre\classes

c:\jdk1.3\bin\jar xf jmaker1.jar

/home/user/jdk

/home/user/jdk/jre/classes

/home/user/jdk/bin/jar xf jmaker1.jar

/home/user/jdk1.3

/home/user/jdk1.3/jre/classes

/home/user/jdk1.3/bin/jar xf jmaker.jar

/user/java/jdk1.6.0_02

/home/user/jdk/jre/classes

/user/java/jdk1.6.0_02/bin/jar xf jmaker.jar

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
jmaker1 foldersubfolder or filecomment
jmaker1/batch/batch command files
jmaker1/config/configuration files
jmaker1/config/insert/text files for the Edit Window's insert function
jmaker1/help/help files
jmaker1/images/graphics used by JMaker
jmaker1/jsrc/sample .java and .fx files
jmaker1/project/project information
jmaker1/syntax/syntax highlighting styles
jmaker1/temp/all the Edit Window undo files
jmaker1/wizards/wizards
jmaker1/jmaker1.class.class files
jmaker1/other .class filesmore .class files

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

JDK locationLocation of JMaker1 installation current working directoryCommand
c:\jdkc:\jdk\jre\classesc:\jdk\bin\java jmaker1.JMaker1
c:\jdk1.3c:\jdk1.3\jre\classesc:\jdk1.3\bin\java jmaker1.JMaker1
/home/user/jdk/home/user/jdk/jre/classes/home/user/jdk/bin/java jmaker1.JMaker1
/home/user/jdk1.3/home/user/jdk1.3/jre/classes/home/user/jdk1.3/bin/java jmaker1.JMaker

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

Edit - History - Print - Recent Changes - Search
Page last modified on June 15, 2009, at 04:38 PM