Help! I do tech support for everyone I know!

Here’s an interesting dilemma: How do you avoid becoming the primary technical support contact for all of your friends and family?
Richard “Rich Job” Jobity asked a really good question, didn’t he? I had to think about it for a while. That label fit me for a very long time. In the past year, 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. 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.

So if you get into a situation like I got into a year ago, when 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, I think it’s perfectly understandable for any reasonable person to be a bit upset. 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 I was fixing her dinner or watching a movie with her. The key is to remember your other obligations and don’t compromise on them.

I remember a week or two ago, I was sitting on my futon with my girlfriend, watching a movie, arms entangled in the weird way the way they tend to do when you want to be close to someone. The phone rang. I didn’t move. “You’re not going to answer that?” she asked. “No,” I said. Since when is it rude not to answer your phone? They didn’t know I was home. If I don’t want to talk at that instant, I’m not obligated to. Besides, both of us would have had to move for me to pick up the phone. So I ignored it. She looked at me like I’d paid her some kind of compliment, that I’d rather stay there with her than yak on the phone. Call me old-fashioned, but that used to go without saying.

Whoever it was didn’t leave a message. If it’d been important, either they would have 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.)

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 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 (you won’t).

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 cocktail of spyware. He runs around on Kazaa and other file-sharing networks, acquiring a cocktail of who-knows-what. He opens every e-mail attachment anybody sends to him, acquiring a cocktail 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. Half.com is your friend.
3. Never open an unexpected e-mail attachment. Even from your best 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.

And? This doesn’t mean I never get computer-related phone calls. A family member called me just this past Sunday with a noisy fan in a power supply. I found him a cheap replacement. I went over to my girlfriend’s family’s house Sunday afternoon and fixed their computer. (It made me wonder if the “4” in Pentium 4 stood for “486.” Its biggest problem turned out to be 255 instances of spyware. Yum.)

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.

Looking back on 2002

It’s been an interesting year.
The biggest change, obviously, is that I now know how it feels to have a six-figure debt. For those who are curious, it feels better than renting.

I started dating again, and while this relationship isn’t yet my longest-ever, this one certainly feels a lot better than my longest-ever, which was the first one to ever force me to ask the question, “Is this better than nothing?” and then answer, “No.” That was two and a half years ago.

In the process of dating again, I had to ask and answer that question twice.

We had a round of layoffs at work. I escaped the chopping block this time. I do believe there will be another round and I’m not at all convinced that upper management is smart enough to not cut our department. And yes, I have an exit plan.

The inescapable tide of Windows XP rendered my book obsolete.

My book seems to have gone officially out of print (I don’t know if it’s customary for publishers to tell authors those kinds of things) and it’s started to show up in remainder bins. My monthly statements are finally giving hard sales figures. At remainder-bin prices, it’s selling again. But I think it’s been more than a year since I’ve cared.

I joined my church’s board of directors this year. We haven’t fallen apart as a result.

I moved this website to a completely database-driven content management system. I really like the results. I can envision a site that does a better job at letting people get at its content, but this one is on its way to that ideal.

I questioned publicly whether I should move from b2 to Movable Type. For now, I’m going to wait until b2 hits version 1.0 and then consider it again. While MT is the industry leader, I don’t think its lead over b2 is insurmountable. And neither b2 nor MT can reach that ideal I’m envisioning without modification.

I alienated some longterm readers this year. That’s par for the course, and I know that’s something that happens just about every year. But I alienated even more people in college than I do today. I’ve always believed you can alienate some of your readers or you can bore all of them. It bothers me when it happens, but there usually isn’t a whole lot you can do about it once the damage is done. In every case I can think of, it was a matter of somebody being disappointed that I didn’t share their opinion about something or think the way they did.

I’m human. I reserve the right to be wrong.

On the other hand, I seem to have gained more in the past year than I’ve lost, as my daily visits is a generally upward trend. (I stopped keeping track about mid-year last year, then picked up again mid-year this year.) It peaked in October; I lost a couple of days in November and December due to problems upstream of me and that hurt my numbers.

There’ll be changes around here next year, but it’ll have little to do with what I say or how the site looks and everything to do bringing more of my content from the past under this roof and with finding related content more quickly and easily.

A sizable number of my readers run Linux now, and I have more computers running Linux than I have running Windows. I expect both trends will continue. Open source has been a growing trend since 1997 and there’s no reason to believe that won’t continue.

I entered the 21st century and got a DVD player and a digital camera.

Here’s to a better 2003.

Why I dislike Microsoft

