Frequently Asked Questions

- Why does the player take so long to start?
- Where do I find the error log?
- Why doesn't the internal Browser View work on some Linux systems?
- How can I configure the data and configuration folders for a networked installation?
- Why can't I...?

Q. Why does the player take so long to start?

A. This is because the player has to wait until an application server (JBoss 3.2.6) starts on your machine. Once it has started, the player can talk to the Coppercore service (which is the engine behind the player) and retrieve the relevant information.

Q. Where do I find the error log?

ln the main menu of the player click "help", then "about" then choose "configuration details". There is then a button at the bottom of this window which says "view error log" .

Q. Why doesn't the internal Browser View work on some Linux systems?

The internal Browser View on Linux depends on the version of Mozilla you have installed and a few other factors. If the internal Browser View cannot be instantiated then the system Browser is used instead. In order to get this feature working, follow these instructions:

  1. Ensure that the “mozilla-browser” package is installed at /usr/lib/mozilla
  2. Ensure that the “libstdc++5” package is installed
  3. Add the line “export MOZILLA_FIVE_HOME=/usr/lib/mozilla” to the end of the file: /etc/environment

See this link for further information: http://www.eclipse.org/swt/faq.php#browserlinuxrcp


Q. How can I configure the data and configuration folders for a networked installation?

A. One problem when run on a network is that the LD Player will try to write to the installation folder located at reload-ldplayer/configuration. This might be a read-only folder for the networked user. To set this to another location suitable for each user, edit the reload-ldplayer/configuration/config.ini file and add the following, or similar, line:

osgi.configuration.area=@user.home/reload/ldplayer-workspace

Similarly, the user's default data location is set to @user.home/reload/ldplayer-workspace. You may change this in the reload-ldplayer/configuration/config.ini file by adding the following, or similar, line:

osgi.instance.area=@user.home/your_location

On the Macintosh version, the config.ini file is located inside the .app package. You will have to view the contents of the package in order to edit it.

Note - "@user.home" signifies the current user's home directory. You may replace this with an absolute location if you wish.


Q. Why can't I...?

A. We're still working on the Reload Learning Design Player. There are more features to come!