A PC Laptop

I had to buy a new PC.

Although I’m primarily a Mac person, I also write about Windows. (This was a good thing a few years back when the future of the Mac was in question.) In fact, nearly half my books are either Windows only or cross-platform.

While other writers claim that they can write Windows books while running Windows emulation software on their Mac, I think they’re nuts if they do. PCs aren’t terribly expensive and it isn’t as if you have to buy a new one every year. The Dell Dimension desktop computer I used while working on the WordPress book is at least four years old now. It runs Windows XP and all the current versions of the software I write about — Excel, Word, and Quicken. It also does a fine job with the few Windows-only software packages I actually use, like the software to update my handheld Garmin GPS, the software to update the Garmin GPS in my helicopter, and…uh, I guess that’s it. My Mac really does just about everything I need it to do.

But now I’m gearing up to write about the upcoming version of Microsoft Office. I have at least two titles to update, possibly four. It depends on sales and what the powers-that-be at Peachpit decide.

One thing’s for sure, though: they want the book written about software running on Vista. And my old Dell desktop would roll over and drop dead if I got a Vista beta anywhere near it.

It’s unfortunate. I was hoping to get away with another cheap computer. But because of the processor, memory, and graphics memory demands, I had to buy a “hearty” computer. One that’s above midrange.

And I’d already decided that all of my new test mules — which is what this computer really is — would be laptops. Why? So I could take them on the road and not be tied to my office when I’m working on a book.

Besides, laptops take up less room, usually make less noise, and are easier to keep clean.

I settled on a Dell Latitude D820 laptop, partially loaded. Extra RAM, the faster processor, the better graphics processor, the better monitor. Wireless networking and Bluetooth built in. DVD player/CD writer. Heck, I don’t remember what else it has. It’s way more loaded than I wanted it to be, but I needed it like that. And I paid for it — believe me.

But with luck, I’ll get it to last me five years.

It arrived today and is sitting in a box on a chair by the door. I haven’t decided if I’m going to take it home and fiddle with it over the weekend. I have a Grand Canyon helicopter charter tomorrow and we’re hoping to go up to Howard Mesa to work on the electrical system on Sunday. That doesn’t leave much time for Windows brand frustration.

But maybe I’ll take it home anyway, just so Mike can look at it. He’s a Windows guy and might actually enjoy playing with it.

Now if only Cliff would get those contracts together for me so I can pay for this darn thing.

Dell, laptop, Vista, Windows

WordPress

Maria Speaks Episode 25: WordPress.

A discussion of the WordPress blogging platform.

Transcript:

Hi, I’m Maria Langer. Welcome to Maria Speaks episode 25: WordPress.

First of all, I have to apologize for not keeping up with the podcasts as promised. Although I have plenty to write about in my blogs, I don’t seem able to get it together for a podcast. I know there are podcast subscribers out there waiting for new content, but none of them have provided any feedback about what they’d like to hear. So I’m just kind of floundering around without guidance, waiting for someone to give me an idea.

To make matters worse, I had a bit of surgery early in May and have been recovering more slowly than I expected. I’m okay — I’m just a little slow — and you can take that any way you like because it probably applies. It’s very frustrating for me. I can’t wait until everything’s healed and I can really get on with my life.

Today I decided to do a podcast about WordPress. Those of you who read my blog know that I use WordPress now to create and maintain not just my blog but my personal Web site and my book support Web site. You also might know that I’m co-authoring a book with Miraz Jordan about using WordPress. The book, which is for Peachpit Press, is called WordPress 2 Visual QuickStart Guide and it should be in stores by June.

WordPress is, on the surface, a blogging platform. With PHP, MySQL, XHTML, and CSS under the hood, it offers an easy-to-use, Web-based interface for adding posts, managing categories, handling comment moderation, and performing other blog-related tasks. A novice user can use WordPress without knowing a thing about what’s under the hood. But a user with some knowledge of HTML and CSS could go nuts customizing the blog’s appearance. Add a little knowledge of PHP and plugins available to WordPress server installations and the sky’s the limit on blog customization.

