Home » leaks » Page 2


Getting Firefox out of the doldrums

John C. Dvorak asks what’s wrong with Firefox, and suggests forking as a possible solution.

It sounds to me like one or more plugins he’s running is causing problems. I run Firefox on Vista (unfortunately), with as few plugins as possible, and I don’t have the issues he describes. Memory usage does spiral out of control if I go long enough between restarting the browser, but restarting the browser once a week keeps it tolerable.
Read More »Getting Firefox out of the doldrums

Make something! Fix something!

Clive Thompson: I’m sitting on the floor of my apartment, surrounded by electronic parts… It’ll look awesome when it’s done. If it ever gets done — I keep botching the soldering. A well-soldered joint is supposed to look like a small, shiny volcano. My attempts look like mashed insects, and they crack when I try to assemble the device.

Why am I so inept? I used to do projects like this all the time when I was a kid. But in high school, I was carefully diverted from shop class when the administration decided I was college-bound. I stopped working with my hands and have barely touched a tool since.

I can relate a little too well.I think part of the reason I was misunderstood for so much of my career was because I used to do stuff like this. I still remember the day when a new OS arrived for my Amiga 2000. It came on a ROM chip (remember those?) and some floppies to install. I had the Amiga completely disassembled, sitting on Dad’s orange OMT table in the basement. Dad came downstairs, his eyes got big and his jaw dropped, he pointed, and then looked at me. “You going to be able to get that back together?”

I barely looked up. “Yep,” I said, continuing whatever I was doing.

Granted, the Amiga’s design made it look like an onerous task–you had to remove the power supply, the assembly that held all the disk drives, and at least one plug-in card to get at the ROM chip I needed to replace. But at this point, I’d disassembled at least a couple of PC/XTs even further than that. It wasn’t long before I’d replaced all those parts that were strewn about Dad’s table and fitted them back into the case, just as they all belonged. I powered it up, and immediately knew I was successful–all those royal blue screens of Amiga DOS 1.3 were replaced with the gray screens of 2.1.

Dad watched me put it back together, and although he didn’t say much, I think he was impressed.

That wasn’t the only modification I did to that computer. Amigas operated a bit differently in Europe and in North America because of the differing video standards. Software designed for European Amigas didn’t always run right. There was a soldered jumper on the motherboard to switch between PAL and NTSC operation. I bought a small slide switch from Radio Shack, soldered a couple of wires to the motherboard, and ran them to the switch, which I hung out an opening next to the mouse port. Elegant? Not at all. Functional? Totally.

There were tons of homebrew projects for Amigas in the early 1990s. Some worked better than others. But you learned a lot from them. And I think that’s part of the reason I look at things differently than people who grew up with Macintoshes (a closed black box if there ever was one) and PCs. Sure, people have been assembling their own PCs from components for 20 years now (ever since PC Magazine declared on a cover that you could build your own PC/AT clone for $1,000). But there’s a subtle difference between assembling components and modifying them. No two 286 motherboards were the same, while the design of Amiga motherboards tended to change very little, giving lots of time for people to study and learn to tweak them.

So while the PC owners were swapping their motherboards, we Amigans were tweaking ours to give ourselves new capabilities on the cheap. And in the process I think we were learning more.

So I agree with Clive Thompson that I’m a lot less likely to take a salesperson’s claims at face value. And I think that gave me a lot less patience with people who are. With only one exception I can think of, I always worked well with (and for) people who’d taken a soldering gun directly to a motherboard or programmed in assembly language. Thanks to these rites of passage, we had a much better idea of how things worked. And it gave a certain sense of skepticism. Commodore’s own engineers didn’t know the full capability of the machines they built. So if the engineers who design a system can’t know everything about it, then what on earth can a mere sales drone know?

And that’s why I’m reluctant to buy anything that’s just a black box if I can avoid it. What if it breaks and needs to be fixed? What if I need to change something about how it looks or works? And besides that, if it doesn’t do what it’s supposed to do, I don’t want to just throw it out and buy a new one–I paid good money for it!

But I have my limits. A few years ago I checked out some books on repairing Lionel trains from the library. The books suggested using mineral spirits to clean out the old grease and oil from a motor and bring it back to life. That would be good advice, except for one thing: I had no idea what mineral spirits were (a kind of paint thinner), or where to buy them (a paint store or the paint aisle of a hardware or discount store). And have you ever tried to punch it into Google? Trust me, in 2003, there weren’t many answers. The Wikipedia article didn’t exist until 2005.

I’m sure there are lots of people who are laughing at me because I didn’t know what mineral spirits are. But I’ll bet you that if you were to go find my 120 or so high school classmates and separate out the males who lived in the suburbs whose fathers were white-collar workers, the overwhelming majority of them would have no idea what mineral spirits are either. Why not?

