|
You need to setup multiple profiles, one for each configuration/version. Make sure there are no spaces in the profile name you create.
You can find out how to create profiles here: http://support.mozilla.com/en-US/kb/Managing+profiles
The profile manager will allow you to decide which profile to run when you start firefox, but as long as an instance of firefox is open, all new instances will use the same profile.
Below are two methods around this.
You need to setup multiple profiles, one for each configuration/version. Make sure there are no spaces in the profile name you create.
You can find out how to create profiles here: http://support.mozilla.com/en-US/kb/Managing+profiles
The profile manager will allow you to decide which profile to run when you start firefox, but as long as an instance of firefox is open, all new instances will use the same profile.
Below are two methods around this.
The best solution that I have found is to use the WebKit launcher and pull the necessary parts of the package files for the version of Safari that you would like to run as a standalone.
The process in documented in this How To. This assumes that you are making a standalone version of Safari 4 beta; however, this will work with other versions of Safari you just need to substitute in the correct package name.
Here is the link to the WebKitLauncher
h4 Safari 4.0.5