Flying for Food

Posted on by
2

Mike tries to arrange a group outing for lunch.

We were at Stan’s house on Saturday afternoon when Mike said, “Let’s go fly together somewhere tomorrow.”

Stan’s wife, Rosemarie, and Dave, another local pilot, were there. Stan flies a Cessna 182 and Dave just got a second plane, an RV-4, that he needed to build time in before he could take up passengers. Mike is half owner of a Grumman Tiger.

What followed was a discussion of various responsibilities the next day. We finally decided to meet at the airport at 1 PM and fly somewhere for lunch. The “somewhere” wasn’t decided.

On Sunday morning, during breakfast, Mike and I started to discuss where we could fly. We brainstormed and came up with a list of airports within flying distance that had restaurants nearby:

Restaurants on Field:
– Prescott
– Falcon Field (2!)
– Payson
– Kingman
– Deer Valley
– Glendale
– Scottsdale
– Chandler
– Winslow (weird hours)

Restaurants within walking distance:
– Seligman
– Valle
– Chiriaco Summit (CA)

Restaurants within free shuttle distance:
– Parker (restaurant at the casino)
– Bullhead City (restaurants across river in Laughlin)

Quite a selection. (Note that Wickenburg isn’t on this list. Why someone with a few bucks doesn’t build a restaurant on the field is beyond me. I know why I don’t do it: I’ve already been through the employer nightmare in Wickenburg and have learned my lesson.)

Sunday morning progressed. We had chores to do around the house. We even cleaned a small part of the garage! Then Mike made the fatal error of attacking the mistletoe that had begun killing some of our mesquite trees. (Mistletoe is a parasitic plant and, if not periodically cut out of the trees it infests, it’ll kill the trees.) It was hard work that required him to stand in awkward positions with a heavy saw over his head. After 45 minutes of that, he was too tired to do anything. Including fly.

That didn’t bother me. I wanted to fly anyway. I felt pretty confident that I could get to the destination around the same time as the two planes. Zero-Mike-Lima cruises at 110 knots, but I could easily push it to 120 knots with only two people on board. I’d already called Jim to invite him to join us with his Hughes 500c. Although he wasn’t sure he would, it would be nice to have two helicopters with the two airplanes. I was hoping we’d go to Falcon Field; I really love the Italian restaurant, Anzio’s Landing, on the southeast end of the runway. And there’s plenty of parking right out front.

By the time we got to the airport at 12:40 PM, the wind had kicked up a bit. It was blowing across the runway at about 8 to 10 knots. Airplane pilots don’t like crosswinds. When no one had arrived by 12:55, I got the feeling that Mike’s plan wasn’t going to become a reality.

Jim was already there, working on his Beech 18. He bought the Beech a few months ago in Florida and managed to leak 10 gallons of oil from one of its engines on the ferry flight back to Arizona. Since then, he’d been working on finding and fixing the leaks. He thought he had it taken care of when he flew out to Blythe for some touch-and-goes the other day, but the left engine was still oozing. A bad O-ring on one of the cylinders. He has to pull the cylinder to fix it. In the meantime, he’s begun pulling just about everything else. Last month, he pulled out the floor and replaced it. He’s now waiting for new runners on which to mount the rear seats. Yesterday, when we arrived, he was pulling instruments out of the panel and rearranging them in more logical positions. His helicopter was not at the airport. His wife, Judith, had already said she didn’t want to come with us, so Jim had decided to work on the Beech — something he could probably do for the rest of his life if he wanted to.

Stan and Rosemarie drove up right around 1 PM. I was talking to Jim when they pulled up, so I missed the beginning of their conversation with Mike. But the end result was that they’d come with us in the helicopter. Dave wasn’t coming. So a flight that started with potentially four aircraft ended up with just one.