But WordPress is more than just a blogging tool. It’s a complete content management system. That means you can use it to build an entire Web site, with static pages and navigation. This is what I’ve done with the two sites I recreated with WordPress: aneclecticmind.com (where you can find the transcript for this podcast) and wickenburg-az.com. WordPress is a perfect tool for maintaining a Web site that needs fresh content added regularly because its blog format automatically displays new content on the home page and archives old content so it’s always available. No need to code HTML and manually revise pages. WordPress does it all for you.

When I first started using WordPress last year, I got very excited about it very quickly. Finally, a Web publishing tool that gave me the power to create my own custom solution without knowing XML. (I never did bother to learn XML or JavaScript, both of which are popular programming languages for Web publishing.) I realized that I could customize my sites little by little, tweaking them to meet my needs. It was a dream come true — a Web publishing project that I could work on forever without it ever looking only partially completed.

Best of all, WordPress is open source software built with open source software. That means its free for most uses.

WordPress comes in two versions: WordPress.com and a WordPress server installation. Let me take a moment to explain the differences between the two.

WordPress.com is a Web site built and maintained by the WordPress development team. Users can create a free WordPress.com account and immediately start blogging. There’s no need for a server or a domain name or any knowledge of any programming languages. WordPress.com bloggers have some control over the appearance and navigation options of their blogs, so they can personalize them to some extent. A WordPress.com account is a great, free way for novice bloggers — or bloggers on a budget — to get their words out.

A WordPress server installation requires the blogger to either install WordPress on his own server or on an ISP’s server. This requires a bit of technical know-how, as well as certain versions of MySQL, PHP, and an Apache-compatible Web server to be installed on the server. It isn’t difficult to do — after all, I managed to do it on a spare Macintosh G4 running Mac OS X Tiger server. But you can also set it up on an ISP’s server if the server meets the minimum system requirements. I was able to set it up, for example, on a GoDaddy.com hosting account. A WordPress server installation is a costlier and more complex way to use WordPress, but it does give you complete control over the way your WordPress-based Web site looks and works. Only through a server installation can you fully customize theme files and install WordPress plugins.

No matter how you set up your WordPress blog, it’s easy to create blog entries and static pages. Just use a Web-based form with just about any Web browser — I prefer Firefox — to compose and edit content. The blog’s administrative interface gives you access to all the tools you need to set up categories, moderate comments, add links and blogrolls, and manage user accounts. WordPress.com server installations support multiple blogger accounts for a blog, making it great for a site that’s built and maintained by multiple people. Content appears online immediately, as soon as it’s published.

It’s also easy for blog readers to enter comments about your entries — if you allow commenting. This creates a dialog between you, the blogger, and your readers. (A two-edged sword sometimes!) Both types of WordPress installations have comment spam prevention tools, so you don’t have to worry much about comment spam.

There are millions of blogs out there, millions of bloggers sharing their thoughts with readers. If you’ve always wanted to be one, why wait? Visit WordPress.com to get started.

But if you’re like me and are just looking for that perfect Web publishing tool to make your sites easy to build, customize, and manage, a WordPress server installation may be just what you need.

The Eyes Had It

I begin to lose my close vision.

It’s inevitable. As a person ages, he loses his close vision. Now, as I approach my 45th birthday, I’m beginning to lose mine.

My far vision has always been bad. I started wearing glasses in 5th grade and I’ve been wearing contact lenses since my college days. Because I seldom wear glasses, however, people assume I have normal vision. I don’t. My vision is very bad. At this point, I wouldn’t trust myself to walk five steps without my contacts or glasses on.

It always makes me laugh when I see the “corrective lenses” restriction on my driver’s license and pilot medical certificate. Do they honestly think I’m crazy enough to drive or fly without some kind of visual aid?

I’m fortunate in that my vision, although bad, is extremely correctable. That means that with my lenses on, I can see just as well — if not better — than most people who don’t have “vision problems.” In my life, I’ve had two friends who weren’t so fortunate. Their vision was not correctable. Both worked with computers for a living. I still remember sitting with one of them at his desk while he stuck his face up against his 21″ monitor — considered very large at the time — reading something onscreen.

(Apple has a software solution for this called Universal Access. I wrote briefly about it in my Tiger book.)

