--
@~@ You have the right to remain silent.
/ v \ Simplicity is Beauty! May the Force and farces be with you!
/( _ )\ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
^ ^ 18:38:01 up 12 days 7 min 0 users load average: 1.00 1.02 1.05
不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA):
http://www.swd.gov.hk/tc/index/site_pubsvc/page_socsecu/sub_addressesa
you ever going to learn to put your question into your post?
Cache Fixer is an add-on of Firefox. It's lately been disabled by Admins.
Cache Fixer never worked for me anyway, back when I was on dial-up, but
Firefox rarely crashes on me these days anyway.
I found it useful, at least up to Firefox 3.x.x. It kept the cache after
a session crash, so that I did not need to download the whole page again.
Keeping, or not keeping, the cache is a user option. I used to have
mine deleted on exit, but you can keep it, if you wish.
You can probably accomplish the same thing with a batch file. As I
recall, FF creates a dummy file at startup, and then deletes it when it
closes. If it crashes, it never gets a chance to delete it, so when it
starts back up, it sees that it already exists and deletes the old
cache. So you'd just need a batch file to look for that file and delete
it if found, and then run Firefox.
He's talking about when Firefox crashes. It deletes the old cache,
presumably in case it might cause it to crash again. I don't believe
there is a user option to change that.
IN Firefox 3, when a session crashed, ALL caches (not just the URL that
caused the crash) were invalidated. :)
--
@~@ You have the right to remain silent.
/ v \ Simplicity is Beauty! May the Force and farces be with you!
/( _ )\ (x86_64 Ubuntu 9.10) Linux 2.6.39.3
^ ^ 20:48:01 up 20 days 2:17 0 users load average: 0.00 0.01 0.05
Right. My point is, Firefox does that when it sees the temp file still
there. So if you create a batch that deletes it before starting FF, it
will never know that it crashed.
I don't see enough Firefox crashes to have ever noticed if it kept the
cache or not. Some users routinely delete the cache after each session,
for security reasons. Mine is in RAMdisk, so it doesn't thrash my HD.
You probably wouldn't notice it with your connection. On dial-up (as
the OP is using), it's painfully obvious when it's starting with a fresh
cache.
Check out this older thread where I explained how to manually flip the
bit in cache to prevent it from being deleted after a crash.
https://groups.google.com/group/mozilla.support.firefox/browse_thread/thread/a3e74b0fe5bc4a9e/fd1e86d6682e9178
JB
Good stuff. I remember that thread, though I obviously didn't remember
the part about the bit, as I was thinking it was using a temp file.