A New Computer

The end of a rough month brings a nice reward.

I’d been thinking about replacing my aging 24-inch iMac computer with a newer, faster model for some time. I almost did it in April, but some Twitter friends wisely advised me to wait for the new models, which were due out in May. By that time, I was hard at work on My Mac OS X Lion book, racing against a deadline set not only by the software’s pending release but by my annual trip to Washington State for cherry drying work. I didn’t get the book done before I had to leave, so I packed up my iMac and other office equipment and headed north. I decided to wait until I was finished with the book. If I had a computer sitting there, waiting for me to set it up, I’d be too distracted to get any work done.

Death of a[nother] Hard Disk

Not buying the new computer turned out to be a bad decision. On Friday, June 17, the iMac gave me a weird error message about ejecting a disk — when I hadn’t ejected a disk. I was running out the door to take care of other business and when my computer wouldn’t shut down the usual way, I just powered it off. Later that day, it wouldn’t start from its internal hard disk.

That’s when I started to realize I might have a problem.

I knew I had a problem the next day when Disk Utility — the Mac software that can usually fix disk and directory related problems — couldn’t fix the disk.

My last full backup had been in May. I use Time Machine for effortless backup, but I’d disconnected the backup drive when I left home. Although I didn’t bring the drive with me last year, I did bring it this year. I’d been thinking about hooking it back up, but laziness got the best of me. So my most recent backup was about three weeks old.

Since then, I’d written at least a dozen chapters of my book.

I was lucky. Really lucky. I was able to mount the disk and suck important documents off it — including those all-important manuscript files. I also sucked off the applications, which had not been backed up. With my most important files on an external hard disk and the big Time Machine backup handy, I tried to format the hard disk, figuring I’d reinstall the software I needed to finish up the book.

My luck didn’t hold. The hard disk just wouldn’t consistently mount. I couldn’t successfully reinstall the operating system on it. It looked as if it needed a new hard disk. Again.

A Temporary Solution

So now I had a book project due very soon that required a working computer with a big monitor to complete. After all, I do layout for my Visual QuickStart Guide books and I shudder to think of laying out a book in InDesign on a 13-in MacBook Pro.

I stayed amazingly calm. First, I hopped into the truck and went to Wenatchee. At Costco, I bought yet another portable WD 1TB USB hard disk.

Yes, I know FireWire would be faster, but it isn’t as if Wenatchee, WA has a lot of choices when it comes to computer hardware. Besides, rain was moving in and there was a good chance I’d need to fly. I didn’t have time to look for a better option.

A new internal hard disk was out of the question. Special tools and expertise is required to disassemble an iMac and install a hard disk. I lacked both.

So I set up a USB hard disk with Snow Leopard, Photoshop, and InDesign. I had the original discs with me, since I planned to do a clean install on my new computer when I got it. I didn’t even bother updating any of them. I just got back to work.

And I was surprised. I expected the computer to be painfully slow. After all, it was booting from an external USB 2 hard disk. It was running some pretty intense software from the same disk. Although I saw a spinning beach ball a lot more often than I like to, it was tolerable.

The New Computer

Of course, while all that software was installing, I was on my laptop, configuring the computer’s replacement. I ordered a very sweet system:

    27" iMac

  • Computer Model: 27-inch iMac – the monitor size is 3 inches larger than my old computer, but it’s widescreen instead of standard so it really doesn’t seem that much bigger.
  • Processor: 3.4GHz Quad-Core Intel Core i7 – this is the best and fastest processor offered for this computer. The Apple sales guy told me that it was faster than current Mac Pro models. (Of course, those are due to be updated shortly.)
  • RAM: 8GB 1333MHz DDR3 SDRAM (2x4GB) – this is twice as much RAM as I had. And the configuration will allow me to double it in the future because there are 4 RAM slots and I’m only using two.
  • Hard Drives: 1TB Serial ATA Drive + 256GB SSD – yes, that’s two hard disks to destroy.
  • Graphics: AMD Radeon HD 6970M 2GB GDDR5 – this is the best offered. I figured it would come in handy for my video editing work.
  • Mouse: Apple Mouse – call me old-fashioned, but I don’t like to depend on battery power for a mouse. Besides, already I have all kinds of Bluetooth pointing devices I had to buy to write about.
  • Keyboard: Apple Num Keyboard – I don’t like to depend on batteries for a keyboard, either. I do have a Bluetooth keyboard if I decide I want to use it.