Two years ago, I got an eye exam. My far vision had worsened again. My doctor gave me an option.

“You can keep the prescription you have or go with a stronger prescription. But if you go with the stronger prescription, you might have some problems with your close vision.”

I didn’t believe her and I went with the stronger prescription. After all, I liked being able to see things off in the distance, especially when I flew. The air can be so clear up here, away from the city. Visibility often exceeds 50 miles. I wanted to see those 50 miles as well as I could.

But she was right. After switching to the new prescription, I started noticing a problem with reading small print. At first, it was just a minor problem that could be solved by adding light. But it seemed to get worse and worse. I finally broke down and bought a pair of “cheaters” — you know, those cheap reading glasses you can buy in a drugstore. They were a +1.25 prescription and they really helped.

The trouble with wearing cheaters is that the more you wear them, the more you come to depend on them. I tried hard for a long time to just wear them when I was reading in bed. But it wasn’t long before I found myself needing them other times, like when trying to read package ingredients in the supermarket or drug store. Add more light.

I had an eye exam earlier this year and my far vision prescription has gotten worse again. But I learned my lesson. So far, I haven’t bought contacts in the new prescription. I don’t want my close vision to get any worse.

The doctor told me that with my new prescription, I’d need cheaters with a prescription of +1.5 or +1.75.

Oddly enough, with my contacts and glasses off, my close vision is still incredibly good. I can, for example, read the microprint on newly designed $100 bills. You wouldn’t believe how much stuff is printed in those tiny letters all over our new money! Of course, at the same time, I can’t recognize Mike sitting across the kitchen table from me. Or read the page of a book more than 5 inches from my nose.

I’m not complaining. I still consider myself very fortunate to have vision corrections available to me. So many people have vision problems that can’t be fixed. Many of them are probably grateful for what they have, too.

I saw an episode of Scientific American Frontiers yesterday that featured a man who’d been blind for the past 11 years. They’d given him an implant and a special pair of glasses with a video camera built in, enabling him to see up to 16 blobs of light. (Think of a computer monitor with a resolution of 16 blurry pixels.) He was so grateful to have even that — the ability to see the way the light changed when something moved in front of him, the ability to see something bright nearby. I’m lucky compared to someone like him.

You’re lucky if you don’t have any visual problems.

Right now, I’m sitting at the kitchen table, typing this onto my laptop. I’m having no trouble seeing or reading it. Yet.

But I know what lies ahead. I’m not anxious to go there, but I know I can’t stop time.

10.6 Miles on Horseback

Four of us join Mike on his annual ride to Wickenburg Mountain.

Every winter, Mike takes Jake, his horse, on a ride to Wickenburg Mountain. Altough this mountain is only about 3 miles as the crow flies from our house, there’s no trail that goes right to it. Instead, you have to pick your way along a maze of trails that go up and over or around about a dozen ridges.

Wickenburg Mountain is not named Wickenburg Mountain on any map I have. I don’t know where Mike got that name for it. Someone probably called it that and Mike remembered the name. If you’re looking at a topo map for Wickenburg, it’s the 2977-foot peak at the north end of the Vulture Mountains, south of Turtleback Wash.

I don’t usually go with Mike on this ride. He’s out most of the day and he always brings back stories of bushwhacking through the desert. While there isn’t much bush to whack in the desert, riding off trails (which is what I mean here) can often take you to the edge of cliffs that even horses can’t climb down. I don’t enjoy putting my somewhat neurotic horse through that kind of experience, especially with me on his back.

But yesterday, he’d invited Janet and Steve, who were visiting from Colorado, and Hans, who has recently gotten over a broken ankle suffered when his horse fell on him. I thought it would be nice riding with a small group of friends, so I went along for the ride, too.

Also along for the ride were Jack the Dog and Janet and Steve’s two dogs, Tasha and Maggie. And when my neighbor’s dog, Trixie, saw us leaving, she decided to join us, too. Tasha wasn’t too happy about that and kept attacking her, but after a while, they calmed down and tolerated each other nicely.

We started out from our house, taking the trail beside my neighbor’s property that would take us into the state land south of our house. We rode familiar trails that dropped us into a tributary of Turtleback Wash, where a Jeep trail ran.

