Gee, thanks. That tells me so much. I would have never understood the problem without this detailed explanation.

At least it appeared over and over, as though with repeated exposure I’d eventually get the point.

Let me begin by saying that I don’t know anything more about the new product(s) Apple will be announcing on January 27 than anyone else outside the company. (And I can’t get over how often people ask me what I know about future Apple products, as if Apple would share their trade secrets with me but not the rest of the world!) The only thing I can say for sure is that I’ve had discussions with two publishers about the possibility of writing a book on the next iProduct, whatever it is and whenever it’s released, so it’s a fairly safe bet you’ll see my name and the name of the new whatever-it-is sharing a book cover later this year.

But last night while I was lying in bed trying to fall asleep, I was thinking about the various rumors I’ve read, the paint-spattered “Come see our latest creation” invitation to the upcoming event, and the fact that no one, to this point, has proposed anything I’d consider a killer application for a product that’s presumably something like a large iPhone/iPod touch or a MacBook without a keyboard. So far, I haven’t read any descriptions of what the thing might do that make me conclude I really need to spend another however many hundreds of dollars on a device to supplement my iPhone and MacBook Pro—something that’ll do things neither of those devices can do, and do them so well that I can’t live without it. (Other than, you know, in the sense that I can’t live without money, and I make money by writing books about technology.)

As all these ideas were bashing around in my head, I thought of Wacom’s Cintiq, which is a graphics tablet with a display underneath the surface, so the artist doesn’t have to choose between looking at the pen and looking at the screen. And I thought, hmmmm, there’s a handheld device with a wide-screen display and touch-sensitive surface, no keyboard, hooks up to a Mac or PC, and costs $1000. Where have I heard those specs before?

So this is what I’m thinking:

• One of the major selling points (not the only point, by any means) of the new iProduct will be its painting/drawing capabilities. Which means…
• Apple will introduce some brand new iApplication that runs on the device and does for graphics what GarageBand does for music creation—puts high-quality results within easy reach of non-professionals. But that would make the most sense if…
• A version of said application also runs on your desktop computer—though probably just Macs, like most of Apple’s other apps. So, in addition, I’m guessing…
• The iProduct could be used for painting/drawing in either a stand-alone way, with the new iApplication, or as an input device for an existing program on your computer (Photoshop or Illustrator or whatever). Needless to say…
• This’ll all work wirelessly, unlike the Cintiq. And…
• A stylus will be optional. (Hello, finger painting!)
• If Apple does use the name “iPad,” I think it’ll apply to the software, not the hardware.

So, if this all came true, you’d be getting a thing with considerably more capabilities than the Cintiq for (I imagine) about the same price. This all seems utterly logical to me, and I’m rather surprised that none of the gadget blogs and rumor sites I’ve read have been playing up this particular scenario. But since I have nothing to lose by being wrong, I wanted to go on record with my predictions, such as they are.

Now, I have zero artistic skills or ambitions, and personally, I don’t think this set of capabilities would interest me much regardless of how easy and snazzy Apple were to make the software. I can’t imagine watching movies on such a thing (my flat-screen TV would get jealous), and I’m not a gamer, so those capabilities (which will surely also be present) won’t attract me either. I’d read books on it, sure, and surf the Web from the sofa, but I can already do that on my iPhone. So I’m still waiting to find out what it is about this hypothetical device that would induce me to buy it if I weren’t doing so for entirely professional (and tax-deductible) reasons. We’ll know soon enough!

So I was trying out Twitter Tools, which can do interesting things like creating a tweet when you post on your blog, and creating a blog post when you post a tweet. Both of which are potentially useful things. From the FAQ in the Read Me file:

What happens if I have both my tweets posting to my blog as posts and my posts sent to Twitter? Will it cause the world to end in a spinning fireball of death?

Actually, Twitter Tools has taken this into account and you can safely enable both creating posts from your tweets and tweets from your posts without duplicating them in either place.

