An Unusual Landing Zone

This is what it’s all about.

This is why I fly helicopters. So I can visit places like this: a mesa overlooking the north Phoenix area.

Zero Mike Lima on a Mesa

This photo was taken by my friend Jason, who proposed to his wife during a camping trip on this spot. He’d sent me some GPS coordinates and a photo of the place from his plane and asked me to take them up there. I wrote about the gig here.

I ran into Jason the other day at the airport and he told me he had some photos from that trip. He e-mailed them to me yesterday. This one says it all and is now the desktop picture on my main computer.

I distinctly remember taking off from this spot. Lifting about 5 feet off the ground, nosing forward, and just “dropping” off the edge of this cliff. (No, I didn’t do a pushover; I’m not insane.) It was sweet.

On Geniuses

Why I don’t Genius Bar hop and other comments regarding my recent hard disk problem.

One of my jobs as a blogger is to produce at least one blog entry a week. As you may have noticed if you follow this blog, it looks like I’ve been slacking off lately. Well, I just want to take a few moments to assert that looks may be deceiving.

Last week was a busy one for me. I finally got my computer back up and running after its second hard disk crash in a year. This crash was far more serious than the last and required the geniuses at the Apple Store to fix.

Now I know that lots of Mac pros laugh at the word “genius” when applied to the Apple Store’s tech support folks. And I do agree that it would be difficult to call any of them geniuses in the true sense of the word. (Think Einstein.) But if you were to compare their computer skills to the average Mac user’s, they could indeed be considered geniuses. They know a lot more about the current computer models than 95% of Mac users. Sadly, I fit into that 95% these days. I could tell you all kinds of things about fixing a Mac II cx or a PowerMac 7100/66 — and that’s because I used to teach a course about troubleshooting those computers running System 7. Nowadays, my troubleshooting capabilities are limited to what I need to know — like much of my other knowledge — and I don’t really need to know all the things the geniuses need to know to do their daily fix-it jobs.

So I’m not uncomfortable applying the word genius to many (but not all) of them. To me, some of them really are geniuses when it comes to diagnosing and fixing Mac problems.

I’ll also be the first to say that the capabilities of an Apple Store genius staff on any given day for any given store is hit or miss. It all depends on each staffer’s experience, knowledge, and interest in the topics he or she needs to know. I was at the Genius Bar in the Chandler, AZ store on Monday and the geniuses that day were pretty good. One of them was a super genius, the one who helped me was definitely above average, and the guy working the iPod slot was about average. (Let’s face it: it doesn’t take much skill to fix an iPod problem. Every iPod should come with a cheat sheet printed on back that explains how to reset it; that will resolve 95% of an iPod’s problems. The iPod guy probably resets a lot of iPods in a day. I’ve gotten so good at it that I can reset mine with one hand while flying my helicopter. Darn vibrations lock it up more often than I’d like to admit.)

I’ve had repeatedly bad luck at the Biltmore Apple Store in Phoenix, which is at least 30 miles closer to my house. The two times I tried to get assistance there, the lead Genius didn’t seem interested in looking deeply into my problem and didn’t seem to care whether it was resolved or not. On my fried motherboard problem, it seemed that she spent more time telling me how much it would cost to fix the problem than diagnosing what the problem was. This, coupled with her obvious lack of sympathy, made me doubt her diagnosis, so I had to go to another store (Chandler) to get a second opinion. I got a bad taste in my mouth (so to speak) from the experience. And that’s why I don’t go to the Biltmore store anymore.

Oddly enough, sympathy for my problem seems to be important to me. My main work computer or “production” machine (currently a Dual G5) is like a partner to me. It holds onto the projects I’m working on, it has the tools I need to get the job done as smoothly as possible. When it works right, we’re a team getting the job done. When it starts acting up, I get concerned. It’s not just a machine on the fritz. It’s a work partner feeling ill. What’s the problem? Can I fix it before it becomes critical? Is its motherboard about to go (again)? Or its hard disk? Will I lose data? Will I need to take it to the hospital (fix-it place) to get it working right again? How long will we be apart? And, of course, the selfish questions, like how long will I be unable to work?

