Stalled by a Bad CD-R/DVD-R Drive

I get ready to wipe my server clean and start installation but get hung up by bad hardware.

By Friday, I had all my Web sites moved over to GoDaddy.com. The LangerBooks.com site, which had been having problems since I initially set it up there on Monday, was not fixed by Friday. So I deleted the setup an started again. Within minutes, it was set up properly and ready to go. Over the weekend, the DNS change was propagated through the system. Just about every browser looking for one of the 18 domain names I host was pointing to the appropriate site on GoDaddy.com.

My e-mail is already hosted by GoDaddy.com. All my e-mail addresses use the theflyingm.com domain name and that domain has been hosted on GoDaddy for at least a year now. So I didn’t need to move any of my e-mail server stuff. Although it exists on my local server, nothing points to it.

There are only three things that remain hosted on my server:

(1) FileMaker Pro provides live access to searchable data. I’m running FileMaker Pro Server 6 on that machine, even though version 8 is current. I wrote all my Web-compatible routines using FileMaker’s CDML language, which is no longer supported by FileMaker Pro 8. So if I updated to the new version of the software, I might have to rewrite the Web interface. That’s not something I want to do. FileMaker also creates the static text ssi files I use on serveral sites. Those files are now put into place using AppleScripts that call Fetch into action. A cool solution, if I do say so myself. After I install the server, I’ll have to reinstall FileMaker Pro, including all the databases and CDML files that run with the Web sites. I’ll also have to reinstall Fetch and make sure the AppleScripts go in the right places. This should take about an hour.

(2) Nicecast is what gets KBSZ-AM radio on the Internet. It’s pretty much plug and play with just a few settings to tweak. I expect this to take about 20 minutes to reinstall.

(3) Evocam is what creates the Webcam image for wickenburg-az.com. It’s actually two images and a movie. It has FTP built right in. Reinstalling should be pretty straightforward.

One other piece of software runs on the server all the time. It’s called Audio Hijack Pro and its job is to automatically record and save certain broadcasts from KBSZ’s stream. For example, the 8 AM news report is available online every day after 8:20 AM. This is all automated: Audio Hijack Pro records the show and runs an AppleScript routine that uses Fetch to upload it to the appropriate directory on the KBSZ-AM Web site (now at GoDaddy.com). Likewise, Audio Hijack Pro records the daily “Around the Town” show and the first hour of the weekly “Rock-a-billy & Beyond Show.” (Starting tomorrow evening, it’ll also be recording my first radio show, “Classic Rock Cuts.” You can tune in online on Wednesday nights at 8 PM MST. I’m looking for sponsors; call KBSZ at 928/668-1250 during office hours to see how much bang you can get for $5 or $10 bucks. Make sure you tell Jo you want to advertise on my show, which will be podcast, too.)

So yesterday morning, I had a clear idea of what I needed to do and what files I needed to preserve from the server. I made copies of all the files I needed to preserve and put them in a folder that I’d use to create a CD. This would make it easy to load them all back in after I wiped the computer clean and reinstalled the software.

And that’s where I hit a brick wall. The CD burner wouldn’t work. It kept giving me error messages.

No problem. I used my network to move all the files over to my main production computer and created the CD there. Now I was all ready to install.

I put the Mac OS X 10.4 Server Unlimited Client DVD disc into my server computer and slid the drawer close. Then I waited expectantly for the disc icon to appear onscreen.

Nothing happened.

I pushed the button to slide the disc in and out and in and out. Nothing. I pulled the disc out and put in the first install CD. (It comes on one DVD or a bunch of CDs; I’d rather use the DVD so I don’t have to switch discs.) Nothing happened.

I put the DVD into my production computer. It appeared onscreen just like it should.

Shit. I had a real hardware problem.

I blew canned air into the CD drive. Lots of dust flew around. Not good.

