Firefox Portable - 64 bit version
br0adband - November 17, 2011 - 8:42am
I've been using Firefox Portable for several years now as my "primary" browser regardless of what machine I use it on with great success. My question is related to using the 64 bit version of Firefox (which I do presently use with the Firefox Portable runtimes or whatever they're called).
I use custom VS2010 compiled builds posted online that are far more efficient and roughly 20-30% faster than the stock Mozilla provided builds, meaning the ones that PortableApps releases as portable versions. It's easy to do this: the custom VS2010 builds are released as an archive with the firefox folder inside which contains the core browser.
I create a "new" Firefox Portable installation with the latest version available (8 for the moment), then go into the App\Firefox folder and delete the core files, replacing the contents of that directory with the core files from the custom VS2010 compile build files, and then execute the FirefoxPortable.exe and voila...
But, what I've noticed - and it's NOT a problem, so please understand this isn't a request for support for some big serious issue here - is that when looking at Task Manager I still see firefox.exe *32 shown - in other words, the loader is functional but it's still not "pure" 64 bit obviously. The browser I use IS 64 bit, through and through, but now my question boils down to this:
Can someone more knowledgeable than myself find a way to compile the Firefox Portable runtime - I really don't know what to call that thing, sorry - so it's fully 64 bit?
What I mean by runtime is this:
If I do a clean installation of Firefox Portable, it will obviously create the FirefoxPortable folder with all the files inside it including those inside the App\Firefox folder which is the core browser.
Now, if you delete everything inside the Firefox folder you're left with just the "runtime" components for the portable app itself - that's what I mean by runtime.
Or can someone just compile the FirefoxPortable.exe file so it's fully 64 bit, that might work as well.
Again, this is NOT a problem; everything works fine and dandy as it is. I'm just somewhat nitpicky about looking at Task Manager and seeing *32 anywhere - I'm trying to ensure my machine's performance is top notch as best it can be, and anytime the *32 appears that means the Wow6432Node in Windows x64 is going to be called into action and I'm trying to lessen that to every extent possible.
So, if anyone can help I would greatly appreciate any assistance.
Thanks, and have fun, always...