Thursday, September 2, 2010

Packaging Mozilla Firefox

1. The following changes are made to the file firefox.js (located at [ProgramFilesFolder]Mozilla Firefox\defaults\pref\)


Changed the values from True to False on the following lines:

pref("app.update.enabled", true);

pref("app.update.auto", true);

pref("browser.shell.checkDefaultBrowser", true);

pref("general.startup.browser", true);

Changed the value to 0 in the following line

pref("app.update.mode", 1);

The following line was added to the firefox.js file

// Preferences for the Get Add-ons pane

pref("extensions.checkCompatibility", false)



2. Add the file "override.ini" under "[ProgramFilesFolder]Mozilla Firefox\" with the below information:

[XRE]

EnableProfileMigrator=false

This will suppress the Import wizard that pops-up when shortcut is launched.

Disable splash screen in Windows Live Messenger

To disable splash screen in Windows Live Messenger, add the below properties:

ADDBHO = "No-ADDBHO"

ADDLINKS = "No-AddLinks"

SETHOMEPAGE = "No-SetMyHomePage"
 

Disable License Agreement ,Help assistance and Auto Updates in iTunes

Launch iTunes.It then shows the License Agreement Window.


Click on Agree

If the User don’t want to

1. Add MP3 and AAC files

2. Add WMA files (As Default)

uncheck the Checkboxes and Click Next.

Select "No i'll Change the file and folder names myself"

Click on Finish to launch the application.

Click on Edit->Preferences

Uncheck "Check for updates automatically" and then close the application and launch again.

Help Assistance, license Agreement and Updates are disabled.

The Below files will have the modified information.

1. C:\Documents and Settings\[USERPROFILE]\Application Data\Apple Computer\iTunes\iTunesPrefs.xml

2. C:\Documents and Settings\[USERPROFILE]\Local Settings\Application Data\Apple Computer\iTunes\iTunesPrefs.xml

Using Active setup for the application having Dependency

If the application require {1234....} to repair after {989A44...} the solutions is to place the ">" character before the [ProductCode].


For Example:

If you had App A (with product code {448E2D77-E504-4221-B2C2-93646B344729}) that has an advertised shortcut, and App B (with product code {22d6f312-b0f6-11d0-94ab-0080c74c7e95}) had no advertised shortcut but had a launch condition for app A.
The solution would be to place two Active Setups in app B (1 for app A and 1 for app B). Then, to make app B repair second, use the ">" character for app B as shown below.


MSI Validation using Darice.cub

MSI Validation runs tests on the MSI package. These tests are called Internal Consistency Evaluators (ICE). They can find bad conditions, duplicate file targets, invalid records, per user issues and so on...


Tools required for validating MSI will be available after installing "Windows Installer 4.5 SDK".

Hence we will first install “msi45sdk.msi” (Windows Installer 4.5 SDK).

Windows Installer 4.5 SDK will be installed under "C:\Program Files\"

In "Windows Installer 4.5 SDK" folder we can see "TOOLS" folder.

We can see many tools in this folder like orca, msidb, msival2, etc.

MsiVal2.msi extracts MsiVal2.exe and some .cub files when installed. MsiVal2.exe is a command line tool that will run the validation test for us.

Now Install "MsiVal2.msi".

After completing the installation of Msival2.msi, we get an "MsiVal2" folder under "C:\Program Files\". The CUB files in this folder have the actual ICEs to execute. Darice.cub contains all of the MSI ICE's and equates to Full MSI Validation Suite.

For validating an MSI, copy that msi and source folders associated with it (if any) to the location where MsiVal2.exe is installed (i.e., C:\Program Files\MsiVal2\).

Run MSI Validation from the command line:

MsiVal2.exe <.cub file> /l "Output file" /f

Example:

MsiVal2.exe "C:\Program Files\MsiVal2\BankID_Security.msi" "darice.cub” /l “C:\New Folder\Validation.log” /f

We can create a cmd file (New Test Document.cmd) to run MSI Validation from the command line.

After executing this file we will get Info, Warnings and Errors in the "validation.log" file.
MSI Validation typically contains 3 levels of output (Info, Warnings, and Errors) which will be shown in the "validation.log".

Nice player application

When we install Nice player, even in silent mode, it pops up a dialog box as shown below


1. Disable the below Custom actions (from MSI Script ->Execute Deferred).
*Call DLL From Installation Function ManagedInstall__23509C46_6243_4AF3_B176_0BB38DA2434E.uninstall

*Call DLL From Installation Function _F25E8ED6_E9FD_4130_8CA2_927358A81E52.install.

2.Now, if you install the application, you get the following dialog box

3. To suppress this, add "InstallClasses9_10_5_01.InstallState" to [ProgramFilesFolder] NICE Systems\Nice Player Release 3

(Get the file ”InstallClasses9_10_5_01.InstallState” from "[ProgramFilesFolder] NICE Systems\Nice Player Release 3\" by installing the given media)

4. Add folder "Help" (Help\) to [ProgramFilesFolder] Nice Systems\Nice Player Release 3\
Get the "Help" folder by installing the media.

(As the "Help" function will not work due to disabling of Custom action, it needs to be added)