My office can be a very dusty place. Part of the problem is that a few years ago, some idiot decided to drive a perfectly good western business — the Big Corral horse boarding/riding facility — out of its downtown home and bulldoze all the trees, shrubs, and buildings off the property. In its place, the idiot planted a “For Sale” sign and erected part of an ugly chain link fence. To this day, the land lies open and barren, baking in the sun, supplying that side of town with all the dust it can handle. In my situation it’s a bit worse. I had some work done on the floors in my unit’s kitchen and bathroom and the sanding done by the floor guy sent more fine dust into the air than I thought possible. With a big fan on the back of each of my computers sucking air in, it’s no wonder they were filled with dust.

Of course, I’d already used the canned air on that computer. Just a few days before, I’d installed 512 MB of RAM. While the machine was wide open, I’d used the canned air on it and it was pretty clean. But I hadn’t dusted the drives.

Long story short, I couldn’t get the drive to work. And I didn’t have a spare. And the nearest Apple store didn’t have one. And Apple’s telephone support people told me a replacement drive would cost $354 with tax and shipping. But while I was waiting on hold to hear this bit of news, I discovered I could buy an external Firewire drive for about $100. Sheesh.

By this time, it was after 2 PM and too late to do any installation anyway. I figured I’d bring my new 80 GB external Firewire hard drive — the one I bought t help out my PowerBook — to the office, make a disk image of the DVD onto that, and use the disk image to install the server. If that didn’t work, I’d just buy an external CD-R for the computer and use that. Of course, all this was putting me back in schedule, but I really had no reason to rush. The Web sites were enjoying their new home and were paid up for 2 months.

Of course, I had to give the CD-R/DVD-R drive one last try at repair. So I went to the local hardware shop, bought a cheap ratchet screwdriver with a bunch of heads, and removed the drive from the computer. This was no easy task because although the computer opens easily enough, the CD drive and the Jaz drive I’d bought to go with it (and used about 4 times) were really jammed in there. Then, with the computer up and running without it — no reason to keep that software offline — I removed screws and protective plates until the optical lens and drive mechanism were revealed. I had to peel back two pieces of tape that were obviously in place to prevent the average user from doing what I’d done. I blew more air on it and moved the drive mechanism back and forth with my fingers. It didn’t look screwed up. Satisfied that I’d done all I could do, I put it all back together and stuffed it back into the computer. I fired it all back up and pressed the button to slide the drawer out.

The drawer wouldn’t slide out at all anymore. I’d mounted it a tiny bit too high and it was catching on the computer case.

So I opened up the computer while it was running and did what anyone else in my position would do: I banged on the top of the CD drive to nudge it down. The drawer slid open.

I stuck the DVD in there, fully realizing that that might be the last time I ever saw it. Then I slid the drawer back in.

Would you believe it? It worked!

I couldn’t believe that it was really reading the DVD as well as it was, so I decided to test it by starting the computer from the DVD. That worked, too.

Of course, I didn’t really want to install the software then. It was after 3 PM and I didn’t feel like tackling the installation that late in the day. So I restarted from the hard drive and let all that software come up and run again.

But now I have my work ready for me today.

The Chickies are Here!

A day late, but twice as many as I expected.

If you know anything about me, you know that I live in a rather rural area and have been keeping a small flock of chickens for the past six or seven years. My first flock was the best: eight hens who were tame and friendly because I’d raised them from chicks. Coyotes got three of them in a day (which is why I have a coyote tail hanging from the rearview mirror in my S2000), and, as a result, I had to keep them cooped up all day long, first in their relatively small chicken coop and later in a fenced in chicken yard my friend John built for me alongside the coop. The remaining five chickens produced, on average, four eggs a day. We’re not really big egg eaters, so we wound up giving away fresh eggs to just about anyone who showed up at our door — the farrier, the FedEx man, and the APS meter reader — as well as friends and neighbors.

