Configuring Outlook 2003 to use Contacts for email in an Exchange Server environment

I recently had to migrate to a new machine using old Office software (don’t ask), so I had to rediscover how to fix a common problem with Outlook 2003.

When you first start Outlook 2003 in an Exchange server environment it’s not configured to look for email addresses in your Contacts folder.

If you right click on your Contacts icon you’ll see, somewhere in a mess of tabs, one that says “Outlook address book”. In it you’ll find a checkbox “Show this folder as an e-mail Address Book”, but it will be grayed (greyed) out and uncheckable.

Turns out, as described here, you need to …

1. Tools/E-mail accounts
2. Choose “View or change existing directories or address books”
3. Click Add …
4. Click Additional Address Books

You should then see an option to add your Outlook Contacts. I suspect, however, you can’t add any old Contacts folder from a PST file, it must probably be the Contacts folder you synchronize with Exchange server.

Once you do this if you return to Outlook the check box will no longer be gray and Contacts should be checked.

Windows Live Writer: moving between machines (yech)

I love WLW, but it has an Achilles heel. On XP it’s pretty much impossible to move your configuration data between machines.

Of course that’s true for almost all of  Microsoft’s products, but we expect better of WLW. On the other hand, I hear rumor there’s a configuration migration service built into Vista (some OS), so maybe it works fine there.

I found out about this after I switched machines. I have the old data of course, but I’ll just migrate manually. It would be nice if the WLW were to build in a migration utility, but for now here are two somewhat useful references:

• Backup your WLW Settings: a post about this utility, but the utility is quite old and hasn’t been updated
• Migrate Windows Live Writer data: reveals location of the files, unfortunately key data is in the foul pits of Hell, aka the Windows Registry.

There’s some accessible data in ..

• C:\work\My Weblog Posts (path will vary)
• C:\Documents and Settings\[userid]\Application Data\Windows Live Writer

You might imagine you could copy your older WLW posts and drafts to C:\…\My Weblog Posts and WLW would be able to browse and search them, but that doesn’t work. It can open them if you double-click on them, but there’s a cache/index missing somewhere.

Happily, if you copy our old posts and drafts into the new WLW folders (ex: C:\work\My Weblog Posts) and delete the XML cache files WLW will rebuild them and find all your draft and new posts.[1]

[1] I got messed up here because when I forgot to point the “My Documents” folder to my personal file store. So WLW was only looking in My Documents. I copied the data from My Documents then pointed My Documents to c:\work then launched WLW.

Update 6/17/09: Corrected my mistake about posts recovery.

Why is Safari 4 so slow, when the beta was fast?

Safari 4 feels much slower than the beta version. I often run into typing problems on my MacBook -- I type far ahead of the cursor when working with Blogger's Gmail's rich text editor.

I never ran into that with the beta version.

Did Apple mess something up?

Probably.

Deep dive into the Palm Pre

An escaped image is giving techies a deep look into the innards of the Pre. Turns out the PalmOS is based on OpenEmbeddded Linux which in turn incorporates OpenZaurus which is descended from the 1990s Sharp Zaurus PDA.

And you thought the PalmOS was built new in 2 years. Not so. The genius of the thing is how much GPL software it contains.

The Pre continues to please, with positive reviews from Mac folk like Scott Gruby. Maybe I'm not the only one who needs a phone that excels at basic PIM functions (see Andy, I'm not always a market of one). I think Apple made a mistake blowing off the entire personal productivity domain.

One big caveat however. I fear the cloud. The Pre is a cloud phone -- it syncs with Google, Facebook and other Cloud properties. That's a problem for me.

Nisus Writer Pro 1.2

Three years ago I wrote a review of Nisus Writer Express. I recently updated to last November's Nisus Writer Pro 1.2 so I figured I'd supplement my original review.

In general, I'm a contented user. I wish I could use it more, but most of my printed writing is done with Word on an XP box. I use it for limited writing on OS; I've never really given it an acid test.

Over the years I've had two medium and one big issue with Nisus.

The first medium issue is that earlier versions didn't manage Word .DOC images well. Nisus would open the document, but when it saved the documented the images were not compressed. In particular, Nisus did not implement even PNG compression. I don't know if this is still a problem, but I've never seen mention of a fix.

The second medium issue is that even at NW Pro 1.2 you still can't save in Open Document Format.

