Tag Archives: Macintosh

It’s Too Cool

Posted on by
1

I rediscover the cool things I can do with my Mac.

One of the reasons I got into the business of writing about computers is because I thought that the things you could do with computers were very…well, cool.

I got my start with Macs back in 1989 with a Mac II cx. My previous computer had been an Apple //c and the Mac was a huge step up for me. One of the reasons I wanted it was so that I could start a BBS. I needed a hard disk and a bit more processing power than the Apple //c offered. Back in those days, the Mac IIcx was hot. It was one of the first Macs to offer a color monitor option and it ran at whopping 16 MHz. I taught myself everything I needed to know about that machine and had a BBS up and running within a month. I also learned enough to get a per diem job as a computer applications instructor, so I quit my “day job” to pursue a writing career. I like to say that that computer changed my life. It did. If I hadn’t bought it and learned my way around it so quickly, I would never have developed the expertise to change careers.

Anyway, back in those days, shareware was a big thing. There was all kinds of shareware out there and much of it was pretty cool stuff. I distinctly remember the sound editing software I used — I believe it was called SoundEdit — which enabled me to record sounds and edit sound waves. Macs had “sound cards” built in from Day 1, so sound was always part of the Macintosh experience. Everyone had their own custom sound effects and used MacInTalk to get their Macs to read.

I did other cool stuff, too. For a while, I thought I wanted to learn how to program, but I soon realized that it wasn’t worth the bother with so much good shareware and freeware out there. But somewhere along the line, I got pressed for time just trying to make a living. The time between books got shorter and shorter and I developed new interests such as motorcycling and photography, and when we moved out west, horseback riding and flying. Although I still spent the same amount of time sitting in front of my computer, that was mostly work time. I didn’t get to play around as much as I used to. The “cool factor” of the computer seemed to fade away. It was a tool for getting a job done and that job happened to be to write about using this tool. It didn’t help that I somehow became an “expert” on productivity software like Word and Excel. I’d hopped on the Web publishing wagon early on and had a book about PageMill Web authoring software that did very well. But when Adobe killed PageMill, they also killed my book. So the path back toward a cool aspect of computing was removed and I didn’t have time to cut another one.

Things haven’t changed much. I’m sill busy writing books — I think I did six or seven last year — and still interested in other things — primarily flying. But I’ve managed to crack open a door to start writing about cool things again. An eBook I’ve got lined up should be very interesting. And it has me thinking about other topics, other cool things I can do with my computer.

That’s how I stumbled upon Nicecast. Nicecast, published by a company named Rogue Amoeba, is software that enables you to broadcast from your Macintosh onto the Web and it’s very cool. To be honest, I’d seen Nicecast at MacWorld Expo last January and had thought about it as a way for the local radio station to get started in Web broadcasting. KBSZ-AM is a low budget station that isn’t particularly high tech. They have a wonderful studio with a computerized broadcasting setup, but their knowledge of computing is limited and some of their equipment is very old. In fact, Pete’s wife Jo still uses a Mac IIci (the next model after my old IIcx) to do word processing and other stuff! But Pete does surf the Web via modern PC in search of information to include on-air and to keep abreast of what’s going on in the world. Anyway, I’d seen Nicecast at Macworld and had brought back a brochure for Pete. But it didn’t seem like they’d make the hardware investment to get it all up and running. You’d have to sell a lot of ads at $2 each to get started.

A few weeks ago, I discovered a Web site that has live broadcasts from various air traffic control (ATC) locations throughout the world. It’s called LiveATC.net. You click a link for an airport and a small file is downloaded to your computer. A moment later, iTunes launches (if you’re on a Mac; I don’t know what it does on a Windows machine) and the live ATC feed plays through your speakers. You can listen to ground control at JFK directing 474s around the airport or the tower at Boston clearing AirBuses to land. Live. How cool is that?The Home page at LiveATC.net mentioned that they were looking for feeder sites. All you needed was a computer running Windows or Unix, a scanner, some relatively inexpensive software, and a connection from the scanner to the computer. Although I have a Windows PC, I don’t usually turn it on unless I’m writing about Windows software. But my Mac OS X Macintosh runs Unix “under the hood.” Perhaps I could get it to work on my Mac. Wouldn’t that be a hoot! So I e-mailed the Webmaster and told him about my setup. He responded within an hour with a friendly message that told me it could indeed work. Some more e-mail crossed between us and I had a list of possible hardware and software to get the job done. I put the hardware on my Christmas Wish List and started looking into the software.