The computer cost a small fortune. I get a minuscule discount from Apple as a Peachpit author; it was almost enough to cover sales tax. But I can justify the expense. I use my desktop computer for so many things in all of my business endeavors, from writing and laying out books to processing video to invoicing and accounting to creating marketing materials. Why settle for less than the best (if you can afford it) when the best can make you more productive?

It took nine days for the computer to arrive. It was shipped via FedEx directly from China. (I sure do wish Apple and other companies would build things here.) It was delivered to my RV in Quincy, WA, where I’m living for the summer, the day I finished writing the book. It sat in its box overnight as I finished up a bunch of editing.

There was no unboxing ceremony. I deactivated Photoshop and InDesign on my old iMac and shut it down. I moved it from desk to countertop, wiped down the desk, and set up the new computer.

I know this is going to make me sound like an Apple fan-girl, but as I took the crystal clear cellophane off the monitor, I couldn’t help but think how beautiful the computer was. And, as I thought about it, I realized how incredibly weird that was. Hell, it’s just a computer.

Setting Up

My Hard DisksBecause the computer had two internal hard disks, I decided to get a bit fancy with the setup. I left the operating system and applications on the smaller SSD drive and moved my Home folder to the larger ATA drive. I didn’t just put my home folder on that drive. I made my home folder the drive itself. Not only does the disk icon look like a Home folder icon, but when you open it, you find the contents of my Home folder. One less level of folders to dig through.

As for hard disk names, I always try to give my disks meaningful names. Now I had two disks to name. It was quite a dilemma for me. I put it to my Twitter friends and @BrianDunning came up with an interesting suggestion: Cyclic and Collective. At first, I didn’t think they were quite right. But the names grew on me and I wound up using them.

I spent most of yesterday installing software from original program disks and downloads from the Internet. My Internet connection here is via MyFi with a 3 GB monthly bandwidth cap. (I’ve already hit 6 GB this month; that’ll cost me an extra $30.) So I did most of my downloading from a coffee shop yesterday morning and from a wine bar yesterday afternoon. Microsoft Office 2011 was contained in a 1 GB file; other updaters were nearly as large. Had a hiccup with my Final Cut Pro installation and had to restart it; sure hope it works this time because it seems to take forever.

As for Time Machine, I also bought a Seagate 2TB desktop hard drive at Costco. I set that up to back up both drives. I plan on getting some mirroring software to mirror each disk on portable drives. That’ll be a total of two full backups. Lesson learned.

I have some final editing to do on my book and I expect to get to that this afternoon. I’m sure it’ll take quite a while to get the new computer set up the way I need it to. But I’m looking forward to the process and having a clean installation of software and files on a much faster computer.

Why I Bought a MacBook Air

I needed a new test mule. Really.

MacBook Air MeasurementsToday, I finally broke down and bought an 11-in MacBook Air. For those of you who don’t know what this is, it basically a full-powered Mac OS computer that measures in at 11.8 x 7.56 x 0.68 inches and weighs 2.3 pounds. It’s the laptop I wanted two years ago when I needed a new laptop and the smallest thing Apple offered was a 13-in MacBook Pro.

Mac OS X 10.6 Snow LeopardOf course, back then I did buy the MacBook Pro. I bought it as a “test mule” for the book I was working on: Mac OS X 10.6 Snow Leopard: Visual QuickStart Guide for Peachpit Press. Test mule is my name for a computer I own primarily to run software on while I’m writing a book about the software. I bought the 13-in MacBook Pro to run Snow Leopard, which had several features that took advantage of the computer’s touchpad. My older MacBook Pro (15-inch; just handed it off to my husband for use) didn’t support all the new features. At the time, I even wrote a blog post lamenting why I couldn’t fully enjoy my new computer.