Of course, with the helicopter, the list of dining opportunities increases. Helicopters don’t need no stinkin’ runway. There were at least five more places we could eat:
– The Wayside Inn, near Alamo Lake, is the destination for Flying M Air‘s “Hamburger in the Middle of Nowhere.”
– Robson’s Mining World, in Aguila, has a nice little cafe.
– Wild Horse West, near Lake Pleasant, has great burgers.
– The Kofa Cafe, out in Vicksburg Junction, used to be very good, but I haven’t been back since my first experience with the new owner.
– A truckstop on I-10 south of Vicksburg has a dirt strip out back where you can land and not dust the truckers.

Mike wanted to go to the Wayside Inn, so that’s where we went. You can read all about it in another blog entry. The food ain’t bad and the atmosphere is definitely different, especially if you live in a big city and don’t have much exposure to an off-the-grid lifestyle.

We flew by way of Robson’s, which was pretty quiet that afternoon. Robson’s big anniversary celebration is coming up on the first Saturday in January, and I think they get more visitors in that one day than they get all year long. I do helicopter rides out there during the event and it’s always a lot of fun. Then we followed Ballard Wash (I think) from its narrow start almost all the way to Alamo Lake. I circled the Wayside once, trying to find a flag to judge the wind, then realized there wasn’t much wind there and just set down in my usual spot near the intersection of two dirt roads and the old, unmaintained dirt strip. (If you ever fly out there in a small plane, I recommend landing on the road rather than the strip; it’s a lot smoother and better maintained.) I kicked up a huge cloud of dust that drifted to the east as I cooled down the engine and shut down.

We crossed the road and went into the restaurant. Everyone at the bar looked at us. “I knew it was you,” the waitress said.

“Yeah, well…” I said. Everyone laughed.

We had lunch among the fish photos and trophies. The place was relatively quiet. The last time we’d been in there with helicopters, a crowd had gathered and the restaurant was completely full. I guess having four helicopters and a plane parked outside is a bit of a draw to the locals. But that day it was just us and a man eating at the bar. A few people came and went.

We paid up and left. As I started up, a few people in ATVs parked at the end of the dirt strip, facing us, ready for a show. They were not rocket scientists. Not only had they parked right in front of me, forcing me to depart in a different direction so as not to overfly them, but they were close enough to get seriously dusted when I took off. I took off to the northwest, along the road to Alamo Lake.

We did a tour of Alamo Lake, then the Santa Maria River, and then Date Creek before heading into Wickenburg. It had been a nice little outing — even if we were the only aircraft to participate.

A Trip to Sedona

Posted on by
Comment

I spend the day in Sedona, waiting for some passengers.

Yesterday, I had the pleasure of flying two very nice people from Canada from Wickenburg to Sedona for the day. We arrived at Sedona Airport, after a scenic flight around Wickenburg, Prescott, and Sedona’s red rocks, around 11:30 AM — just in time for the Pink Jeep Tour shuttle to pick us up and bring us down to the town. My passengers were taking a Jeep Tour; I planned on just hanging around downtown until they were ready to return at 3 or 4 PM. I escorted them to the Jeep Tour desk, reminded them that they could change their reservation, and watched them reserve a Jeep and driver all to themselves for departure at 1 PM. Then I left them to walk around town on my own.

The Pink Jeep Tour company’s offices are in “uptown” Sedona. That’s the heart of the tourist district in the northwest corner of town at the mouth of Oak Creek Canyon. The tourist shops that line both sides of the street there are dwarfed by the massive red rock formations behind them. But all attention in uptown Sedona is concentrated on those shops. I admit that mine was, too.

I hadn’t been to the town of Sedona for years. I’ve been flying in quite regularly with passengers, but I seldom come down off the mesa where the airport is located. There’s a restaurant up there and I usually have breakfast or lunch or whatever while my passengers explore the town on their own. They’re usually gone about 2 hours at the most, so I busy myself with a book while I’m waiting. It’s a nice, relaxing place.

But yesterday, my passengers wanted a longer stay in town. And since the Pink Jeep people offered me a lift in the shuttle, too, I went down the hill with them.

