a) when using the installer packages
The installer packages contain launchers for QeD.
b) when using the archive
The archive doesn't contain a launcher so it has to be run like a regular Java application. The only restriction when running QeD is that you must specify the full path to the qed.jar file. Otherwise you will only be able to start QeD from it's directory! This is especially an issue on Linux (and probably other *nix systems as well) as you won't be able to create a working link/alias to start the program. I recommend that you remember this no matter what OS you are running. So in order to run the application just execute a command similar to the ones below (you don't have to be in the program directory):
java -jar "C:\Program Files\QeD 2.0\qed.jar"
java -classpath "C:\Program Files\QeD 2.0\qed.jar" Qed
java -jar /usr/qed20/qed.jar
java -classpath /usr/qed20/qed.jar Qed
If it starts then everything is OK, if not - you will have to configure the JRE.
When you don't want to configure your JRE you can run the commands above in a bit modified way (you still don't have to be in the QeD dir) - you will have to give the full path to the java file e.g.:
"C:\Program Files\Java\jre1.5.0_02\bin\java" -classpath "C:\Program Files\QeD 2.0\qed.jar" Qed
/usr/java/jdk1.5.0_01/bin/java -classpath /usr/qed20/qed.jar Qed
c) opening files on startup
If you want to specify which file to open on QeD startup you will have to pass the path and filename as the first argument of QeD. The path has to be full (starting with a drive letter in Windows or with a / in Unix) or relative to the directory from which you are running QeD. You can do it in any of the ways below (depending on your operating system and QeD package used):
java -classpath "C:\Program Files\QeD\qed.jar" Qed ..\..\FILE.cue
/usr/java/jdk1.5.0_02/bin/java -classpath /home/you/qed/qed.jar Qed ../cues/FILE.cue
When you have JRE configured properly in Windows (jar files associated with javaw.exe) you can just double click qed.jar and the app should start. I don't recommend this method though, because for me it always stopped working after a few weeks from installing JRE.
In Windows you can easily associate QeD with .cue files, just like any other application. Right click on a cue file and select 'open with'. A list of programs will appear - just select QeD (you might have to Browse for it first) and that's it. Alternatively you can select from any folder menu - Tools | Folder options | File types, find the cue file type and select QeD as the program to open with. The Windows installer can associate cue files with QeD (just press 'Yes' when asked about the association).
The Windows installer package comes with an included library called jRegistryKey. This library is used for determining what is your current default Internet browser. When using the QeD launcher this library is included automatically, but if you are starting QeD from the command line you will need to add the jRegistryKey.jar to the -classpath option of the java application. So to run QeD with the jRegistryKey library included you will have to execute one of the commands below:
java -classpath "jRegistryKey;C:\Program Files\QeD 2.0\qed.jar" Qed
java -classpath "C:\Program Files\QeD 2.0\qed.jar;.\jRegistryKey" Qed
java -classpath "C:\Program Files\QeD 2.0\jRegistryKey;C:\Program Files\QeD 2.0\qed.jar" Qed
You cannot run QeD with jRegistryKey using the -jar option of the java application.
jRegistryKey is not included in the zip archive, but you can download it from here. Just extract the files to a temporary directory, copy jRegistryKey.dll and jRegistryKey.jar into the QeD directory and run it according to the description above.
If anything is still unclear please ask at the