Frequently Asked Questions:
Q: What does "Installer JAR" mean?
A: Starting from Version 2, Magellan does not consist of just one file any more.
We have divided it into several files. In order to keep the installation of Magellan simple,
we have packaged the program into one file called "Installer JAR". It's a Java program, just like
Magellan itself. It unpacks its content to a location you can specify during installation.
Starting from version 2 it is also possible to copy a new version over an old version without first de-installing the old version. The configuration files are conserved and adjusted when you start magellan the next time.
Q: magellan-client.jar? Shouldn't the file be called magellan.exe?
A: No. To be honest, it is (almost) nothing more than a renamed ZIP-file, but one that Java can handle and that you therefore don't need to unpack with WinZip or a similar program. Magellan really consists of a lot of files that are simply gathered within magellan-client.jar, but Magellan should start when the JAR-file is double-clicked.
Q: Why does another program (e.g. WinZip or PowerArchiver) start, when I try to start Magellan by double-clicking?
A: Because it is set to be the default program for the .jar extension instead of Java. In PowerArchiver and WinZip you can undo that in these programs' options, otherwise some manual action is needed:
Q: Why doesn't Magellan start when I click the file magellan-client.jar?
A: A possible cause for this is that the file magellan-client.jar is in a folder with a name that has spaces in it. This isn't a problem that is caused by an error in Magellan, but by an inconvenience in the default link between .jar-files with java.
The simple solution is of course to move Magellan to a different folder. The complex solution is as follows:
Background: If Magellan is in C:\My Documents\magellan-client.jar, then the regedit entry would try to initiate java to call (Path to Java)\javaw.exe -jar C:\My Documents\magellan-client.jar, which means that java would try to run the file C:\My with parameters Documents\magellan-client.jar, which doesn't quite work out right. With the quotes this looks like this: (Path to java)\javaw.exe -jar "C:\My Documents\magellan-client.jar", and here the actual magellan-client.jar file is started.
If this didn't help you can try to start Magellan from the commandpromptto be able to read possible error messages.
Q: How do I make Magellan the default program for CR-files under Windows2000/XP?
A: To do this you need to set up a link between Magellan and the "CR" filetype. You can do this in Explorer under Extras, Folderoptions, Filetypes:
Q: How do I start Magellan from the commandprompt?
A: Magellan (or Java) often only gives error messages at the command prompt, therefore it can be useful to start Magellan from here.
To do this you first start the command prompt (in Windows ME under Start menu open 'Run', type command and click OK, under Windows 2000/XP the command is cmd). Then enter the following command: javaw -jar "(Path to Magellan)\magellan-client.jar", so e.g. javaw -jar "C:\My Documents\magellan-client.jar".
The commandprompt parameters for Magellan are listed in the Reference.
Q: How do I get Magellan to run on a Mac?
A: Unfortunately Apple has only with the Mac OS X just released a current Java-version that will support Magellan. To run Magellan use the console the same as under Windows at the command prompt.
Q: How do I handle resource paths?
A: Resource paths are described on their own site.
Q: Even though I have enough RAM, Magellan reports a lack of memory. Why?
A: Simply allocate a bit more memory for the Java Virtual Machine (VM). Magellan requests memory from the VM, and when VM does not have any to give, Magellan simply fails.
You can allocate memory as follows:
Create an icon for Magellan on your desktop, right-click on it and go to "Properties". Under "Target" enter the following (the path should of course match your particular setup):
C:\Program Files\Java\jre6\bin\javaw.exe -Xms128M -Xmx512M -jar "c:\Program Files\Eressea\Magellan\magellan-client.jar" or simply
javaw -Xms128M -Xmx512M -jar "c:\Program Files\Eressea\Magellan\magellan-client.jar"
Under Linux simply type (in the shell, in the magellan
java -Xms128M -Xmx512M -jar magellan-client.jar
This tells the Java-VM to allocate a minimum of 128MB and a maximum of 512MB. You can change these values according to your own setup.
Q: Why does Magellan all of a sudden not use Base-36 numbers for the units anymore?
A:Most like the 36;Basis tag is missing in the CR. This basic tag defines the number base that Magellan uses. For Eressea-CRs this usually is 36, other PBeMs using older CR-versions (e.g. Verdanon) use decimal (base 10) and don't know this tag. That's why Magellan assumes base 10 when there is no mention of another number base in the CR.
Q: How can I use Vorlage to automatically confirm the orders of units?
A: With // #tag EINHEIT ejcOrdersConfirmed 1
Q: I just don't get the ARR, ATR or the Tooltips!
A: A good help to ARR, ATR and the Tooltips can be found here.