The ride up to that point had been pleasant, following trails we knew. It was a lightly overcast day, cool and comfortable. We saw some mule deer, which gave Jack something to chase. As I rode, I began stripping off a few outer layers. My horse was behaving well — which means he was behaving like most other horses, for a change. He was even trotting nicely when we trotted. And he hadn’t bitten the butt of the horse in front of us yet, either.

From the Jeep road, things got iffy. The road ran mostly northeast to southwest, but we needed to go southeast. But we followed the road southwest, looking for a trail or road that would branch off to the left. Steve was leading at that point and he led us right by a possible trail. I’d seen it but didn’t think it was a trail. It turned out to be an old mining road. We followed it in the right direction, climbing a steep hill. We paused near the top to rest the horses and give the dogs some water. Then we continued and, moments later, the road ended.

Dang.

Mike led and the bushwhacking began. We rode over steep, rocky terrain, past nasy cacti and thorny trees. We climbed, we descended. At one point, we reached what I thought was the edge of a cliff. But Mike steered Jake down it and Jake, the good horse that he is, just went. We followed.

Eventually, we ended up on another Jeep road in another wash. We could see Wickenburg Mountain and it was much closer. We even saw a string of four horses and riders coming down one of its old mining roads. But there were more hills to climb over or around. Fortunately, there were also a lot of roads. The trick was to pick the right ones.

We did pretty well. At one point, we rode up a steep piece of road and I heard Hans say, “Oh no. That looks like the kind of place we fell.” He was referring to his recent horse accident, when he tried to walk his horse up a steep hill and his horse slipped back and fell on him, breaking Hans’s angle and chipping numerous bones in the horse’s foot. We hurried up the hill and I was comforted to hear him right behind me.

Wickenburg Mountain Lunch SpotWe reached the base of the mountain and climbed on another road. About two thirds of the way up, on a road that wound past the front of the mountain’s peak, we stopped for lunch. We tied the horses to bushes along the road; they were so tired, they didn’t seem interested in moving. Then we sat down on the rocky slope, opened up our lunch bags, and ate.

Tasha and Trixie had a huge fight right behind my back, nearly knocking me over, but they broke it up when Mike squirted them with his water bottle. Then they settled down and rested. Jack the dog was smart and hung out in the shade.

Jake on Wickenburg MountainOur lunch spot had incredible views of Wickenburg several miles to the north and east of us. But for some reason, I didn’t take any of those pictures. I did get one of Jake with the town in the background, far in the distance. But most of the rest of the photos I took were for wickenburg-az.com, my so-called “labor of love,” which features random header images. To get just the right image, the photo needs to have something on the left and nothing much on the top right. Go to the site and keep refreshing the page to get an idea of what I’m looking for. The image changes on every page, every time it’s refreshed. There are about 20 images now and one blank image that I’m trying to remove.

(But Larry doesn’t want to read about this. I’m starting to talk too much about computers. Sorry, Larry.)

The back side of Wickenburg MountainAfter lunch, we mounted up again and continued on a trail that led to the back side of Wickenburg Mountain. The trail climbed up through beautiful Sonoran desert to a saddle between the mountain’s peak and a lesser outcropping. This is where I took my favorite photo of the day — this vertical shot of the peak’s side and some saguaro cacti. I was very surprised to see a fence and drag gate up there. Mike dismounted and handled the gate for us and we all squeezed through. On the other side of the fence was just a tiny bit of level ground before the land dropped off on a steep downhill slope. There was a trail and Mike led the way down it.

We wound around the back of the mountain and joined up on some old mining roads again. We followed those back toward the main Jeep road. And that’s where we made our wrong turn. If we’d gone right, we would have hooked back up with Turtleback Wash and, from there, we could have found easy trails back to our house. But we went left, following the Jeep road back toward where we’d bushwacked down the mountainside.

How do I know all this? It isn’t because I have an excellent sense of direction and keen eye for landmarks. My sense of direction is good but my eye for landmarks sucks. That’s one of the reasons I had my GPS with me. And my GPS has a moving map with the local topo maps loaded in. I could see exactly where we were and exactly where we needed to go to avoid bushwhacking.

