I Bought an iPod Photo

I didn’t want to do it, but I had to.

The biggest problem I have as the author of computer books and articles is that in order to write about hardware and software, I have to own it. Or at least have it in my possession for enough time to learn and write about it.

That’s why I bought an iPod years ago. I had to write about using iTunes with an iPod for my Mac OS X book. I couldn’t get a loaner from Apple and I didn’t know anyone who had one. So I had to buy one. I still have it and still use it. It’s the original iPod, which held 1,000 songs on its whopping 5 GB hard drive. At the time, it was an incredible breakthrough in MP3 technology. But today, it’s a dinosaur, almost embarrassing to admit owning. (I own a Newton, too. But let’s not go there today, huh?) But it works, so I don’t care.

Want to know where I spent the most time listening to my ancient iPod? In my old helicopter, Three-Niner-Lima. I had Paul, my old mechanic, install an audio patch into the intercom system and put an RCA jack on the side of the instrument panel. I bought a nice leather case for the iPod with a mounting do-dad so I could hang it beside that jack. Then I used a standard Radio Shack cable (not bought locally; those guys don’t have anything you need when you need it) to patch the iPod into the helicopter’s intercom system. I could listen to tunes while I flew. Best of all, when there was a radio transmission, the music would automatically cut out so I could hear the radio. Ditto when I talked on the radio. A great arrangement. It made some of those long cross-country flights over Arizona and California and Nevada deserts a bit more pleasant.

The iPod Photo came out about a month or so ago. Probably less. I can’t remember. Anyway, Apple took the next logical step and made it possible to put photos on an iPod. So they’re worth looking at, they changed the screen to color. And since 10 or 20 GB isn’t enough to hold all your music and photos, they come with either 40 GB or 60 GB worth of storage.

I tried to get one from Apple as a loaner. They have an editorial loan program that is extremely difficult to get hardware from. I succeeded twice times in the past — I got an iBook loaner once and an iMac (ET style) loaner another time. But this time I wasn’t as lucky. I was told the waiting list was “a mile long.” Wow. So I bought one.

It came yesterday. I had company so I couldn’t tear open the box and immediately play with it. So I took it to work this morning. I’d just finished work on [yet] another Word book and was waiting for the index to come from the indexer so I could lay it out. I’d promised articles to two publishers. But I could spare a few hours to configure and learn about my new toy — I mean, vital piece of hardware.

It’s cool. No doubt about it. The dock it comes with sure beats that FireWire cable I left on my desk for syncing and recharging the old iPod. And the color screen is beautiful.

I stuck it in the dock and immediately started putting songs on it. I was able to fit my entire iTunes music library, which really isn’t much — only about 1,600 songs. (No reason for me to copy all my CDs to my computer’s hard drive when they weren’t going to fit on my iPod anyway.) Then I copied my iPhoto photo library to the iPod. All 2,600 photos. When I was done, I’d used less than half of the iPod’s 40 GB. Sheesh.

I got an e-mail from one of the editors waiting for articles and wrote back to her, mentioning that I’d just gotten an iPod Photo. How about an article that explains how to create a custom slide show with music on the iPod? She wrote back saying that they’d been talking about iPod photo in a meeting that morning. Write the article! So I did. And I submitted it this afternoon.

So I guess it must be an important piece of hardware, necessary for my work. After all, I’d owned it for less than 24 hours when I wrote an article about it that earned me $300. Another article and it’ll be paid for.

And yes, the new helicopter will be iPod-compatible. It has a built-in audio jack. But I think I’ll stick the old iPod in there, just for old time’s sake. After all, 1,000 songs really is enough.

Through the Magic of Photoshop…

I get a photographic image of a helicopter that hasn’t been built yet.

Three-Niner-Lima in FlightMarketing is an important part of any business. And the most effective marketing includes visuals. Take, for example, my slides at the movie theater. There are a few aerial shots of the town and some cattle tanks, giving people an idea of what they can see from the air. But there’s also an excellent air-to-air photo of my old helicopter, Three-Niner-Lima. In the photo, I’m flying past Vulture Peak, just like I do on my Grand Tour of Wickenburg. It’s a real photo that Mike took from the passenger seat of a Piper Cub years ago, when we were flying in formation just to take the photos. I have several of these shots. One — the one you can clearly see me in the cockpit, looking at the camera — is on my business card. These photos look so good that I’ve been accused of cooking them up in Photoshop. But I didn’t. They’re real.