I walked the few blocks of uptown Sedona at a leisurely pace. I saw lots of T-shirt shops and lots of souvenir shops. The usual collection of real and fake Indian crafts and jewelry. Imported Mexican rugs. Jeep tour companies. Reservation centers. The wonderful map and bookstore that had been in one of the shopping areas was gone and I was sorely disappointed. I’d depended on that shop for reading material while I waited and it didn’t appear, at first, as if there were another bookstore in town. I finally found one across the street from the Pink Jeep storefront, the last shop on my walking tour.

My Sedona passengers from last week’s flight had spent only 90 minutes in town before returning to the airport. They called Sedona a “tourist trap.” And frankly, as I walked the streets, I couldn’t argue with them. But I hadn’t really expected it to be any different. I don’t know what they expected. After all, take a beautiful place, make its beauty well-known, and people will flock there. When enough people flock there, the tourist shops will start springing up like mold on old bread. After a while, those shops (like mold) completely cover the area, masking what people found so beautiful in the first place.

Now I don’t want to give you the idea that Sedona is “ruined.” It isn’t. There are still plenty of beautiful sights around town. Sadly, there are so many people there to view those sites, you’re always part of a crowd. You need to come to Sedona with your own Jeep and a trail map to get away from the herd. Bring a picnic lunch and your camera. And, for heaven’s sake, don’t come on a weekend!

I ran into my passengers on the street just before they went to lunch. They invited me to join them, but I felt as if I would be intruding, so I declined. I had lunch at a tea shop across from the Pink Jeep place and sat outside on a narrow balcony to eat and read the book I’d bought in the bookstore down below. It was windy and rather cold up there, so I didn’t last long.

Afterwards, I went for a walk back the way I’d come. That’s when I saw the Hummer tour sign. They had a 1-hour tour leaving immediately. It was the “Jeep Eater” Tour. Supposedly, this tour took passengers places were Jeeps couldn’t go. I pulled out my credit card and, minutes later, was seated in the front passenger seat of a Hummer, about 6 feet away from its driver. (Okay, so maybe it wasn’t that wide, but it sure seemed like it.) There were two passengers, a couple from Baton Rouge, in the open-air seating behind us. That was it.

The road that Jeeps can’t drive on isn’t in Sedona. It’s halfway back to Cottonwood, off of 89A. It’s a power line road — that’s a road built to maintain a power line — and frankly, there were only about 4 places on the whole ride that I would have been uncomfortable about taking my Jeep. That’s not to say that my Jeep couldn’t have done it. But I’m not sure that it could have done it with me at the wheel. During the whole ride, the driver kept pointing out other roads that the couple from Baton Rouge could explore on their own with the ATV’s they’d trailered up from home. The driver was obviously working hard to add value to the ride and maximize his tip potential. Whatever. It managed to stretch the tour out to 90 minutes, bringing us back to Sedona just when my passengers were due back. In case couldn’t read between the lines in this paragraph, I don’t recommend this tour. It wasn’t worth the $100 I spent on the tour plus tip. But at least I know what it’s like to ride in a real Hummer.

I hurried back toward the Pink Jeep place and found one of my passengers outside a gift shop. His wife was inside, shopping. They’d had a great time and had looked for me to join them before they left. I didn’t tell them about the Hummer.

I left them for a short while to pick up a gift for a friend of mine and a piece of apple pie that was really good. Then we got back on the shuttle, rode up to the airport, and flew home.

I’m glad I got to go to Sedona for the day. I feel all caught up with things down there. And I’m sure I’ll be back soon — not only by helicopter, but perhaps by Jeep to see just what my Jeep can do.

Snagged the Server!

Posted on by
Comment

Another eBay success.

I managed to win an auction for a copy of Mac OS 10.4 Tiger Server Unlimited. Apple sells this for $995; I got it for $449 including shipping. According to the seller, it’s in an unopened box, so it sounds legal to me.

I’m excited about this. I’ve been sitting on the fence about switching to Mac OS X server for about two years now, but my recent dealings with the folks who sell WebSTAR made me decide to take the big step up. I run a bunch of Web sites on the G4 in my office. I also run a FileMaker Pro database Web publishing server, Webcam software, and audio streaming software.