Because when we were growing up, we were college-bound. People like us didn’t need to know what mineral spirits are. We needed to know things like the fact that there’s no such thing as the square root of a negative number. (Yes, I know that’s not a correct statement–but those were the exact words of my Algebra II teacher, and those words cost me a lot a couple of years later.)

I even remember one time, a group of us were talking about something, and one classmate’s name came up. “He’s going to end up being a plumber,” someone snickered.

Never mind that the last time I had to call a plumber, my plumber most certainly made more money than I made that year, and he probably got a head start on me because he didn’t have to go to college for four years either.

One of the reasons plumbers make a good living is because so many people don’t even know how to shut off the water valve when their toilet leaks, let alone how to go about fixing that leaky toilet. For the record, I can shut off the water valve, but I don’t know how to fix the toilet. I’m hoping they’ll show me on This Old House sometime.

My gripe with DIY books today is that the authors don’t necessarily realize that there are one or possibly even two or three generations of readers who may very well not know the difference between a wood screw and a machine screw. They don’t learn it in school, and Dad might or might not know, but in an age when fewer couples marry and divorce rates are sky high, is Dad even around to tell them any of this stuff?

Today, I couldn’t care less about imaginary numbers. But I’m reading old DIY books, desperately trying to learn the lost arts of making and fixing things. Thanks to Disney and other useless companies, I can’t use a computer to locate digital copies of anything newer than 1922. That’s a shame, because it condemns all of the DIY books of the 1930s, 1940s, and 1950s to obscurity. They won’t be reprinted because there isn’t enough market for them, they aren’t worth the expense of hiring a lawyer to find out if they somehow slipped into the public domain before the laws started really changing in the 1970s, and they’re scarce enough that you won’t always find them where old books lurk, making them a bit more difficult to borrow or purchase.

That all but eliminates a golden age, limiting me to 1922 and earlier. But admittedly it’s very interesting to read how people made and fixed things in the decades immediately before and after the turn of the previous century. So many books today start out with a list of exotic and expensive tools before they tell you how to do anything. One hundred years ago, people didn’t have as much money to spend on tools, and since things like electricity weren’t necessarily always available, there weren’t nearly as many exotic and expensive tools to buy either.

I found an incredible quote in an 1894 book by Charles Godfrey Leland, a teacher and author from Philadelphia. “It is much better not to have too many implements at first, and to learn to thoroughly master what one has, and to know how to make the utmost of them. This leads to ingenuity and inventiveness, and to developing something which is even better than artistic skill.”

That’s not just good advice for metalworking, which was the subject of this particular book. That’s an excellent philosophy of life.

Unfortunately right now I have more time to read than I have to tinker. But I think once I have a little time to tinker again, I’ll be able to make some nice stuff. And maybe someday when someone says they don’t make ’em like they used to, I’ll be able to smile and say that I do.

Optimizing Firefox

Firefox is a better browser than Internet Explorer by a long shot, but at times it’s made me wonder if it’s strayed from its original mission of being a lean, quick, simple browser based on the Mozilla engine.

I’ve seen several “Optimizing Firefox” guides and most of them talk very little about performance, and the ones I did find were not only disappointing, they also appear to be widely copied verbatim without attribution. So here’s what I do to shaq-fu Firefox into shape.Try out Firetune. Firetune is a wizard-like program that configures most of the common Firefox tweaks based on criteria you select. In my case, since I have a P3-700 with 192 megs of RAM, I selected Slow computer/Fast connection on the Performance tab, and Optimize Firefox memory usage on the tab labeled Other useful settings. For me, the payoff was immediate.

Install PDF Download. If you view a PDF file online, Firefox keeps Acrobat in memory essentially forever, where it does nothing but chew up precious memory until the next time you view a PDF, which might be in a minute, or it might be next month. Take control over this behavior by installing PDF Download.

By default, after installing PDF Download, you’ll get a dialog box asking what you want to do when confronted with a PDF file. If you click the View PDF button, it loads it in your OS default PDF viewer. This behavior is less seamless than viewing the PDF directly in your browser, but it’s much better for performance because after you close the file, the viewer unloads from memory. For even better performance, forget about Adobe’s Acrobat Reader and install Foxit Reader, which is much smaller and faster. By default, when you install Foxit Reader, it will make itself your OS default PDF viewer. Trust me, this is what you’ll want.

On my 700 MHz P3 running Windows 2000, PDF documents display in one second with PDF Download and Foxit Reader installed. That’s faster than Acrobat ever was, even if it was already in memory.

I like the combination so much, I went to Tools, PDF Download Options, and set the default action to Open PDF, rather than displaying the dialog box. Now I no longer dread downloading PDFs from the Web.

Optimize memory usage a bit more. Type about:config into a browser window and scroll down to browser.sessionhistory.max_total_viewers. The default value is -1, which will determine the number of pages in your browser history to cache based on the amount of memory you have. I set it to 1, since I do tend to use my browser’s back button a lot. If you almost never find yourself clicking the back button, or you have a very low-memory machine, set this to 0. Each page it stores takes up about 4 megs of RAM.