Time passed. I got more chickens and coyotes and neighborhood dogs took some chickens away. We got a rooster from my friend Janet. I hatched one chick on my own, then bought two more to keep it company. One my my hens hatched her own brood of chicks, all of which were killed by the rest of the flock. Later on, I started replacing chickens with older birds that were less likely to be killed by the flock. Neighborhood dogs dug their way into the yard and killed all my chickens but one; we later electrified the outside of the yard fence to keep them out.

As I write this, I have two hens and a rooster that I got from my hairdresser, Sue. She was moving and looking for a home for her flock. When I got the hens from her, one of them was laying. But now neither of them do. We say they’re lazy chickens. And I’ve already decided that they’ll soon go to a new home in Wenden, where my Mexican friend Celia will turn them into enchiladas. She says fresh chicken is a lot better than store-bought. I don’t doubt her, but I’m not about to wring their necks, pluck them, and gut them to find out for sure.

When I decided to replace my little flock, I decided to start from scratch again — no pun intended — with a fresh batch of chicks. I ordered from Ideal Poultry in Texas. They’re one of the few hatcheries that will ship small orders (less than 25 chicks) and will vaccinate for Marek’s disease (which killed a few of my chickens a few years back). I ordered Ameraucanas (Araucanas), which are also known as the “Easter Egg Chicken.” Why? Because they lay colored eggs: brown, green, and sometimes even blue.

I’d had Ameraucanas before and I loved the green eggs. One of my hens laid a beautiful sage green colored egg that was almost the same color I’d painted my kitchen. The colored eggs are a novelty, but what’s nice is that this breed is a pretty good producer. All of my chickens laid regularly until their untimely deaths.I ordered 10 hens and 2 males from Ideal Poultry. I got an e-mail message a few days later, saying my chicks would be shipped out on December 7. Ideal ships via Priority Mail and I knew from experience that I could expect a call from the local post office on Friday morning, around 6 AM, telling me that my chicks had arrived. I prepared a large plastic storage container with pine shavings and paper towel sheets on the bottom. Bought new a new chick waterer and chick feeder, and bought the smallest bag of chick starter I could: 25 lbs. I also set up the heat lamp over my makeshift brooder. All I’d have to do when the call came was to plug in the heat lamp, fill the waterer and feeder, and bring the chicks home.

But the call never came on Friday. I went to the post office to try to track down the chicks, but without a tracking number, it was impossible. I was told to wait for the 11 AM express mail truck. It arrived at 1 PM. No chicks aboard.

Meanwhile, I’d called the hatchery and left numerous messages and e-mail messages. Chicks can survive without problems for up to 48 hours after hatching without food or water. After that, nothing’s guaranteed. All I could think of was a box arriving at Wickenburg Post Office the next day with a dozen dead chicks in it.

But there was nothing I could do. I had to be in Tempe that evening for Mike’s company Christmas party. The plan was to spend the night at the Embassy Suites on South Rural. I was hoping to do some Christmas shopping while I was down there — I needed a Lowe’s gift certificate for my brother and his wife — but I was already out of time. So I hopped in my Honda and zipped down to Tempe.

The hatchery called my cell phone just after I checked in at the hotel. The guy who called was probably the owner and he had a thick Texan drawl. He told me that the shipment had probably been delayed on Wednesday because of an ice storm in Dallas. (I guess I missed that on the news.) A lot of flights were cancelled. But the chicks, which had been hatched after noon on Wednesday, definitely went out. They should arrive by Saturday morning. The hatchery would replace them if they died enroute.

Not much I could do in Tempe, so I tried not to think about them.

We went to bed around midnight, which is almost like staying up all night for me.

Mike had a bad night. Neither of us drank very much at the party, but something he ate didn’t agree with him and he was up half the night. I woke at 7:30 AM and left him to sleep for a while. We had a suite, so I surfed the channels on the television in the other room while drinking coffee I brewed in the tiny pot in our kitchenette. I wanted to go home and get the chicks settled in — if they were still alive — but I was worried about Mike.

We finally checked out at about 9:30 AM. We each had our own car, so we went our separate ways. I got in to Wickenburg at about 10:45 AM and went right to the post office. I heard my new little babies peeping as soon as I got in the door.