“Windows 2000,” I muttered as one of my computers fired up so my girlfriend could use it. “Must mean something about the number of bugs that’ll be discovered tomorrow.”
She told me she liked Windows and asked me why I hated Microsoft so much.

It’s been a while since I thought about that. She speculated that I was annoyed that Bill Gates is smarter than me. (Which he probably is, but aside from a couple more books in print, it hasn’t gotten him anything I don’t have that I want.) There’s more to it than that.

I’m still annoyed about the foundation Microsoft built its evil empire upon. In the ’70s, Microsoft was a languages company, and they specialized in the language Basic. Microsoft Basic wasn’t the best Basic on the market, but it was the standard. And when IBM decided it wanted to enter the personal computer market, IBM wanted Microsoft Basic because nobody would take them seriously if they didn’t. So they started talking to Microsoft.

IBM also wanted the CP/M operating system. CP/M wasn’t the best operating system either, but it was the standard. IBM was getting ready to negotiate with Gary Kildall, owner of Digital Research and primary author of the OS, and ran into snags. Gates’ account was that Kildall went flying and kept the IBM suits waiting and then refused to work with them. More likely, the free-spirited and rebellious Kildall didn’t want to sign all the NDAs IBM wanted him to sign.

Microsoft was, at the time, a CP/M subcontractor. Microsoft sold a plug-in board for Apple II computers that made them CP/M-compatible. So IBM approached Microsoft about re-selling CP/M. Microsoft couldn’t do it. And that bothered Gates.

But another Microsoft employee had a friend named Tim Patterson. Tim Patterson was an employee of Seattle Computer Products, a company that sold an 8086-based personal computer similar to the computer IBM was developing. CP/M was designed for computers based on the earlier 8080 and 8085 CPUs. Patterson, tired of waiting for a version of CP/M for the 8086, cloned it.

So Seattle Computer Products had something IBM wanted, and Microsoft was the only one who knew it. So Microsoft worked out a secret deal. For $50,000, they got Patterson and his operating system, which they then licensed to IBM. Patterson’s operating system became PC DOS 1.0.

Back in the mid-1990s, PC Magazine columnist John C. Dvorak wrote something curious about this operating system. He said he knew of an easter egg present in CP/M in the late 1970s that caused Kildall’s name and a copyright notice to be printed. Very early versions (presumably before the 1.0 release) of DOS had this same easter egg. This of course screams copyright violation.

Copyright violation or none, Kildall was enraged the first time he saw DOS 1.0 because it was little more than a second-rate copy of his life’s work. And while Digital Research easily could have taken on Microsoft (it was the bigger company at the time), the company didn’t stand a prayer in court against the mighty IBM. So the three companies made some secret deals. The big winner was Microsoft, who got to keep its (possibly illegal) operating system.

Digital Research eventually released CP/M-86, but since IBM sold CP/M-86 for $240 and DOS for $60, it’s easy to see which one gained marketshare, especially since the two systems weren’t completely compatible. Digital Research even added multiuser and multitasking abilities to it, but they were ignored. In 1988, DR-DOS was released. It was nearly 100% compatible with MS-DOS, faster, less expensive, and had more features. Microsoft strong-armed computer manufacturers into not using it and even put cryptic error messages in Windows to discourage the end users who had purchased DR-DOS as an upgrade from using it. During 1992, DR-DOS lost nearly 90% of its marketshare, declining from $15.5 million in sales in the first quarter to just $1.4 million in the fourth quarter.

Digital Research atrophied away and was eventually bought out by Novell in 1991. Novell, although the larger company, fared no better in the DOS battle. They released Novell DOS 7, based on DR-DOS, in 1993, but it was mostly ignored. Novell pulled it from the market within months. Novell eventually sold the remnants of Digital Research to Caldera Inc., who created a spinoff company with the primary purpose of suing Microsoft for predatory behavior that locked a potential competitor out of the marketplace.

Caldera and Microsoft settled out of court in January 2000. The exact terms were never disclosed.

Interestingly, even though it was its partnership with IBM that protected Microsoft from the wrath of Gary Kildall in 1981, Microsoft didn’t hesitate to backstab IBM when it got the chance. By 1982, clones of IBM’s PC were beginning to appear on the market. Microsoft sold the companies MS-DOS, and even developed a custom version of Basic for them that worked around a ROM compatibility issue. While there was nothing illegal about turning around and selling DOS to its partner’s competitors, it’s certainly nobody’s idea of a thank-you.