Three-Niner-Lima is gone now and I’m in a transition phase as far as the helicopter tour business goes. I’ve been getting calls for rides, but I have to tell callers that there won’t be any rides until mid-December, when the new helicopter arrives. In the meantime, I need to warm up my marketing machine. Christmas is coming and I usually do a nice business with gift certificates. I want to sell a bunch of rides now, so I have plenty to do when Zero-Mike-Lima arrives in town. I also want everyone to see what the new helicopter will look like. Lots of people thought Three-Niner-Lima was a kit helicopter because it was so small. They won’t think that they they see Zero-Mike-Lima. It’ll be considerably larger and more impressive.

The trouble is, Zero-Mike-Lima hasn’t been built yet. Just this week, it should have taken its place on the factory’s assembly line. But there certainly isn’t anything to take a picture of yet.

And I won’t have my hot little hands on its controls until December 8 at the earliest. That’s a bit too late for Christmas marketing.

So what was I to do? I thought about John Stonecipher. He runs Guidance Helicopters in Prescott, AZ, a flight school that also does tours and charter work. His R44 looks very much like mine would. Did he have some air-to-air photos I could use? I could use Photoshop to remove the N-Number (if visible) so it couldn’t be identified as his. I asked him and he said he did have some photos. He said he’d send them. I waited. And waited. And nagged. And waited. Finally, he sent a CD-ROM disc, probably just to get me to stop nagging him. There were three photos on it. None of them were suitable — they were blurry and the helicopter was too far away. I think when I do get my ship I should go up there and help him take some decent air-to-air photos of his.

So I wasted a month waiting for photos that wouldn’t do the job for me. Back to square one.

N45PG in FlightMeanwhile, I had a number of air-to-air photos of my friend Tristan’s R44 taken here in Wickenburg. I leased Tristan’s ship last year for the season and did relatively well with it. That’s what convinced me that I could build the business much better with a 4-seat helicopter. We’d taken the pictures for last year’s ad campaign: “Share the view with a friend or two!” Trouble is, Tristan’s ship is metallic gray with a dark blue stripe. My ship will be Ferrari red with no stripe.

Now I know that a knowledgeable person can work miracles with Photoshop. One of the things you can do is change the color of something. Unfortunately, I’m not a knowledgeable person. I use Photoshop to fine-tune the screenshots for my computer books, prepare photos and other images for the Web, and turn photographic images into computer-generated paintings for greeting cards. But I do know a Photoshop whiz. It was time to bother him.

Bert Monroy is another Peachpit author. He’s an artist and his specialty is Photoshop. He’s amazing — he can create, from scratch, photorealistic images. I have seen him do this at presentation. He blows me away.

N630ML NOTSo I sent Bert an e-mail with a thumbnail image of the photo I wanted him to convert and brief instructions. He said he’d do it, that I should just send him a bigger image. I sent the image with more complete instructions. I asked him to remove Tristan’s N-Number. I told him that if he wanted to get really fancy, he could add mine. The next day, the fruits of his labor arrived in my e-mail inbox. It was a photo of Tristan flying a helicopter that hadn’t been built yet.

I was incredibly excited. I couldn’t believe how good it looked. It looked real because it was real. The only thing he’d done is given Tristan’s helicopter a paint job and changed the N-Number.

I immediately started building my marketing materials.

Slide 1
Slide 2
Slide 3

First was the series of slides for the local theater. The slides would be released one at a time, about 2-3 weeks apart. The last slide would take its place in the carrousel when the helicopter arrived in Wickenburg, before I had a chance to take new photos. I e-mailed the PowerPoint slide file to ColorMark (in Phoenix) and got their assurance that I could pick up the slides on Monday morning. (I have a meeting down in Scottsdale with the FAA that day.) The first of the new slides should make it into the carrousel on Friday. The next marketing item was a 4×6 postcard that would serve as a rack card until I could take new photos for a real rack card. It would also make a good insert for the WE event scheduled for November 19. I laid out the postcard in InDesign, then FTPed all of its files to SimplyPostcards.com, which prints 4-color postcards at a very reasonable price. I’m hoping to get those back within a week or so. Then I’ll be leaving them all over town.

On Monday, when I get back to the office, I’ll use Bert’s creation to modify a few of the photos on the Flying M Air Web site. And I’ll probably show it off on my own Web site, too.

After all, how often do you get a photo of something you’ve bought before it’s even built?

Wireless Works

I find that wireless networking is the way to go.

I’m not on the road right now. I’m in my bedroom, lounging on my bed with two big pillows behind my back. The air conditioning is on and the house is comfortably cool. My laptop is where it should be: on my lap. When I’m finished writing this, I’ll upload it to the Internet without moving more muscles than it takes to click a mouse button.

