MCExe64

MCExe64 is a configurable executable for launching Java applications.

Features of MCExe64

  1. MCExe64 reads its configuration from a .ejc file upon execution.
  2. Five Java configuration parameters read by MCExe64.
    • classpath = some.jar;other.jar
      Used by Java to find required JAR files. This is a required configuration option.
    • mainclass = org.fulano.ProgName
      Used by Java to start application. This is a required configuration option.
    • jre = jre-11.0.1
      Used to find the Java to run with. If not specified, the default value will be jre. When used, MCExe64 will append \bin\java.exe to the JRE variable.
    • usejre = T
      When true: MCExe64 will use Java where the jre variable points to. When false: MCExe64 will use Java from the Windows path. If not specified, the default value will be true.
  3. No external DLL files or libraries are required to run MCExe64.

Standard Installation Instructions

  1. Download program and source code archive from Sourceforge.net.
  2. Extract the MCExe64 .exe and .ejc files into a convenient directory for your Java application.
  3. Rename the MCExe64.exe file to the non-console desired name of the application.
    Rename the MCExe64C.exe file to the console desired name of the application.
    For example: If you want your application to be NiftyJava, rename MCExe64.exe to NiftyJava.exe for non-console operations, and MCExe64C.exe to NiftyJavaC.exe for console operations.
  4. Configure the .ejc file with the requisite values as described above.
    For example: Using the NiftyJava example from above, create NiftyJava.ejc and NiftyJavaC.ejc to match the executable names.
  5. Double-click the renamed MCE64 executables to run your application.
    Every time MCExe64 is run three files are created to help in diagnosing problems. The files are:
    1. MCExe64-Help.txt - Text file on how to configure MCExe64.
    2. <Program Name>-Env.txt - Text file showing the environment that started the program.
    3. <Program Name>.txt - Text file showing the result of reading the configuration file.
    If there are errors a fourth text file will be created showing the error generated. The error file will be <Program Name>-err.txt.
    The program will try to create these files in the same directory where the MCExe64 program is running from, but if that doesn't work, the program will try to write to wherever the TEMP environment variable is pointing.

Release Notes

Valid CSS!