New Computer Diary – Prelude

Why I need to order a new Mac.

I write books about computers for a living. That’s a blessing and a curse.

It’s a blessing because I get to buy new computers and related hardware (like cameras and scanners and printers) and software to keep up with technology. I can write most of this stuff off as business expenses because I actually need them to get my work done. Some of this stuff is really cool, so using them is almost like playing with new toys. I also often get prerelease software, so I can work with it before anyone else.

It’s a curse because I have to buy new computers and related hardware. I don’t get most stuff for free. And because I often have to buy new hardware right after it comes out — when the prices are highest and their problems haven’t been identified yet — they’re costly and sometimes problematic. My goal is always to buy a computer that’ll last at least three years so I don’t have to do this too often.

And if you think working with beta software is fun, try running Office 2007 on Windows Vista four months before the scheduled release dates. Not only did I have to buy an expensive computer just to run this software on — Vista has some pretty serious system requirements for all those pretty graphics — but I have to struggle to work around bugs and incompatibilities caused mostly by unavailable driver software updates.

I have three computers I use for work, as well as a laptop for business and home use:

  • Dual Processor G5My production Mac, which is currently a 2-year-old Dual G5 tower, is the computer I sit at when I’m writing. It has a 21″ Sony monitor (the old, heavy CRT type) which is really great when I’m doing layout on Visual QuickStart Guides and Visual QuickProject Guides. It also has all the built-in and attached equipment I need to get my job done, including three printers, a scanner, and numerous mobile devices like cameras, digital video cameras, iSight cameras, external hard disks, and more.
  • G4 eMacMy Macintosh test mule, which is currently a 3- or 4-year-old G4 eMac, is the computer I run software on when I’m writing Mac books and articles. I like the all-in-one design of the eMac and the price when I bought it was within reason. When I bought it, it had the bare minimum I needed to get the job done: a G4 processor (at the time, G5 had just come out), a SuperDrive (because I often need to write about creating CDs and DVDs), built-in modem, networking capabilities, and adjustable screen resolution. When I went wireless last year, I installed an AirPort card. This computer was the machine I used to run beta Mac OS software for my Panther, Tiger, Word 2004, Excel 2004, WordPress 2, and QuickBooks 2006 books. Maybe even my Jaguar book, although I admit I can’t remember that far back.
  • Dell LatitudeMy PC test mule, which is currently a Dell Latitude D820 laptop, is the computer I run Windows software on when I’m writing Windows books. (The computer recently replaced a 4-year-old Dell Dimension tower, which was really showing its age.) This computer is loaded and it isn’t by choice. As mentioned earlier in this entry, I needed souped up graphics and a fast, modern processor (or two?) to run Vista with the Aero Glass effects. It has a CD writer but not a DVD writer, although it will read both. (This became a rather ironic thing when I downloaded the Vista beta from Microsoft’s Web site and had to use my Mac to create the DVD I needed to install Vista on my PC. It worked. Of course.) I’m hoping this computer, which cost me a small fortune, will last at least four years.
  • imageMy business/personal laptop, which is currently a 12″ PowerBook G4, is the machine I keep at home and take on the road with me. It’s used for e-mail and blogging these days, although I sometimes use it for podcasting. And, every once in a while when I need to do a presentation, I plug it into a projection monitor and do demos. I love the size and configuration of the computer, although I admit that the 40GB (really 37 GB, but who’s counting?) hard disk is a bit small. I recently had to offload a bunch of music and podcasts just to make room for some other stuff. And with only 640 MB of RAM and 867 MHz of processing power, it sometimes slows to a crawl when taking on heavy-duty tasks like sound conversion and iMovie visual effects. I also noticed that its fan starts more frequently than usual these days, like its always hot and bothered.

Why all these computers? Well, I’ve found that the best way to write about a software product is to run two computers side by side. The test mule runs the software I’m writing about. My production Mac runs the software I’m using to write — normally InDesign or Word. I perform a step on the test mule, take a screenshot if necessary (which is automatically dumped over the network to my production Mac), and write about what I see on my production Mac. Not only do I have the benefit of seeing what I’m writing about as I write, but I can keep that test mule in pristine condition. In fact, it’s common for me to reformat the hard disk and reinstall all system and application software I need to write about each time I start a new project. I really do use those two computers just for work.

