By the use of commandline parameters you can access some minor functions of the ME Toolkit directly. To start the application with such a parameter do the following:
Starts the application with the tab „Uru (Language)“ in front if there is an Uru installation on the system, else it shows the „Welcome“ tab.
Hints: I. This parameter is ignored at the first startup after the installation, if you choose that there are other Uru Installs to configure.
II. Can only be combined with the „/usestaticpath“ parameter.
Starts the application with the tab „Myst IV (Language)“ in front if there is an Myst IV installation on the system, else it shows the „Welcome“ tab.
Hints: I. This parameter is ignored at the first startup after the installation, if you choose that there are other Uru Installs to configure.
II. Can only be combined with the „/usestaticpath“ parameter.
Starts the application with the tab „Myst IV (Journal)“ in front
Hints: I. This parameter is ignored at the first startup after the installation, if you choose that there are other Uru Installs to configure.
II. Can only be combined with the „/usestaticpath“ parameter.
This parameter starts the repair function for faulty Uru installs. The function reconstructs deleted Uru entries in the Windows registry.
Hint: I. Can only be combined with the „/usestaticpath“ parameter.
Ensures before an uninstall of the ME Toolkit, that an existing UserKI isn't removed by the uninstallation. This function is called automatically by the uninstall routine and is only relevant for users who want to uninstall the ME Toolkit manually. However this is not recommended as the automatic uninstall normally works better.
Hint: I. Can only be combined with the „/usestaticpath“ parameter.
Forces the ME Toolkit to load its related data from the path „c:\programme\yeesha“ , no matter where it was installed to. This function is only useful for development.