And look Mom! No wires!

I had cable modem installed in my house the other day. It isn’t a traditional cable modem. It’s a wireless one. We live beyond the cable boundaries and depend on Dish Network for television. But satellite Internet service isn’t Mac friendly and I won’t buy a PC just to have Internet in the house. So I went with wireless cable. They put an antenna on the roof of the house and it points at the big transmission tower about a mile west of here. A wire from our antenna comes into the house where it attaches to an Apple Airport Extreme Base Station. The base station acts as a DHCP router and shares its signal with an old Strawberry iMac (via old-fashioned Ethernet cable) and any computer within range that has a wireless card. That’s how I can lounge upstairs and surf the net at relatively fast speeds.

My home network isn’t the only wireless network my PowerBook connects to. When I’m up at the Grand Canyon, waiting for a flight at Papillon, I sometimes wake up the PowerBook to check my e-mail. As soon as I flip open the lid, it connects me to Papillon’s wireless network, which has been configured so I can access it. And two weeks ago, when I was in New Jersey for a funeral, I flipped the PowerBook open at Newark Liberty Airport and was surprised to find myself connected to the terminal’s wireless network. There are a few other networks I’ve managed to connect to, too, but there’s no need to go into details. Still, I find it amazing that wireless networks are so prevalent these days.

Makes you kind of wonder what’s traveling around us in wavelengths these days.

I’ve got all the equipment I need to set up a wireless network in my office. I just don’t have the time. I’m working on my Quicken book revision (again) and am too burned out at the end of a day to sit around and configure a network. But one of these days I’ll get around to it.

Hard to believe there are still people accessing the Internet via dial-up connection, isn’t it?

My Computer Setup

Some information about what I consider to be the “perfect setup” for writing books about computers.

I’ve been writing computer how-to books since 1990 (13-1/2 years at this point). I just finished #55 the other day. Do the math and you’ll see that I average about 4 books a year. (My biggest year was 10; my smallest was 1.)

I write all of my own books, with a few exceptions here and there. For example, I didn’t write the Unix or AppleScript chapters of my Mac OS X Visual QuickPro Guides — I lacked the expertise and didn’t have time to learn. I also co-authored two of my books. But other than that, I wrote them all and will continue to do so until I find someone who has skills that meet my standards.

As you might imagine, my writing setup is an important part of what makes me so productive. I like to tell people that I have it “down to a science,” and I think I do. I’m fortunate that I’ve been able to earn enough money over the years to build what I think is the ideal setup.

I have three computers that I work with with when I’m writing a book: my “production machine,” and two “test mules.”

Currently (November 2003), my production machine is a Macintosh G4/866 minitower. It’s about two years old at this point. It has 512K of RAM and a 40GB hard disk. It also has a built-in modem, SuperDrive (that’s a drive than can read and write CDs and DVDs), and Zip drive. It also has all the standard Mac OS ports (USB, FireWire, Ethernet, etc.), as well as a SCSI port, which I thought I’d need but never have used. The computer is connected to a 21-inch Sony monitor and an array of USB and FireWire devices, including a scanner, Epson photo printer, digital camera, graphics tablet, iSight, digital video camera, and iPod (original).

I have two test mules, one for my Mac OS books and one for my Windows books.

My Mac OS test mule is an eMac 800 with a SuperDrive, built-in modem, bunch of RAM and 80GB hard disk. I’m really fond of this machine — it’s a great machine for someone with limited space who doesn’t need a lot of expansion or bells and whistles. And frankly, it’s a lot more “normal” looking than those ridiculous ET-looking iMacs that Apple is selling like crazy. It has a 17-inch monitor and can be hooked up to all the devices I need to write about in my Mac OS X books. It’s about a year old now.

My Windows test mule is a Dell Dimension 933Lr (or something like that). What can I say about it? It’s a Windows PC running Windows XP Home edition. It has a built-in modem and networking card and some kind of Pentium processor. Enough RAM, although I can’t remember how much. And enough hard disk space. It’s hooked up to a 17-inch Gateway monitor that I kept from my last Windows test mule, a Gateway PC. I think this Dell is about three years old now.

All of my computers, as well as my LaserJet 2100TN printer, are hooked up to an Ethernet network. They do file, Internet, and printer sharing using the built-in networking tools in Mac OS X and Windows XP.

My Internet connection comes from my old G3/300, which was my last production machine. It’ll soon be my Web/E-mail/DNS server, connected to the Internet with a cable modem. It feeds Internet to my three desktop computers, plus my PowerBook (when it’s added to the network) and Mike’s Sony Vaio (when he’s in town).