Yeah, except it didn’t. As soon as I turned it on and set up the various options I wanted, two things happened. First, it downloaded my last 20 tweets and made blog entries out of them. (Not at all what I wanted, because some of them are quite old…I was assuming it would start with my next tweet.) And then, having discovered 20 new blog entries, it created 20 new tweets, one for each. (That’s what the Read Me explicitly said wouldn’t happen.) So they were totally duplicated—highly annoying. Nor did this stop after the initial batch—my next tweet, to apologize, was also turned into a blog post that was immediately re-tweeted.

I also discovered another missing feature: when Twitter Tools creates a blog post from a tweet, it just truncates the tweet arbitrarily and turns that into the title, but with no verbiage like “From Twitter…” (comparable to the “New Blog Post” it puts in tweets). So, another big minus.

So: Twitter Tools = FAIL. And sorry for all the birdy poo. Now to uninstall…

Almost exactly four years ago, on October 24, 2003, Apple released Mac OS X 10.3 Panther. On that same day, the very first ebook in the Take Control series appeared—my upgrading guide, Take Control of Upgrading to Panther. Little did I know then that this little publishing experiment, undertaken by most of the TidBITS staff and a handful of other talented authors and editors, would be so successful as to eventually produce the majority of my income. But today, less than 24 hours after Apple finally announced the shipping date of Mac OS X 10.5 Leopard, I’m pleased to report that my 14th title in the series is now on sale: Take Control of Upgrading to Leopard: Early-Bird Edition.

When I wrote my second Upgrading book, Take Control of Upgrading to Tiger, I naturally started with what I’d written about Panther, added some stuff, removed some stuff, and generally updated everything to be accurate under the new system. But this time I wanted to go way beyond that. Leopard is a big, big release with lots of serious changes; I wanted the Upgrading book to reflect that and prepare users as thoroughly as possible. So in addition to massively reworking the text to cover all the changes to the Leopard installation process, I pulled in some material from my ebooks on backups, maintenance, and troubleshooting. Now I provide detailed instructions on getting your Mac in tip-top shape, complete with an excellent backup, before inserting that Leopard DVD—and I think the extra steps up front will lead to much happier installations later.

Of course, there was a tiny problem: ideally, you’d do all that preparatory stuff days or even weeks before you get your Leopard DVD, but I can’t actually release the full book, with all its top-secret information about the ins and outs of Leopard installation, without violating my NDA. So we decided to create two versions of the book. The Early-Bird Edition, which you can buy (for $10) and download today, has all the background information you need to get your Mac ready for the upgrade, but leaves out all the information I’m not allowed to reveal (which amounts to quite a large portion of the book). The full edition will become available the instant Leopard goes on sale in North America (that’s 6:00 p.m. Eastern Time next Friday, October 26). Anyone who has already purchased the Early-Bird Edition can simply click a link on the cover of the PDF to go to a Web page where they can download the full version for free. And then they can skip (or skim) about 50 pages of text and get on to the actual upgrading process fairly quickly. Of course, if you wait until next Friday or later to make your purchase, you’ll simply get the full version, which is a superset of the Early-Bird Edition.

Now then…what’s crazy to me about all this is that I initially wrote (both versions of) this book back in February, when Apple was still saying Leopard would be released in the spring. It went through our whole editorial and technical review process way back then. In April, when Apple announced a delay until October, we just put the project on ice. This summer I picked it up again, and updated the manuscript with new information from each new beta version of Leopard. Yesterday, as soon as Apple made their announcement, I had to tweak a few things in the Early-Bird Edition to correspond to the latest truth, but even so, we were organized enough that the PDF was available for sale within hours. Between now and next Friday, I very much hope to see an even more recent version of Leopard than what I’ve been working with, and should it contain any significant changes, I’ll work those into the final text as well. The result should be our most thorough and up-to-date upgrading guide ever! If you’re planning to install Leopard, I think you’ll find this ebook to be immensely helpful.

Among the many interesting announcements from Apple yesterday was an expansion of .Mac’s capabilities, but with the same price as before. And there are lots of groovy new things, such as the Web Gallery and the capability to use .Mac with your own domain. Unlike most people, my reaction to these changes was, in a word, “Ugh,” by which I mean “I now have to spend many days updating my book Take Control of .Mac to reflect the current truth.” Yeah, I know, boo hoo.

