Customising an MS Windows Installation

This section applies if you installed Jim on a Microsoft Windows system. It describes how to tailor the installation if the programme will not start, if you wish to improve the performance of Jim, or if you want to run Jim's stand-alone tools in batch (text-only) mode.

In the installation directory are executables (.exe files) that are used to start Jim and the stand-alone Tools from the start menu. In a sub-directory called JExpress, there are properties files that are used when the Jim and the tools are run. For example, for Jim, there is a file called Jim.properties, which will have contents similar to that shown below:

#Menu for Jim
#Thu Apr 13 17:06:23 BST 2006
programName=Jim
args=-Dlicense.filename\=license.dat -Dlicense.debug\=false -ms16m -mx512m -cp .;xinapse.jar;itext.jar;mstemplate.jar com.xinapse.apps.jim.Jim
startDir=C\:\\Program Files\\Xinapse\\Jim4
execFilename=C\:\\PROGRA~1\\Java\\JRE15~2.0_0\\bin\\javaw.exe
      

1. If you receive messages from Jim that it does not have enough memory to load images, or if it hogs memory. The setting -mx512m allows Jim to use a maximum of 512 MB of memory, regardless of how much RAM your computer has. You can increase this number if you find that Jim runs out of memory. For example, to allow Jim to use a maximum of 1024 MB of memory, change it to -mx1024m

   The setting -ms16m set the amount of memory consumed by Jim immediately on startup, and should not need to be changed.

2. If Jim cannot find the license file, you can tell it explicitly where to look. Change the setting of -Dlicense.filename\=license.dat to give the exact path to the license file. For example:
   -Dlicense.filename\=C\:\\license.dat
   if you put your license file in the root directory of the C drive.

   N.B. you must 'escape' special characters such as = : and \ with an extra backslash character.

3. If Jim is still having problems with the license, you can turn on debugging messages from the licensing system, by setting -Dlicense.debug\=true.

   You will also need to change the java command from javaw.exe to java.exe in
   execFilename=C\:\\PROGRA~1\\Java\\JRE15~2.0_0\\bin\\javaw.exe
   in order to see the debugging messages in a console window.

You can customise the amount of memory used by each of Jim's stand-alone tools in exactly the same way above, to tailor the amount of memory used, etc. Do this by editing the appropriate .properties file for the tool.

Running the Stand-Alone Tools from Batch Files

WWW Xinapse Web Site