Running Knoppix on a Proliant with a SmartArray controller

If you’ve ever tried to run Knoppix on a Compaq or HP Proliant with a Smart Array controller, you probably got a rude surprise.

Here’s how to make the hard drive(s) show up.Open a shell window.

Type ‘su’ (no quotes) to become root.

Type ‘insmod cciss’ — you may get a message that it’s already installed.

Type ‘cd /dev’

Type ‘MAKEDEV cciss’ (this is case-sensitive).

Now Knoppix will see your drives so you can mount them and/or edit the partitions with qtparted.

How to get that dusty old train running again

How to get that dusty old train running again

It’s the weekend after Thanksgiving. The time of year when nostalgia runs high and ancient toy trains come out of the basement or the attic and get set up again until sometime after the new year.

Well, hopefully they make it that long. Here are some tips for getting old Lionel, American Flyer, Marx, and similar electric trains running again.

Read more

Things to look for in a flatbed scanner

David Huff asked today about scanners, and I started to reply as a comment but decided it was too long-winded and ought to be a separate discussion.

So, how does one cut through the hype and get a really good scanner for not a lot of money?The short answer to David’s question is that I like the Canon Canoscan LIDE series. Both my mom and my girlfriend have the LIDE 80 and have been happy with it.

For the long answer to the question, let’s step through several things that I look for when choosing a scanner.

Manufacurer. There are lots of makers of cheap and cheerful scanners out there. Chances are there are some cheap and nasty ones too. Today’s cheap and nasty scanners will be a lot better than 1995’s crop of cheap and nasties, since the PC parallel port was a huge source of incompatibilities, but I want a scanner from a company with some experience making scanners and with good chances of still being around in five years.

Driver support. Much is made of this issue. But past track record isn’t much of an indicator of future results. HP and Umax infamously began charging for updated drivers, for example. But at least I could get a driver from HP or Umax, even if it costs money. My Acer scanner is forever tethered to a Windows 98 box because I can’t get a working driver for Windows 2000 or XP for it.

Umax used to have a stellar track record for providing scanner drivers, which was why I started buying and recommending them several years ago. I don’t know what their current policy is but I know some people have sworn them off because they have charged for drivers, at least for some scanners, in the recent past. But you can get newer drivers, in many cases, from Umax UK.

But that’s why I like to stick with someone like Canon, HP, Umax, or Epson, who’ve been making scanners for several years and are likely to continue doing so. Even if I have to pay for a driver, I’d rather pay for one than not be able to get one. Keep in mind that you’ll be running Windows XP until at least 2006 anyway.

Optical resolution. Resolution is overrated, like megahertz. It’s what everyone plays up. It’s also a source of confusion. Sometimes manufacturers play up interpolated resolution or somesuch nonsense. This is where the scanner fakes it. It’s nice to have, but there are better ways to artificially increase resolution if that’s what you’re seeking.

Look for hardware or optical resolution. Ignore interpolated resolution.

Back to that overrated comment… Few of us need more than 1200dpi optical resolution. For one thing, not so long ago, nobody had enough memory to hold a decent-sized 4800dpi image in memory in order to edit it. If you’re scanning images to put them on the Web, remember, computer screen resolution ranges from 75 to 96dpi, generally speaking. Anything more than that just slows download speed. For printing, higher resolution is useful, but there’s little to no point in your scanner having a higher resolution than your printer.

I just did a search, and while I was able to find inkjet printers with a horizontal resolution of up to 5760dpi, I found exactly one printer with a vertical resolution of 2400dpi. The overwhelming majority were 1200dpi max, going up and down.

Your inkjet printer and your glossy magazines use different measurements for printing, but a true 1200dpi is going to be comparable to National Geographic quality. If your photography isn’t up to National Geographic standards, megaresolution isn’t going to help it.