However, what most caught my attention was the change in storage limits. Previously, .Mac came with 1 GB of storage for $100 per year, and you could increase it to either 2 GB (for $50 extra per year) or 4 GB (for $100 extra per year). Now, at those same prices, you get a base level of 10 GB, which you can increase to either 20 GB or 30 GB. And it seems a lot of people are thinking, “Wow, a 10x increase in space at no extra cost! Great!” But I’m thinking: not great.

As before, that space has to be divided among Mail, .Mac Groups, and iDisk—and, of the iDisk space, a lot of that will presumably go toward sharing all your photos and videos and iWeb sites. You can use whatever’s left for sharing files or backups. But here’s the thing. Apple is still way behind the times; they should have done that two years ago and made yesterday’s upgrade another order of magnitude greater. At least. Compared with other Web/email hosting providers (because really, that’s basically what .Mac is), .Mac still gives you a fraction of the typical storage space at a higher price. For example, Dreamhost will give you 145 GB of storage (which, by the way, increases by 1 GB each week) in their cheapest plan, which is $9.95 per month—just $20 per year more than .Mac (and you can decrease that to $7.95 per month by prepaying for two years).

My particular area of concern here, though, is backups, because I’ve written a lot on that subject, and am at this very moment in the process of updating Take Control of Mac OS X Backups to say a lot more about, among other things, online backup services. If .Mac stacks up poorly against Web hosting providers, the comparison with online backup providers is even bleaker. Mozy gives you unlimited backup storage space for $5 per month. And CrashPlan is right behind—you get 50 GB for $5 per month, with additional gigs at 10 cents each (so, 100 GB would be $10 per month, and so on). That’s exactly the sort of space:price ratio where Apple should be. Previously, they were at 1 percent of that, and now they’re at 10 percent. I find that kind of insulting, as though I’ll see all the pretty graphics (yes, they are pretty) and forget that I’m still being overcharged and underserved.

Speaking of that 1 percent figure…I find it interesting that the new iMacs released yesterday can include up to 1 terabyte of disk space. Clearly, Apple expects you to fill up that space with all your excellent new media. Equally clearly, they expect you to put no more than 1 percent of it (10 GB)—or, maybe, 3 percent (30 GB)—online. That’s weird and sad. I say this even realizing the realities of internet bandwidth (sure, it’d take months to back up 1 terabyte over a DSL connection). That’s no excuse to let your competitors leave you in the dust.

All this is not to say I don’t find .Mac useful. I do find it useful—enough so that I keep renewing every year (even though I also have to supplement it with other services). And I’m happy that it’s gotten considerably more useful in the past 24 hours. But let’s not kid ourselves: this is one area in which Apple is still far, far behind the curve.

My article in last week’s issue of TidBITS, Stewing Over Safe Sleep, generated an awful lot of feedback. Most of it was of the “Yeah, that was really stupid of Apple” or “Thanks; now I know how to solve an annoying problem” varieties. Some of it was along the lines of “How could anyone not love safe sleep?” or “I’m not seeing 49-second delays on MY machine” or “It probably doesn’t really matter if you move your computer while the RAM is being cached to disk” or the simple and elegant “You’re an idiot.” Well, thanks one and all for sharing your thoughts, constructive and otherwise.

Two particular threads of discussion, though, are worth a more detailed look.

Hibernating Only When Necessary First, Greg Nicholson sent me a clever script he wrote (to replace the one I showed in TidBITS) that’s significantly smarter. Greg pointed out that there are certain situations, such as a long flight to China, in which one might be much more likely to want the default Safe Sleep behavior. So his script, which he runs every 10 minutes with cron, checks the battery life. If it’s over 50%, it turns off hibernatemode (as my script does). But if the charge is less than 30%, it turns hibernatemode back on. Very spiffy, and I wish Apple would have built something like this right into Mac OS X. You can, of course, tweak the percentages and so on to your liking. Here’s (my slightly modified version of) Greg’s script:

#!/bin/sh
MODE=`/usr/bin/pmset -g | grep hibernatemode | awk '{ print $2 }'`
LEFT=`/usr/bin/pmset -g batt | grep Internal | awk '{ print $2 }' | awk -F % '{ print $1 }'`

if [ $LEFT -lt 30 ] && [ $MODE != 3 ] ; then
  {
     echo "Less than 30% remains" >> /var/log/system.log
     echo "setting Hibernate mode 3" >> /var/log/system.log
     `/usr/bin/pmset -a hibernatemode 3`
  }
elif  [ $LEFT -gt 50 ] && [ $MODE != 0 ]; then
  {
     echo "Greater than 50% remains" >> /var/log/system.log
     echo "Setting Hibernate mode 0" >> /var/log/system.log
     `/usr/bin/pmset -a hibernatemode 0`
     `rm /var/vm/sleepimage`
  }
fi

Greg noted that since the script requires root privileges, you need to add the following to your sudoers file:

ALL ALL=(ALL) NOPASSWD: /usr/bin/pmset -a hibernatemode 3
ALL ALL=(ALL) NOPASSWD: /usr/bin/pmset -a hibernatemode 0

An easier way to achieve that effect would be to put the cron job in your system crontab, if you feel comfortable doing that.

Dealing with an Unencrypted “sleepimage” file Correction (08-Aug-2007): I see I munged some of my facts here earlier, so I’ve rewritten this paragraph to reflect what I currently believe to be the truth.

Second, the issue of encryption came up. It turns out that using hibernatemode values of 5 or 7 (the prescribed values for those using Secure Virtual Memory) don’t actually result in your sleepimage file being encrypted—in fact, it’s just the opposite. If you have Secure VM turned on and use 5 or 7, your encrypted RAM is apparently decrypted while being written to the sleepimage file. So if you’re using Secure VM and want your sleepimage file, too, to be encrypted (which you should), stick with values of 1 or 3 (3 being the default).

Now, in the real world, this fact probably makes little practical difference for most people, most of the time. Even if you don’t encrypt your VM, it’s not a given that any particular password (or other sensitive data) will actually be in RAM when it comes time for your computer to sleep—it might be, or it might not, depending on a long list of details about how particular programs do things, how recently you logged in, what applications you have running, and so on. And also, the risk is certainly greater for power users who enter an administrative password multiple times per hour than people for whom that is a rare occurrence. Even then, the contents of your RAM is cached to that unencrypted disk image only when your computer goes to sleep and only when the hibernatemode setting is at its default (3) or “always hibernate” (1). And even then, the fact that potentially sensitive stuff is sitting on your hard disk in a readily readable format only causes problems if someone gets access to your computer and knows how to find this data. So, like I say, not a problem for most people, most of the time.

If you’re concerned about this, though, DO follow my advice to turn of Safe Sleep. But go a step further. Instead of using

sudo rm /var/vm/sleepimage

to delete the RAM cache, use the secure version of rm, srm, and use the -m flag for a 7x overwrite rather than the default 35x overwrite:

sudo srm -m /var/vm/sleepimage

The command will take a long time to run, but the disk image holding your RAM contents will be safely overwritten. Note that you only have to do this the first time. If you’ve set up a script (as discussed previously) to check regularly to see that hibernatemode hasn’t turned itself back on, having a simple rm in that script will do the trick. The reason? When hibernatemode turns back on, Mac OS X recreates the sleepimage file immediately. But initially, it’s blank. It doesn’t fill up with the contents of your RAM until your machine tries to go to sleep. If your script runs and deletes the (blank) image before then, nothing incriminating will have been in that file.

I truly hope this all gets sorted out in Leopard.

For the past umpteen years, I have dutifully installed every new version of Microsoft Office for Mac that the company has put out. I expect I will continue doing so indefinitely. I’m not particularly fond of Microsoft as a corporation for all the usual reasons, and I’ve found plenty to complain about in every piece of Microsoft software I’ve used. Nevertheless, I use Office (and particularly Word and Excel) every single day, as probably 90 percent of my income requires it in some fashion. When new versions appear, I fantasize that certain bugs that have existed since the mid-1990s might finally be gone, and they never are, but at least a few things generally get better.