Microsoft’s predatory behavior in the 1980s and early ’90s wasn’t limited to DOS. History is littered with other operating systems that tried to take on DOS and Windows and lost: GeoWorks. BeOS. OS/2. GeoWorks was an early GUI programmed in assembly language by a bunch of former videogame programmers. It was lightning fast and multitasked, even on 10 MHz XTs and 286s. It was the most successful of the bunch in getting OEM deals, but you’ve probably never heard of it. OS/2 was a superfast and stable 32-bit operating system that ran DOS and Windows software as well as its own, a lot like Windows NT. By Gates’ own admission it was better than anything Microsoft had in the 1990s. But it never really took off, partly because of IBM’s terrible marketing, but partly because Microsoft’s strong-arm tactics kept even IBM’s PC division from shipping PCs with it much of the time. BeOS was a completely new operating system, written from scratch, that was highly regarded for its speed. It never got off the ground because Microsoft completely locked it out of new computer bundles.

Microsoft used its leverage in operating systems to help it gain ground in applications as well. In the 1980s, the market-leading spreadsheet was Lotus 1-2-3. There was an alleged saying inside Microsoft’s DOS development group: DOS ain’t done ’til Lotus won’t run. Each new DOS revision, from version 3 onward, broke third-party applications. Lotus 1-2-3, although once highly regarded, is a noncontender in today’s marketplace.

Once Windows came into being, things only got worse. Microsoft’s treatment of Netscape was deplorable. For all intents and purposes, Microsoft had a monopoly on operating systems by 1996, and Netscape had a monopoly on Web browsers. Netscape was a commercial product, sold in retail stores for about $40, but most of its distribution came through ISPs, who bought it at a reduced rate and provided it to their subscribers. Students could use it for free. Since the Web was becoming a killer app, Netscape had a booming business. Microsoft saw this as a threat to its Windows franchise, since Netscape ran well not only on Windows, but also on the Mac, OS/2 and on a number of flavors of Unix. So Microsoft started bunding Internet Explorer with Windows and offering it as a free download for those who already had Windows, or had an operating system other than Windows, such as Mac OS. In other industries, this is called tying or dumping, and it’s illegal. Netscape, once the darling of Wall Street, was bought for pennies on the dollar by AOL, and AOL-Time Warner is still trying to figure out what to do with it. Once Microsoft attained a monopoly on Web browsers, innovation in that space stopped. Internet Explorer has gotten a little bit faster and more standards compliant since IE4, but Microsoft hasn’t put any innovation in the browser for five years. Want popup blocking or tabs? You won’t find either in IE. All of the innovation in that space has come in browsers with a tiny piece of the market.

One could argue that consumers now get Web browsers for free, where they didn’t before. Except every new computer came with a Web browser, and most ISPs provided a browser when you signed up. So there were lots of ways to get a Web browser for free in the mid-’90s.

And when it came to the excesses of the dotcom era, Netscape was among the worst. But whether Netscape could have kept up its perks given its business model is irrelevant when a predator comes in and overnight renders unsalable the product that accounts for 90% of your revenue.

Allegations popped up again after Windows 95’s release that Win95 sabotoged competitors’ office software, such as WordPerfect and Lotus 1-2-3. Within a couple of years, Microsoft Office was a virtual monopoly, with Lotus SmartSuite existing almost exclusively as a budget throw-in with new PCs and WordPerfect Office being slightly more common on new PCs and an also-ran in the marketplace. It’s been five years since any compelling new feature has appeared in Microsoft Office. The most glaring example of this is spam filtering. Innovative e-mail clients today have some form of automatic spam filtering, either present or in development. Outlook doesn’t. “Microsoft Innovation” today means cartoon characters telling you how to indent paragraphs.

And the pricing hasn’t really come down either. When office suites first appeared in 1994, they cost around $500. A complete, non-upgrade retail copy of Microsoft Office XP still costs about $500.

Pricing hasn’t come down on Windows either. In the early 90s, the DOS/Windows bundle cost PC manufacturers about $75. Today, Windows XP Home costs PC manufacturers about $100. The justification is that Windows XP Home is more stable and has more features than Windows 3.1. Of course, the Pentium 4 is faster and less buggy than the original Pentium of 1994, but it costs a lot less. Neither chip can touch Windows’ 85% profit margin.

And when Microsoft wasn’t busy sabotaging competitors’ apps, it was raiding its personnel. Microsoft’s only really big rival in the languages business in the ’80s and early ’90s was Borland, a company founded by the flambouyant Phillippe Kahn. Gates had a nasty habit of raiding Borland’s staff and picking off their stars. It didn’t go both ways. If a Microsoft employee defected, the employee could expect a lawsuit.