The post office folks had been kind enough to cut down a plastic cup, put some water in it, and give it to the chickies. So I think some of them got something to drink. At this point, they were nearly 72 hours old and very vocal. I thanked the post office folks, put the box of chicks in the car, and drove home.

Ideal Poultry ships chicks in a small cardboard box with plenty of air holes. The box is held closed by a plastic strap, making it easy to open up the sides and peek in. The box is small on purpose; it forces the chicks close together so they keep each other warm. And it probably prevents them from falling over all the time. Normally, Ideal puts a rolled up straw thing in one side of the box, since I always place small orders. This time, it decided to fill the empty space with extra chicks. So when I started pulling them out, I didn’t stop until I had more than 20 of them in their new home.

There were two dead chicks on the bottom of the box; they’d obviously died early in transit because they were very small and their brethren had stomped them into the hay. Normally, I’d feel pretty sad about this, but with so many live chicks to occupy my mind, it didn’t bother me as much as it should have.

Most of the chicks were very active. I went through my ritual: taking each one and dipping its beak into the water to teach it how to drink. It sounds silly, but they really don’t know how to drink until you show them. And that’s kind of what gets them started on their unaided lives. Kind of like slapping a newborn baby on its butt to get it to breathe.

I haven’t gotten an exact count yet, but I think I have 28 chicks. The hatchery may have thought it was doing me a favor by shipping so many extras for free, but I have a definite space problem. The plastic bin I bought to house them for their first 3 to 4 weeks won’t last more than a week now. I’m already scrambling for a large box to move them into. Maybe they thought I had a nice, warm Arizona yard to keep them in. In reality, they’ll live in my garage for at least two months. That’s when they’ll have enough feathers and down to handle the cold winter nights.

They are cute. No doubt about it. Most of them already have feathers growing on the ends of their tiny wings. They’re babies, so they’ll walk around and eat and drink and jump over each other and then suddenly get tired and fall asleep. They’re fun to watch. And when they’re all awake, they make a ton of noise.

As for my current adult flock: their days are numbered. I’ll see Celia again right before Christmas. Although I already gave her her Christmas present, she might be taking three bonus birds home with her that day. Enchiladas? Tamales? Or just roast chicken? If those girls don’t start laying eggs soon, they’ll be the main course on Celia’s table one day soon.

Two Interesting Charters

I find that there’s more to flying helicopters than giving tours.

Lately, I’ve been getting calls from folks who want to use my helicopter for more than just transportation or tourism.

The first good assignment I got came a few months ago, when I flew a camera crew around the a carmaker’s test track in Arizona. I wrote about it in another blog entry. This past week, I did two more.

The first, on Tuesday, was for a professional photographer hired to take aerial and ground photographs of the new bridge being built over Burro Creek on state route 93. There’s already a beautiful bridge there and the construction crew is building a twin on the north side of it (the road runs pretty much east-west there). Burro Creek runs in a deep canyon there and the Sonoran desert landscape is breathtaking. The site is also far from civilization — about 55 miles north of Wickenburg and perhaps 20 miles south of Wickiup.

It was a cold morning when we left Wickenburg, so I left the helicopter’s doors on. It took us about 30 minutes at my top cruise speed (110-115 knots with two on board and full fuel) to reach the site. I set down in a fenced-in area where the construction folks were storing cactus to be replanted after work was done. I took the passenger door off while my client got his camera equipment out — a pair of Hasselblad medium format cameras with three different lenses. A construction truck pulled up and my client got out to talk to the driver. He came back and told me that the next time I landed, I could land on the new road right near the bridge. It was closed to traffic and was smoothly paved. We took off and began circling the bridges from various altitudes. My client snapped away, cranking the camera’s advance do-dad after each shot. He was perfectly at ease leaning out the door; he’d flown in many helicopters before. After about ten of fifteen minutes of that, I set down on the road near the bridge and shut down. (I had to set down on the edge of the road, as shown in the photo below, because the road was banked for a curve and the only real level spot I could find was at the very edge of the road.) My client climbed out, filled a smaller camera bag with equipment, and walked off to take his ground shots.