I used to run e-mail there, too, but the IP address I had was somehow linked to a spam account and all my e-mail was getting bounced from the sender as spam. What a hassle that was. So I moved my theflyingm.com domain name to a GoDaddy.com server and use that for e-mail and hosting my podcasting files. Although I now have a different IP address, I think I’ll keep theflyingm.com on GoDaddy’s server. They offer a ton of bandwidth for a very affordable price.

Now, I need to come up with a plan of attack for the new server. I want to take my time about setting it up, so I’ll probably start by moving all the Web sites I host over to GoDaddy.com for a month. Then I’ll set up my new server’s features, step-by-step, and get the Web sites all in place. I’ll “flick the switch” back to my server and, with luck, there won’t be any service interruption at all.

Those of you reading this who don’t know about GoDaddy.com and have a need for domain name registration or Web site hosting should really check them out. They’re affordable and reliable and have excellent free technical support by phone. (E-mail tech support stinks.) They also have a lot of how-to documents on the site to answer the easy questions.

Speaking of how-to documents, I got an answer to my MIME Mapping question that pointed me to a file named .htaccess. A Google search got me the information I needed from the JavaScriptKit Web site’s Web Building Tutorials pages. I think this will be a gold mine of information for me as I work directly with a Unix-based Web server for the first time.

As I work my way through this project, I’ll probably report my progress here and provide detailed how-to information in the companion Web site for my Mac OS books — that’s where most readers interested in this kind of stuff are mostly likely to look for how-to information from me.

Oddly enough, I haven’t felt this excited about a computer project for a long time. I’m really looking forward to the challenge and to learning the new things that’ll make it all work.

Oh, and the good news is that I didn’t win the other hard disk auction.

Flight Planning

Posted on by
3

A quick review of my Part 135 Flight Planning Routine

My company, Flying M Air, is an FAA Part 135 operator. What that means is that I had to go through a lot of paperwork and testing with the FAA to be allowed to take paying passengers more than 25 miles from my starting point or to land with paying passengers on board.

As a Part 135 operator, I have the FAA looking over my shoulder to make sure I do everything “by the book.” The book, in this case, is my Statement of Compliance, a 50+ page document I wrote that explains how I’ll follow the Federal Aviation Regulations (FARs) that pertain to my Part 135 operations. The FAA reviewed this document in painstaking detail and it took about three months to fine-tune it to the FAA’s satisfaction. Of course, the FAA also conducts surprise and scheduled inspections of my aircraft and my base of operations (my hangar) to make sure everything is just right. And because I’m required to be on a drug testing program, I’ve been told that I can expect a visit from the FAA’s “drug-testing police” one day in the future.

For the record, I have no problem following FAA’s requirements for my operation. They’re not asking for anything unreasonable and everything they require is in the interest of safety for me, my passengers, and my aircraft.

Anyway, one of the requirements for Part 135 operations is flight planning. And, at this point, I have it down to a science.

I start by getting the names and approximate weights of the passengers I’ll be carrying, along with our destination, expected time on the ground, and any special route requests.

Today’s a good example. My two passengers want to fly from Wickenburg to Sedona and back. They want a scenic route both ways so they can see as much of the area as possible. At Sedona, they want to take a Jeep tour at least 2 hours long. I’ll have to line that up for them so the Jeep folks meet them at Sedona Airport when we arrive. With lunch and other activities on the ground, I expect to be there 4-5 hours. I expect to depart Wickenburg at 10 AM and depart Sedona by about 4 PM. My route will take them past some of the area’s mining areas, over Prescott, near Sycamore Canyon, and past Sedona’s red rocks before landing. On departure, we’ll swing past Jerome and follow the Bradshaws down to Lake Pleasant, where I can show them some Indian ruins and the house on Sheep Mountain. A final swing around Vulture Peak and over the ranch where they’re staying will get us back to Wickenburg. Total time enroute: about an hour each way.