When I was finished with the book, I outfitted the computer for my own everyday use. It would replace the aged 12-in PowerBook I’d bought long before. (At this point, you must think that I’ve had a lot of Macs since my first one in 1989. You’d be right.) Since then, the old test mule has become my traveling computer and has been many miles with me.

Outlook for Mac 2011Recently, when I began working on Microsoft Outlook for Mac 2011 Step by Step for Microsoft Press, I needed a test mule to run Office 2011 on while I wrote the book. I didn’t want to sacrifice my 13″ MacBook Pro, since it had really become my main travel computer. So I dug out my 15-in MacBook Pro and installed the software on that. It worked like a charm. Problem solved.

But now I’m starting work on a new book about software that simply won’t run on that old 15-in MacBook Pro. Worse yet, if I installed the software on my 13-in MacBook Pro, it would significantly impact how I could use the computer. This was quite a dilemma.

I had two options:

  • Stop using the 13-in MacBook Pro as a travel computer and use it as a test mule. Hmmm…that sounds like fun. Either face the next two months without a laptop or spend hours on the time-consuming, nightmarish task of shifting software and data files to the older laptop still in my possession.
  • Buy a new test mule. And oh, by the way, wouldn’t that 11-in MacBook Air that you’ve been admiring be the perfect machine for the job?

Guess which option was more attractive to me (although less attractive to my bank account)?

MacBook AirI picked it up at the Apple Store today. I went all out and got the faster processor, bigger flash drive, and 4 GB of RAM. I got a tiny discount because of my relationship with one of my publishers and that saved enough money to buy a neoprene case for it. The wireless Epson printer, which I’ll use in my RV this summer, was free after rebate.

So now I can begin a new lament. As I type this in my Phoenix office on my 13-in MacBook Pro, sitting beside it on the desk is my brand new 11-in MacBook Air. So far, I’ve plugged it in, started it up, told it who I am and how to access the network, and downloaded 1.6 GB of updates to installed software. Not exactly fun stuff. But right now, it’s downloading the beta software I need to write my book. All work, no play for this new puppy.

It’s okay. when I’m done with this book and the other projects lined up after it, I might actually use it for my own computing needs. We’ll see.

The State of Macworld Expo

The end of an era? Looks that way to me.

When Apple announced, two years ago, that it would no longer attend Macworld Expo, lots of people said the announcement was Macworld Expo’s death knell. Like some other people, I thought that opinion was a both harsh and premature.

I don’t think that anymore.

On Friday, I did a presentation as a member of the Macworld Expo Conference faculty for the first time in at least eight years. I used to speak at Macworld Expo all the time, having at least one session in San Francisco and Boston (and later, New York) and even Toronto from about 1993 through 2002 or so. Back in the early 2000s, IDG took over the show and the conference management changed. They also went off in a new direction that stressed the creative aspects of working with the Mac. I was always more of a productivity person, so I didn’t fit in.

I still went to the show once in a while, but not very often. I came a few years ago, mostly to meet with one of my publishers. But that was it.

Looking back at it, I realize that I was deep in the Mac world at Apple’s first peak in popularity. The shows — especially in San Francisco — were huge. The very biggest shows took up both exhibit halls of Moscone Conference Center. All the big vendors were there — Apple, Microsoft, Adobe, Macromedia, Claris (later FileMaker), Quark — the list goes on and on. The show floor was buzzing all day long. The noise was deafening and there was a pure adrenaline rush on first entering the exhibit hall. And the products introduced! Even my husband talks about innovations like the Video Toaster (which, ironically, I believe ran on an Amiga). I remember all of Apple’s big hardware and software releases and the software demos that were both educational and entertaining. And how could I forget the Boston show where Mac OS 8 went on sale and my first Mac OS Visual QuickStart Guide sold out?