Well, Kahn decided to play the game once. He warmed up to a Microsoft staffer whose talents he believed weren’t being fully utilized. The employee didn’t want to jump ship because Microsoft would sue him. Kahn said fine, let Microsoft sue, and Borland would pay whatever was necessary. So he defected. As expected, Gates was enraged and Microsoft sued.

Soon afterward, Kahn and his new hire were in an airport when a Hare Krishna solicited a donation. Kahn handed him $100 on the spot and told him there was a whole lot more in it for him if he’d deliver a message to Bill Gates: “Phillippe just gave us $100 for hot food because he suspects after this lawsuit, your employees are going to need it.”

He delivered the message. Gates wasn’t amused.

It was a bold, brash move. And I think it was pretty darn funny too. But smart? Not really. Borland’s glory days were pretty much over 10 years ago. For every star Borland could lure away, Microsoft could lure away three. Borland’s still in business today, which makes it fairly unique among companies that have taken on Microsoft head-on, but only after several reorganizations and major asset selloffs.

The only notable company that’s taken on Microsoft in the marketplace directly and won has been Intuit, the makers of Quicken. Microsoft even gave away its Quicken competitor, Microsoft Money, for a time, a la Internet Explorer, in an effort to gain market share. When that failed, Microsoft bought Intuit outright. The FTC stepped in and axed the deal.

The thanks Microsoft has given the world for making it the world’s largest software company has been to sell buggy software and do everything it could to force companies and individuals to buy upgrades every couple of years, even when existing software is adequate for the task. While hardware manufacturers scrape for tiny margins, Microsoft enjoys 85% profit margins on its product. But Microsoft mostly sits on its cash, or uses it to buy companies or products since it has a terrible track record of coming up with ideas on its own. The company has never paid dividends, so it’s not even all that much of a friend to its own investors.

For me, the question isn’t why I dislike Microsoft. The question for me is why Microsoft has any friends left.

Cheap laptops from Sotec

David Huff e-mailed me this morning about a Sotec 3120X laptop that sells at Office Depot, Wal-Mart, Sam’s, Bestbuy.com, and possibly other places, for around $900 and asked if I knew anything about it.
It would appear not many people do. I found a handful of discussions on Usenet, including a couple of people who claim to have bought one. They described it as quiet, cool-running, and fast. One user said it was faster than his Dell 1.4 GHz P4 at work. (Which I don’t doubt, because the P4 is a horribly inefficient chip–the Tualatin-based Celeron is the better processor, and with its 100 MHz FSB and 256K onboard cache, it’s very nearly a P3. Its specs aren’t far off from the last P3s, the chip Intel didn’t want to sell because it made the P4 look so bad.)

One user complained about the keyboard. The itty-bitty spacebar would drive me nuts. But the only laptop keyboards I’ve ever used and halfway liked were Thinkpads. You definitely pay for the privelige–the keyboards had better be good, considering the price.

Back to the Sotec. One user reported it’s less than an inch and a half thick. It has a mobile Celeron 1.2 GHz, a SiS 630T chipset (with integrated video), a 20 GB HD, 256 MB of SDRAM, 12.1″ LCD screen, LAN and modem built in, a combo DVD/CD-RW drive, and a PCMCIA slot for expansion. It weighs 4.4 pounds, and its lithium ion battery specifies a life expectancy of about 2.5 hours. It runs Windows XP Home.

What it doesn’t have: serial or parallel ports, floppy drive, or PS/2 ports. Definitely legacy-free here. Depending on your intentions, that may or may not matter to you. (I find myself dealing with floppies a lot more often than I’d like, but part of that is because of my job.) No Firewire either, so this isn’t an instant portable video-editing machine. One user reports its memory maxes out at 384 megs. Apparently there’s 128 megs non-replaceable, and another 128-meg stick you can replace with a 256 to get to 384.

So what about Sotec? A Usenet suggests they’re not a newcomer. A post from 1995 asked for parts for a 386sx notebook manufactured by the company. There are suggestions that Sotec has made notebooks for Gateway, Dell, and Winbook in the past.

The price is definitely right, and the feature set is definitely right. It’s not a performance laptop, but most people don’t need performance laptops. It’ll read e-mail and run a word processor and presentation graphics and browse the Web just fine.

