Possibly the recent update of eQuake, and/or FlashGot, both of which I installed on Oct. 2, might be causing Firefox to fail to launch just within the past two days. In ProcessExplorer, the Firefox process is running, though; it just never launches the window. I've left it running for three hours with no launch, so by that time I'd say I can give up on it.
But I don't know whether extension updates are the problem. I've been running everything just fine for nearly a week, and I've been running the Firefox 2.0.0.7 update since it first came out, with slow but always successful launches. I tried reinstalling 2.0.0.6 from a fresh download, just over the existing installation, and at first that seemed to help---meaning, I twice got the program to launch.
I updated it to 2.0.0.7 again, and either coincidentally or through something I did htere, it won't launch again. I tend to think it's coincidental, that the program might have hit a little window in which there was no conflict preventing it from opening completely.
My main question is, can I disable those two extensions even though I can't run Firefox? (I've only enabled and disabled extensions from within the program before.) Is it a matter of editing an .ini file somewhere, and if so, which one(s) and what changes do I need to make? A quick search reveals several .ini files within the Firefox Portable directory, but I can't guess as to which need to be changed.
Look here:http://kb.mozillazine.org/Safe_mode
I will try find the path you need for FFPE. I will post you in a minute.
x:\PortableApps\FirefoxPortable\FirefoxPortable.exe -safe-mode
"x" represents your portable drive letter. Make sure you put the space in there betweeen the .exe and -safe-mode. Works for me.
Life is about the journey not the destination!
The Kazoo Spartan
Safe mode allowed it to fire right up, so it's undeniably an extension conflict, and this makes the extensions available so I can load them one by one. I'd forgotten all about Firefox's safe mode. Thank you!!
Cheers!
---Fox