Here’s how it works. Suppose I’m writing a book about Mac OS X. I fire up the eMac test mule, reformat the hard disk, and install the Mac OS X software on it. I also install Snapz Pro, which is the best screen shot software out there for Mac OS X. Then I fire up my production G4 and open the file for the chapter I’m revising or the template for the chapter I’m writing from scratch. When I’m writing a Visual QuickStart Guide, I use InDesign 2.0; otherwise, I use Word X. As I work with the software on the eMac, I write about it on the G4. The two machines are sitting right next to each other and I can swivel in my chair to work on one or the other. I take screen shots on the eMac and copy them from the pictures folder, which I’ve opened on the G4, to my manuscript folder. If the screenshots need editing, I do it with Photoshop 7.0. If I’m doing layout, the screenshots get copied into the manuscript file. I add captions and callouts as necessary. Using this technique, I can turn out a completed manuscript page for a revision in as little as 10 minutes, if very little editing is required. For brand new titles, it takes 30 to 60 minutes for a page. On a good day, I can whiz through a chapter in a day or two.

The whole thing works pretty much the same when I’m writing a Windows book, except I use the Dell test mule and don’t reformat the hard disk before starting. I have to use two different screen shot software packages, because neither one does everything I need: Collage Capture and HiJaak Pro. And the shots always need to be touched up a little in Photoshop on the Mac. The process is generally slower, but not by much. Frankly, I don’t like writing Windows books, but my setup doesn’t have that much to do with it. I just don’t like working with Windows.

I believe that some authors write computer books with only one computer. They write, then switch to the program they’re writing about, fiddle around with it, take screen shots, then switch back to the program they’re writing in. (A very well-known author that I’ve often traded stories with confessed to me that he once wrote a book about Windows software by running the software under SoftPC on his Mac. Is he nuts?) With computer prices being well within the realm of affordability these days, there’s no reason an author should subject himself to such abuse. Two computers — one to work on and one to run the software on — are required, along with a network connection between them. I have three because I write about two different platforms.

By the way, if you were to peek into my office these days, you’d find quite a collection of computers. In addition to the G4, eMac, and Dell, you’d find the G3 that will soon be my Web/E-mail/DNS server and the old 8500/180 that’s currently my Web/E-mail/DNS server, still running on an ISDN connection. The 8500 was my production machine before the G3. (Before that was a 7100/66, which my sister now has. Before that was a Mac IIcx, which is long gone.) On my desk, you might also find my 12-inch PowerBook G4, which replaced my iBook SE, which replaced my PowerBook 3400c.

A production Mac lasts me about 2 years, although the G4 will probably last me another year — there’s no reason right now to replace it; it’s doing its job quite well. I replace each production machine with a current model Macintosh that isn’t top-of-the-line, but has enough RAM, speed, and hard disk space to last a few years. Test mules are good for 3 to 4 years. I replace them with low-end models that can run current operating system software and connect to the hardware I need to write about. I usually pump up their RAM enough to ensure that they operate smoothly. Laptops are good for about 3 years; I hope this PowerBook lasts longer because I really like it. My average annual expenditure on computer hardware is about $5,000, which really isn’t bad.

I don’t buy the latest and greatest gadgets unless I need to write about them. The iSight camera is a perfect example. I needed to write about iChat AV, so I bought a compatible camera. My AirPort wireless network, which lives at home when I’m not writing about it, is another good example. I bought it to write about it. Once or twice a year, I disconnect it and bring it to my office, where I reconnect it and write about it. Only one of my computers — the PowerBook — has AirPort networking built in. I don’t mind wires in my office, but its kind of nice to connect to the Internet at home from the kitchen, living room, den, bedroom, or back patio — without needing a really long cord.

The other thing I need to mention is that I don’t spend long hours “playing” with my computers or surfing the ‘Net. I have a life away from my computers that I enjoy. Computers are tools I use to make a living. Although I find them interesting, I think the other things I do with my life are far more interesting and fulfilling. My PowerBook is the only computer I spend non-working hours with. It’s my notebook, my tool for writing. And since I occasionally do that for pleasure, it makes sense to keep it handy, even when I’m not working.

Like right now.

Finished “Mac OS X 10.3 Panther: Visual QuickStart Guide”

Thoughts and insights on a tough revision and the computer book publishing industry.