That’s when I stumbled onto Nicecast again. And this time, I downloaded it to give it a try. I figured that if I could get it to work with my weird network setup, I could get it to work anywhere. I had to reconfigure it to use a different network port than the default 8000 (which was in use by my Web server software) and then had to reconfigure my Airport wireless station to send requests to the new port to that computer (my production machine). Then I began broadcasting directly from my iTunes playlist. About 15 minutes of setup and it works flawlessly. Not bad for $40 worth of software. I shouldn’t have any trouble at all getting it to work with the scanner.

Then I thought about recording things that I could play on my radio station. I went in search of additional software that would enable me to use my PowerBook’s built-in microphone to record voices and sounds. I wound up with two packages that seem to complement each other nicely: Audio Hijack Pro, which is a $32 product by Rogue Amoeba, and Audacity, which is a freeware product distributed by SourceForge.net. Audio Hijack is cool because it can “hijack” other programs and record their sounds. This makes it possible to record a soundtrack from a game or a video presentation, as well as from the Mac’s built-in sound sources. Although you can apply special effects, you can’t edit the sounds. That’s where Audacity comes in. Although it can’t hijack sounds from other programs, it can record from Mac sound sources and it has editing capabilities. In fact, it reminds me a lot of SoundEdit, the shareware program I used years ago on my first Mac.

I played with all this last night. I recorded my bird, Alex, saying some of his usual things

So that’s where I stand now. I have the tools to record and broadcast. But I don’t have the time to set anything up. (What else is new?) But maybe one of these days, you’ll tune into Flying M Radio and be able to hear these blog pages.

Books of 2004

Posted on by
Comment

I bring readers up to date with the titles I churned out over the past year.

I realized, in writing my last blog entry, that the last book I’d mentioned finishing on these pages was my Mac OS X 10.3 Panther: Visual QuickStart Guide last October. Don’t think for a minute that I’ve been idle since then.

It’s been just over a year and, believe it or not, I had to consult a list of the titles I’d put out to see just what I’d been up to. I just couldn’t remember them all. Here they are:

Microsoft Office Excel 2003 for Windows: Visual QuickStart Guide was the most recent revision of my Excel for Windows book. Not much new in the way of content because there’s not much that Microsoft can already add to that feature-packed program. It came out in December 2003.

QuickBooks Pro 6 for Macintosh: Visual QuickStart Guide was a brand new title for me (and Peachpit). I’d proposed it early in the year, when I was looking for work and it took several months for them to say yes and come up with a contract. By that time, I had other work lined up. (Feast or famine.) The book underwent a lot of content changes as I wrote. For example, it was originally going to include payroll coverage, but since payroll is done with a separate program bundled into QuickBooks and the future of the bundling was questionable, we decided to drop it. (Frankly, I think payroll is so confusing that a whole book could be written about it, but don’t think I’m volunteering.) The book came out in May 2004 and is doing surprisingly well. So well, in fact, that Peachpit wants me to revise it for the recently-released new edition.

Quicken Premier 2005: The Official Guide is the sixth revision to my original Quicken Official Guide. It was finished in June 2004 and published in August 2004.

Creating Resumes, Letters, Business Cards, and Flyers in Word: Visual QuickProject Guide was a brand new title in Peachpit’s brand new Visual QuickProject Guide series. The series is great for beginners or people with computer phobias because it shows every single step in a process, with callout lines and numbered instructions. It makes a VQS look like a technical guide for MBAs. And it’s in full color! It’s 160 pages long and costs only $12.99. A great deal. The only thing I don’t like about it is the title — it’s way too long! It came out in September 2004.

Creating Spreadsheets and Charts in Excel: Visual QuickProject Guide is another brand new book for me. This one offers the basics of working with Excel spreadsheets and charts in a format anyone can understand. It’s eight chapters took me eight days to write and lay out. (That’s not the record. My record is a 350-page book that I knocked off in 10 days back in 1993. Of course, I didn’t do layout for that title.) I think it’s a great book and I’m extremely pleased with the way it came out. Like the Word book, it’s cross-platform. It came out in October 2004.

Microsoft Word 2004 for Macintosh: Visual QuickStart Guide is the latest revision to my Word for Macintosh book. It has a bunch of new stuff inserted throughout the book and a brand new chapter covering Word’s new Notebook Layout view feature. I finished it two days ago and it’ll go to the printer today. I expect to see it by the first week in December and, of course, it’ll be at Macworld Expo.

So in the course of a year, December to November, I finished six books. Of these, three were revisions and three were brand new titles. (That’s not a record. My record is 10, set a number of years ago, and I hope I never do that again. Talk about burnout!)

In addition to writing all those books, I also managed the Wickenburg Airport’s FBO (for a short time, anyway), did helicopter tours in the area, got a part-time job flying at the Grand Canyon, and wrote a handful of articles. So anyone who says I have an easy life obviously doesn’t have the big picture.