I pulled out my iPod and a book and settled down on the side of the road to read. Cars and trucks drove by and I wondered how many of them were headed to or from Wickenburg.

He was gone about 90 minutes. When he returned and finished fiddling around with his equipment, we climbed back on board and I fired the helicopter back up. The light had changed, so we did another 10 or 15 minutes of circles around the bridge at all different altitudes. Then he told me to head back and I broke off circling and headed back.He took some more photos on the way back — using up extra film on shots he thought he might be able to sell the construction folks. Then we set down on Eric Barnes’s dirt strip, on route 93 near the Santa Maria River, so I could put the door back on. With the door off, it was loud and my speed was limited to 100 knots. With it on, it was quieter and I could get it up to 120 knots. When we got back to Wickenburg, I’d put 1.4 hours on the Hobbs. My client paid for that, as well as for some waiting time.

Two days later, I was in Aguila, doing a job for the maker of a “breadcrumb” communications system. Breadcrumb systems, as they were explained to me, create a wireless network that can be used for voice, data, or video communications. The folks who hired me had an impressive system they wanted to mount in the helicopter. The idea was to have me fly around with the system and a few techs on board to see how well the system stayed connected to other breadcrumbs on the ground and how well video that one of my passengers shot could be seen at ground-based stations.

As the photo here shows, I had to remove both doors on the pilot side so they could mount the unit’s antenna. The breadcrumb box itself was positioned at the feet of the passenger behind me; you can barely see it in this photo because it’s just a flat box standing on one end. Although the unit can be powered by batteries, my helicopter has a 28 volt DC port that looks like a cigarette lighter port. The breadcrumb had a cable that could take this voltage, filter it, and step it down to the 12 volts it needed. So they just plugged it into my DC port. The boss of the operation wasn’t happy about the positioning of the antenna — he wanted to dangle it somehow under the helicopter’s body — but we soon proved that it was fine.

One of the techs also had a GPS and, at first, they wanted to mount it on my tailcone. They claimed that in the work they’d done with RC helicopters, they’d found that there was too much interference from the main rotor disk for the GPS to get a good signal. When I told them that my handheld GPS worked in the cockpit cabin, they decided (to my relief) to give it a try. (For the record, I would not have let them mount it on my tailcone. That’s much too close to the tail rotor! We might have mounted it on a skid if we had to.)

My passengers climbed aboard and we took off, flying circles around their base of operations at Robson’s Mining World. One guy in the back did the video while the guy beside him kept reporting on the status of the breadcrumb: green, blinking green, green, green, etc. We kept in touch with other breadcrumbs on the system at all altitudes and even when we flew behind a mountain. We only lost touch once, and that was for only a few seconds. The video went down to the guys on the ground, who clustered around a laptop set up on the hood of a car in the parking area. We did this for about 20 minutes, then landed.

I didn’t realize it then, but I was done with my assignment. What followed was about an hour spent giving everyone there a ride. I took them three at a time and did a 4-minute ride around the base, climbing up the mountain behind Robson’s and descending back into the desert for landing in my designated landing zone. When everyone had their ride, they told me to shut down and have lunch with them. Some other folks would be taking photos of the setup while I was eating.

I ate outside, with the guys from Rotomotion. They build RC helicopter systems to be used for surveillance and unmanned observation. The company founder started the company when he got frustrated that he couldn’t fly an RC helicopter. (Having owned one for a while, I know exactly how he feels; I couldn’t fly mine, either.) He wrote a computer program that would fly the helicopter for him. His company now builds helicopters that work with his Linux-based software system. They had three helicopters with them: a small electric model (on the table in this photo), a medium diesel model, and a large model powered by a chain saw engine.

