.\Firefoxes\Profiles
Each OS will have their own binary/script that will read the single common profile folder.
For 0.1 we started by installing Firefox 2 on a USB Key. For proof of concept we confirmed that the program is running from the Key by adding an alert to one of the buttons on the browser. The alert triggered during testing, confirming to us that it is in fact running from the key and not from the local machine. We further confirmed this by running Firefox from the key on a Windows XP image that only had the default installation and no Firefox previously installed.
ProfileFor 0.1 we decided to start the project on the Windows platform. We installed Firefox 2 on a USB Key and comfirmed program is running from the Key by adding an alert box to one of the buttons on the browser. We further confirmed that Firefox is running from the key by testing it on a Windows XP image that only had the default installation and no Firefox previously installed. At this point the Firefox program would create a default profile on the local machine hard drive. We wanted to alter this behavior so that Firefox would read the common profile on the USB Key. We researched for ways to redirect where Firefox was looking for its profiles. We realized that Firefox looked up Profiles.ini in the Windows Application Data folder for the location of each profile. We later discovered that there is a program switch to tell firefox where to get its profile. We initially hard coded the directory and profile used by the command line switch. <insert code here> Using an absolute path name we managed to have Firefox read the profile from the USB Key. because the drive letter for the USB Firefox would change on different machines. bash
== Project Leader(s) ==