Since I don’t particularly expect that any of my long-standing complaints will disappear in Office 2008, I’ve been looking forward to it for primarily one reason: it’ll be a Universal Binary, and should therefore run faster on my Intel-based Macs than Office 2004 does. In other words, I’ll be glad when Office 2008 ships only to the extent that it should scratch one certain long-standing itch; otherwise, I would have been reasonably content to keep running Office 2004 for years to come.

I say all this to put into context my remarks about today’s announcement that Office 2008 will not, as the company previously claimed, ship in the second half of 2007 but will instead ship in mid-January 2008. As a user, this slippage in ship dates is barely worth noticing. Its net effect on me will probably be next to nil. As a Mac journalist, I find it highly significant that a company the size of Microsoft can’t hit a release window that’s six months wide even when they set that target a mere six months in advance, and I think that’s worth giving the company at least a mild tongue-lashing. But really: I don’t care about the slip. It’s a pity, but no big deal.

What I do care very much about, though, as someone who uses words for a living, is the language Microsoft chose to use in the press release they sent out announcing this delay. It is, truly, a delay: a difference of (depending on how you interpreted “second half of 2007″) anywhere from two weeks to six months and two weeks. And most of the news sites that reported on the delay described it as such. But Microsoft themselves did not use the word “delay.” They didn’t mention that they’d previously announced an earlier date. They didn’t say they were sorry. Instead, they used standard weaselly marketing language to make it sound like they were announcing a virtual non-event, and perhaps even to subtly suggest that anyone who wanted to think about it differently doesn’t care about quality.

Here is the exact text of the press release I received:

Office 2008 Coming January 2008

Microsoft’s Macintosh Business Unit (Mac BU) today announced that Microsoft Office 2008 for Mac will be available in the US in mid-January of 2008 (planning for Macworld), with global general availability in the first quarter of 2008. This was a business decision based on the Mac BU’s commitment to deliver a high-quality product.

“Our number one priority is to deliver quality software to our customers and partners, and in order to achieve this we are shifting availability of Office 2008 for Mac to mid-January of 2008,” said Mac BU General Manager Craig Eisler. “We’re successfully driving toward our internal goal to RTM in mid-December 2007, and believe our customers will be very pleased with the finished product.”

As the Mac BU moves closer to the product launch, Microsoft will share more details about features and exact timing.

More information at the Mac BU’s Mac Mojo blog at http://blogs.msdn.com/macmojo

Now then…what Microsoft could have said in their press release, instead, is this:

“Office 2008 for Mac, which we previously said would ship in the second half of 2007, has been delayed until January 2008. We ran into some unexpected problems, and we now realize we can’t get this out as soon as we said. We apologize for any inconvenience this delay may cause. We hope our customers will find the final product to be worth the wait.”

See how much better that is? It’s easy: just plain English. No weasel words, but no protracted pseudo-explanations either. Just: “Look, stuff happens. It happened. We’re sorry. Here’s the new plan.” And yet, with those few words, you acknowledge that there’s a difference between what you said and what you’re doing, that that is in fact a bad thing that you wish hadn’t happened, and that you understand why people might be a bit upset with you.

Why is that so hard? Why can’t a company bring itself to admit any fault, however minor, to say they feel badly about something? It’s OK, really. Your customers will forgive you. What customers should not forgive is marketing speak. I don’t cry over spilled milk. I cry over “The erstwhile contents of the glass have been redistributed in a more horizontal fashion. This was a business decision based on gravitational forces. Information on forthcoming moisture containment strategies and potential new sources of dairy products will be made available by mid-January 2008.”