Is it a risk? Absolutely. Any laptop is. But having all the stuff integrated minimizes compatibility concerns. One of my biggest gripes about laptops has always been getting them onto networks. Usually it’s easy. When it’s not, you can just about forget it. Or you can count on networking breaking something else.

That leaves reliability. The part that most often fails is the hard drive. That’s luck of the draw. I’ve seen a lot more dead Hitachi laptop drives than IBMs. Some of my readers agree with me. At least one tells me he sees lots of dead IBMs and never sees a dead Hitachi. But I know you can’t count on getting an IBM laptop drive even in an IBM Thinkpad–occasionally those ship with Hitachi drives.

All I can say is, keep a backup of any important data you’ll keep on this or any laptop. And be ready to buy a replacement hard drive in a year or two. At least they’re not terribly expensive.

Can I recommend it? Not without seeing it and spending some time with it. From looking at the picture, I think they tried to cram way too many keys into too small of a space and they’d have been much better off without some of them.

But the price is definitely right. It’s powerful enough to be useful until it dies. With 1.2 GHz of CPU muscle and 256 megs of RAM, it’ll always run Windows XP well, and if some future version of Windows manages to outgrow it, there’ll always be a Linux that’ll run very nicely on it. It’ll give much better battery life than a P4, and it’ll outrun any low-end P4 as well. (P4-based laptops aren’t a good buy right now.)

And it’s small and light, which I know matters a lot to some people. (I’m old enough to have serviced one of the old Compaq luggables. I never had to carry one with me, but since I know and remember those, I have a hard time listening to anyone complain about the size and weight of any modern laptop.) Don’t buy one sight unseen. But don’t write it off sight unseen either.

Picking out a camcorder

I had someone ask me for some advice in picking out a camcorder yesterday. I know I’ve talked a little bit about that before, but this field is always changing, so it doesn’t hurt to revisit it.
I’m going to link to a bunch of stuff on Amazon here. Amazon’s not the only place to buy this stuff, of course, but their selection is good, and I have an affiliation with them. If someone clicks on one of these links and ends up buying something, I get a kickback. But my primary motivation is informational.

Second things second: I know they’re cheap, but think twice about analog camcorders. A Quasar VHS-C camcorder will run you $200. You get a nice 20X optical zoom and a few digital effects, and it’s nice to be able to play your tapes in your VCR, but those are the only benefits you get. The image resolution is a lot lower than with a digital camcorder, and it’s a lot less convenient to dump video from an analog camcorder into a computer for editing. Since any computer you buy new today will have at least some editing capability (current versions of Mac OS and Windows include at least rudimentary video editors, so all you’d need to add to a PC is a $25 Firewire card if it doesn’t have built-in Firewire), you’ll probably want to be able to take advantage of it. If you don’t have Windows XP or ME, you can pick up a $65 Pinnacle Studio DV, which will give you the Firewire ports, rudimentary editing software, and most importantly, slick capture and titling software. The capture software is especially nice; it’ll detect scene changes for you and catalog them. Even if you do have editing software, you might want this. It saves me a lot of time.

Digital8 cameras are getting hard to find. Their chief selling point, besides price, was the ability to use analog Hi8 tapes, which was nice if you were upgrading. If you have some Hi8 tapes and want to continue to use them and want an easy way to move them to a computer for editing, look for a Digital8 camera. But there’s a good possibility you’ll have to buy online. And the resolution isn’t as high as MiniDV–Digital8’s selling points in the past were price and backward compatibility. The price advantage is evaporating, leaving just backward compatibility as a selling point. MiniDV is the future.

Panasonic has a digital 4-in-1 device that does video, still, voice, and MP3 duties. I don’t recommend it. The image quality is substandard, its fixed focus will make it even worse, and you can’t mount it on a tripod. Its list price is $450 and I saw it at Amazon for $340, but it’s a toy. Given a choice between it and a $250 analog camcorder, I’d go analog every time.

MiniDV is pretty clearly the way to go. It’s the emerging standard, as it’s become inexpensive, the tapes are compact and reliable, and the resolution and picture quality is fantastic.

You can spend as much as you want. An entry-level MiniDV camera, such as the JVC GRDVL120U, will run you about $400. For $400, you get 16X optical zoom, S-Video output for TV playback and a Firewire connection to dump your video to computer for editing, image stabilization, the choice between manual and autofocus, and the ability to take still shots and dump them to tape.