Afterwards, the parties would start. They were amazing affairs — the Exploratorium is a good example; the party sponsors rented the entire facility, leaving us to wander around and play with the exhibits. There was headliner entertainment, too: one year was Chris Isaac at one party and Jefferson Airplane at another. There were cruises and bungee jumps at Boston Harbor. There were full food, open bar parties at the top of the Fairmont in San Francisco. As one of the B+ list speakers/authors (in those days, anyway), I’d party hop with my peers. I remember one year bouncing from one party to the next with Bob Levitus, who always managed to get into all the parties, whether he had tickets or not.

Things change. Apple took a serious downturn. Things looked bad. Then Steve Jobs came back. The original iMac breathed new life into the company. More products followed. I remember seeing hundreds of buses all over San Francisco skinned with images of five colors of iMacs. But despite Apple’s subsequent successes, Macworld Expo was never quite the same. The show began to shrink.

What I saw on the show floor this year was a shock. The show was tiny — by old standards — occupying about half of one floor at the relatively new Moscone West building. At least 80% of the items on display could be classified as accessories — mostly protective or decorative covers — for the iPad and iPhone. There were very few Macintosh items.

Macworld Expo had become iAccessoryworld Expo.

Although most of the folks I spoke to about their thoughts on this matter seemed to agree with me — some more strongly than others — the members of the Macintosh press that I met there were surprisingly upbeat about it. One of them even commented that Microsoft’s support for the show is a good sign. Support for the show? They didn’t even have a booth! Having a party for a chosen few and being one of the sponsors on another party isn’t the kind of support I’d be upbeat about.

If I had travelled to San Francisco for the sole purpose of seeing the show floor — as I know many people did in the past — I would have been sorely disappointed. Disappointed enough to demand my money back. What I wouldn’t be able to get back was the travel time and expense and the three hours of my life spent trying to understand how so many accessory developers could think there was a market for yet another version of an iPad case. Or skin. Or screen protector.

The real value in Macworld Expo was the conference sessions — now more than ever. The conference management assembled a collection of experts — some old timers like me, some younger and newer to Mac OS (and iOS, of course) — and offered a variety of interesting tracks and sessions for Mac, iPhone, and iPad users.

My session about building your iPad for business was relatively well attended — the room was about half full. I received a handful of follow-up questions and a polite round of applause at the conclusion of my talk. Several of the attendees came up to the front of the room to thank me or offer complements. It was like the old days, but on a much smaller scale.

After all, Friday’s room could have held only about 100 people when, in the past, I did sessions that packed a room that seated more than 300.

And the meeting room area at Macworld Expo used to be busier than a high school hallway between classes each time a session let out. Now only a few dozen people meandered about, shuffling from room to room.

At least these people got something worthwhile for their money.

I know these are harsh words and, as a member of the Mac community with a long Macworld Expo history, it’s hard for me to type them. The conference faculty was treated quite well, with generously filled swag bags, a comfortable place to rest between sessions, and both breakfast and lunch every day. The session rooms were relatively well equipped. It’s hard to share negative opinions about Macworld Expo when IDG staff responsible for the conference part of the show treated me well. But if this blog post precludes me from ever speaking again at a Macworld Expo, so be it. I don’t sugar coat anything and I’m certainly not going to sugar coat this.

While I realize that the old days are long gone, I think that if IDG can’t do better than what I experienced this past week in San Francisco, they should throw in the towel on Macworld Expo and concentrate on better ways to share valuable information with Mac OS and iOS users.

The Trouble with Troubleshooting

I troubleshoot a Photoshop CS3/Mac OS X 10.6.3 problem.

Yesterday, after composing a blog post on my MacBook Pro, I went into my office with an SD card full of photos with every intention of choosing one or two to include in the post. I copied the photos to my hard disk along with my GPS track log and geotagged the ones I could tag. Then, after using QuickLook to make a preliminary selection, I opened five images with Photoshop CS3.

Or at least I tried to.

The problem was that Photoshop wouldn’t launch. It kept “unexpectedly quitting.”

And so began more than 2 hours of troubleshooting that culminated with my making an appointment today to visit the Arrowhead Apple Store down in Peoria, 50 miles from my home.

If you’re having this problem and are looking for a solution, read this post that I wrote this morning for Maria’s Guides.