Bit depth. If resolution is the most overrated factor, bit depth is the most underrated. Generally speaking, the better the bit depth, the more accurate the color recognition. While even 24 bits gives more colors than the human eye can distinguish, there is a noticeable difference in accuracy between scans done on a 24-bit scanner and scans from a 36-bit scanner.

If you have to choose between resolution and bit depth, go for bit depth every time. Even if you intend to print magazines out of your spare bedroom or basement. After all, if the color on the photograph is off, nobody is going to pay any attention to how clear it is.

Size and weight. Some flatbed scanners are smaller and lighter than a laptop. If they can draw their power from the USB port, so much the better. You might not plan to take one with you, but it’s funny how unplanned things seem to happen.

The HP 4101mfp multifunction device

I set up an HP 4101mfp printer-scanner-fax machine today. My first impressions weren’t good, but once we actually had it working, it worked as advertised.

I’m not about to buy one for home, but if I need a multifunction device in the office (or a client does), I won’t feel too bad about recommending this one. Read more

Troubleshooting a Compaq Proliant 1600

I still work on a lot of Compaq Proliant 1600s. In their day, they were a very versatile server, packing lots of drive bays and open expansion slots into a 5U package. They were also very reliable.

Now that they are five years old or even older, they are less so. But I’ve collected some good suggestions from Compaq and HP technicians about working on them.The biggest problem with the 1600 is that so many parts are socketed. Over time, socketed components tend to work themselves loose. So, when a 1600 crashes a lot but will pass its built-in diagnostics with flying colors, the best thing to do is to completely disassemble it and put it back together.

If it seems to be having memory problems, don’t just reseat the processor board and/or replace the memory. I had one 1600 exhibit memory failures that would not go away until I replaced the PCI board, of all things. Why? Beats me. The HP technician was as stumped as I was. So reseat that board too.

It never hurts to clean the connectors when you have the system apart. Get some zero-residue contact cleaner from a hardware or auto parts store. Be sure it’s zero-residue. A lot of contact cleaners contain oil, which isn’t going to help intermittent electrical connections at all. If in doubt, skip the contact cleaner entirely and clean the contacts with a cotton swab and rubbing alcohol instead. Need I also mention you need to stay grounded at all times while doing these procedures?

When replacing the PCI and CPU modules, you have to use a lot of force. Don’t rely on the plastic releases on the back to put them in. Whenever I’ve seen a veteran Compaq technician reinstall one of these modules, he’s slammed the module into the back computer with so much force that it moved the system. If you don’t think you’re going to break it, you probably aren’t doing it hard enough.

Newer Proliant servers have many fewer socketed components, so their long-term reliability prospects are higher. They also usually have LEDs that indicate failed components, making diagnostics virtually irrelevant and system repair much more straightforward. But when replacement isn’t an option just yet, it’s nice to know there are things to do to return a 1600 to life.

Hard drive upgrade tips for older PCs

A hard drive upgrade is one of the best ways to extend the usable lifespan of a computer.

A lot of people come to this site looking for hard drive upgrade advice, but I realized that it’s been a long time since I’ve written anything about that. Since there are some gotchas, I need to address them.

Read more

How to get your RSS/RDF feed working with Mozilla Firefox\’s Live Bookmarks

As soon as I upgraded to Mozilla Firefox 1.0, I started noticing that when I visited certain sites that had RSS/RDF feeds, a big orange “RSS” icon showed up in the lower right hand portion of the window.

That’s cool. Click on that, and you can instantly see that site’s current headlines, and know if the site has changed, just by looking in your bookmarks.

Except my site has an RSS feed and that icon didn’t show up. Here’s how I fixed it.At first I figured Firefox was looking for the standard “XML” icon everyone uses. So I added that. No go.

So I investigated. A Google search didn’t tell me anything useful. So I went to Slashdot’s page and viewed the source. Four lines down, I found my answer.

In your section, you need to add a line. In my case, since I run GeekLog, it was this:

LINK REL=”alternate” TITLE=”Silicon Underground RSS” HREF=”//dfarq.homeip.net/backend/siliconunderground.rdf” TYPE=”application/rss+xml”

Just substitute the URL for your RSS feed for mine. The two slashes at the beginning are necessary. The whole line has to be enclosed in , of course. (I can’t show them here because my blogging software is trying to protect me from myself.)

But since Geeklog doesn’t have an index.html file, and its index.php file is mostly programming logic, where do you add your code?

In your themes directory, in the file header.thtml, that’s where. I put mine right after the line that indicates the stylesheet.

The location for other blogging systems will vary, of course. But I notice some seem to do it automatically.

Now your readers can keep track of you without constantly refreshing your page (which they probably won’t do) and without having to run a separate RSS aggregator. Pretty cool, huh?

Any Unix gurus care to help me with mod_rewrite?

I’ve watched my search engine traffic decrease steadily for the past few months since I changed blogging software. It seems most engines don’t care much for the super-long arguments this software passes in its URLs.

The solution is mod_rewrite, and I think my syntax looks correct, but it’s not working for me.The goal is to fake out search engines to make them think they’re looking at static files. Search engines are reluctant to index database-driven sites for fear of overloading the site. Since I can’t tell them not to worry about it, I have to make the site look like a static site.

To that end, I created a section at the end of my httpd.conf file:

# rewrites for GL

RewriteEngine on
RewriteRule ^/article/([0-9]+)$ /article.php?id=$1 [NC,L]