The geniuses at the Chandler store are always sympathetic to my problem. They understand that my computer isn’t just a machine I use for e-mail and to surf the Web. They understand that its hard disk contains lots of important information — including books in progress — and the tools I need to get my work done. They understand that without my production computer, there’s very little real work I can do. And even though they don’t necessarily push any harder to complete a job for me than they do for anyone else, they make it seem as if my problem is one of the most important ones they’ll tackle that day. And they soothe me with reasonable reassurances that make it easier to face the 90-mile drive home and wait for their call.

This time around, the problem was a toasted hard disk. Personally, I believe it has something to do with my Firewire ports — it occurred while my iSight was plugged in and I was attempting to suck something off a portable Firewire hard drive. (My motherboard problem also manifested itself when working with multiple Firewire devices, including an iSight, so I’m very wary of using it these days.) They replaced the hard disk — which IS something I could have done myself if I really wanted to — and managed to get about 50% of the data off my old hard disk before it ceased to function at all. This cost me dearly, but the way I see it, I was paying for my own stupidity. If I’d had my entire Home folder backed up, recovery wouldn’t have been necessary at all and I could have saved the $150.

What hurts even more is that I’d written an article for Informit.com about backing up with Fetch before I had the problem and neglected to utilize my own instructions to protect myself.

The computer was done the next day and my husband, Mike, picked it up on his way home. It isn’t exactly on his way — he works about 15 miles north of there — but it was a lot more convenient for him than for me to make the 180-mile round trip drive. On Wednesday morning, I set about restoring the whole computer to it’s normal setup. I didn’t like the way the Apple folks had set up the machine — for some reason I was really bugged about my home folder being called maria (note the lowercase) rather than its usual mlanger (which I’ve used on all my computers for years). (Is that anal or what?) So I pulled off the recovered data, reformatted the hard disk, and spent the next two days installing software and updates. The updates were particularly painful now that I’m on the super-slow wireless Internet connection I whined about elsewhere in this blog. The 139 MB Mac OS X 10.4.8 combined updater took quite a while to suck off the Internet before I could install it.

Fortunately, I managed to pull e-mail messages, endo settings and contents, ecto contents, and some other stuff off my PowerBook. My iCal and Address book data was already set up to synchronize with .Mac, so getting all that data moved over was very easy. The only thing of real value that I lost was Chapter 6 of my Excel 2007 for Windows book, which I’d been working on for the second time. (The first revision went bad and I started from scratch. So today I look forward to starting my Chapter 6 revision for the third time. I knew it would be the book’s Chapter from Hell, but I couldn’t imagine how hellish it would be.)

By Friday, the computer was 90% back to its old self and I was working on it regularly instead of my laptop. So I was out of commission for two full weeks. I blame myself for that, too, letting the disk recovery software run as long as I did before finally bringing it to the geniuses.

Computer Wait Speed

Maria Speaks Episode 34: Computer Wait Speed

My current computer woes remind me of something I heard long ago.

A long time ago — ten or more years, which is the middle ages in terms of the computing industry — computers were being marketed primarily on the basis of processor speed. Every time Intel or Motorola would come out with a new processor chip, members of the geeky set hurried to the stories to buy a new computer or upgrade that would bring their machines up to speed. It was then that I heard this rather curious statement:

All computers wait at the same speed.

The statement, of course, was meant to poke fun at computer users. At least that’s how I read it. Your computer could be the fastest in the world, but if you weren’t up to speed, all that extra fast processing power would be wasted. After all, each time a computer completes an instruction — whether it’s opening a dialog box, applying a font style change to some text, or matching e-mail addresses in your address book when you type into a field in a new e-mail message form — the computer faithfully waits…for you. As long as it has to. And while computer processors are getting ever faster, computer users are simply not keeping up.

Let Me Tell You About My Mom

All this reminds me of a sort of funny story. My mother, who has been using computers for nearly as long as I have, is not what you’d call a “power user.” She pretty much knows what her computer can do for her and she can usually make it do it. But she’s not the kind of person who pushes against the boundaries of what she knows very often. And when she’s working with her computer, she spends a lot of time making the computer wait while she thinks about what’s onscreen and how she needs to proceed. That isn’t a big deal — I’d say that 95% of computer users are like her. People react to what the computer does rather than anticipate what’ll come up next and have the next task prepared in their minds when the computer is ready to accept it. And all these computers are waiting at the same speed.