I’m not complaining — certainly not! I usually take a week or two off between books and spend that time catching up on things like bills, surfing the ‘Net, shopping, and writing in my blog. If I had a helicopter, I’d be flying, but I’m between ships right now and grounded. This week, I’m trying to write three or four articles that I owe various editors. I knocked off one yesterday and started a second one. I’ll finish that and write at least one more today. Tomorrow, my brother, his wife, and my sister are coming in for a week, and my mother and stepfather are showing up on Tuesday for a week, so I’ll spend time with them.

Then it’s back to the salt mines for me. Mac OS X 10.4 Tiger is on its way and I have to revise the existing book to turn it into Mac OS X 10.4 Tiger: Visual QuickStart Guide. I always have the first Mac OS book out in stores and I’m not about to ruin my record this year.

After that, it looks like a QuickBooks revision, but if I’m lucky, they’ll let me write one or two more Visual QuickProject Guides. I proposed a bunch of titles, and they finally seemed to like one of them. Cross your fingers for me. I’m also writing an eBook about iBlog 2.0 for Spiderworks. I’ll probably finish that sometime in December, if I can find time for it between my work on the Tiger book. I’m also working on a book about the Grand Canyon with a photographer and hope to have that ready for publication in May. It’ll be nice to have a book that doesn’t need revising every one or two years. (The Canyon doesn’t change much.) And I’ll always be writing articles. Informit.com likes my work and I like writing for them. FileMaker Advisor also wants me to write for them, but I’m always having trouble coming up with fresh ideas for them, so we’ll see how I do.

That’s it in a nutshell: the past year and the next four to six months. Busy, busy, busy.

Another Chapter Done

Posted on by
Comment

I revise book number 59 or 60 — I’ve lost count again.

These days, I’m hard at work on a revision to my Microsoft Word for Macintosh book. Officially titled Microsoft Word 2004 for Macintosh: Visual QuickStart Guide, the book covers the latest and greatest version of Word for Macintosh.

The book I’m revising (which covers Word v. X) is only about 300 pages long. It has a companion book that covers more advanced features. For this edition, I’m rolling the two books into one big fat book. That’s what I did earlier in the year for the Windows version of the book (which covers Word 2003). That book is 450+ pages long.

Revisions are not as easy as they sound. Books in the Visual QuickStart Guide series are extremely screenshot-intensive, with 3-6 images per page (on average). The tiniest little change in Word’s interface requires that any screenshot of that interface element must be redone. Since Microsoft changed the way the ruler looks, for example, any screenshot that includes the ruler — basically any shot of a screenful of text — must be redone. Rather than try to determine what elements have changed and run the risk of missing something, I just redo every single screenshot in the book.

Of course, not only do I write the book, but I lay out its pages using InDesign software. When I’m done with a chapter, I create a PDF and e-mail it to my copy and production editors. They print out the pages, mark them up, and mail them back to me. I then make changes as they requested, finalize the files, and send them to the production person on CD or via FTP. The book is in print 3-4 weeks later. The whole process, from my start to book in stores usually takes 6 to 8 weeks. But as soon as I’m finished with one book and have taken a week or two off to clear my head, I’m starting work on the next book.

I’ve got revisions down to a science. For this book, I’m starting with the InDesign files for the Windows version of the book, which has most of the content I need, organized in the right order. I’ve printed out an outline of that book’s contents with a few Macintosh-only features inserted in the appropriate areas. For example, Chapter 13 will be a brand new chapter covering Word’s NoteBook Layout View feature. Then I open a chapter file and go through it, page by page. I edit the text for correct Mac OS terminology and instructions. I replace the screenshots, removing some completely while adding new ones. I modify all the figure references and caption numbers as needed. (This is, by far, the most tedious part of the revision job.) When I’m done, I have a finished chapter, all ready for review and edit.

I try to knock off a chapter a day. Sometimes, when the chapter is short, that’s easy. Yesterday’s chapter was only 20 pages. But Wednesday’s chapter was 28 pages. That may not seem like a big difference, but it is. This will be a 20-chapter book, so I’ll have it done in 20 working days. If I get two short chapters in a row, I’ll try to do them both in one day to speed things up.

The deadline for this book is roughly around Thanksgiving time. I’d like to get it done sooner, since I have out-of-town guests coming in that week. More important, my Mac OS X book is due for revision shortly. That book takes priority over all others. If it’s ready for revision before I’m done with Word, Word will go on the back burner until I’m done.

I wrote somewhere that I sometimes feel like a machine. When I work on revisions like this one, I do. But I’m a well-oiled machine with the parts worn in just right to get the job done smoothly.

My Computer Setup

Posted on by
2

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”

Posted on by
Comment

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.