Pay no attention whatsoever to digital zoom. Using digital zoom to get much more than double your maximum optical zoom is completely worthless. There’s enough fudge factor in NTSC television that you can get away with using a little bit of digital zoom, but with this camera, once you’ve zoomed in to 32X, you’ve cut your effective resolution from that of DVD to that of VHS tape. Zoom in much more than that, and your image will look very pixelated. This particular JVC advertises 700X digital zoom, but you definitely don’t want to use it.

You can spend three times as much on a Sony DCRPC120BT. For your money you’ll get a better lens, so your image quality will be a little bit better. Whether that makes a difference will depend mostly on the television you’re displaying on. You’ll get much higher-resolution still shots, and the ability to store your stills on a memory stick. That’s a very nice feature–no need to advance and rewind your tape to find shots, and no need to interrupt your video sequences with stills. You actually get less optical zoom. You get less digital zoom too, but that’s not important. You’ll also get a microphone jack, which is very important. The microphone built into the camera will pick up some motor noise and won’t necessarily pick up what’s happening across the room. It’s very nice to have the ability to wire up a microphone to get away from the camera motor and possibly get closer to the sound source, to keep the sound from being muffled. You probably won’t buy an external mic right away. But chances are it’s something you’ll eventually want.

Personally, when I’m on a project, I’d much rather have the inexpensive JVC (or something less expensive that offers a microphone input) because the $800 more I would spend to get the Sony would let me buy a digital still camera with much better capabilities than the Sony offers. And when I’m shooting a video, having two cameras is an advantage–I can set them both up on tripods and shoot, or hand one camera off to someone else and tell them to get me some shots. Having two cameras can get me a whole lot better picture of what’s going on. But not everybody’s shooting documentaries like me. For travel, the Sony is a whole lot more convenient and more than worth the extra money. And if you’re recording your child’s birthday party, you probably just want one camera in order to avoid turning your living room into a TV studio.

So you need to figure out what you plan to do with it.

As far as accessories go, you absolutely want a tripod. Again, you can spend as much as you want. Amazon offers a Vivitar kit for about $40 that includes a bag and a tripod. With image stabilization, you can run around shooting birthday parties and vacation scenes and have a reasonably good-looking image that won’t give you the shakes. But if you’re recording Christmas morning, then set the camcorder up across the room, then go over and open presents with your family. I know, I hate being on camera, and you might too. But I wish I had some home video footage of my Dad. I remember his laugh and I remember how he loved to joke around, but I can’t show that to anyone.

If you just want to set the camcorder up at a fixed angle and run across the room, a cheap tripod will do the job nicely. If you’re going to be standing behind the camera and panning the scene, buck up for a fluid-head tripod. You’ll be able to move the camera much more smoothly. My Bogen tripod wasn’t cheap, but I wouldn’t be without it now that I have it. I think some people with arthritis have steadier hands than I do, but even I can do good-looking pans and zooms with that tripod.

Sometimes people ask me about brands. I learned on JVC equipment, so I’m partial to it. But it’s hard to go wrong with any of what I call the Big Four: JVC, Panasonic,
Sony, or Canon. Professionals use all four brands with excellent results. Sure, every professional has a preference. But the differences among the Big Four will be pretty slight. I’m less comfortable with offerings from companies like Sharp and Samsung. They haven’t been in the business as long, and they’re consumer electronics companies. The other companies sell to professionals. Some of that expertise will inevitably filter down into their consumer products as well. And the difference in price and features between a Sharp or a Samsung and a JVC, Panasonic, Canon or Sony isn’t very much, so a top-tier offering is a better bet for the money.

Windows XP networking advice

I ran into a problem yesterday with a VPN client not working in XP. After a Usenet search, someone suggested that removing the QoS client (which does nothing useful anyway) fixes the problem about 80% of the time. In my case, that worked.
If something networking-related isn’t working right in WinXP for you, try removing the QoS client and see what happens. At the very least, you’ll speed up networking slightly, and at best, you’ll fix the problem.

Optimizing Windows 2000

Since there was no Windows 2000 version of my book Optimizing Windows, sometimes people ask me what tweaks they can use to improve Windows 2000’s performance.
It turns out there are a few things you can do to optimize Windows 2000. Here are some tips that I use on a fairly regular basis.
Read more

Dave installs Windows XP

We needed an XP box at work for testing. Duty to do the dirty deed fell to me. So after ghosting the Windows 2000 station several of us share, I pulled out an XP CD. It installed surprisingly quickly–less than half an hour. The system is a P3-667 with 128 MB RAM and an IBM hard drive (I don’t know the model).
It found the network and had drivers for all the hardware in the box. That doesn’t happen very often with Microsoft OSs, so it was nice.