Mac OS X 10.3 Panther: Visual QuickStart GuideMy last entry was pretty depressing. I was under a lot of stress to get the book done. Now that it’s done and the stress is gone, I’m feeling much better. The book is nothing short of a masterpiece, if I do say so myself, and I’m extremely pleased with it. We (Peachpit Press and I) got a lot of feedback from readers about previous editions. It seemed that my VQS wasn’t considered “good value for the money” because it didn’t have as many pages as other competing books. What most people didn’t consider was that VQSes are traditionally short (around 300 pages). Mine was actually long at about 400 pages. And it was considerably cheaper than the other books. But I guess if you calculated price per page, I probably fell a bit short of the competition. And I can’t deny that buying two books (a VQS and a VQP) does cost readers more money. In defense of Peachpit, the idea behind that strategy is that not all readers need all that information and we could provide affordable books tailored to two markets. But that’s not how reviewers saw the situation.

That said, we decided to combine the two books into one title. The resulting “Mac OS X 10.3 Panther: Visual QuickStart Guide” is about 670 pages long and features 20 chapters and over 2,000 screen shots. Topic range from the most basic basics (like how to point and click) to Unix commands. The price tag is an extremely competitive $29.95 US, making it a very good value. If this book doesn’t please readers, I don’t think any book will.

Writing the book was a bit of a challenge. First, there was the merging of the content from two books. What do we include? What do we exclude? Not much. The biggest casualty was the AppleScript chapter written by Ethan Wilde, which was replaced by an AppleScript basics section in the Applications chapter. (Those interested in AppleScript really ought to buy Ethan’s book!) Almost everything else that was in my Mac OS X 10.2 VQS and VQP remained in this edition.

Of course, everything has been updated for Mac OS X 10.3 Panther. That was the second challenge. Not just the update, but merging information about new features into existing chapters. Where do we discuss each new feature? Chapter 4, which is available as an excerpt from my Web site , got quite a few new pages. So did the i-Applications chapter, which was expanded to cover iCal and iSync (neither of which was available when I wrote the Mac OS X 10.2 VQS last year). The only chapter that got trimmed down a bit was the installation chapter. I cut out the info about installing Mac OS 9.2, since that information appears in the Classic Environment chapter.

There was a lot of pressure to finish the book on a timely basis. Timing is everything in the computer book publishing world and when a hot new product hits the market, publishers want their books out first. Trouble is, authors have to work with beta software, which often changes on a weekly (if not daily) basis to get the book done timely. Mac OS X 10.3’s beta software was available for about two months before the software was finally released. But the beta software changed. Any author who wrote about early versions of the beta wrote some stuff that isn’t right.

Want some examples? The first beta or two included a Print command under the Finder’s File menu. That command disappeared before I could try it out. Those first betas excluded a Favorites folder in the Sidebar. Sometime in the middle of the beta process, the Favorites folder reappeared. Then, near the end, it disappeared again. It was almost as if Apple wanted to kill favorites, thought they would get a lot of negative feedback, and then decided “to hell with the bad feedback” and killed it. (But favorites aren’t really gone, as you’ll discover when you read my book.) Icons changed, too. Internet Connect’s new icon didn’t appear until halfway through the beta process. Any screenshot of that icon taken before the beginning of October will be wrong.

So here’s the situation: publishers want the book written quickly. Once the book is written, it has to be laid out, proofed, edited, and printed. For most publishers, this is where time is lost. From the moment the author hands over the last manuscript chapter and TIFF files to the time the book appears in print, two or more months may have gone by. So do the calendar math: if the author waits until Gold Master of the software — on or around October 15 in this case — to finalize the draft manuscript, the book can’t possibly appear in stores until December 15. So what do authors do? Under pressure from publishers, they finalize before Gold Master. As a result, their books contain inaccuracies.

Peachpit and I don’t work this way. We have a remarkable arrangement. I do layout as I write, so I submit fully laid out pages as I work. My editors mark up this draft manuscript and I update pages as the software is changed and I get edits. As a result, when the software went Gold Master, we already had fully laid out pages for about 3/4 of the book. I wrote and laid out the rest the following week. This made it possible to send our completely accurate 650+ page book to the printer only three days after the software’s release date. I expect to hold a copy of the finished book in my hands by November 14 — just three weeks after the software’s release.

Any book that makes it to stores before mine can’t possibly be based on final Mac OS X 10.3 software. It’s just impossible. And that’s not an author’s fault. It’s the fault of publishers who don’t trust their authors to do layout. Peachpit trusts me and I don’t let them down.

Next on the agenda, Excel 2003 for Windows: Visual QuickStart Guide. Another revision — but this one should be a piece of cake.