New
#20
Last edited by mrjimphelps; 18 Nov 2017 at 20:09.
make another the default, like I did with the ESR .
Tools>Options>General>Startup then check that one, then 57 should have them unchecked then.
next step, if you want it, go into your folder for 57
Other>Source find the ini sample file, copy it into the root of the program folder
delete the comment section {do not mess with the original, only work on a copy}
Change the one parameter AllowMultipleInstances= from false to true
If needed place a copy of that copy into the Data>Settings subfolders or if you find one already there,
usually three lines, change the AllowMultipleInstances=true if two lines, add the AMI=true line in alphabetical order, usually AMI ends up in the middle. then you can run both after launching ESR First.
If not, just go to any other browser make it the default, there should be a selection box within prefs/options my Chrome, that I only use for YT, always complains about not being the default and Opera has a regular settings dialogue but wants you import bookmarks first. I just find it better to work with 2 or more versions of Firefox to make it simple to work with.
Thanks for the info BlueGuy, I already had a test profile and that one got buggered to and since then I've found that a fresh profile has seemed to unlock the default browser option.
I also had problems on the options tab where the general page wouldn't show and the new profile fixed that to. Once I move a few bookmarks and I have no problems I'll get rid of those two.
Have you tried a boot of firefox without any add-ons? - It could be that one of your old add-ons is having a problem with the new design but not enough to completely fail. just to go into a loop that causes a memory leak
With 4 tabs open, I'm nearing 1GB memory usage. I've noticed the new firefox actually is faster now compared to my daily browser driver (my laptop) which didn't give any difference.
If anyone is mourning for their lost extensions in v. 57, I'd like to refer you to
forums.mozillazine.org,
where you can get advice on WebExtensions similar to the ones you lost, or css code to add back some of the functionality of your legacy extensions.
Alternatively, you can switch to FF 52ESR and keep your old extensions till next summer, when many of the extensions will have been ported to the new FF.
Last edited by RoWin7; 01 Dec 2017 at 02:10.