Anyway, for years, my Mom used dial-up Internet services. Most of us did. But as better alternatives came around and Web sites got ever more graphic-intensive, most of us updated our Internet connection technology to take advantage of cable or DSL or some other higher bandwidth connection. (I was literally the first (and only) kid on the block to get ISDN at my home. This was back in the days before cable and DSL Internet service. It cost me a fortune — heck, they had to dig a trench to lay new telephone lines to my house — but I simply could not tolerate busy signals, dropped carriers, and slow download speeds for my work. It operated at a whopping 128 Kbps and cost me $150/month. Ouchie!) My Mom, on the other hand, didn’t upgrade. She continued to surf the Internet through AOL on a dial-up connection, right into late 2006. Worse yet, she refused to get a second phone line, so she limited her Internet access or was impossible to get on the phone.

Let me take a little side trip here to discuss why her attitude wasn’t a bad thing at all. Personally, I believe we have too much dependence on the Internet. I recently read “I Survived My Internet Vacation” by Lore Sjöberg on wired.com, which takes a comic but all-too-real look at Internet withdrawal. If you’re the kind of person who uses the Internet to check the weather, look up vocabulary words, and find obscure information throughout each day without really needing that information, you owe it to yourself to read the piece. It really hit home for me. So in the case of my Mom, the fact that her Internet use was minimal wasn’t such a bad thing. Not at least as far as I was concerned.

But it had gotten to the point with my Mom that she was spending more time waiting for her computer than her computer was waiting for her. And it had nothing to do with processor speed. It was her dial-up Internet connection that made it slow.

At first, I don’t think she understood this. I think that when she replaced her aging Macintosh with a PC about 2 years ago, she really expected everything to get faster. But the Internet got slower and slower for her, primarily because Web designers don’t design sites for dial-up connections. (Shame on them!) The Internet had become a tedious, frustrating place for her and she couldn’t understand why so many people were spending so much time using it.

In November 2006, I came for a visit. I had to look up something on the Internet and within 15 minutes, I was about to go mad. I asked her why she didn’t upgrade to a different service. Then she showed me a flyer that had come with her cable bill. We sat down with her phone bill and AOL bill and realized that she could upgrade to cable Internet service and actually save money. A little more research with her local phone company saved even more money.

So she was paying a premium to connect at 56Kbps or less.

I made a few phone calls and talked to people in the United States and India for her. I’ll be honest with you — the price difference between cable Internet and her local phone company’s Internet was minimal, but we went with the phone company because the person who answered the phone spoke English as her first language. (Subsequently, my Mom needed some tech support after I was gone and that person was in India. Sheesh.) The installation would happen the day after I left to go back to Arizona, but I was pretty confident that they would make everything work. And although it didn’t go as smoothly as we’d hoped, my Mom was soon cruising the ‘Net at normal DSL speeds.

In other words, wicked fast.

My Mom was floored by the difference. I’d told her it was much faster, but I didn’t tell her it was 100 times faster. And it’s always on — all she has to do is turn on the computer and she’s online! And she can even get phone calls while she’s on the Internet! Imagine all that!

The happy ending of this story is that my mother now spends a lot more time on the Internet. (I’m not sure how happy that is.) And of course, she’s now back to the situation where the computer is waiting for her.

Who’s Waiting for What in My Office

I reported a hard disk crash here about 9 days ago. I know it was 9 days because that’s how long I’ve been waiting for the data recovery software to churn through whatever is left of my hard disk. And although it’s still progressing, it’s slowed to a crawl. I think it’s teasing me. But I’ll get the last laugh — I’m pulling the plug today.

There comes a time when you simply can’t wait anymore. I think 9 days shows a great deal of patience on my part. I know I couldn’t have waited so long if I didn’t have other computers to work with. I did get some work done this past week. I wrote up the outline for my Mac OS X book revision for Leopard. I did a lot of e-mail, fixed up a bunch of Web sites, wrote and submitted a bid for Flying M Air to dry cherries this summer in Washington State.

But what I did not do outweighed what I did do. I didn’t work on my Excel 2007 Visual QuickStart Guide. (I need the big monitor to do layout.) I did not pay my bills. (The latest version of my Quicken data files are on the sick drive.) I didn’t update Flying M AIr’s brochure. (Original files on the sick disk, need big monitor for layout.) The list does go on and on.

