I use FirefoxPortable on my pc (other than my usb drive)
On the PC Firefox is set as the default browser but nonetheless whenever I click on a file or call an URL in any other external way (another program) I get the "Firefox already running" message.
To be precise I get this message: "Firefox is already running, but not responding. To open a new window, you must first close the existing Firefox process, or restart your system"
Now, this message is given when 1) firefox isn't running at all (verified to the processes), or 2) it is running and also responding very well!!
now, 1) I haven't renamed FirefoxPortable,
2) I have set to allow multiple instances in the ini.file
3) the ini file is in the same directory as FirefoxPortable and works (as correctly doesn't display the splash screen, for example)
4) Firefox is correctly set as default browser in the registry
I haven't found any other suggestion in the forum as a workaround to this problem, so here I am.
Please help! Thanks!
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Try it without multiple instances. If it works, then FF2 may have issues with it. It's never been recommended or supported.
Sometimes, the impossible can become possible, if you're awesome!
already tried, no difference. It is like if giving that message is the normal behavior of FirefoxPortable.
Although I guess it isn't.
Ok, try a base install... download a copy of FFP fresh and install it somewhere else. Bring up task manager and ensure there's no copy of Firefox, Flock, TorPark, etc running. Then run the new FFP copy.
And wait a minute... what do you mean Firefox is set as the default browser? Firefox Portable can't be automatically set as the default browser. It requires altering the registry and it is not recommended or supported.
Sometimes, the impossible can become possible, if you're awesome!
I answer from here to avoid a too narrow cascade:
Suddenly I am stricken by one thought. I just updated to 2.0.0.1. Could it be that the cause? I can't be 100% sure I've seen this behavior before the update.
Also, Firefox is set as default browser (from within firefox itself) and not FirefoxPortable: thus, is this problem caused by Firefox itself and not by FirefoxPortable? It seems so. Could it be?
If that's the case, I'm on the wrong forum!! (apologies)
It seemed natural to blame it on FirefoxPortable but the more I think about it the more I am convinced it is some Firefox issue... of which there is no trace on its forum, though.
Going for the big reinstall, and we'll see.
OK, it is all quite absurd.
-1: installed firefox 2.0.0.1 in another location, copied profile, set it as default browser, it didn't give the problem.
-2: fresh installed FF portable 2 in another location, copied profile, set it as default browser from within FF, it didn't give the problem.
-3: Went back to my original portable installation, set it back as default browser... it didn't give the problem!!!
-4: uninstalled the just installed firefox 2.0.0.1 and removed the other FF portable, went back to the original one and it still didn't give the problem!!!
So why was it giving the problem in the first place? Who knows...
Don't set the Firefox inside Firefox Portable as the default. That sets the copy of Firefox inside it as the defaul but NOT Firefox Portable. It'll use a local profile if you double-click an HTML file when FF is not running.
Sometimes, the impossible can become possible, if you're awesome!
well no if you change profiles.ini to point to the FFPortable /data/profile folder.
Surely at that point one could ask: why using FFPortable on your local machine at all then?
Well, because it provides a neat setup where program and profile are in the same folder and makes it easier to synch with the USB drive. Nothing one couldn't do in other ways, messing a little with folders and the profiles.ini file.
No doubt it would be great if FFPortable -when asked- would go to the profiles.ini file and check whether if it points to the right directory. Many problem would be solved for those who wants to use FFPortable on their local machines.