This post is mostly about what a pain in the butt troubleshooting can be.

My troubleshooting process began with a Google search for Photoshop CS3 with Mac OS 10.6.3. I suspected the problem had to do with my update to 10.6.3 the previous week and I turned out to be right. There were discussions going on in the Apple forums about the problem. The most promising was titled “Installed 10.6.3 and now Photoshop CS3 won’t open.” The thread originator posted a quick description of the same problem I was having and got (so far) 167 responses.

Sadly, the responses were distributed over 12 individual pages, so I’d scan a page, click Next, and wait for the next page of responses to load before I could continue scanning. I don’t have a fast Internet connection in Wickenburg, so it was time consuming and tedious.

But it’s the content of the responses that I have a problem with. Only about 1/3 of them were of any use. The rest fell into one or more of the following categories, listed here with my comments.

  • Did you restart your computer? A person who can find and post a request for help in an Apple forum is likely smart enough to try restarting the computer before looking for outside help.
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m having that problem, too. Okay, what else can you tell us to help us troubleshoot?
  • I’m using Photoshop CS3 with Mac OS 10.6.3 and I’m not having that problem. So the rest of us are imagining it? Why not provide some info so we can learn how our systems differ from yours?
  • Did you try doing ABC? This comment might be helpful the first time ABC is suggested, but when it’s suggested a half dozen times and people have already reported that it doesn’t resolve the problem, it is a waste of time. Please read all the suggestions and the responses before adding your own.
  • It’s Apple’s fault. They don’t test updates. Don’t waste my time with this bull.
  • It’s Adobe’s fault. Their software sucks. Don’t waste my time with this bull, either.
  • It’s because you’re using a Mac. This problem doesn’t happen on Windows. What the hell are you doing on an Apple forum? Go play with Bing.
  • XYZ Program is better for photo editing than Photoshop. You expect me to toss a costly program I’ve been using for 15 years just because of a [likely minor] incompatibility issue? Get real.

It would be great if Apple’s forums had a way to vote down unhelpful comments so only the helpful ones appeared. I think we could have weeded out at least 100 of the comments that hid the solution. Or, better yet, offer some way to flag the comment that actually contains the “answer.” After all, the discussion thread was marked “answered,” so someone must have recognized one of the posts as a solution.

Adobe’s Web site had a TechNote that offered three possible solutions. One, which suggested turning off Rosetta, did not help me, since Rosetta was not enabled for Photoshop. I’m pretty certain the problem is related to an incorrectly entered serial number after having my logic board replaced two years ago. That’s what’s taking me and my 40 pound, 24″ iMac down to Peoria in two hours. Evidently, there’s no way for an end user to fix a serial number issue.

The net result of all this is that I lost two hours of my life to a troubleshooting exercise and will lose another three hours making a trip down to the Phoenix area to get a problem fixed on my Mac that was introduced by Apple.

Side benefit/drawback: I will get my hands on an iPad so I can give it a test drive. If they’re in stock, I’ll likely walk out of the store $500 poorer.

Apple is a Corporation, NOT a Cause

A post by former MacWEEK editor, Rick LePage, really hits the nail on the head.

Yesterday, while having lunch in my hangar at Wickenburg, I checked ÜberTwitter to see what was going on in TwitterLand. Along the way, I followed a link shared by @BWJones to a blog post by Rick LePage.

Rick LePage was the editor-in-chief of MacWeek magazine, a weekly tabloid-sized publication that covered all things Macintosh. Back in the 1990s, not long after I began my writing career, I wrote occasionally for MacWEEK. Not only did the magazine pay well, but it was highly respected. Writing for MacWEEK likely helped my writing career get off the ground — although I never really pursued magazine writing, preferring to author books instead.

So there I was, munching a bacon cheese burger and tater tots while sitting on the back seat of my golf cart at the airport, reading Rick’s blog post on my BlackBerry Storm. One thing I hate about the Storm is its Web browser. I don’t surf on the Storm. I’d lose my mind. But this blog post really sucked me in. It explained what was going on at MacWEEK when Apple was in its “state of confusion” before Steve Jobs came back. It admitted that MacWEEK had gone beyond reporting and had been trying to push its own agenda to sway user opinion on what Apple was doing. (I can’t help but think about FoxNews and its political slant here.) I was so sucked in that I forgot I was reading microscopic print on a cell phone.

