You can start Jaikoz using /usr/bin/Jaikoz. Alternatively you can start Jaikoz with /usr/bin/jaikoz.sh
You can create links on your desktop for both these programs
If everything is OK there will be a short delay whilst Jaikoz initialises and then it should start
Select Path to Open a File Dialog and find the license file that you should have received by email (license.jai) and select Open. Then select OK to verify the license.
If the license is verified Jaikoz will start
This section discusses problems starting Jaikoz due to problems with your Java configuration
bash: java: No such file or directory.
There is a problem with your JRE Installation. Please ensure that Java is installed and can be found in your path
Unable to load help set
There is a problem with your JRE Installation. Please ensure that Java is installed and can be found in your path
Run the uninstall provided program with your OS. If you wish to completely remove the application folder and any work saved in it, you will have to delete this folder manually.
Warning this section is for experienced users of Java only
By default Jaikoz allows up to 800MB to be used for storing the information about your loaded files, this is additional to about 100MB that is required to run Jaikoz. If you are attempting to load many songs (more than 10,000) you may get a warning that memory is low, if your computer has sufficient memory you can increase the maximum value of memory than can be used you will be able to load larger amount of files if you require it. You should not set the memory to the actual amount that your system has because your computer requires some memory to run the operating system and other programs, additionally trying to load too many files may place too high a CPU load on your computer and could severely affect performance.
Jaikoz is usually run using Jaikoz.exe, but you can also run it using Jaikoz.sh, memory is adjusted differently depending on which file you use.
Within the Jaikoz.sh file , the parameters<string>-Xms150m -Xmx800m -XX:MaxPermSize=200m</string> sets the memory in megabytes. Increase the value of Xmx to the value you require, increase MaxPermSize by the same proportion i.e. to double total memory usage to 2GB set it to <string>-Xms150m -Xmx1600m -XX:MaxPermSize=400m</string>, adjust this value and run Jaikoz.sh for it to take effect
You can confirm you have made the change correctly when you start Jaikoz. Click on the Console tab at the bottom and the first line should say how much memory Jaikoz has been allocated. If you cannot see the console you may have hidden the Detail Pane, make sure it is checked in View/Show View Pane.
Jaikoz uses two log files, jaikozuser0-0.log contains the same information as is written to the Console Panel, it contains general information about what you've done within Jaikoz. The jaikozdebug0-0.log file contains warnings and debugging information that helps diagnose problems when running Jaikoz. These files are held in the Jaikoz folder in your home directory, for example /home/paul/jaikoz/logs and are renamed when they get to a certain size, the latest file is always called jaikozuser0-0.log, the next most recent is called jaikozuser0-1.log. if you require support with Jaikoz it is important to send both types of log files, to help diagnose the problem. The amount of logging written to the jaikozdebug0-0.log file can be adjusted, if you have a problem that you can reproduce it would be helpful if you could increase the amount of information logged, recreate the problem, send the logs and then return the logging to the normal levels.
You can send your logs and other support files from within Jaikoz by selecting Advanced/Create Support Files and then emailing the zip file created.
The following parameters effect logging
-l2 -m2
The -l2 parameter specifies how much logging output should be generated by Jaikoz, the -m2 parameter specifies how much output should be generated when reading and writing files. The number 2 can be replaced by any value from 1 to 7, a value of 1 is the minimum and a value of 7 is the maximum. Setting a high value will noticeably slow the performance of Jaikoz, so changes should only be made temporarily to diagnose a problem.