I booted into XP, to be greeted by a hillside that was just begging to be overrun by tanks, but instead of tanks, there was this humongo start menu. I right-clicked on the Start button, hit Properties, and picked Classic view. There. I had a Win95-like Start menu. While I was at it, I went back and picked small icons. I don’t like humongous Start menus.

I also don’t like training wheels and big, bubbly title bars. The system was dog slow, so I right-clicked on the desktop to see what I could find to turn off. I replaced the Windows XP theme with the Classic theme. Then I turned off that annoying fade effect.

Still, the system dragged. I went into Control Panel, System, Performance. Bingo. I could pick settings for best appearance (whose choices are certainly debatable–I guess they look good if you like bright colors and have a huge monitor) or best performance. Guess which I picked? Much better.

Next, I went into Networking. I saw some QoS thing. I did a search. It’s intended to improve the quality of your network, at the price of 20% of your bandwidth. Forget that. I killed it.

After I did all that stuff, XP was reasonably peppy. It logs on and off quickly. I installed Office 2000 and it worked fine. The apps loaded quickly–just a couple of seconds. That’s how it should be. If I went in and edited the shortcuts in the Start menu to turn off the splash screens, they’d load instantly.

WinXP brings up a bunch of popups that I don’t like. If I wanted unexpected popup windows, I’d run a Web browser. I couldn’t quickly figure out how to disable those.

I couldn’t run Windows Update. It froze every time I tried.

I found a Windows XP tuning guide at ExtremeTech. I suspect turning off the eye candy will help more than most of the suggestions in that article. I suspect if I dug around I’d find other things. We’ll see if I get some time.

XP isn’t as bad as I expected, I guess. But I’m still not going to buy it.

This, on the other hand, is worth a second look. And a third. You can now run MS Office on Linux. No need to wait for Lindows, no need to abandon your current fave distro (at least if your fave distro is Red Hat, SuSE, Mandrake, Debian, or Caldera).

It’s 55 bucks. It’s available today. It brings Office 97/2000 and Lotus Notes r5 to your Linux desktop. Other Windows apps work, but their functionality isn’t guaranteed.

You can get some screenshots at CodeWeavers. It even makes the apps look like native Linux apps.

Spontaneous system reboots

Steve DeLassus asked me the other day what I would do to fix a PC that was rebooting itself periodically. It’s not him who’s having the problem, he says, it’s someone he knows. He must be trying to show up someone at work or on the Web or something.
So I gave him a few things I’d check, in order of likelihood.

Static electricity. A big static shock can send a system down faster than anything else I’ve seen. Keep a humidifier in the computer room to reduce static electricity. If you’re really paranoid, put a metal strip on your desk and connect it to ground (on your electrical outlet, not on your PC) and touch it before touching your PC. Some people metalize and ground part of their mouse pad. That’s a bit extreme but it works.

Power supply. This is the big one. A failing power supply can take out other components. And even if you have an expensive, big-brand box like a PCP&C or Enermax, they can fail. So I always keep a spare ATX power supply around for testing. It doesn’t have to be an expensive one–you just want something that can run the machine for a day or two to see if the problem goes away.
Overheating. Check all your fans to make sure they’re working. An overheated system can produce all sorts of weird behavior, including reboots. The computer we produced our school newspaper on back in 1996 tended to overheat and reboot about 8 hours into our marathon QuarkXPress sessions.

Memory. It’s extremely rare, but even Crucial produces the occasional defective module. And while bad memory is more likely to produce blue screens than reboots, it’s a possibility worth checking into. Download Memtest86 to exercise your memory.

CPU. If you’re overclocking and experiencing spontaneous reboots, cut it out and see what happens. Unfortunately, by the time these reboots become common, it may be too late. That turned out to be the case with that QuarkXPress-running PC I mentioned earlier. Had we replaced the fans with more powerful units right away, we might have been fine, but we ended up having to replace the CPU. (We weren’t overclocking, but this was an early Cyrix 6×86 CPU, a chip that was notorious for running hot.) Less likely today, but still possible.

Hard drive. I’m really reaching here. If you’re using a lot of virtual memory and you have bad sectors on your hard drive and the swapfile is using one or more of those bad sectors, a lot of unpredictable things can happen. A spontaneous reboot is probably the least of those. But theoretically it could happen.

Operating system. This is truly the last resort. People frequently try to run an OS that’s either too new or too old to be ideal on a PC of a particular vintage. If the system is failing but all the hardware seems to be OK, try loading the OS that was contemporary when the system was new. That means if it’s a Pentium-133, try Win95 on it. If it’s a P4, try Windows 2000 or Windows XP on it. When you try to run a five-year-old OS on a new system, or vice-versa, you can run into problems with poorly tested device drivers or a system strapped for resources.

