mozdev.org

Translations: cz | en | es | fr |it | ja | pl | zh

Before You Install

General

Close Mozilla before installing plugins

Mozilla should be closed before running any plugin installation programs, as existing files may be overwritten during the installation process.

Close Quick Launch before installing plugins

If you have Quick Launch enabled on Windows, you will also need to close it prior to installing plugins. If you are installing several plugins, you may wish to disable it until you are finished. To do this, right-click in the Quick Launch icon in your system tray, and select the appropriate option (Close or Disable).

Mozilla Quick Launch icon and menu
Mozila Quick Launch icon

Checking which plugins you have installed

To check what plugins you have installed, open about:plugins. If you are using the Mozilla Application Suite, this can also be accessed from the Help menu (Help -> About Plug-ins).

Using XPInstall to install plugins

Some plugins are available as XPInstall packages (XPIs). Where XPIs are available, it is recommended you use them as they often install the plugin completely automatically. After the XPI has finished installing, you should restart your browser.

Important! To install plugins from this site using XPInstall with Mozilla Firefox, you will need to add it to the list of sites software installations are allowed from. You can do this using the Firefox Options, or by using the information bar when the installation is blocked.

Plugin Locations

Microsoft Windows

On Windows, Mozilla and Mozilla Firefox search for browser plugins in the following locations:

Unix Systems (Linux, Solaris, other)

On Unix, Mozilla and Mozilla Firefox search for browser plugins in the following locations:

MacOS 9.x

On MacOS 9.x, Mozilla searches for browser plugins in the following locations:

MacOS X

On MacOS X, Mozilla searches for browser plugins in the following locations:

Plugin Scanning

Introduction

On Microsoft Windows systems, Mozilla and Mozilla Firefox scan for some common plugins at startup. This behaviour can be changed for all users by editing Mozilla's configuration files, and for the current user by using about:config. To change the plugin scanning settings for all users, you will need to edit the following file:

Mozilla 1.6 and earlier: \default\pref\winpref.js
Mozilla Firefox 0.8 and earlier: \default\pref\winpref.js
Mozilla 1.7a and later: [Program Files]\Common Files\mozilla.org\GRE\[Version]\greprefs\all.js
Mozilla Firefox 0.9 and later: \greprefs\all.js

Important! Mozilla configuration files may need to be edited with a text editor that supports Unix line endings, such as Wordpad. Do not use Notepad to edit configuration files.

You can specify any minimum version of a plugin to scan for. To disable an individual scan, simply comment out the scan by adding // to the start of the line. If you are using about:config, right-click on the preference name and modify accordingly.

Java Plugin

The following preference controls the Java Plugin scan if Java is enabled. Unless you run multiple JREs and want Mozilla to use the most recent one, this preference is likely of no use to you.

// Locate Java by scanning the Sun JRE installation directory with a minimum version
// Note: Does not scan if security.enable_java is not true
pref("plugin.scan.SunJRE", "1.3");

Adobe Acrobat Reader

The following preference controls the Adobe Acrobat Reader scan. Unless you have multiple versions of Acrobat Reader installed, you shouldn't need to change this.

// Locate plugins by scanning the Adobe Acrobat installation directory with a minimum version
pref("plugin.scan.Acrobat", "5.0");

QuickTime

The following preference controls the QuickTime scan. You shouldn't need to change the version for this preference.

// Locate plugins by scanning the Quicktime installation directory with a minimum version
pref("plugin.scan.Quicktime", "5.0");

Windows Media Player

The following preference controls the Windows Media Player scan. Setting the version to anything below 7.0 is probably not a good idea, as older versions do not work well or at all.

// Locate and scan the Window Media Player installation directory for plugins with a minimum version
pref("plugin.scan.WindowsMediaPlayer", "7.0");

Windows Registry (PLID scan)

Some plugins add PLIDs to the Windows registry. You should not need to touch this.

// Locate plugins by the directories specified in the Windows registry for PLIDs
// Which is currently HKLM\Software\MozillaPlugins\xxxPLIDxxx\Path
pref("plugin.scan.plid.all", true);

Netscape 4.x

Mozilla can scan the Netscape 4.x installation folder if you have Netscape 4.x, or have installed a fake Netscape 4.x. This scan can be configured to scan for popular plugins in the Netscape 4.x plugins folder, scan for all plugins in the Netscape 4.x plugins folder, or be switched off.

You will probably want to scan for all plugins in the Netscape 4.x plugins folder, particularly if you are using a fake Netscape 4.x. To do this, set the preference to true. To disable it, set it to false. To only scan for popular plugins, comment it out as shown here.

// Controls the scanning of the Navigator 4.x directory for plugins
// When pref is missing, the default is to pickup popular plugins such as
// Flash, Shockwave, Acrobat, and Quicktime. If set to true, ALL plugins
// will be picked up and if set to false the scan will not happen at all
//pref("plugin.scan.4xPluginFolder", false);