Confirm
1,041
edits
Changes
no edit summary
# Rename the mar file you downloaded to update.mar.
# Open a command prompt by running cmd.exe. On Windows Vista or greater you may need to launch cmd.exe with "Run as administrator" (available in the context menu when right clicking cmd.exe).
# Change the working directory to the application's installation directory by using the cd command (e.g. for Firefox <code>cd "C:\Program Files\Mozilla Firefox"</code>). '''Important:''' running the update from within another directory will failto update the existing installation properly with Firefox 3.6 and below, SeaMonkey 2.0 and below, and Thunderbird 3.1 and below.
# Close all instances of the application that are running on the system including those being used by other users before going any further. '''Important:''' not doing so will cause the update to fail.
# For Firefox 34.5 0 and above, SeaMonkey 2.1 and above, or Thunderbird 5.0 and aboverun the following from the command prompt<br><pre><path to outside directory>\updater.exe <path to outside directory> <path to installation directory></pre><br>For Firefox 3.5 and 3.6, SeaMonkey 2.0, or Thunderbird 3.0 and above 3.1 run the following from the command prompt<br><pre>C:\app-update<path to outside directory>\updater.exe C:\app-update<path to outside directory>\</pre><br>For Firefox 3.0.x or Thunderbird 2.0.x run the following from the command prompt<br><pre>C:\app-update<path to outside directory>\updater.exe C:\app-update<path to outside directory>\ 0</pre>'''Note:''' The "0" parameter passed on the command line specifies the PID of a process to wait on before applying the update. When applying updates manually this should be 0 to disable the wait step.
# After the update has completed a file named <code>update.status</code> will be created in the '''outside''' directory. Open the <code>update.status</code> status file in an editor (e.g. notepad.exe). If the update is successful then the file will contain the text "succeeded". If it does not contain the text "succeeded", then the <code>update.log</code> file may be consulted to diagnose at what step the update failed. A failed update should leave the original application's installation intact. '''DO NOT''' continue to the next section unless the update succeeded.
# Copy the <code>update.log</code> to the <code>uninstall</code> directory inside of the application's installation directory.
# Download the appropriate .mar file and put it into the '''outside''' directory you created (see [[Software_Update:Manually_Installing_a_MAR_file#Where_to_get_a_mar_file|Where to get a mar file]]).
# Rename the mar file you downloaded to update.mar.
# Open a Terminal and change the working directory to the application's package directory by using the cd command (e.g. for Firefox <code>cd /Applications/Firefox.app/</code>). '''Important:''' running the update from within another directory will fail to update the existing installation properlywith Firefox 3.6 and below, SeaMonkey 2.0 and below, and Thunderbird 3.1 and below.
# It is recommended that all instances of the application that are running on the system including those being used by other users are closed before going any further. '''Important:''' not doing so can cause the update to fail under some circumstances and it can definitely break a running instance of the application.
# For Firefox 34.5 0 and above, SeaMonkey 2.1 and above, or Thunderbird 5.0 and aboverun the following from the command prompt<br><pre><path to outside directory>/updater.app/Contents/MacOS/updater <path to outside directory> <path to installation directory></pre><br>For Firefox 3.5 and 3.6, SeaMonkey 2.0, or Thunderbird 3.0 and above 3.1 run the following from the Terminal<br><pre>/app-update<path to outside directory>/updater.app/Contents/MacOS/updater /app-update<path to outside directory>/</pre><br>For Firefox 3.0.x or Thunderbird 2.0.x run the following from the Terminal<br><pre>/app-update<path to outside directory>/updater.app/Contents/MacOS/updater /app-update<path to outside directory>/ 0</pre>'''Note:''' The "0" parameter passed on the command line specifies the PID of a process to wait on before applying the update. When applying updates manually this should be 0 to disable the wait step.
# After the update has completed a file named <code>update.status</code> will be created in the '''outside''' directory. Open the <code>update.status</code> status file in an editor (e.g. TextEdit). If the update is successful then the file will contain the text "succeeded". If it does not contain the text "succeeded", then the <code>update.log</code> file may be consulted to diagnose at what step the update failed. A failed update should leave the original application's installation intact.
=== Steps for Linux ===
'''Important:''' this should work with all flavors of UNIX but the following steps have only been tested on Linux and Mozilla only distributes mar files for Linux.
# Create a directory '''outside''' of the application's installation directory to be updated (e.g. <code>/app-update<path to outside directory>/</code>). This directory will be referred to as the '''outside''' directory throughout the instructions below so please make a note of its location. Grant the user account you are using write, read, and execute permissions on this directory if it doesn't have these permission already.
# Copy <code>updater</code> from the application's installation directory that is to be upgraded into the '''outside''' directory. If you would like to display the updater user interface while it is applying the update also copy the <code>updater.ini</code> into the '''outside''' directory.
# Download the appropriate .mar file and put it into the '''outside''' directory you created (see [[Software_Update:Manually_Installing_a_MAR_file#Where_to_get_a_mar_file|Where to get a mar file]]).
# Rename the mar file you downloaded to update.mar.
# Open a shell and change the working directory to the application's installation directory by using the cd command. '''Important:''' running the update from within another directory will fail to update the existing installation properlywith Firefox 3.6 and below, SeaMonkey 2.0 and below, and Thunderbird 3.1 and below.
# It is recommended that all instances of the application that are running on the system including those being used by other users are closed before going any further. '''Important:''' though this should never cause the update to fail there might be cases where it will and it can definitely break a running instance of the application.
# For Firefox 34.5 0 and above, SeaMonkey 2.1 and above, or Thunderbird 5.0 and aboverun the following from the command prompt<br><pre><path to outside directory>/updater <path to outside directory> <path to installation directory></pre><br>For Firefox 3.5 and 3.6, SeaMonkey 2.0, or Thunderbird 3.0 and above 3.1 run the following from the shell<br><pre>/app-update<path to outside directory>/updater /app-update<path to outside directory>/</pre><br>For Firefox 3.0.x or Thunderbird 2.0.x run the following from the shell<br><pre>/app-update<path to outside directory>/updater /app-update<path to outside directory>/ 0</pre>'''Note:''' The "0" parameter passed on the command line specifies the PID of a process to wait on before applying the update. When applying updates manually this should be 0 to disable the wait step.
# After the update has completed a file named <code>update.status</code> will be created in the '''outside''' directory. Open the <code>update.status</code> status file in an editor (e.g. vi). If the update is successful then the file will contain the text "succeeded". If it does not contain the text "succeeded", then the <code>update.log</code> file may be consulted to diagnose at what step the update failed. A failed update should leave the original application's installation intact.