Clear your downloads. Hit ctrl-j to bring up the download manager and clear it out. Too many entries slows Firefox down, partly because it increases memory usage.

Keep your version current. Often newer versions of software are slower and fatter than the old versions, but newer versions of Firefox are often faster than older versions because memory leaks and performance problems tend to get fixed in newer versions. I don’t recommend running beta or preview release versions, and I’m not all that crazy about .0 versions either (when Firefox 3.0 is released, I’ll wait until version comes out). I just upgraded an old computer that had been running a very early Firefox 1.0 to, and the difference is incredible.

For what it’s worth, version (the current version) running with these changes feels very zippy on a P3-700 with 192 megs of RAM.

The Abit BP6 and modern Linux distributions

Mail from Dave T.: I bumped into a place that is selling a used, functional Abit BP6 and a 400MHz Celeron to go with it. I already got another 400 MHz Celeron so it would be perfect. I always wanted to try out SMP but so far I haven't thought it was worth it. Now I can buy this combo and make my dream come true 🙂
I looked for reviews on the board but most of them were from 1999 and early 2000, when Linux was using kernel 2.2 and there also seemed to be problems with bios on the BP6 causing stability issues. None of the reviews were recent.

Being a long time reader I remembered you talking about owning a BP6 and a quick search confirmed that you were running a dual 500MHz BP6. Do you still have it? If I buy the board then I'll be running Linux of course so I was wondering if you do that as well? How well does it work? Stability? I know that processors in a dual configuration should have identical stepping. If the two are not the same stepping, do you think it will pose a problem? What power supply rating would you recommend for 2x400MHz Celerons?


/Dave T.

The Abit BP6, for those who are unfamiliar with it, was a popular board among enthusiasts back at the turn of the millenium, because it was the first really cheap and easy SMP board. Prior to the BP6, to run dual Celerons you had to resort to some trickery, either soldering on slocket-type adapters or, later, playing with jumpers on them. The BP6 just allowed you to buy a pair of cheap Socket 370 Celerons and drop them on. A lot of people bought Celeron-366s and overclocked them to 550 MHz with this board.

It’s been forever since I’ve mentioned my BP6 because I’ve never found it newsworthy. My main Linux workstation runs on an Abit BP6 with dual Celeron-500s (originally a pair of 366s, which I upgraded a couple of years ago). I bought the board in late 1999 or early 2000 and it’s still my second-fastest PC.

I run Debian Unstable on it, running updates every month or two, so I’m running bleeding-edge everything on it most of the time. The kernel is either at 2.4.19 or 2.4.20. I’ve been running 2.4-series kernels on the BP6 pretty much since the 2.4 series came out, although I’ve changed distributions several times since then. The board has an Intel 440BX chipset, which used to be common as dirt, so I expect even 2.6 kernels and beyond won’t have problems with it.

I haven’t updated the BIOS on my BP6 in years, if ever. I’ve found the system to be stable–the only problems I’ve ever had could easily be attributed to memory leaks. Things would get goofy, I’d run top, and I’d find XFree86 had several hundred megs of memory allocated to it. I’d kill X, and then the system would be fine. So the rare problems I have probably aren’t the board’s fault, but rather the fault of bleeding-edge software. I was confident enough in the system’s stability that this Web site ran on that system for several weeks and I never had problems.

CPUs are supposed to be identical stepping. I’ve seen dual-CPU machines with different steppings work together without having any problems that I could directly attribute to the mismatch. It’s not a great idea and I wouldn’t run my enterprise on a mismatched system–although one of my clients does–but for hobbyist use at home at a bargain price, why not?

As far as power supplies, I ran my BP6 with dual 500s on a 235W box in an emergency. It’s had a 300W box in it for most of its life, so I’d go with a 300W unit, or a 350W unit if you want to overengineer the box a little bit.

Performance wise, I find it adequate but I run IceWM on it, and my primary browser is Galeon. Evolution runs fine on it. Some of the more resource-intensive desktop environments might pose a bit of a problem.

As far as upgradability, if you don’t overclock, the fastest Celerons you can use are Celeron-533s. If you want to do dual processing, you’re limited to the Mendocino-core Celerons. Celerons faster than 366 MHz didn’t overclock well; the limit of the Mendocino core seems to have been around 550 MHz or so.

Adapters to allow newer Celerons to work on the board ought to let you go higher (I haven’t tried it) but the newer Celerons have their SMP capability removed. So theoretically this board tops out at a 1.2 GHz Celeron with an adapter, but that pretty much defeats the purpose of getting a BP6. That’s also probably why they’re cheap when you can find them; the kinds of people who bought these boards in the first place aren’t going to be too happy with two CPUs in the 500 MHz range these days.

But I’m pretty happy with mine. I’ll run it until it dies, and that’ll probably be a while.