The major issue is that the 10.5 update broke Nisus Writer Express and Nisus didn't provide a free fix. NWE was the only significant Mac app I use that didn't work in 10.5. It smells like Nisus was doing something programmatically fishy, and so they ought to have provided a free patch.

On the other hand Nisus uses RTF as a native file format, so Nisus documents are more likely than any other word-processing format to be readable in 10-15 years. The Style implementation (Pro version) is simple and excellent (aside: spit upon the Beast), and now that moving Navigator/TOC entries moves document blocks is a very reasonable outliner as well. It's the closest thing to an integrated wordpressor/outliner I've seen since FullWrite Professional. (MORE, bless its heart, was fundamentally an outliner -- though it was a better word processor than most.)

One of the strengths of OS X is that we have choices about word processors. Microsoft Word of course, but also Pages, Nisus Writer (Express and Pro), Mellel, and about 3-4 others (honorable mention to MORE's reincarnation - OmniOutliner). Nisus Writer's RTF support, style sheets, performance, and outliner features mean it's worth a close look by anyone who can avoid Word.

Making sense of Google's user created "My Maps"

I've long been frustrated by the awkward design of Google's personalized May Maps. The service feels crude, and I'm unsure how long the data will stay around.

Today I decided to try and learn a bit more. I recommend the introductory video (a very young sounding narrator) and I really recommend "Browse the directory". Turns out that's not, as I'd imagined, a directory of maps (why should it be?). It's a directory of Map tools that make "My Maps" much more useful.

I'd like to see what I can do in terms of Minneapolis St Paul trails, and maybe get some use of the msptrails.org domain I registered a while back.

Update: Well, I gave it a good try, but it's still a toy. For example, there's no way to edit a map you've created; you can't revise or extend a line. I'll wait until Google puts a bit more energy into this one.

Migrating my MacBook to a 500 GB drive

I'll try to update this with a bit more detail later, but I want to write this minor post while the details are fresh.

I upgraded my MacBook Pro from a 120GB Fujitsu to a 500 GB Western Digital Scorpio Blue drive (totally bare from Amazon, just the drive in a plain brown box). I followed the directions provide by Apple, this is not a hard procedure.

I bought the 5000 rpm drive because I mostly care about reliability, low vibration, low temperature, and capacity. From what I read in this older MacBook the 7200's effective performance boost is very small and some 7200 drives have quite a bit of vibration (seems idiosyncratic).

I won't repeat Apple's directions, except to say they left off one little bit. I think this set of directions is more complete.

Briefly then ...

1. I considered creating a disk image clone on my PPC iMac then using firewire disk mode on the MacBook to clone the image over. Andrew, who is generally reliable, warned me of some issues related to using a PPC to clone an Intel Mac drive (endian?).  I had a very cheap 2.5" USB enclosure I'd used with a 80GB drive; it worked perfectly well with the 500 GB drive. I did discover that Intel and PPC Macs use different partitions for their boot drive. Intel Macs default to GUID partitions, PPC default "Apple partitions". So maybe that's the difference Andrew warned of. I did all the partitioning and cloning from my MacBook.
2. I used Bombich Software: Carbon Copy Cloner [1] to clone from my MacBook. It took about 2-3 hours; it would have gone faster if I'd remembered turn off spotlight when cloning.
3. Apple's directions omit one key step and tool. You need a T8 Torx driver to remove the metal shell that's wrapped around the disk. Maybe if you buy the replacement drive from Apple it comes with the shell? Anyway, if you have a Torx driver it's an easy task, but if you don't you're stuck.
4. Apple's not kidding about the metallic foam shield that's glued on the RAM cover you remove. It's not easy to get the shield back on, you need a non-magnetic plastic card to push it down so you can get the metal band back into place.

The first boot seemed to take an eternity. It was much longer than usual. I think the systems was adjusting to the new drive. Once it started it rebuilt some caches then completed. I almost gave up -- so be patient.

So far so good. The drive is quieter than the original Fujitsu and it feels more responsive (could be imagination, it's a 5,000 not a 7,200. I might put the original in my mother's Mac Mini, though if I'm going to bother with that hard to service job I might as well buy another 500 GB drive.

Now I can carry more media around, and I can play with more virtual machines...

[1] CCC is free and comes from a trusted developer. It now incorporates ads. Since users spend a lot of time checking up on the CCC process this is a fantastic ad platform. I donated $10 via the web site. I rarely use CCC, so I try to make a donation each time it works for me.