This line should make the software respond to Thursday’s entry (https://dfarq.homeip.net/article.php?story=20040902200759738) if it’s addressed as https://dfarq.homeip.net/article/20040902200759738.

Once mod_rewrite is working, in theory I can modify the software to generate its links using that format and watch the search engines take more of a liking to me again. But I’ve got to get mod_rewrite going first, and I’m stumped.

Any expert advice out there?

Thanks in advance.

Thoughts on backups

Backups have weighed heavily on my mind lately. When you have 125 servers to tend to at work, chances are one of them is going to fail eventually. Really what seems to happen is they fail in bunches.

One of my clients has a problem. He’s out of capacity. And that’s gotten me thinking about backups in general.You see, my client’s golf buddies are telling him nobody backs up to tape anymore. Backing up to disk is the hot thing now. Here’s the theory. Your network is fast, right? Why make it wait on the tape drive? Back up all your servers to disk instead, and they can all back up at once, and hours-long backups take minutes instead, and restores take seconds. And no more paying $3,000 for tape drives and $6,000 for a rotation of tapes for it!

Now here’s the problem. A CIO hears "disk" and he thinks of that 400-gigabyte IDE drive he saw in the Sunday paper sales ad for $129 with a $60 mail-in rebate. (It wasn’t really quite that big, and it wasn’t really quite that cheap, but these things are always better on Monday morning than they were the day before.)

No enterprise bases something as important as backups on a single consumer-grade IDE disk. For one thing, it won’t be fast enough. For another, they’re not designed to be used that heavily, that frequently. An enterprise could get away with something like HP’s $1200 entry-level NAS boxes, which use cheap IDE drives but in a RAID configuration, so that when one of those cheap disks fails, it can limp along for the rest of the night until you swap out the failed drive. The chances of one drive failing are small but too large for comfort; the chances of two drives failing at once are only slightly better than Ronald Reagan winning the Republican primary this year. With Abraham Lincoln as his running mate.

One can set up some very nice backups on a Gigabit Ethernet setup. Since Gigabit’s theoretical bandwidth is about 3 time that of Ultra320 SCSI’s theoretical bandwidth, you can back up three servers at once at full speed. Drop in a second NIC, and you can back up six. In reality, the disks in the NAS box can’t come close to keeping up with that rate, but the disk can still back up everything much faster than tape will. Even a lightning-fast state of the art 200/400 GB LTO drive.

Frankly, with such a setup it becomes practical to back up your most important servers over the lunch hour, to avoid losing half a day’s work.

But you don’t get it for $129.

And in reality, no enterprise in its right mind is throwing out tapes either. If they back up to disk, they spool that backup to tapes the next day, so they can store the tapes offsite for archival and/or disaster recovery purposes.

How important is this? I remember about a year ago getting a request for a file that was changed in the middle of a week, and the person wanted that copy from the middle of the week, not from our Friday backups that are archived longer. Even with a tape rotation of 40 tapes, I couldn’t get the file. The tape had been overwritten in the rotation a day or two before.

While rare, these instances can happen. A 40-tape rotation might not be enough to avoid it. Let alone just a couple hundred gigs of disk space.

But what about home?

Consumer tape drives had a terrible reputation, and based on my experience it was largely deserved. The drives had a terrible tendency to break down, and the failure rate of the tapes themselves was high too. The lack of comfort with enterprise-grade tape that I see in my day-to-day work may stem from this.

The last time I was in a consumer electronics store, I don’t think I saw any tape drives.

I suspect most people back their stuff up onto optical disks of some sort, be it CD-R or RW, or some form of writable DVD. The disks are cheap, drives that can read them are plentiful, and if floppies are any indication, the formats ought to still be readable in 20 years. My main concern is that the discs themselves may not be. Cheap optical discs tend to deterriorate rapidly. Even name-brand discs sometimes do. We’ve had great luck with TDK discs ever since Kodak took theirs off the market, but all we can say is that over the course of three years, we haven’t had one fail.

The last time my church’s IT guy called asking about backups, we happened upon a solution: a rotation of USB hard drives. Plug it in, back it up, and take the drive home with you. It’s cheap and elegant. Worried about the reliability of the drives? That’s why you use several. Three’s the minimum; five drives would be better. Use a different drive every day.

It’ll work, and it’s pretty affordable. And since the drives can be opened up and replaced with internal drives, it has the potential for cheap future upgrades.

How about the reliability of hard drives? Well, I have a box full of perfectly readable 120-meg drives in my basement. They date from 1991-1993, for the most part. I bought them off eBay in the mid 1990s, intending to put them in computers I would donate to churches. The computers never materialized, so the drives sat. I fire one up every once in a while out of curiosity. The copies of DOS, Windows 3.1, and the DOS Netware client that were on them when I got them are still there.

Some technology writers have observed that modern IDE hard drives seem to have a use-by date; they just seem to have a tendency to drop dead if they sit unused for too long. I see this tendency in a lot of devices that use inexpensive electric motors. Starting them up every once in a while and giving them a workout to keep the lubricants flowing and keep them from turning glue-like seems to be the best way to keep them working.

At this stage, I’m less worried about the long-term viability of hard drives than I am about optical discs. Ask me again in 20 years which one was the better choice, and I’ll be able to answer the question a lot better.

If you’re stuck using optical discs, the best advice I can give is to use a brand of media with a good reputation, such as TDK, make multiple copies, and store them in a cool, dark, dry place. The multiple copies should preferably be stored in different cool, dark, dry places. Light seems to break down optical discs, and cooler temperatures as a general rule slow down chemical reactions. Dryness prevents chemical reactions with water and whatever the water might manage to pick up.

Help! I do tech support for everyone I know! (Version 1.1)

Here’s an interesting dilemma: How do you avoid becoming the primary technical support contact for all of your friends and family?

(If this sounds vaguely familiar, yes, this is a revised version of something I wrote a year and a half ago.)This was a question Richard “Rich Job” Jobity asked two Christmases ago. I thought it was an unbelievably good question. I had to think about the answer for a while. That label fit me for a very long time. Sometime within the last couple of years it stopped, but I never knew exactly why. He made me think about it, and I found I’d done some interesting things on a subconscious level.

There was a time when I didn’t mind. I was 16 and still learning, I had some disposable time on my hands, and, frankly, I enjoyed the attention. You can learn a lot by fixing other people’s computers. It can also be a good way to meet lots of interesting people. And I used at least one of those friends as a reference to get my first three computer-related jobs. But over time, my desire changed.

I think a good first step is to identify exactly why it is you don’t want to be the primary technical support contact for all your friends and family.

In my case, I spend 40 hours a week setting up and fixing computers. And while I definitely spend some time off the clock thinking about computers, I also definitely want to spend some time off the clock thinking about something other than computers.

I have a life. I have a house to take care of, I have meetings to go to, and I have a social life. Not only that, I have bills to pay and errands to run, and physical needs to tend to as well, like cooking dinner and sleeping. And people get really annoyed with me for some reason if I don’t ever wash my clothes.

I’ve been in that situation. Once I had a friend calling me literally every night for a week with some new computer problem and keeping me on the phone for several hours a night while we tried to sort them out. A couple of years before that, someone in Washington was running a computer company and using me as his primary (unpaid) technical support, often taking an hour or two of my day, and getting upset if more than about 12 hours passed without me responding.

I think it’s perfectly understandable for any reasonable person to not like situations like this. So here are my tips for someone who wants to head off that kind of a problem.

Have realistic expectations on all sides. So the first step is to make sure your friends and your family understand that you have responsibilities in life other than making sure their computers work. You’ll do your best to help them, but it’s unrealistic to expect you to drop everything for a computer problem the same way you would drop everything for a death in the family.

Limit your availability. Don’t help someone with a computer problem while you’re in the middle of dinner. You’ll be able to concentrate better without your stomach growling and you won’t harbor resentment about your dinner getting cold. Have him or her step away from the computer and go for a walk and call back in half an hour. The time away from the computer will clear his or her mind and help him or her better answer your questions. Don’t waver on this; five-minute problems have ways of becoming hour-long problems.

Here’s a variant of that. I had a friend having problems with a Dell. She called Dell. She got tired of waiting on hold. “I know, I’ll call Dave,” she said. “Dave’s easier to get ahold of than this.”

She may have tried to call me, but last week I was everywhere but home, it seemed. She didn’t leave a message, so I didn’t know she’d called. The moral of the story: Don’t be easier to get ahold of than Dell. Or whoever it was that built the computer or wrote the software.

What if I’d been home? It depends. If I’d been home and playing Railroad Tycoon, I’d be under more obligation to help a friend in need than I would be if I were home but my girlfriend was over and we were in the middle of dinner or a movie. The key is to remember your other obligations and don’t compromise on them.

Sometimes that means not answering the phone. In this day and age when 50% of the population will answer their cellphone even if they’re sitting on the toilet, this is heresy. I usually make a reasonable effort to answer the phone. But if I’m in the middle of something, I won’t. At least one time when I made no effort to answer the phone when my girlfriend was over, she took it as one of the biggest compliments she ever got. (That relationship didn’t last, so maybe I should have answered the phone, but hey, at the time I didn’t feel like it.)

Whoever it was didn’t leave a message. If it’d been important, either they would have left a message or they would have called me back. (Maybe it was the friend who’d thought of using me as a substitute for Dell tech support. Who knows.)

Don’t do a company’s work for them. If someone’s having a problem with a Dell, or having a problem dialing in to the Internet, I stay away from the problem. If a Dell is having hardware problems, the user will have to call Dell eventually anyway, and the tech will have procedures to follow, and there’s no room in those procedures for a third-party diagnosis. Even if that third party is a friend’s cousin’s neighbor who supposedly wrote a computer book for O’Reilly three years ago. (For all the technician knows, it was a book about Emacs, and you can know Emacs yet know a whole lot of nothing about computer hardware, especially Dell hardware. But more likely he’ll just think the person’s lying.) For the record, when I call Dell or Gateway or HP, I jump through all the same stupid hoops. Even though I’ve written a computer book and I’ve been building and fixing computers my entire adult life.

And if someone can’t dial into an ISP, well, I may very well know more about computers than the guy at the ISP who’s going to pick up the phone. I may or may not be more intelligent and and more pleasant and more articulate than he is. But the fact is, I can only speculate about whatever problems the ISP may be having. And seeing as I don’t use modems anymore and haven’t for years, I’m not exactly in a good position to troubleshoot the things. Someone who does tech support for an ISP does it every day. He’s going to do a better job than me, even if he’s not as smart as I am.

Know your limits. A year ago, a friend was having problems with OS X. She asked if I’d look at it. I politely turned her down. There are ideal circumstances under which to try to solve a problem, but the moment you’re seeing the OS for the first time isn’t it. She called Apple and eventually they got it worked out. It’s a year later now. Her computer works fine, we’re still on speaking terms, and I still haven’t ever seen OS X.

Around the same time, another friend toasted her hard drive. I took on that challenge, because it was PC hardware and she was running an operating system I’d written a book about. It took me a while to solve the problem, but I solved it. It was a growth opportunity for me, and she’s happy.

And this is related to the next point: If you’re not certain about something, say so. It’s much better to say, “This is what I would do, but I’m really not sure it’s the best thing to do” than it is to give some bad advice and pretend that it’s gospel. Get your ego out of the way. There’s no need to try to look good all the time. No matter what you do, you’ll be wrong sometime. And one of the easiest ways to be wrong is to run your mouth when you don’t know what you’re talking about.

Limit your responsibility. If your uncle has a six-year-old PC running Windows 95 and ran out and bought a USB-only printer because it was on sale at Kmart and now he’s having problems getting it running and he never asked you about any of this, how much responsibility should you be willing to shoulder to get that printer running?

I’m inclined to say very little. It’s one thing to give some bad advice. It’s another to be dragged into a bad decision. If the only good way to get the peripheral running is to buy Windows XP and wipe the hard drive and install it clean, don’t let that be your problem.

Don’t allow yourself to be dragged into giving support for free software downloaded off the ‘Net, supercheap peripherals bought from who-knows-where, or anything else you can’t control.

You can take this to an extreme if you want: Partition the hard drive, move My Documents over to the second partition, and then create an image of the operating system and applications (installed on the first partition, of course). Any time you install something new, create a new image. When your friend or relative runs into trouble, have him or her re-image the computer. He or she can reinstall Kazaa or whatever notorious app probably caused the problem if desired, but you can disclaim responsibility for it.

Which brings me to:

Disclaim all responsibility for poor computer habits. Gatermann and I have a friend whose brother repeatedly does everything I’d do if I wanted to set out to mess up someone’s computer. He downloads and installs every gimmicky piece of free-with-strings-attached software he can find, turning his computer into a bevy of spyware. He runs around on Kazaa and other file-sharing networks, acquiring a busload of who-knows-what. He opens every e-mail attachment anybody sends to him, amassing a large collection of viruses. He probably does things I’ve never thought of.

Gatermann installed antivirus software on the computer, and we’ve both run Ad-Aware on it (if I recall, one time I ran it I found 284 instances of spyware). Both of us have rebuilt the system from scratch numerous times. The kid never learns. Why should he? Whatever he does, one of Tim’s friends will come over and fix it. (I guarantee it won’t be me though. I got sick of doing it.)

Some good rules to make people follow if they expect help from you:
1. Run antivirus software and keep it current. This is a non-negotiable if you’re running Windows.
2. Stay off P2P networks entirely. Their clients install spyware, and you know about the MP3 buffer overflow vulnerability in WinXP, don’t you? Buy the record and make your own MP3s. Can’t afford $17 CDs? Buy them used on Half.com then.
3. Never open an unexpected e-mail attachment. Even from your best friend. It’s trivially easy to make e-mail look like it came from someone else. If someone who knows both of you got a virus, you can get virus-infected e-mail that looks like it’s from that friend.
4. If you don’t need it, don’t install it. Most free Windows software comes with strings attached in the form of spyware, these days. If you don’t want to pay for software, run Linux.
5. If you must violate rule 4, run Ad-Aware religiously.

Don’t take responsibility when someone asks your advice and then refuses to follow it. That unpaid gig doing tech support for a computer company in Washington ended when he had a computer that wouldn’t boot. He sent me the relevant files. I told him how to fix the problem. The next day he complained it didn’t help, and sent me the files again. It was obvious from looking at the files that he didn’t do what I told him to do. I called him on it. He got defensive. He caught me on a bad day and I really didn’t want to hear it. The next day he sent me a long list of questions. I answered the first two or three, then said, “Sorry, I’m out of time.”

I never heard from him again. But at that point it was just as well. Why help someone who doesn’t respect you enough to follow your advice?

A less extreme example was when an ex-girlfriend’s younger brother refused to give up Kazaa. Every time I fixed the computer, he reinstalled Kazaa and one problem or another came back. Finally I told him, her, and their parents that I’d fixed the problems, but they were going to keep coming back as long as he used Kazaa. Ultimately they decided that free music was more important than a stable computer and staying within the law, but that was their decision.

Have other interests besides computers. My former high school computer science teacher took me aside a few years ago and asked me if it wouldn’t be great if someday people asked me as many questions about God as they were asking me then about computers.

I have relatives who know I’m into Genealogy, and they know that I’ve traced one branch of my family through William the Conqueror and all the way back to before the time of Christ. But some of them don’t know I fix computers for a living.

Some nights when I come home from work, I don’t even turn a computer on. I go straight to the basement, plug in my transformers, and watch a Lionel train run around in circles. I might stay down there all night except for when the phone rings (there are no phone outlets in my basement) or for dinner. Ronald Reagan used to do that. He said it helped him relax and take his mind off things. My dad did too. It works. And no, there’s no computer hooked up to it and there won’t be. This is where I go to escape from computers.

So I don’t find I have the problem anymore where people only want to talk to me about computers. Balance is important. Don’t let your computer knowledge keep you from pursuing your other interests.

Charge money. I don’t charge my family members, but with very few exceptions, I don’t do free technical support. I do make sure I give friends, acquaintances, and neighbors a good deal for their money. But if helping them is going to keep me from mowing my lawn, or if it’s going to force me to cancel plans with my girlfriend, then I need to be compensated enough to be able to pay someone else to mow my lawn, or to take my girlfriend out for a nice dinner that more than makes up for the cancellation.

It’s all about balance. So what if your entire block has the most stable computers in the world, if your grass is three feet tall and you have no friends and no significant other because you can’t make time to meet anyone for dinner?

I’ve had employers bill me out at anywhere from $50 to $75 per hour. Under ideal conditions, where they drop the computer off with the expectation of getting it back within 2 weeks, I bill myself out at significantly less than that. But for on-site service at odd hours, I believe it’s perfectly appropriate for a computer professional to bill at those kinds of rates.

Even if you’re a hobbyist, you need to be fair to yourself. Computer repair is a skill that takes longer to learn than mowing lawns, and the tools required are every bit as specialized and every bit as expensive. In St. Louis, many people charge what amounts to $25 an hour to mow a lawn.

And? This doesn’t mean I never get computer-related phone calls. One Sunday when a family member called me with a noisy fan in a power supply, I found him a cheap replacement. I’ve fixed girlfriends’ computers before. The last computer I built was a birthday present for my current girlfriend.

But I’m not afraid to answer the phone, I don’t find myself giving people longshot answers just to get them off the phone long enough for me to go somewhere or start screening my phone calls. And I find myself getting annoyed with people less. Those are all good things.