And then that cell phone rang. I was called into action doing something else. I put the phone away, cleaned up my lunch mess, and got back to work.

But I didn’t forget the blog post. It had impressed me that much. I figured I was only halfway finished with it and I wanted to read it to the end. I can’t tell you how seldom that happens these days.

So this morning, I looked it up and finished reading it. I discovered that I’d nearly finished. But the best was at the end, in the last paragraph. It started with these sentences that really hit home for me:

I don’t think Apple is a better or worse company than most others. I still love the stuff they turn out, and would much rather be pushing a Mac than a Windows box. But, for all of you who think that the Mac—or Apple, or the iPhone—is a Cause, and that somehow Apple cares about you, wake up.

It was as if Rick had written this based on what was in my mind.

I like most Apple products, and have bought many of them. I prefer a Mac over a Windows PC — to me, there’s no comparison worth making. I own numerous Mac computers, including a desktop Mac and three laptops.

But I’m not a blind follower to everything Apple. I’m not a member of the Apple cult. I make my product decisions based on design and functionality, not logo. I don’t hang on Apple rumors. I don’t push Apple products to my friends and family members. I don’t surf the Web looking for all things Apple. And I certainly don’t get into bullshit platform wars in forums and blog comments. Hell, I have a life beyond the computer I chose to get work done.

I don’t like all Apple products — I still can’t see the real point of an AppleTV and prefer my BlackBerry over an iPhone. (I don’t want to surf the Web and run countless pointless applications on my phone.) My days of buying in and adopting early ended not long after I bought a Newton.

I realized years ago — probably around the time iTunes made its debut — that Apple is not putting the customer first. As Rick points out in his piece, Apple is a company with the need to make a profit and stockholders (like me, I might add) who want to see it succeed. Apple has a huge cult-like following — there must be something hypnotic about Steve Jobs at a keynote intoning, “Isn’t this incredible?” — and it’s cashing in on it. More power to ’em!

The sentences I quoted above should be a reality check for everyone. Apple is not a cause. It’s a corporation. Its goal isn’t to make you feel good or solve all your problems. Its goal is to get you to buy its products so it can make a big, fat profit.

Wake up, folks. Look beyond the logo and pretty white packaging and think about what you’re buying. If you still want to evangelize the “Apple cause” — well, it’s your life.

And now lets see how many people completely misunderstand the point of this post and come to Apple’s rescue in Comments.

Why I Canceled My Nook Order

And why I might buy one anyway.

As an avid reader, I’ve been attracted to the idea of an ebook reader for years. But until this past autumn, I haven’t really found one I thought I’d actively use.

Before that were offerings from Sony, which seemed to fall far short of what I thought was a good design. The blinking page turns would drive me batty, since I knew I could go through an average page in 10-20 seconds. (Have I mentioned that I read very fast?)

Kindle came out and lots of people loved it, but I was turned off by Amazon.com’s aggressive marketing, limited format support, and high book prices. (Like many other book buyers, I don’t feel that an ebook’s cost should be anywhere near the cost of its printed version.) And when Amazon snatched purchased books off of Kindles without warning, I started wondering what other kind of access Amazon had and whether it would use it.

Enter, the Nook

NookThen Barnes and Noble introduced its Nook. Or at least it announced it. It seemed more in line with what I was looking for in size, cost (for the unit and books), features, and flexibility. I visited B&N stores regularly to get my hands on one and give it a try. No joy there. Even after November 30, when the units were supposed to be available for purchase, I could not seem to find one. And I certainly wasn’t going to buy one until I either read a lot of reviews about it or had some quality time with a demo unit. I did see a few reviews and they were, for the most part, positive. But I still wasn’t prepared to buy one until I could walk away from the store with it.