Another good OS-related troubleshooting trick for failing hardware is to try to load Linux. Linux will often cause suspect hardware to fail, even if the hardware can run Windows successfully, because Linux pushes the hardware more than Microsoft systems do. So if the system fails to load Linux, start swapping components and try again. Once the system is capable of loading Linux successfully, it’s likely to work right in Windows too.

Troubleshooting advice: When you suspect a bad component, particularly a power supply, always swap in a known-good component, rather than trying out the suspect component in another system to see if the problem follows it. The risks of damaging the system are too great, particularly when you try a bad power supply in another system.

And, as always, you minimize the risks of these problems by buying high-quality components, but you never completely eliminate the risk. Even the best occasionally make a defective part.

Linux Performance Tuning

I found a very superficial Linux Journal article on performance tuning linked from LinuxToday this week. I read the article because I’m a performance junkie and I hoped to maybe find something I hadn’t heard before.
The article recommended a kernel recompile, which many people don’t consider critical anymore. It’s still something I do, especially on laptops, since a kernel tuned to a machine’s particular hardware boots up faster–often much faster. While the memory you save by compiling your own kernel isn’t huge and was much more critical back when a typical computer had 8 MB of RAM, since Linux’s memory management is good, I like to give it as much to work with as possible. Plus, I’m of the belief that a simple system is a more secure system. The probability of a remote root exploit through the parallel port driver is so low as to be laughable, but when my boss’ boss’ boss walks into my cube and asks me if I’ve closed all possible doors that are practical to close, I want to be able to look him in the eye and say yes.

The same goes for virtual consoles. If a system runs X most of the time, it doesn’t need more than about three consoles. A server needs at most three consoles, since the only time the sysadmin will be sitting at the keyboard is likely to be during setup. The memory savings isn’t always substantial, depending on what version of getty the system is running. But since Linux manages available memory well, why not give it everything you can to work with?

The best advice the article gave was to look at alternative window managers besides the ubiquitous KDE and Gnome. I’ve found the best thing I’ve ever done from a performance standpoint was to switch to IceWM. KDE and Gnome binaries will still run as long as the libraries are present. But since KDE and Gnome seem to suffer from the same feature bloat that have turned Windows XP and Mac OS X into slow pigs, using another window manager speeds things along nicely, even on high-powered machines.

I take issue with one piece of advice in the article. Partitioning, when done well, reduces fragmentation, improves reliability, and allows you to tune each filesystem for its specific needs. For example, if you had a separate partition for /usr or /bin, which hold executable files, large block sizes (the equivalent of cluster sizes in Windows) will improve performance. But for /home, you’ll want small block sizes for efficiency.

The problem is that kernel I/O is done sequentially. If a task requires reading from /usr, then /home, then back to /usr, the disk will move around a lot. A SCSI disk will reorder the requests and execute them in optimal order, but an IDE disk will not. So partitioning IDE disks can actually slow things down. So generally with an IDE disk, I’ll make the first partition a small /boot partition so I’m guaranteed not to have BIOS issues with booting. This partition can be as small as 5 megs since it only has to hold a kernel and configuration files. I usually make it 20 so I can hold several kernels. I can pay for 20 megs of disk space these days with the change under my couch cushions. Next, I’ll make a swap partition. Size varies; Linus Torvalds himself uses a gig. For people who don’t spend the bulk of their time in software development, 256-512 megs should be plenty. Then I make one big root partition out of the rest.

With a multi-drive system, /home should be on a separate disk from the rest. That way, if a drive fails, you’ve halved your recovery time because you’ll either only have to install the OS on a replacement drive, or restore your data from backups on a replacement drive. Ideally, swap should be on a separate disk from the binaries (it can be on the same disk as /home unless you deal with huge data files). The reason should be obvious: If the system is going to use swap, it will probably be while it’s loading binaries.

Still, I’m very glad I read this article. Buried in the comments for this article, I found a gem of a link I’ve never seen referenced anywhere else before: Linux Performance Tuning. This site attempts to gather all the important information about tuning Linux to specific tasks. The pros know a lot of this stuff, but this is the first time I’ve seen this much information gathered in one place. If you build Linux servers, bookmark that page. You’ll find yourself referring back to it frequently. Contributors to the site include kernel hackers Rik van Riel and Dave Jones.