Reasons it’s good to be a co-founder of Apple

Number one: free 65-watt power adapters. I think I speak for PowerBook owners everywhere when I say it’s too bad that this courtesy doesn’t extend to all PowerBook G3 and G4 owners; certainly my experience with the dreaded M7332 adapter suggests that many of us might have benefited, not just the Mighty Woz.

I don’t begrudge him his power adapters, though. Since every home computer that I’ve ever owned (//c, SE/30, 7200/90, Pismo, TiBook, MacBook Pro) and a few my friends had on which I learned computers (][e (and IIe platinum!), //gs, PowerBook 170) has benefited from his work (and in the case of my friend’s //gs, actually been signed by him!), he probably deserves free Apple hardware for life.

Hell freezes over, again: Windows on Macs, with Apple’s help

NY Times: Apple Allows Windows On Its Machines. Apparently Apple pays attention to its user community. Following the hack contest to get Windows running on the new Intel Macs that ended with a $13,000 prize and a successful hack, Apple has announced beta availability of Boot Camp, a free download that enables installing Windows XP on Mac OS X and switch-booting.

Looking at the Boot Camp page, it’s a little bit fiddlier than the average grandmother would want to mess with, but still really straightforward for a utility of this kind. The utility helps you to partition the hard disk (which is required for this kind of switch boot) and burns a CD with Windows drivers for the appropriate Mac hardware. Interesting note, though, that the Windows XP install might not find the right partition and could accidentally delete your Mac partition… After that, the switch-boot mechanism appears to be exactly the same one that enabled booting into OS X or OS 9 back in the early days of Mac OS X Public Beta and 10.0: hold down the option key at start time and choose the appropriate partition.

And I think it will perform the same function for new Mac OS X users: it will provide them with a safety net so they can gradually transition off Windows and onto their new machines. The question is, will it be good for Microsoft, good for Apple, or good for both? For Microsoft, it probably means that Virtual PC will never be ported to Intel Macs—though running multiple virtual machines is a very different usage scenario from switch booting, it may not be a common enough scenario to justify the investment. But Microsoft may get a lift in Windows XP license sales. And Apple should see a few more Windows users buying their hardware, lured by the prospect of totally cool, totally compatible hardware.

Happy Mac text geeking

Via MacOSXHints, a great article about Cocoa’s text bindings and the Amazingly Cool Things you can do with them—like, implement a standard keystroke to wrap a piece of text in some HTML formatting in every Cocoa text field in your whole system. Also a list of default bindings as shipped in Mac OS X, and a list of all the usable selectors that you can combine with keystrokes to get some really cool things to happen.

Hmm. Or, the downside of Mac on Intel.

I have a very brief report on the quality of the PowerPC emulation layer (Rosetta) built into the new Intel based Macs, like the MacBook Pro. It’s good—it’s very good. I haven’t found any native Mac OS X apps that didn’t run correctly with it.

Except. There is a small catch, which is that plug-ins that are not written to support Intel based Macs won’t load if an application is started in Intel native mode. Apparently the Rosetta functionality only applies to the main process, not plug-ins. This means that productivity plug-ins like Keyword Assistant in iPhoto and (apparently) Sogudi, the search enabler for Safari, won’t work until new Intel versions are released.

Ah well. This has been a small price to pay. There have been Universal binary versions of other important Mac applications, such as MarsEdit 1.1.2 (with which I’m blogging this) and the public beta of NetNewsWire 2.1 that was released today. Now all I need is Office and I’m good to go.

Honestly, though, there have been enough pleasant surprises with the machine that I’m not going to complain at all. For one thing, Spotlight and the Dashboard work and are really fast. For another, so does Quicksilver. I finally see why Merlin thinks it’s the best thing since sliced bread. It was unbearably slow to invoke or operate on my 1GHz, 512 MB PowerBook G4. Amazing what an extra half-gig of memory, 0.83 GHz of processor, plus a new processor architecture will do.

Let’s Talk System 7

While I’m on tenterhooks about my new Mac hardware waiting at home, a quick shout to System7Today, a site about using your pre-G3 Apple hardware to its fullest extent. (Pointer via the Cult of Mac blog at Wired.)

The site makes the cogent point that nothing much useful happened in the Mac OS world between System 7.6.1 and Mac OS X (with, of course, the major exception of early Mozilla builds). I mean, if I recall correctly, the only reason they moved to Mac OS 8 rather than System 7.7 was a marketing decision that Apple needed to put the years of vaporware around Copland behind them. But at the time there was such hype for all the new features as they were released: QuickDraw GX! OpenDoc! Cyberdog! Open Transport! The Control Strip! All of which of course are deader than doornails now.

But I grew up with that OS. My first computer related job involved managing some Macs at NASA Langley, which I upgraded to System 7. I was so thrilled when I could run System 7 on my first Mac, an SE/30. I made the PowerPC jump in 1995 to a PowerPC 7200/90, which ran systems 7 through 9, and held onto it for five years until I got my PowerBook G3 (FireWire) The G3 ran Mac OS 9, dual-booted the Mac OS X public beta, and then ran Mac OS X 10.0 through 10.2. The G3 lasted three years until I got the 1GHz G4 TiBook that is my main machine today, and has so far been the only Mac on which I have never booted into Classic. Of course that won’t be an option at all with the MacBook Pro.

Life’s little ironies

I got a phone call from Lisa a few minutes ago that my MacBook Pro arrived this morning, one day ahead of the promised ship schedule and six days ahead of the originally projected delivery schedule. I’d love to be really excited about it but I can’t right now—my head is so stopped up that I can’t really think about it until I get home.

I’m also doing everything I can to keep my expectations realistic about how the experience will be with this machine, so I’m linking without comment to varying user reports at Macintouch about extra noise and possible display and networking issues. But there appear to be many more positive than negative reports about the machine, so I’ll throw out a gratuitous link to a set of MacBookPro unboxing pictures, for those of you that enjoy that sort of thing.

Can there be happier words…

…than “Apple Store Shipment Notification”? I don’t think so. As I predicted, Apple is jumping the gun on my anticipated ship date by a good five days. My MacBook Pro is currently in FedEx’s system (though not picked up yet) and scheduled to arrive by Thursday.

Of course, Thursday is the busiest day of my week, so I probably won’t be able to do a detailed unboxing report until the weekend. But still… yay.

Update: Apparently new MacBook Pros (MacBooks Pro?) come from Shanghai, China (at least according to FedEx’s pickup records). Who knew?

Give me a PowerPC Mac mini

Well, the Intel-powered Mac mini is out, released as part of a home-focused set of Apple product announcements yesterday. And my only criticism is that they’ve eliminated the current PowerPC based models from the channel. I understand the reasoning—pricing them at a discount, as has been done with the PowerPC powered iMacs, would lower the price point too far to allow the channel any margin. But I still want one of the original series of Mac minis, even after our purchase of a MacBook Pro (anticipated arrival date still March 22).

Why? It comes down to Classic. At first I didn’t cavil too much at the thought of losing access to programs that run under Mac OS Classic aka Mac OS 9. There is nothing that I run on a daily basis that requires Classic, and that’s been the case ever since the release of Microsoft Office for Mac OS X.

But I’ve been a Mac user for 16 years, and there are quite a few programs that I ran in the first 10 of those years that require Classic that I’ll miss an awful lot if I can’t access them again. Some, like the Talking Moose, have made the jump to Mac OS X versions; for others, like most multimedia CD-ROMs (e.g. the Laurie Anderson Puppet Motel or Peter Gabriel’s media titles), it’s already too late. But there are a host of programs, including the LucasArts Star Wars and Indiana Jones games, Crystal Quest, and even the Mac version of MORE that will be inaccessible to me after this platform transition.

So it’s impractical, but I think that having continued access to the Classic environment in a small form factor machine would be really useful. It appears that Amazon still sells the original Mac minis; I may have to decide about putting my money where my mouth is.

Remote configure your Tiger Mac through the command line

I was trying to configure my Mac’s built in Remote Desktop sharing last night through the command line. The RDC client, which is built into every Tiger Mac, was prompting me for a password when I attempted to connect using an open source VNC (screen sharing) client from my PC. So I did some research and found some very interesting information about configuring Mac OS X’s Remote Desktop (ARD) client from the command line. The kickstart command line tool referenced in the Apple KB article is included in the Remote Desktop Client and is therefore in every 10.4 Mac as well as some earlier systems.

The cool thing about it is that kickstart enables you to remotely activate and deactivate ARD connections. So as long as you leave SSH enabled and you have administrative privileges, you can tunnel into an SSH command line session on your Mac, sudo kickstart with the appropriate settings, and turn ARD on, then get the screen of your Mac and do your thing. As the discussion thread points out, this works even for Macs that have no physical screen attached, like a PowerBook with a broken LCD or a headless Mac Mini.

You can do even more with two more command line utilities included in ARD, networksetup and systemsetup, which allow you to do things like configuring the network settings and other “control panel” level settings.

I like this so much that, in combination with a dynamic DNS solution, I might throw out the rapidly aging Timbuktu client we bought to help my mother in law troubleshoot her system.

T Minus MacBook Pro: One month and counting

Following up on my earlier note, the elapsed time to delivery of my new MacBook Pro will be close to 5 weeks. Ordered on February 16, it’s currently scheduled to ship on March 17 and arrive on March 22, even with 2-day shipping. So we’re one month out. The only comfort is that the Apple Store seems to habitually pad delivery dates so as to deliver only positive surprises, so I’ll probably get it sooner.

Frustrating, especially since the battery isn’t getting better on my current PowerBook. It falls off a cliff and shuts down with 58-60% remaining now, meaning effective battery life is only 1-2 hours.

Elapsed time to MacBook Pro: 3-4 weeks

I knew I should have ordered the new Intel-based MacBook Pro when it was announced. I put the order in tonight and saw “estimated ship: within 3-4 weeks.” Sigh.

Backing up: my PowerBook G4 has been pretty good over the last few years, but it’s starting to show its age. In addition to the fact that Dashboard and Spotlight cause some significant slowdowns, and the spinning beachballs of doom, there’s the broken hinge, which is slowly causing the two halves of the case around the screen to separate. And the MacBook looks to be a significant step up from the 1GHz model.

But I definitely shouldn’t have waited until the day its availability was announced.

Time to buy a Shuffle?

My 512 MB USB memory stick has gone missing; I’ve looked all over for it. But I’m not sure I care after seeing the news from CNet that Apple has lowered the price of the 512 MB Shuffle to $69 (and the 1 GB to $99).

I don’t really think I can get one, of course, right now; but it’s still a suddenly compelling value proposition. Who needs a screen? It’s a memory stick with previous-next and a headphone port. What more do you need? Besides, it would be good to have a backup for those long flights when my regular iPod’s battery goes.

The only catch: 1 GB of memory is not designed for people who rip losslessly. I think I could fit about 100 minutes of music on it. (Update: I missed reading a review that points out that iTunes can automatically downsample lossless files for a particular iPod to 128kbps AAC. I never knew iTunes could do that!!)

But what’s the message in the new 1 GB Nano? I guess that people like the small form factor enough to want to have access to the screen even if they only have a few songs on it. And that it’s important to get new models out to customers so that the market gets even more saturated before the competitors catch up.

My experience ordering iPhoto books from Apple

Yesterday in passing during the keynote I alluded to Apple’s need to improve its process for ordering iPhoto books. (If you don’t know what an iPhoto book is, check out the information on Apple’s site.) I realized that I never told the story of my own experience getting one of these books made—partly because I didn’t want to tip off the recipient to what I was doing. Hopefully my experience will help others who are considering giving these books as gifts.

First, the concept: my sister and I had kicked around the idea of making something for our parents this year, but with her still in grad school many of our ideas were too labor intensive. Finally we hit on something that was achievable by Christmas: she would filch photos from my parents’ albums while she was at their house for Thanksgiving, scan them, and mail them to me on a CD. I would compose a book in iPhoto from the best of them and have it made in time to have it under the tree at Christmas. No problem, right?

Heh. It turns out I failed to anticipate two things: hidden criteria on image resolution that would prevent the book from being published, and the time it took for Apple’s printing services to notify me of problems.

First point: unless your images are 2 megapixels or more, they won’t be printed as a large-size image in an iPhoto book. You can get away with printing some lower res images in smaller layouts, like a four to six photo per page layout, but not as a single large image. iPhoto will warn you if there is a resolution problem on your page by flagging the page with an exclamation point icon. Unfortunately, it doesn’t advise you that Apple’s print service will refuse to print the book if one of the photos fails the resolution test, and doesn’t prevent you from submitting the book with exclamation points.

I included a lower-res photo that was the only image I had of my mother’s grandmother in the first draft of my book and submitted the book with no warning other than the exclamation point. I then hit the road for a week. When I returned home, a week before Christmas, I checked the order status site and was startled to see my order had been cancelled. I had no email notification that there was a problem.

With visions of no Christmas present for my parents dancing in my head, I tried calling Apple’s support line, who referred me to an online form. I submitted a question asking why my book had been rejected. I then deduced that the exclamation point page was the problem, substituted another photo, and resubmitted the book. The next day I got an email indicating that a book order had been cancelled, but providing no order number.

At this point I had a headache from dealing with the problem. I submitted another question asking for clarification on which order had been cancelled, verified that the second book was still processing via the online status page, and waited. Two days later, I got another email, indicating that it was the first order that had been cancelled. It still gave me no specific guidance that it was an image resolution problem, but at least I had enough information now to rest assured that my book was going to ship.

And fortunately it did. It was a beautiful book and was a real hit with my parents. But the process of creating it contributed significantly to my pre-holiday stress.

Final advice to anyone planning to order an iPhoto book: take those exclamation points seriously, give yourself six weeks before you need the book in case any problems arise, and make sure you specify in any support requests to Apple that you want them to reference your order number in any replies.

I plan to order another book once I get iPhoto 6 so I can get some of my favorite photos collected in a portfolio and will report on the process for that book when I put it together.