Christmas came. My husband decided to buy one for me. Of course, he couldn’t get his hands on one, either. But he ordered one online. They said it would ship in January. He asked for some kind of card he could give me on Christmas Day, in its place. They charged him $4 for a card that looked like a nook. And that’s what I opened on Christmas Day.

A few days later, he checked with B&N again to see when the Nook would arrive. They projected the end of January.

FAIL

An Apple Tablet?

This week, the Apple Tablet rumors have been in full swing. I’ve been wanting an Apple Tablet — or at least thinking I wanted an Apple Tablet; more on that in a moment — since last spring. I actually put off the purchase of a 13-inch MacBook Pro, hoping a Mac netbook would become available before then. Apple kept insisting they weren’t going to develop a netbook. I caved and bought the 13-inch MacBook Pro to replace a 15-inch MacBook Pro and the 12-inch PowerBook before it. (I still have both of those; anyone want to buy one?)

So here I sit, on January 6, expecting a Nook right around the same time that Apple might announce something infinitely better.

Or not.

The way I see it, Apple could do one of two things:

  • It could announce an Apple Tablet that basically reinvents ebook readers and tablet computers at the same time. Kind of like what the iPod did for MP3 players years ago. Something that would blow all the existing options out of the water. Something not only I’d want, but everyone with a need (or desire) for mobile computing or an ebook reader would want.
  • It could announce an Apple Tablet that, although attractive in its design and interface, falls short of what I need or want as an ebook reader or tablet computer. Or marry the device to a partner that I can’t do business with. This is what I thought about the iPhone and AT&T. I might have gone with the iPhone if I could choose my own carrier — without jailbreaking — but the AT&T partnership was a deal breaker for me.

An iPhone-like Situation

Indeed, my situation today has a lot in common with the iPhone announcement and release. Back then, I was in the market for my first smartphone. My Motorola flip phone was four years old (at least) and I wanted to tap into the basic computing power of a smart phone to store contact information, calendar events, and simple applications that would help me as a pilot (weather, flight planning, etc.). It was vital that the phone be able to communicate with my Macs to exchange information. When the iPhone came out, it looked like a dream come true.

Yet just days before people started lining up to buy iPhones, I bought my Palm Treo 700p. At the time, it was a better decision for me. Two years later, I updated to a Blackberry Storm. Again, it was better for me.

You see, unlike so many other people, I don’t buy the hot new gadget just because it’s a hot new gadget. I buy it because it meets my needs. The iPhone doesn’t meet my needs. I need a carrier with coverage in remote places. Verizon is that carrier. (Hell, AT&T can’t even get a good signal at my house.) I’m not interested in dropping $1.99 every few days or weeks on cool apps I don’t need or playing games on my phone. I’m not interested in being able to join wi-fi networks — in the very remote places I go, I consider myself lucky to have a cell signal at all. I need “tethering” to get my computer on the Internet via my cell phone’s Internet connection. The Treo and the Storm both support that through Verizon; I just learned that the iPhone still does not via AT&T. I’m not interested in jailbreaking a phone to add features that the maker and carrier don’t want me to have. I want a fully functioning, fully supported smartphone that does exactly what I need it to do, right out of the box. That’s why I don’t have an iPhone.

Now before you iPhone lovers get your panties in a bunch, just remember that I’m talking about my needs and wants. Not yours. Yes, your iPhone is very cool. Yes, I wish it met my needs. But although it might be perfect for you, it simply doesn’t meet my needs. I made my decision. Don’t waste your time and mine blasting me in Comments because I haven’t drunk the iPhone Kool-Aid and sacrificed my needs so I can be cool, too.

My Point

And that brings up one of two points in this post:

  • Barnes & Noble failed when it introduced its Nook right before Christmas and didn’t have enough units on hand to sell to customers who wanted them. That failure was only made worse when the Apple Tablet rumors starting churning up again. Why would anyone buy now and wait until January month-end for a device when Apple, which is known for innovative, game-changing designs, could announce a competing product around the same time? Hell, if the Apple Tablet is the product I hope it is, I’d buy one even if I already had a Nook. But the Nook hasn’t arrived and B&N has just lost a sale.
  • Although I’m huge Apple fan who has been using Macs since 1989, writing about them since 1990, and, indeed, earning a living as someone who teaches others about Apple products and software, I won’t buy an Apple Tablet if it doesn’t meet my needs. (Maybe it’s because I’d be buying it for me, and not to impress others with it. ) I’d like to think that there are other people like me who feel the same way. Don’t buy it just because it has an Apple logo on it. Buy it because it’s the best product to meet your needs.

