This bugs me to death since I'm on dial-up. Just last night, I pulled a process out from under the nose of my firewall while it was asking about it and it locked up my (Windows) system pretty nasty. I should file a bug report with PC Tools about that…

Anyway, thanks to burning desire and this and this thread on mozillaZine Forums, I found Cache Fixer. Quote: "Cache Fixer extension drops the "dirty" flag on every startup and if Mozilla crashes, you still loose cached data, but only the current (crashed) session. I think it’s better, than loosing all cached data."

That's awesome, but it only works up to Firefox 3.0pre. So I used the maxVersion trick so it will work with up to Firefox 4.0. Here it is on Box.net. Hopefully the developer will put an official updated version up soon. Please note: I have nothing to do with development, I just changed a text string and then zipped the files back up.

Also, as I posted back here, the dumped cache is intentional behavior. We're just choosing to change that behavior (woot!).

Thanks much, Mr. Ivanov.

How annoying. A day or two ago, Javascript popups started opening in new tabs. They are popups for a reason. I had Firefox set so that links that would open in a new window would open in a new tab, but popups like this didn't use to be affected.
Anyway, after another Google today, I found the fix. 1st Byte Solutions has the answer. Quote:

if you open about:config in your address bar, you can change the setting manually.
Change: browser.link.open_newwindow
Mine was set to 3, which told the popups to always open in a new tab.

Niceness. It's a pretty easy fix. Set it to 2. I just wonder what changed it to 3. Wasn't me. It appears this is something of a longstanding issue; the Firefox team should probably add a GUI option for this. Check out this thread on Mozillazine, where the same fix is given (in 2004) and this one, where Tab Mix Plus is the solution (it occurs to me TMP might change that value).
Go give some kudos to 1st Byte if this makes you happy.

Update; Feb-15-2010: So it busted again. And this time setting browser.link.open_newwindow to 2 didn't fix it. Garr. Fortunately, setting browser.link.open_newwindow.restriction to 2 did fix it. Thanks, harrymc.

I got my Sansa fixed up on Sunday. What was happening is that only the ring would light up when I turned the thing on and I had to "reset" (really a forced power off, it seems) to get it off. I was advised to drain the battery, charge it, and then see what happened. I did, and same result. Some more talk online informed me that the daughter card may have come loose. Over the span of two days I got it all the way open (part of this took over two hours on IRC and a video from someone on there… how nice of them), disconnected the daughter card for sure, and reconnected it. I plugged my Sansa in on USB and the wheel came on but it seems the player turned off. I put the battery back in and tried again, this time presented with a blessed SanDisk logo. Whoooo-hooo!

I had intended to start hacking my Sansa after the warranty had expired, but I figured that I might as well start then since I had been poking around on the insides of the thing. I downloaded the alternative mp3 player firmware Rockbox and installed it on my Sansa (it keeps the original firmware on, too). And, wow, Rockbox blows the original firmware away in most areas. Very very customizable and supports plugins, which you can use even while you're playing music. These plugins fall under the categories of Applications, Demos, and Games. And yes, you can even play Doom.