A couple of days ago, Take Control Books released version 2.5 of my ebook Take Control of Running Windows on a Mac. Even though the version number didn’t jump all the way to 3.0 (meaning this is a free update for people with version 2.0 and 25% off for people with version 1.x), version 2.5 was a massive revision. I added new sections on VMware Fusion and VirtualBox, took out the section on Q (which is now pretty much irrelevant), and provided up-to-date info on the latest versions of Parallels Desktop and Boot Camp. And that’s just the biggest changes—tons of smaller stuff was tweaked too. If you have any interest in running Windows on your Intel-based Mac, this ebook should tell you everything you need to know.

Because things are moving so fast in this area, I predict that at least one, and more likely two, additional updates to this ebook will occur later this year. And I suspect I’ll start getting into more detail about actual usage scenarios. For example, even though I’ve now got two Intel-based Macs, I still haven’t gotten used to the notion that I can now run practically any software whenever I want. When I read about something that’s PC-only, I still have that old habit of disregarding it with a grumble, and I really have to train myself to stop. The world (of software) is my oyster now—almost any Mac, Windows, or Unix program out there will run happily on my Mac—and it will take me some time to fully come to grips with this new sense of freedom.

And, I’d just like to say that my new 17″, 2.4 GHz MacBook Pro—fully loaded with the high-res screen and 4 GB of RAM, of course—is an awfully nice way to run any and every operating system. It’s my first new laptop since my 1 GHz TiBook (ca. 2002), and I’m really digging it.

Among the things I’ve been busy doing over the past month (besides, you know, getting ready to move to Paris and not updating any of my Web sites) has been finishing my latest ebook: Take Control of Troubleshooting Your Mac. As usual, it’s $10, comes with free minor updates, and has a free excerpt available for your perusal. I’ve already, of course, written about maintaining and backing up your Mac (in fact, the three titles together make a nice bundle at only $24—cheap!), but actually solving problems, rather than merely preventing them, was the big missing piece.

I get a lot of requests for Mac help. Some of it comes from friends and family; even more comes from people who have read my various books and articles. And I don’t mind offering a bit of assistance when I can, but as I’m perpetually tied up with a zillion things, I can’t always devote as much time as I’d like to solving other people’s Mac problems. But now, you can get a virtual Joe-in-a-box (book?), because this book more or less describes the algorithm I’d use to solve your problem. Well, yes, I took some liberties, because I was under strict instructions to make this a reasonably short book, and because my own troubleshooting technique is probably more of an art than a science. But still: for a great many problems, this’ll get you as close to a solution as I could in person.

Needless to say, it’ll also expand over time. We’ll add more problems, solutions, and techniques. But even as the book stands now, it should apply equally to past, present, and future versions of Mac OS X. It’s a handy thing to have around before problems occur, so if you’ve ever wished you had a little help available when your Mac goes kerflooey, now’s a great time to add this to your library.

When I turned 40 in January, I declared that the next 10 years would be my Decade of Wealth and Influence. (My 30s were, at least in theory, my Decade of Risk. That’s a story for another day.) Six months in, I can’t say I’m making much progress in the wealth department, but much to my surprise, at least some people seem to think I’m influential. I’ve been named one of MacTech’s 25 most influential people in the Macintosh community—I even get my picture in a printed magazine. Weird. My blurb in the article, featuring a now somewhat outdated bio (I really should update my “about” page a little more frequently), is on this page.

The article, cribbed as it was from (an earlier version of) my description of myself on this site, doesn’t say why it is that people think I’m an influential figure. And I find the whole thing curious, in a way, because even though I write an awful lot about Macs, I don’t really write with the goal of changing anyone’s mind about anything. I help people to get their work done and solve problems, and I report some news, but in terms of offering actual opinions, I haven’t said much beyond “you really really really need good backups.” Even Interesting Thing of the Day, which now has well over 150,000 feed readers, is merely expository in nature, not hortatory. Not that I’m complaining or anything; it’s just that I honestly don’t know who I’ve influenced to do what. But, you know, I’m OK with being famous for being famous.

Anyway, I’m in really good company: four other TidBITS personalities are on the list, along with numerous other Mac movers and shakers I respect a great deal. I’m honored to be counted among the Mac illuminati.