Now it’s time to get back to work. So I’ll pull the plug on the current data recovery attempt, put the hard disk in the freezer for a few hours, then reinstall it and try again by accessing the sick disk via Firewire from another computer. I can try multiple software solutions to fix the problem. And if that doesn’t work, I take the long drive down to the nearest Genius and let them give the computer a check up to make sure there’s no motherboard damage (again). If the mother board is still fine, I’ll leave them the disk to play with, get a new disk to replace it, and get the hell back to work.

That’s the plan, anyway.

Long Lost Cousin Found

A true story involving an odd last name, the Daytona 500, Google, and one of my Web sites.

The other day, I got an e-mail message from a guy named Steven P. Obviously, his name was not just P. It began with a P and was somewhat unusual. Pretend, for simplicity and to keep this guy’s identity private, that it was just plain P.

Here’s what he wrote.

My name is Steven P. I was getting tickets for the Daytona 500 and was surprised to find another P in the Ticket registery. All I got was Mike P from Pheonix. I googled his name and got a website with your writings. I also got a guest book for Benny Parson’s that Mike had left a message at. I was just wondering if you know Mike? I have lived in Tampa Florida all my life. I have family in Bradenton. All of them have passed, just cousins left. I was just trying to find out if we are family. If you know him and could tell him about this message I would be thankful. My EMail is scp@yahoo.com [not his real address].
Thanks, Steven

I don’t know who or what Benny Parson’s is, but I did track down a comment written by Mike P on my wickenburg-az.com Web site.

I don’t know Mike P. He’s not listed in the Wickenburg phone book. And I wrote back to Steven P to tell him that. But, at the same time, I told Steven P that I’d send Mike P a copy of his message. Since WordPress requires commenters to enter an e-mail address, I had one for Mike P. (Oddly enough, it was also a yahoo.com address.) So I forwarded Steven P’s message to Mike P with an apology for bothering him just in case they weren’t related.

A few days later, I got the following message from Steven P:

Thank you so much for forwarding my Email to Mike P. He Emailed me back and we are family. His Dad is my cousin who lives in Florida. We don’t see each other and I never knew he had kids. Thanks again. Steven

Now doesn’t that make you feel all warm and cuddly inside?

The Importance of XHTML Validation

When will I ever learn?

Miraz has told me again and again — validate your pages after making changes to your WordPress theme templates. She even advised readers in our book, WordPress 2: Visual QuickStart Guide. And every time I validate, I find errors, proving that it’s a step I really do need to take.

Yet I continue to skip this step when I tweak my theme’s template files on every single blog I run.

This morning, I got an e-mail message from someone named Tine who wrote:

I’m completely new to WordPress but found your site because of the book you have made and was curious.

Are you aware that your blog don’t look good in Explorer 6? Some of the text to the left is cut off.

I use Explorer 6 on XP Pro and 1024×768.

Uh-oh.

I fired up my PC and loaded up my home page in Explorer 6. The situation was worse than Tine reported. What appeared did not look much like my site at all. And in the status bar, Explorer was politely telling me that page had errors but didn’t offer any way to find out what they were.

My first instinct was to panic. But then I remembered the XHTML validator at http://validator.w3.org/. I ran the page’s URL through the validator and settled down to find and fix the 110 errors it found.

Sheesh.

The main culprit in this case was some code I’d inserted into my post.php file to display RSS links beside category names in each post’s header. This rather slick piece of coding, which I was pretty proud of, contained the dreaded unencoded ampersand error. That means I’d included & in the code when I should have included & in the code. That error was all over the place, but Explorer seemed to be choking on it in the new code. When I fixed its first occurrence and reloaded the page in Explorer, the page appeared fine, although the status bar smugly reported that there were still errors in the document.

Other problems included

    and tags without

  • and tags. Oops. And

    tags without tags. (It appears that ecto was causing that problem in the way it codes Technorati tags. Good thing I’m not using tags in my posts anymore.) Of course, all my Amazon.com book cover links were missing alt attributes. And some of my rotating ads used IMG instead of img for coding. The list goes on and on.

    Of course, if I’d been validating the XHTML after each template change as Miraz recommends, I would have caught these errors as I introduced them. I wouldn’t have spent my Sunday morning debugging code.

    Have I learned my lesson? I think so. At least for a few days.