I used to buy a new production Mac every two years and a new personal laptop every three years. Earlier this year, however, when my production Mac was only a year and a half old, the motherboard went on it. I faced a tough decision: fix it (at a cost of about $700) or put that money into a brand new Mac and throw this one away. But it still had a lot of life in it and there wasn’t anything really better to trade up to. So I fixed it. And life went on. It’s still serving me faithfully, running all the software I need to run. Keep in mind that I don’t update software unless I need to — for example, I’m still using Photoshop 7 (don’t laugh!) and InDesign CS (not CS2).

I can usually get 3 to 4 years out of a test mule. My old PC test mule lasted about 4 years (at least). I think the G4 might be close to 4 years old now, too. I basically keep using them until I have to upgrade — in other words, until the software I need to run needs more processing power than an old mule has.

Every once in a while, the moon and stars align in such a way that I need to buy two (or, heaven forbid) three computers all around the same time. This is one of those years. I absolutely had to get a new PC to run Vista with the Aero Glass effects. I went with a laptop because I’m trying hard to downsize my office and make it something I can take on the road. A laptop test mule is just the thing. Close it and stick it on a shelf when I’m not using it. Throw it in a bag when I decide to get some work done on the road. Why the hell didn’t I think about that before?

Of course, I do hate the keyboard on the Dell PC — it’s so awkward after years of typing on the PowerBook’s wide open keyboard. And I had to buy a wireless mouse for it, mostly because I can’t seem to find the right track pad drivers for use with Vista and the track pad tracks very slowly, no matter how I set it. But I don’t use the computer every day (and hope I never need to) so it really isn’t such a hardship. And the video on that machine really is incredible. It should be, considering it’s the newest in my stable.

As for the Dell Dimension tower…well, I still have it. It runs Windows XP and as soon as I’m done with these two Windows books I’m working on, I’ll use the laptop’s restore disk to bring it back to factory settings. That’s when I’ll be donating the PC tower, along with its ancient Gateway monitor, to my local library.

And the stars have also told me that I need a new Mac test mule. Why? I’ll need to run Leopard, the upcoming version of Mac OS X, pretty soon now. While I’m not sure whether it’ll run on a G5, I’m pretty sure it won’t run on a G4. And besides, I have to write about Boot Camp and that’s going to require an Intel processor Mac.

So that’s why I need to buy a new Mac — to run the upcoming new stuff.

imageIn keeping with my downsizing plan, I decided that I wanted to get a Mac laptop. After struggling and finally succeeding in understanding the differences between a MacBook and a MacBook Pro, I decided on a MacBook Pro. 15″ monitor, 1 GB RAM, SuperDrive (need to write about iDVD a bit), 100 GB hard disk. This is going to be one hot computer.

Which makes me wonder…will it replace the 12″ PowerBook G4?

Part of me says no: a test mule is a test mule. It sits in my office, turned off, waiting to run software I’m writing a book or article about. It doesn’t get personal data files; its hard disk is often reformatted and restored to factory settings — or at least the current OS.

But I admit that it’s going to be hard to keep using this G4 when I have Core Duo (is that right?) processor laptop with almost twice the RAM and more than twice the hard disk space and processor power sitting around, waiting for me to tickle its keys. I’m actually kind of hoping that I don’t like its keyboard, so I won’t want to use it more than I have to.

But there’s no way in hell that I’m buying two new Mac laptops this year.

We’ll see what happens. Need to make the big purchase first.

Melon Investor Services Online

A poorly designed Web site.

You think that with the money they obviously have to spend, the folks at Mellon Investor Services would have used some real talent to build their Web site. They obviously didn’t.

Sure, it looks pretty, but it’s nearly impossible to navigate without clicking a bunch of wrong navigation buttons. And half the buttons you press spawn a new little window that displays a stop-light graphic and the message that the information is being accessed. The thing that bugged me the most was when I was required to change my pin to a 6-15 character number. It took me four tries to enter a number the system liked, and when I did, the dialog that appeared gave me the impression that I’d screwed up so bad that they were offering to do it for me. I later discovered that the PIN Manager wasn’t a person but a feature of the site that had been unlabeled as such.

Jakob Nielsen of Web usability fame would have a field day with the Mellon site.

I called for help when a feature I was trying to use kept displaying an error message. After various discussion and hold sessions with two different people on two different calls, I was asked to confirm that I was using Internet Explorer. I told her that I wasn’t, that I was using Firefox on a Mac and wouldn’t waste space on my hard disk with a Web browser that hadn’t been updated for four years. She obviously didn’t understand my sarcasm because she told me to “exit” Firefox and “start” Explorer. I repeated that I was on a Mac and if their site didn’t work on a Mac they were alienating a lot of users.

After another hold, I was told that her supervisor could duplicate the error message and that there was probably something wrong with the site.

