In the earlier versions I could do the following..
I set the cache to the temp file on the computer browser.cache.disk.parent_directory; C:\\WINDOWS\\Temp\\Temporary Internet Files
http://xmb.stuffucanuse.com/xmb/viewthread.php?tid=5757
This meant that the flash drive didn't work so hard, as the pages were being cached on the local machine and deleted out afterwards. It made FF run faster, as the flash drive slowed it down. As well there was less wear on the drive itself, having a limited lifespan.
Anyway in the 3.5 I can't seem to get that option working again. This part browser.cache.disk.parent_directory; is missing and when I create it it makes no difference.
Anyone have a solution?
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
FFP caches its files in the RAM so there shouldnt be any wear on the drive.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Thanks, I found the setting to turn on the ram and turn off the disk caching, it does seem faster
I was hoping for a local profile mode, even though it does go against the no trace left behind mantra. Chromium Portable has this feature and I think FFP could benefit from it as well. It works by copying the profile to a local disk for faster access and then copying it back to the drive when it's closed. This does pose a security concern though.
The more extensions you have the slower FFP will run off of an external device. If the profile was being accessed locally the speed could increase, albeit at a risk to personal information.
While I'm excited at both prospects, the problem is that there are only so many changes JTH is allowed to make to Firefox to stay in Mozilla's good graces. The profile manager was removed, and there are a couple other tweaks, but some features which break portability, such as the update check and automatic update, must be left intact and the user educated on how to fix this manually. Also the anti-phishing filter must be left on, even though disabling it grants a huge performance increase.
I would very much like it if PortableApps.com offered a re-branded Firefox with a different logo and name, so that JTH & crew would be able to customize it further. It could come with Adblock Plus, QuickProxy, and other extensions which augment the portable nature of the browser. The problem with that is that Firefox is a recognized name, and many of Firefox's biggest fans aren't aware that browsers like Iceweasel, Blackbird, Orca, Cometbird, and others are Firefox, tweaked, and wouldn't use this hypothetical product. Plus, Mozilla doesn't work with just anyone how they work with JTH, so that agreement, I suppose, must be honored. I guess. And with Personas (CSS-based browser theming framework), a special PortableApps.com theme could be made. I don't know who'd feel what about PA branding, but it works in CoolPlayer.
I am not well versed in Mozilla's distribution schemes, I assumed the rules were very lax having scene customized versions (pigfoot's, tete's) for certain hardware but those were never feature related. I suppose maintaining a vanilla distribution of FFP and then "upselling" a customized one would be too big of an undertaking. Then again, there are a number of Mozilla based products that don't carry the official brand. These days "a Mozilla based product" is a good tagline to have. See: Songbird, Postbox (I like it better than Thunderbird even, 2.x at least),Spicebird, etc. It is redoubtably a complex issue.