The software is extremely cool. Once the helicopter is airborne, the software takes over and can hold it in an absolutely perfect out of ground effect hover. You can also tell it to go to certain coordinates at a certain altitude and it’ll go. It uses wireless communications to control an onboard camera or other equipment. If it loses its radio control signal, it’s programmed to return to its home base. Although they have a routine for software-controlled take off, they need a reliable but small altimeter to judge distance from the ground before a good landing program can be written. I have no doubt that they’ll add this feature soon. These guys definitely know what they’re doing.

While the rest of the group went off to go shooting out in the desert, a small group of us remained to watch the RC helicopters fly. A police officer from Chandler had come up to get a demonstration and we just watched. He said that the system has many applications in law enforcement and he seemed excited about it.

I went home a while later and put my dusty helicopter away. I’d logged 1.6 hours for the assignment — not much, but enough to make it worthwhile. And the technology I’d seen while I was out there was well worth the time spent.

The Server Project Begins

I [finally] get Mac OS X 1.4 Server and start to plan for installation and deployment.

If you’ve been following this bLog, you know that I recently purchased Mac OS X 10.4 Server from someone on eBay. I got the software at a smoking price — less than the Apple employee discount, in fact — and considered myself very fortunate. The only thing I can’t figure out is why it took the seller more than 10 days to send the software to me in a flat rate Priority Mail box.

The software arrived in good condition. The box looked a little worn, as if it had been handled by too many people or shuffled around from one shelf to another. But the seals were intact and the box appears to contain all the discs, documentation, and proof of purchase info — including the all-important serial number — that a legal copy of the software should. So I’m pretty confident that I did not buy used or pirated software.

Now that I have the software, I have no excuse to put off my big server project.

The goal, as I think I’ve mentioned elsewhere, is to install Mac OS X 10.4 server on my current Web server machine and use the following features:
– Web server (Apache) with PHP and MySQL for dynamic content
– E-mail server
– Mailing List server
– FTP server
– Streaming Video (QuickTime)
– Blog

I’ll also set up secure space on the server to back up my own personal documents, as well as Mike’s.

In addition to all that, the server will continue to run the same other services the server runs now:
– FileMaker Pro databases
– Webcam
– Steaming Audio (for KBSZ-AM)

All this on a Power Macintosh G4 running at 866 MHz. Seems pretty ambitious, but we’ll see how I can do. If all else fails, I’ll take my old G3/300 (beige, mind you) out of retirement and use that for the Webcam and FileMaker Pro databases.

I’ve made a list of steps that need to be done to get the project going. Here’s what I hope to accomplish today:

1) Adjust the upload address for all Webcams. Although the KBSZ-AM Webcam currently uploads to some GoDaddy hosting space I have, I think the wickenburg-az.com and Editor SpyCam Webcams both upload to my current server. I need them to upload someplace that won’t be affected by the change — probably that GoDaddy space — so I don’t lose Webcam service. I also need to adjust all Web page references to that new space.

2) Adjust the file locations for the ini files I use to display sunrise/sunset and upcoming event info on various Web sites. This information is generated each morning as a text file that is inserted in the appropriate locations on various Web pages. I need to change the source location for the ini files in the Web page HTML and then set up an AppleScript that automatically uses Fetch to move the files where I said they’ll be right after the files are created.

3) Set up hosting on the GoDaddy server for the Web sites I host on my server. This is temporary and will give me the time I need to make all the changes on the new server before moving the sites back. Some sites will move over without any major changes. Other sites, like wickenburg-az.com and aneclecticmind.com will undergo complete facelifts using new features available to me in Apache and the blogging software that comes with Mac OS X 10.4 Server. By moving them off my server to a place where they’ll continue to be served without interruption, I won’t be rushed to build the new sites. Some will be at GoDaddy for less than a month; others might be there for several months.

