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. The browser I use IS 64 bit, through and through, but now my question boils down to this:Ĭan 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?
#Firefox for windows 8.1 64 bit 64 Bit#
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.īut, 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. 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 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.
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've been using Firefox Portable for several years now as my "primary" browser regardless of what machine I use it on with great success.
0 kommentar(er)
