Date of this edition: November 20, 2009
Target OS: This software is compatible with target systems running QNX® Neutrino® 6.4.0 or 6.4.1.
Host OS: You must have already installed the QNX® Software Development Platform 6.4.0 or 6.4.1 as a self-hosted QNX Neutrino system, or on one of the following hosts:
|Version of QNX SDP||Microsoft Windows||Linux|
|6.4.0||Windows Vista, Vista 64-bit, XP SP2 or SP3, or 2000 SP4||Linux Red Hat Enterprise Workstation 4 or 5, Red Hat Enterprise Server 5.1 64-bit, Red Hat Fedora Core 6 or 7, Ubuntu 6.0.6 LTS or 7, or SUSE 10|
|6.4.1||Windows Vista, Vista 64-bit, XP SP2 or SP3, or 2000 SP4||Linux Red Hat Enterprise Workstation 4.0 or 5.0, Red Hat Enterprise Server 5.1 64-bit, Red Hat Fedora 10, Ubuntu 8.04 LTS or 8.10, or SUSE 11|
To support USB transport connections to iPods (“one-wire” connections), you need the following patch:
The table below lists the minimum disk space requirements (in megabytes) for installation of the different MME components, as well as component dependencies.
|QNX Aviage Multimedia Core 1.2.0||63||190||80||None|
|QNX Aviage Multimedia Software Codec for AAC 1.2.0||9||19||29||Core|
|QNX Aviage Multimedia Software Codec for MP3 1.2.0||8||19||28||Core|
|QNX Aviage Multimedia Software Codec for WMA9 1.2.0||11||21||31||Core|
|QNX Aviage Multimedia Interface for iPod 1.2.0||9||19||28|| Core
Software Codec for AAC, if AAC codec support is required.
|QNX Aviage Multimedia Interface for PlaysForSure 1.2.0||8||19||28|| Core
Software Codec for WMA9, if WMA9 codec support is required.
Interface for WMDRM10-ND, if DRM support is required.
|QNX Aviage Multimedia Interface for WMDRM10-ND 1.2.0||8||19||28||Core
Interface for PlaysForSure
|QNX Aviage Multimedia Interface for Zune 1.2.0||8||18||28|| Core
Interface for PlaysForSure
|QNX Aviage Multimedia DVD Playback 1.2.0||11||20||30|| Core
Aviage Multimedia Suite 1.2.0 Intel Performance Primitive Codecs package: patch-640-1507-ipp-decoder.tar
Aviage Multimedia Suite 1.2.0 A/V Sync patch: patch-640-1521-av-sync.tar
|QNX Aviage Multimedia Interface for TI OMAP Codec Engine 1.2.0||n/a||n/a||625||Core|
For information about what's in this release, see the Release Notes. For the latest version of this Installation Note or the Release Notes, go to our website, www.qnx.com, log into your myQNX account, then go to the Download Center.
This section explains how to install the QNX Aviage Multimedia Core 1.2.0 and optional components. For detailed information about supported hosts and targets, see the release notes. For information about how to get the QNX Aviage Multimedia Suite's MME (MultiMedia Engine) up and running, see the chapter “Quickstart Guide” in Introduction to the MME.
If you are upgrading from an older version of the QNX Aviage Multimedia Suite, before you begin the installation you need to:
|Before restarting the MME, you will also need to replace the QBD configuration file, qdb.cfg, as instructed in the Quickstart Guide chapter of Introduction to the MME.|
# chmod a+x qnxaviage-mmedia-core-1.2.0-200904231718-nto.sh
On Ubuntu hosts, you must run the installation script with the sudo command -E option in order set the correct environment for the installation. For example:
# sudo -E ./qnxaviage-mmedia-core-1.2.0-200904231718-linux.bin
|If you have more than one version of QNX SDP that co-exist on your system (for example, 6.3.2 and 6.4.n, where n is the 6.4. version number):
|Windows XP SP2 may display a security warning the first time you install the QNX Aviage Multimedia Suite. You can verify the checksums for the installation package when you download the file from our website.|
To install optional components, download the appropriate installation package and follow the instructions for installing the QNX Aviage Multimedia Core 1.2.0 for the host OS, substituting the appropriate name where required, and taking note of the information below.
Please note the following when installing QNX Aviage MME 1.2.0 optional components:
Thus, if you are installing an optional component on such a system, install from the command-line, specifying the installation location for all packages installed after the MME Core 1.2.0.
For example, on a Linux system:
# qnxaviage-mmedia-ipod-1.2.0-build#-linux.bin -P beanProduct.installLocation="/opt/qnx641"
Or, on a Windows system, for example:
C:\path> qnxaviage-mmedia-ipod-1.2.0-build#-win32.bin -P beanProduct.installLocation="C:\QNX641"
Where /opt/qnx641 and C:\QNX641 are the location of the baseline installation under which you are installing the QNX Aviage Multimedia components.
|If you are installing the QNX Aviage Multimedia Interface for TI OMAP Codec Engine, after the installation has completed you must also launch dsp-bins/omap3530image.exe and complete the click-through license agreement to install the sample DSP image on your host.|
The QNX Aviage Multimedia Interface for iPod and the QNX Aviage Multimedia Interface for PlaysForSure packages are designed for use with the QNX Aviage Multimedia Core package. If you intend to use these packages independently of the QNX Aviage Multimedia Core package, please contact your sales support team.
For a complete list of dependencies between MME packages, see “Dependencies” in the Release Notes.
This section explains how to uninstall the QNX Aviage Multimedia Core 1.2.0 and optional components.
When you uninstall the QNX Aviage Multimedia Suite, you must delete the old MME database tables and schema files, for example:
# cd /db # rm *mme* usb*
If you do not know where the MME database and schema files are stored, see your qdb.cfg file for the location of your database. This file is usually located under /db (from the root directory).
InstallShield will now remove the MME.
|In the case of coexistence, if you've installed MME 1.2 on multiple baselines (for example 6.4.0 and 6.4.1), before you uninstall make sure that you select as the active configuration the baseline from which you want to remove the MME or the MME component.|
|In the case of coexistence, if you've installed MME 1.2 on multiple baselines (for example 6.4.0 and 6.4.1), don't use Add or Remove Programs to uninstall MME 1.2:
To uninstall optional components, follow the uninstall instructions for the host OS, substituting the appropriate component path and name where required.
The documentation for this release includes:
If you have any questions, comments, or problems with a QNX product, please contact Technical Support. For more information, see the How to Get Help chapter of the Welcome to the QNX Software Development Platform guide or visit our website, www.qnx.com.