lasongs.blogg.se

and have had to struggle to keep valuable Initially pulled the trigger two months ago.Īt the time, Asa Dotzler, director of Firefox, said: "Ourĭevelopers have not been able to take advantage of new compiler features Mozilla has been discussing the change forat least three years and "This support change allows us to significantly improveįirefox performance on Windows by using a more modern build Firefox 13 will not work on WindowsĢ000, Windows XP RTM (release to manufacturing, the original mid-2001įirefox 12, set to ship April 24 and due to be replaced by the nextĮdition on June 4, will be the last that supports the three older Starting with Firefox 13, the browser's minimum requirements The company also reiterated that it will stop serving security Last version to run on early editions of Windows XP and the 12-year-old Mozilla Firefox 12, which will be released next month, will be the

However, I don't know how I would do it so that the folder would change for each user? I was thinking of using the SetProperty Custom Action and the Set Directory Custom Action and using them to take in the %username% variable and populate the directory that way.

So I was thinking of adding these files to my msi and using Active Setup to install them for each user. I noticed that a number of files are created/modified in the users Appdata folder - AppData\Mozilla\Firefox\Profiles\%username%. I have performed a capture of ticking each of the boxes on first run and managed to capture what changes were made. This is also a per-user setting and not a per-machine setting so will need to be done for each user. This is an issue, as, one of the Addons is Symantec Intrusion Prevention which we really want turned on.Ī user can tick the relevant tick box and it will install for that user but if a user chooses not to install the Addon then it's not installed and the user could be left vulnerable. Therefore the user is presented with a window where they can select/deselect whatever Addons they feel like instaling. However, on Windows XP, on first run Firefox checks to see what Addons are available and want to interact with Firefox. I created my msi package from a snapshot and set my firefox properties using the Mozilla.cfg, override.ini and local-settings.js files after following the recommended guidelines for packaging Firefox. On Windows 7 once the package is installed and the user runs Firefox for the first time it runs without any prompts and without a problem. We are currently transitioning from XP to Windows 7 therefore require it on both builds. I have packaged Firefox 14 for both our Windows XP environment and our Windows 7 environment.