Since it’ll take up to 48 hours for the DNS info on the Web site move to propogate, I’ll have to wait a few days after I finish these steps to move onto the next step. Hopefully, while I’m waiting, the new RAM will arrive. I’d already ordered and installed 512 MB of RAM on the server and quickly discovered that the RAM was bad. When I get the new RAM, I’ll install it and send back the bad RAM. It should arrive today. If this RAM doesn’t work, I can only assume that they sold me the wrong kind of RAM.

When I’m sure that the sites are being served from GoDaddy’s servers, I can move on with the next steps in the project. I’ll write about those later on.

Stay tuned for progress reports, including problems I’m sure to encounter. And wish me luck!

A Ride in the Desert

We spend three hours on horseback, enjoying perfect weather.

Mike and I have two quarter horses. Jake, a retired ranch horse, is now about 24 years old and is starting to show his age. He’s sorrel (that’s brown) with some white on his feet. He’s also swayback — that means that the place you put his saddle is way lower than it should be on a normal horse —  and has very high withers. Mike bought a special saddle pad for him and then had his saddle custom made to fit the horse. I got Jake for a good price and I think I know why. He’s an alpha male and likes to boss around the other horses he lives with. He’ll bite them and chase them and generally annoy them. That must have really been a nuisance for his previous owners, so they sold him off. But he’s an excellent horse, serious about work, and can be ridden by almost anyone at all. As far as I’m concerned, he was a bargain.

Cherokee, is another story. Cherokee’s main problem is that he’s beautiful. He’s a paint horse, brown and white, and his face is just so pretty, with big gentle eyes and a forelock that’s just the right length. He was 11 when I bought him six or so years ago, and he’d already had at least three previous owners. They evidently spoiled the hell out of him because when I got him, he was lazy, poorly trained, and extremely spooky. That horse taught me more about staying in the saddle during a Cherokee-style rodeo than any other horse I’ve ridden (or fallen off of). To add insult to injury, he cost more than I should have paid. But like his previous owners, I was suckered in by his good looks.

Jake and Cherokee have completely opposite personalities. Jake was always very standoffish — he didn’t really want anything to do with people on his time off. His definition of time off was any time there wasn’t a lead rope or saddle on him. Cherokee is incredibly friendly and curious and loves to be petted. When Jake is ready for work, he works. He’ll do anything you tell him to. When Cherokee is saddled up and ready for work, he’ll do everything he can to get out of doing it. While they both like to be fed treats, Cherokee will actually beg for them. At least that’s what it looks like to me. And if you’ve been reading these blogs for a while, you’ve probably seen the photo of him eating dropped bird food out of the bottom of Alex’s cage.

Cherokee is a big eater and it shows. He’s fat. Jake’s thin. Now if you recall what I said about Jake being the alpha male and consider that they both share the same space, you might wonder how it is that Jake can’t scare Cherokee away from the food. It isn’t like he doesn’t try. He puts his ears back (a horse’s way of saying “f*ck off”) and chases Cherokee. He even bites Cherokee once in a while, putting three or four rows of parallel teeth marks on that beautiful coat. But Cherokee is accustomed to his place at the bottom of the pecking order and is very stubborn. He also eats very fast. So as Jake ages and seems to get thinner and thinner, we’ve taken to separating them at dinner time and overnight, giving Jake more food than he can eat and plenty of time to eat it. Cherokee, of course, doesn’t like this, and after he gobbles up his food, spends the rest of the night pacing around outside the gate to Jake’s enclosure. Over the years, they’ve both changed a bit. Jake is now more friendly. Although his previous owners probably hit him in the face (he was very hand shy when we first got him), he now lets us pet him, even around his head. Cherokee has calmed down and isn’t afraid of rabbits anymore, so I haven’t had any rodeo practice lately. He’s also been trained to walk when I tell him to — without the use of a riding crop! — and to let me position him so I can open and close gates while on horseback. And a few years back, they both posed for a Christmas photo, wearing antlers on their heads.

Photo
Christmas Horses