With this information in mind, I fire up my Web browser and visit the Duats Web site. Duats is a free flight planning service for pilots. I log in and enter my flight plan for a weather briefing that includes current conditions at airports on or near my route (Prescott and Flagstaff) as well as NOTAMs. Today I learned that we’ll have typically clear Arizona weather with the possibility of some high cirrus clouds. It’s windy right now in Flagstaff, with gusts up to 34 knots, but the wind is expected to calm a little bit as the day wears on. Still, I can expect some very light turbulence as the winds pass over the mountains we have to cross or fly around: the Weavers, the Bradshaws, and Mingus Mountain.

Duats also has a flight planning feature and I use this next. It takes the information I’ve already entered to get the weather and uses it to calculate the route and enroute time for the flight. Since I can’t put as much detail into Duats as I need to, its flight plan is much simpler than my scenic route. It says it’ll take 45 minutes to get there and 40 minutes to return. I file both of those flight plans, each with their own times (10 am and 4 pm) with the FAA. They’ll sit in the FAA’s computers until I either activate them (one at a time, of course) or they expire.

Next, I whip out my Manifest form. This is an Excel spreadsheet I designed that automatically calculates weight and balance for my helicopter. I enter all the flight plan information, as well as my starting fuel load and the names and weights of my passengers in the seats I expect to put them. For weights, I add 20 lbs. I used to add 10 lbs, but the folks who book these flights don’t seem to have a clue about weights. It’s always better to overestimate than underestimate. And since it’s nearly impossible to load an R44 out of CG, it doesn’t matter if the two passengers sit somewhere other than the seats I expect to put them in. When my passengers are light — as these two are — I usually put them both on the same side of the helicopter so they have the same basic view. I then fly so that the most interesting views are on their side. But if they both want to sit in back, that’ll work, too. Or any combination they want.

The Manifest form is also designed to be used when I don’t have access to the Internet. It creates the same flight plan that I file with the FAA. So if I have to get the weather from a telephone briefer, I can file my flight plan over the phone at the same time rather than via the Internet.

If I have access to a printer, which I usually do during flight planning, I print out my manifest form for each leg of the trip, my flight plans for each leg of the trip, and my weight and balance for each leg of the trip. If I plan to start each leg of the trip with the same amount of fuel and take the same amount of time, I only print one weight and balance sheet. No sense wasting paper. But today I printed two sheets — I plan to fill up in Sedona since my passenger load is light and fuel is currently cheaper there than in Wickenburg.

I usually give a copy of my manifest — that’s the form with the passenger names and flight plan — to Mike. He’s my backup flight following. I call Mike when I depart and arrive each leg of the trip. If I don’t call in on time and he can’t get me on my cell phone, he takes the next steps with Flight Service.

Of course, I also open my filed flight plans with the local Flight Service Station (FSS). Although I prefer to do this on the ground before I start up, the FSS prefers that pilots do this on departure. My problem is that as a helicopter, I don’t always get enough altitude to access one of the radio frequencies the FSS uses. So I sometimes can’t activate a flight plan until I’m 10 minute into my flight. I close the flight plan by phone when I land, then call Mike to let him know I’ve arrived safely.

All the paperwork that’s generated for the flight is left on my desk in my hangar. After the flight is done, I file it. The FAA likes to look at these papers when they do their base inspection, even though I’m not required to save them.

And that’s about it. As you can see, the whole routine is designed to make sure I properly plan the flight and have at least one form of flight following to make sure a search is conducted promptly if I do not arrive at my destination. It sounds like a lot of work, but I can normally do it in less than 20 minutes with my computer and an Internet connection. To do it manually would take about twice the amount of time.

So I’m flying to Sedona today. I’d better bring a book; I have a feeling I’ll be spending a lot of time at the airport there.

MPEG-4 Lessons, Server Woes, eBay Shopping

Posted on by
Comment

Maria Speaks Episode 20: MPEG-4 Lessons, Server Woes, and eBay Shopping.