But Mike wasn’t interested in any of that. “We’re not in a hurry,” he told me.

Well, I wasn’t in a hurry, but I was interested in getting home. Especially since most of our water was gone and I was worried about Janet’s dogs, who seemed to have some trouble keeping up.

So we went left down the road. There was a gate across the road and Mike opened it so we could all go through. And we continued along the wash while the hills rose ever taller on both sides of us. Soon, we were riding into a narrow canyon. And then the canyon ended with a steep rocky cliff carved out by the force of water over thousands of years.

Dead end.

Flume in a Dead End CanyonWe paused there to give the dogs more water and explore the cliff face. There was a neat shelf where you could imagine water gathering in a pool after coming down a flume. (This photo doesn’t do the place justice.) The horses got goofy in the narrow area and Steve’s horse almost ran off. So we mounted up and backtracked, looking for a place where we could — dare I say it? — bushwhack over the ridges to the north.

So the bushwhacking began again. This time, the hills were steeper and, for some reason I can’t comprehend, we managed to get separated. Steve was the first to get down to the wash on the other side. Hans made it soon afterward. Then Mike and I, together. Janet was trapped on top of the ridge, unable to find a safe way down. I think the problem was that none of the ways down looked safe and Janet just happened to be a lot more cautious than the rest of us. So Steve rode back up and she followed him back down.

More bushwhacking. I really don’t like it. Cherokee, my horse, managed to cut his nose on a tree or something, so he wound up with a bloody nose. Janet’s dogs were definitely trailing behind. We stopped to give them water again and pretty much finished off all the water. We’d been out for about five hours.

We finally climbed onto a ridge and saw a familiar Jeep trail ahead of us. A few moments later, we were on the trail. We took turns leading the way. Soon, we were coming back through the gate by my neighbor’s house.

We unsaddled the horses and hosed ours down. (Cherokee hates getting hosed, but he really needed it. Of course, he got us back by rolling in horse manure right after his “bath.”) Hans and his horse hurried home while Janet and Steve put their horses in one of our corrals and joined us up at the house for drinks. Trixie went home. Janet’s dogs were walking on very sore feet. They admitted to us that their dogs had become “couch potatoes.” Our dog, Jack, was obviously tired, but didn’t seem quite as sore.

According to my GPS, we’d travelled 10.6 miles in about 3-1/2 hours of riding with about 1-1/2 hours of non-movement time. (I figure that Jack the Dog and Trixie must have covered at least 50% more distance.) Our average speed was 3 MPH; our top speed (on a gallop, I suppose) was just over 10 MPH.

This morning, it was me who was sore. You don’t realize how many muscles you use when you ride a horse. I think I can feel every one of mine.

Hard Disk Project Done

And problems gone (knock wood).

If you’ve been following this topic, you know that I was having hard disk problems and decided to resolve them by reformatting my hard disk and reinstalling all my software from scratch.

After some problems getting Mac OS X 10.4 Tiger to install properly — I think there were scratches or dust on the disc — I was finally able to start installing software on my hard disk. iLife ’06 went first because I needed to work with iWeb for a project and I wanted to get my iPhoto library back online. One by one I pulled out the original program discs for my big software products: Microsoft Office, Photoshop, and InDesign. And then I pulled out the archives I use to save the original installers for downloaded software like Fetch, Nicecast, Audacity, and others. It took me most of the day last Wednesday to get the job 75% done. I’ll do the rest as I need to.

One thing that disappointed me was that I couldn’t find my original Auto F/X Photographic Edges disc. I use that product to add interesting edges to photos on wickenburg-az.com. But I poked around on the Web and found an old article (and here’s another one) that explained how to add interesting edge effects with various built-in Photoshop filters. I created an effect I liked, turned it into a Photoshop action, and can now apply it without the overhead of the Auto F/X package.

It took quite a while to get all my music and photos from the backup hard disk to my nice, clean hard disk. But everything transfered over without problems and I can access everything just like I could before the reformat.

The result of all this work and worry? My computer is running great, with no unexplained pauses, unexpectedly quitting applications, or lockups. Was it worth it? Of course it was!