Anyway, yesterday Mike and I went for a long horseback ride out in the desert. The horses seemed very pleased about going. Of course, when we got to the top of the hill, Cherokee thought we were going to Uncle Pete’s house. That’s where they stay while we’re away and I think he spoils them. When he realized we were turning left instead of right, heading down the trail instead of down the road, he did some Cherokee dancing. In the end, he just followed Jake, like I knew he would.

We live on the edge of town, about two lots from state land. So we normally saddle up and ride out from our house. We have two choices for a ride in the desert: turn down Cemetery Wash, which runs through our property, and take that or any of the trails that go into it or ride up the easement road from our house just past our neighbor’s house on 328th Avenue to a trail that goes right into the state land. We usually follow the second route, since there are far more trails closer to our house when we go that way. That’s also the same trails that the wranglers at Rancho de los Caballeros use for rides, so most of the trails are well worn in — perhaps too worn in in some cases — and easy to follow.

Jack the Dog came with us, of course. Jack likes to go horseback riding. He doesn’t ride a horse. He just runs along on the trail in front of us, chasing rabbits and birds. We realized that he liked horseback riding more than us when we sent two of our friends out for a ride on our horses and he went with them instead of coming back up to the house with us.

We went through the gate in the fence that separates state land from private property. The fence is there more to keep cattle out of people’s back yards than to prevent people from coming in or out of the state land. It also helps keep quads off the horse trails, although it doesn’t help enough. Every once in a while, a couple of quads will get in there and tear up the narrow trails with their wide wheels. There are so many places the quad riders can ride in town — hell, the hills are just criss-crossed with old mining roads and surrounded by sandy washes. Why do they insist on ruining the horse trails and going through people’s private property?We took the “golf course trail” west along the edge of the state land to Los Cab’s golf course, then we turned south to go around Los Cab’s property. We passed through another gate and followed a trail we’d followed a hundred times toward the west again. Spotting a new trail, we took that toward the east, climbing a small ridge that offered nice views of Los Cab. Then back down onto familiar trails, heading west again.

We spent three hours mixing old trails that we knew well with new trails. More than once, we were on trails I’d never been on before. And we wound up going a lot further southwest than we thought we were. I won’t say we were lost — that’s too strong a word — but at one point we were definitely not where we thought we were.

The ride was wonderful. Cherokee had settled down into a good pace and wasn’t the least bit jumpy. Jack chased rabbits and even a few deer. The temperature was perfect: warm enough that a long-sleeved shirt was fine without a jacket. There was some wind on the hills, but the air was quite still near the ground. We found one trail that took us high up onto a mountain, with incredible views of the town far below us, to the northeast. And we didn’t pass another soul.

It was the first time I’d been out for a good, long ride in a while. I’ve been so busy lately with work on my books, building up the helicopter business, and doing flights that I just haven’t had time to ride. And I seem too good at making excuses: it’s too hot, too cold, too windy, too early, too late. Sheesh. I’m an excuse machine when it comes to riding. I think that the truth of the matter is that I’m just too lazy to saddle up. But the reality is that it really isn’t that much work and it’s worth every minute once you get out into the desert on a nice trail.

I’d like to find a riding partner here in town who’d be willing to ride one day a week for about 2 hours. Sometime around noon or early afternoon. But it seems that few of the new people coming into town have horses and many of the ones who do prefer riding with big groups, so they can show off their riding clothes, saddles, and horse’s grooming. I like to ride in small groups, with people who don’t fuss about the terrain being too steep or rocky, with people who know how to control their horses, with people who have enough sense to wear the right clothes and bring enough water for the ride.

Anyway, there are two things about yesterday’s ride that I regret: 1) I didn’t bring my camera. How stupid is that? There were lots of photo ops and I think this entry would have been a lot more interesting with photos. 2) I didn’t bring my GPS. A few years back, I’d started a trail mapping project. Now I’m determined to finish it. And with 3 hours worth of riding yesterday, I could have mapped a lot of trails.

Anyone out there want to go riding on Wednesday afternoons? Get in touch. Experienced riders only, please. And don’t worry; I have a spare horse if you need one.