User manual

license making it show up on the support network under the correct IP and network access

permissions.

3. It will then start two processes - (1) the interface process (GUIapp.exe), and (2) the

MediaPlayer.exe process.

After it has finished, it will exit and be removed from memory. Support engineers can then upgrade

it remotely by replacing it with a new version.

GUIapp.exe

This process is used to display the control interface. When it starts, it will wait until a live control

socket to the MediaPlayer.exe is operational before loading the control. The way the interface

is displayed, screen, position etc, is controlled by the MediaSetting.xml file. Note: it is possible to

operate the software with the control hidden. This would be a more common method for a Video

out only installation with remote access only used to control the system.

MediaPlayer.exe

This is the playback engine of the MediaPlayer. It controls all playback, operates the automation

tasks and also acts as a http and ftp server.

Quitting the Application

To quit the application, you must exit both the GUIapp.exe and the MediaPlayer.exe. To do

this you need to set focus on the application you want to exit. For example, click on the video

display area (MediaPlayer.exe), then press “CONTROL-Q”. Click on the control area

(GUIapp.exe), then press “CONTROL-Q”.

Operating system optimisations

The operating system the MediaPlayer is installed on to should have a number of optimisations.

Some of these are performed by the upgrade process, but many cannot be and must be done by

hand. These include:

1. Removing the bootup graphic from the boot sequence (Adding /noguiboot to

boot.ini file)

2. Disabling the ability for switching users in the login preferences.

3. Disabling all autostart features on all drives and types. This is an important change that