You forgot to add the URL (it's empty)
Cheers
-Jed

http://www.tweakguides.com/Firefox_1.html

Asa, I'm assuming you mean the newly posted Guide here.

If so, I wish you would definitively debunk the tip on Page 12. According to this tip, which is posted in various places around the Internet (Google firefox prefetch switch for a sampling), you can add the /Prefetch:1 switch to the end of a Firefox shortcut and it will somehow speed up the program's loading.

This tip is based on a fundamental misunderstanding of the Windows Prefetch feature, which is completely different from the prefetch capability in Firefox. Anyway, I document how this rumor got started here.

If by some chance Firefox really does have a /Prefetch switch, please let me know. It's not documented in any official source. Otherwise, it would be useful to put this myth to rest once and for all.

How come there are no comments here? I would love to see the answer... Is everyone ashamedly rushing to their computers to remove the Prefetch switch, so that they don't have time to comment? :-)

The browser.cache.memory.capacity setting appears to be based on a documentation error. I've been ragging on that one for a long time, and I just noticed the documentation error.

The browser behavior appears to have been changed, and the memory cache does not work like that any more. Instead of specifying the capacity, the setting actually specifies the maximum inactive memory that is held in cache. The actual value held in cache seems to be limited only by available virtual memory, and is not limited by the capacity setting. [url=https://bugzilla.mozilla.org/show_bug.cgi?id=250558]Bug 250558[/url] describes failure to adhere to capacity setting, but the bug is marked as invalid because it describes expected behavior.