Duh.

She then suggested that I try another time. By this time (30 minutes after my initial attempt to use the system), I was fed up and ready to hang up. But she had to get one last dig in: “Have I helped you with all your concerns today?”

“No,” I said. And I hung up.

The Miracle of Google

How did we live without it?

We have the power to find virtually anything on the Internet. And that power is called Google Search.

Moments ago, I found a question in my FAQ system (horray!) from a reader of one of my long out-of-print books (darn!). He asked a question about an error message he’d seen (that I’d never encountered) while he was attempting to build additional administrative pages for a FileMaker Pro CDML-published database.

The book he’d bought is called Database Publishing with FileMaker Pro on the Web and it dates back to April 1998. It’s long out of print. If I recall correctly — I’m not at my office so I can’t consult my copy of the book — the book covered FileMaker Pro 3, which was the first version of FileMaker to support Web publishing. FileMaker Pro is now in version 8.5 and no longer supports CDML for Web publishing. CDML was the language and technology that FileMaker, Inc. bought from the Lasso folks to make FileMaker Pro Web publishing work.

So it should come as no surprise that I was unable to answer his question. And unable to replicate it, of course.

But Google has all the answers and it proved it again yesterday. I did a Google search for CDML Error 102 and Google came up with a list of Web pages that discussed the problem. I suggested this as a way for the person with the question to find his answer. (It would be silly for me to repeat what was on those pages when he could just as easily find the same pages himself.)

Google is like this. Have a question? Google it. If you enter the right search phrase, Google will come up with a Web site that answers the question. I think I can report a 90% results rate. And considering some of the questions I come up with sometimes, that’s pretty darn good.

The trick, of course, is to come up with the right search phrase. Googling a single word won’t usually get the results you seek. You need to come up a string of words that succinctly describes what you are searching for. In the example above, if I’d entered FileMaker Error, a much more general search phrase, I seriously doubt whether I’d see any results about the specific CDML error code the reader was getting. If a search phrase doesn’t get desired results, rethink it and try another phrase. In my example, I got the results I was seeking right away, so a second try wasn’t necessary.

With the amount of junk out there on the Web — including, some people might say, sites like this one — we’re very fortunate to have search technology like Google’s available to us. It helps cut through the chaff to get to the important stuff we want (or need) to read.

Searching for Myself

I’m finding myself in the most unexpected places.

I’ve been having a tiny bit of trouble with this Web site lately — it appears that folks are accessing the printable version of these pages more often than the blog version. That got me thinking that Google, which accounts for about 60% of my total hits, was listing the printable version of this site’s pages in its search results.

So to test this theory, I Googled myself.

I didn’t find confirmation of the problem, but I did find this page on the Bookpool Web site: Bookpool: Maria Langer. It lists my Top 10 favorite computer books. I vaguely remember writing something about my top 10 books a while back. It must have been a long while back because none of the books on the list are very recent.

I also discovered electronic versions of my Quicken books online: Maria Langer eBooks. Hope I’m getting royalties for those.

And I’m even in Wikipedia, but just as a stub. I removed an outdated link there.

I guess AllExperts on About.com has no qualms about stealing info from Wikipedia, because the same exact entry is on their page for me.

And there’s a really old picture and bunch of info about me on Ilene Hoffman’s site. (Anyone know if Ilene is still around?)

And, of course, there are a bunch of links to shop for me. Take that any way you like. One even promises “Instant access to Maria Langer and more.” I wouldn’t bother clicking that link if I were you. Trust me: it won’t work.

Strange, the places I turn up.

Of course, this isn’t helping me solve the problem I turned to Google to solve. Back to work!

A Commercial

Maria Speaks Episode 29: A Commercial.

This is my first attempt to create a podcast with GarageBand. Not bad, if I do say so myself.

It’€™s a ‘€œcommercial’€ for Flying M Air’s Southwest Circle Helicopter Adventure. Short, with lots of pictures. A decent example of how a podcast can be created with Garageband on a Mac.

This is my first attempt to create a podcast with GarageBand. Not bad, if I do say so myself.

It’s a “commercial” for Flying M Air’s Southwest Circle Helicopter Adventure. Short, with lots of pictures. A decent example of how a podcast can be created with Garageband on a Mac.

A transcript can be found on the Southwest Circle Helicopter Adventure page of Flying M Air’s Web site.

Use the Comments link here to enter your comments about this podcast.

I’ll probably whip up a how-to article that explains how I did this. Apple’s documentation is pretty crummy. (I guess that’s why I can make a living writing books about Apple software.)