It’s because I’m willing to wait and see what might be available soon that I’m in a good position to get what I want instead of compromising on features. I like immediate gratification as much as the next geek, but after buying so many gadgets over the years — heck, I still have a Newton MessagePad on the shelf! — I’ve learned not to rush out and buy what might be the next great thing. I’m willing to wait, at least until April or May, to make my ebook reader purchase.

Whether it’s an Apple Tablet or a Nook or something else that materializes between now and then remains to be seen.

But one thing’s for certain: it will be the right purchase decision for me.

Word 2004 Does Not Like Mac OS X 10.5.8

It may be time to update Office.

I just started work on a new book revision. The project requires me to take relatively lengthy, style-laden Word documents, turn on the Track Changes feature, and edit like crazy. It wasn’t long before I was pulling my hair out.

You see, the other day, I updated my iMac from 10.5.7 to 10.5.8. I suspect that something in that update just didn’t sit well with Word 2004, which I was still running on that computer. After all, the iMac has an Intel dual core processor. Office 2004 was written for the old PowerPC processor that came in older Macs. Whether the problem was Mac OS X’s inability to run the old PowerPC application or Word’s inability to run on the 10.5.8 update is a mystery to me. All I know is what I experienced: text editing so slow that I could type faster than Word could display the characters.

Revisions, RevisionsAt first I thought it might be the document itself. It’s 40 pages of text that utilizes about 20 styles and fields for automatically numbering figures and illustrations. The document was originally created about 10 years ago and has been revised and saved periodically for every edition of this book. It pops from my Mac to an editor’s PC and back at least five times during each revision process. I thought it might have some internal problems. So I used the Save As command to create a new version of the document. The new file was about 5% smaller in size, but had the same symptoms as the original.

Next I sent it over my network to my new 13-inch MacBook Pro. That computer’s processor isn’t as quick as my iMac’s and it has the same amount of RAM. The software on that computer was different, though. I had a developer preview version of Snow Leopard installed and, in preparation for a Microsoft Office 2008 project I’ll be starting in the fall, I’d installed Office 2008 with both major updates. I opened the file on that machine and it worked just fine. Great editing and scrolling speed. Exactly what I needed.

So I bit the bullet and installed Office 2008 on my iMac. And the two major updates. And two smaller updates that became available on August 5. It took hours — the updates totaled over 400 MB of downloads and I’m connected to the internet on a horrible 600-800 Kbps connection that likes to drop. (I’m living in a motel right now, traveling for my helicopter business.)

The result: All the performance issues are gone. Word is snappy yet again on my iMac.

You might ask why a person who writes about Microsoft Office applications had not yet upgraded to Office 2008. This all goes back to last year’s revision on this project. I actually did upgrade but then I downgraded. It was mostly because I needed the macro feature of Word, which wasn’t available on Word 2008. I’d upgraded my iMac last year, but when I decided to reformat my hard disk to ward off computer issues I was having (which were apparently caused by a bad logic board), I reinstalled Office 2004 instead of 2008. You see, I liked the old version better.

But it’s obvious to me now that I need to keep moving forward with the rest of my technology if I want it to perform as designed. Everything must be in sync. If I want to keep using Word 2004, I should use it on a computer that has the system software available during Word 2004’s lifespan. My old 12-inch PowerBook would be a good example. It has a G4 processor and runs Tiger. That’s as advanced as it will ever get. Office 2004 is a perfect match for it.

If there’s a moral to be taken away from this story, it’s simply that if you want your hardware and system software to be new or up-to-date, there will come a time when you’ll have to update the applications that run on it. Bite the bullet and do what you have to. It’ll be worth it.