Transcript:

Hi, I’m Maria Langer. Welcome to Maria Speaks Episode 20: MPEG-4 Lessons, Server Woes, and eBay Shopping. This episode is a hodgepodge of information related to my podcasting efforts and the trouble it has been giving me lately. You can find the transcript of this podcast in the “Call Me a Geek” area of Maria’s WebLog. The easiest way to find that is to click the link on my home page, www.aneclecticmind.com.

Let’s start with the MPEG-4 lessons. If you’ve been following my podcasts, you know that I’ve begun creating the occasional enhanced podcast. Enhanced podcasts include images and links and are saved in MPEG-4 format with a .m4a extension. My other podcasts are saved in MP3 format with a .mp3 extension.

Podcast publishing is not exactly a simple task — well, not when you do it the way I do. After recording, editing, and saving the audio file, I then log into Blogger where I create a blog entry for the podcast. There’s a link field that I fill out with the URL for the audio file’s location on a server. I put a short blurb about the episode in the entry and publish it.

Publishing the entry on Blogger does two things. First, it creates the Maria Speaks home page. That’s the plain old Web page you see when you browse www.aneclecticmind.com/mariaspeaks. Then it creates an XML feed file called atom.xml, in the same location as the home page. This feed file has all the codes necessary for podcatching software — like iTunes and a bunch of others I really don’t know — to see and download the new audio files.

But that’s not what most subscribers use to access my podcast. They use my Feedburner feed. Every 30 minutes or so, Feedburner’s software checks out my atom.xml file to see if it has changed. If it has, it revises its version of my xml feed file, which can be found at feeds.feedburner.com/mariaspeaks. That’s the file most subscribers subscribe to and it’s the one with all the bells and whistles to make sure my podcast entries appear correctly in the iTunes Music Store and elsewhere.

Sound confusing? It is, in a way. But I don’t usually have to deal with too much of it. As I said, I create and save the audio file, then create and publish the corresponding blog entry. Blogger, Feedburner, and subscriber’s software does the rest.

My MPEG-4 lesson started yesterday. Well, in all honestly, it started about four months ago, but I didn’t realize it then. Back then, it was a problem getting my podcasts to work. But I changed the way I was doing things and it started to work, so I assumed I’d been doing it wrong in the first place. Actually, I wasn’t.

Here’s the symptom: my enhanced podcasts weren’t accessible from the Maria Speaks podcast. Anyone trying to access the file from the Maria Speaks home page by clicking the entry name got an error message. File not found. And there was no attachment to either version of the xml feed file.

The regular podcasts were fine.

Thus began my troubleshooting exercise. I zeroed in on the difference in the file name extensions and started researching. To make a long story short, I discovered that in order for me to include m4a files in my podcasts, I had to set up a MIME mapping on the server to identify the m4a extension’s type as audio/MPEG.

If you’re completely lost, don’t worry about it. This isn’t the kind of thing most computer users need to deal with. I certainly don’t. Fortunately, I have a server in my office that I can set up MIME mapping. I added the appropriate entry, moved my m4a files over to that server, fixed the URLs in Blogger, republished, resynced Feedburner, and everything began working fine.

I’m still trying to find out if the server space I have on GoDaddy.com can be modified to add the MIME mapping I need there. I’d much rather serve from that server than the one in my office.

So that was my MPEG-4 lesson.

Server woes started this morning. I was still fiddling around with the MPEG-4 files and was very surprised to see that the folder on my GoDaddy server that I’d been using to store my MP3 files was gone. I mean gone like it was never there. And oddly enough, two folders that I thought I’d deleted were back. What the heck was going on?

I assumed that I’d accidentally deleted the missing folder and was mistaken about the other two folders. After all, I’ve been busy lately with my QuickBooks book and a bunch of unexpected helicopter charters. I was obviously being careless. So I rebuilt the missing folder from backup files on my iDisk and went to work.

All the way to work — it’s a ten-minute drive — I thought about my carelessness. And when I got to my office, I did some more research. What I soon realized was that all of the space on my GoDaddy server had been reverted to the way it looked on October 10. Over a month ago. What the heck was going on?

I called GoDaddy technical support and was fortunate enough to have a tech guy answer right away. I told him the symptoms. We did some brainstorming, using the info we both had. We soon discovered that on October 10, I’d requested a change from a Windows server to a Linux server. For some reason, it had taken GoDaddy five weeks to process the change. In the meantime, I kept uploading files to the Windows server when the Linux server was already set up but not accessible to my account. Last night, GoDaddy switched my access to the Linux server, which hadn’t been updated since I requested the change. So I was suddenly faced with a server that hadn’t been updated for five weeks and access to the server I’d been using all along was completely cut off.

Well, this wouldn’t have been so bad if I was using the server space for a Web site. I keep backup copies of all my Web site on my main production computer. If a Web site’s directory or disk is trashed, I can have it replaced in a matter of minutes. But the only thing I use this server for is storing my podcasting files. Not just for Maria Speaks but for KBSZ-AM’s Around the Town radio show, which is broadcast every weekday. When GoDaddy made its change, it wiped out about 20 podcast files.

The really tragic part of all this is that I’d been saving all those podcast audio files on my PowerBook’s hard disk. Two days ago, I got an onscreen message saying I was running out of disk space. Well, why not delete some of those podcasts, I asked myself. After all, I can always get new copies from the server.

Two days later, of course, I couldn’t.

Well, the GoDaddy tech guy was very helpful. He told me they’d do a server restore for the Windows server and copy the files in my directory there to the Linux server. Although GoDaddy usually charges $150 for this service, they admitted that they were at least partially at fault for the screw-up and waived the fee. Now I just have to wait up to 10 days for the files to reappear. And, when that happens, I have to re-upload any files I uploaded to the server between yesterday at midnight and the day the server is restored. Like this podcast.

Oh, and I did lose one of my enhanced podcast episodes. It was one of my better ones, too: Mac and Windows File Sharing. It was on my .

Mac disk space, which I also cleaned up in an effort to get rid of unneeded files. So if you have a copy of it — that’s the version with the m4a file extension — please send it to me at mariaspeaks@mac.com. I’d really like to put it back online for the latecomers here. The lesson I learned in this ordeal is that I must have a copy of every single file I want to make available on a server. If I’d had all my files, I could have just restored the server back to its original condition and got on with my life. And not bore you with this story.

SmartDiskWhat’s weird about this is that I considered the server my backup and I deleted the originals, depending on the backup. If you recall my famous NaNoWriMo podcast episode, you’ll remember how I spoke about the importance of backups. Yeah, well the originals are important, too. Which brings me to the final topic of this podcast: eBay shopping. I’ve been surfing eBay for the past two weeks, trying to get a deal on a portable FireWire hard disk. The idea is to use the external hard disk to store all my media files, thus keeping them off my PowerBook’s internal hard disk, which is only 40GB. SmartDisk makes a drive called the FireLite and I figure I can get an 80GB model for about $130. There’s plenty to choose from, all in unopened boxes. But I seem to have the worst timing; I’ve lost about a dozen auctions in the past two weeks. I’ve gotten to the point where I actually bid on two of them at a time, knowing I can’t possibly win both.

That’s the same technique I used to snag a new iSight camera this week. I put the same bid on both cameras. I won one and lost the other. Fine with me. I figure I’ll bring the camera home and use it on my laptop for a Webcam and for iChat. I might also do some video podcasting — but don’t hold your breath on that.

My other big eBay acquisition is Mac OS X 10.4 Tiger Server Unlimited. It’s about half the price on eBay as it is in the Apple Store. Sealed boxes, unregistered. Sounds almost too good to be true. We’ll see.

The server, of course, is so I can finally get rid of WebSTAR and do some serious Web hosting on my server. I’ll bore you with that in another blog entry.

That’s all for today. I hope you learned something from this mess. Thanks for listening!