iPhoto 7.1 (iLife 2008): that red eye is really bad

I like most of iPhoto 7.1, but the more I use it the more I'm appalled by the red eye "correction". Red eye in iPhoto 7.1 is a gray-blue splotch applied to anything with red pigment -- including skin.

You can see the effect in this picture of my son. I set the red eye to max and stamped away. Of course this isn't how you'd use red-eye correction, but it shows the problem. They've messed up the color detection algorithm and the edge-detection (automatic setting) has also failed. It's about as "smart" as a hammer.

Imagine how bad this looks on eyes. Anyone treated this way looks robotic.

Red eye correction in iPhoto 1 through 6 was quite good, so it took me a while to realize how bad it became in iPhoto 7. I'm tempted to imagine an angry developer deliberately sabotaging the product, but I'll put money on incompetence any day.

I would now advise anyone with iPhoto 6 to stick with it. Don't upgrade.

I finally replace my decrepit Palm Tungsten E2 with a ...

Palm Tungsten E2.

Let me explain.

It's been four years since I wrote a review of the original Tungsten E. Three years since aggravation with the flaky T|E (bad switch) drove me to the short-lived SONY CLIE TJ-27. One year and nine months since the CLIE gasped its last and I reluctantly switched to the Tungsten E2 (same bad switch [2]):

...When the last of its styli was lost, then it would go to the junk drawer. I was ready for the end. I cursed each moment with its hell-spawned stylus - a demented offspring of a toothpick and needle. The earth itself had rebelled against that satanic tool -- there were no replacements anywhere. If I did not already despise SONY for their spyware scam, I would loathe them for that stylus.

And yet, I did not entirely welcome the end. I knew that the noble lineage of the US Robotics Pilot was fallow. True, the CLIE was a twisted shadow of its grandfather -- the Vx, and its great-grandfather -- the III, but what better options were there? The much disliked Tungsten E2? (Let us not speak of the father -- the ill-fated Tungsten E -- nor of the bastard IIIxe.)...

That E2, I swore, would be my last Palm device. Something better had to come along ...

Something like the iPhone.

But the iPhone isn't ready. It doesn't meet my minimum set of requirements and version 2 is at least four months away. Too long for my crashy T/E2 and it's too short battery life.

I thought I might buy an HP Windows Mobile, but nobody I trust can tolerate WM. Blackberry definitely, but that would foreclose an iPhone. Blackberry is my fallback option, and I'm not ready to give up yet.

That left Palm. I needed a stopgap that I was pretty sure would work with minimal pain. So I bought another E2.

Sigh.

At least my old chargers, SD card, and styli work with the new device.

I backed up my Palm and Outlook data [1] and just synced. Most everything works, except I have to resync my KeySuite office data to get my work life onboard [3].

So, really, it was pretty painless. The new E2 appears identical to the old one, and they both run Garnet 5.4.7. The new one is definitely faster, but I can't see why it should be. I doubt they have different CPUs.

I should be safe now until February. If iPhone progress is as slow as I expect it to be, I might continue to use the T/E2 as my work PDA.

Footnotes

[1] That's not easy of course, you have to track down the secret location of Outlook's data file: "C:\Documents and Settings\jfaughnan\Local Settings\Application Data\Microsoft\Outlook".

[2] I think even the best Palm of all time, the Vx (ok, so the i500 is a contender), had a bad switch. It tells you something important about Palm that they can't, or won't, spec a on/off switch that lasts two years.

[3] I've given up on any vendor ever delivering a product that would given me an integrated calendar/tasks/notes on the PDA and home, while synching only work related data at the office. It's not easy to do this and I'm the only customer who cares about this.

Windows 2003 Server for the home

Microsoft's Windows Home Server supports their excellent remote access software and provides an integrated backup and media server solution. Note it runs on a variant of the rock solid Windows 2003 Server OS, not Vista. So it's the only variant of XP Microsoft actively sells, though they aren't marketing WHS very hard - yet.

In the meantime Apple's Time Machine can't backup up to a (slow) USB drive hanging off an Airport.

I don't like it when Microsoft makes things I want. Windows Live Writer and Windows Home Server are annoying me.

Reverting from Office 2007 to Office 2003: MAPI32.DLL vs. MSMAPI32.dll

When my XP boxen go to heck, they do it all at once.

One one front I'm a defeated geek. I had to abandon hope for my "possessed" (really, it is) corporate Dell Latitude (XP SP2 +) -- I'm now wiping the drive and starting over. This is the first time in years of fighting with Microsoft's OSs that I've actually capitulated up and wiped a drive. There was something eating away at the process that authenticated me as an administrative user, with lots of curious side-effects.

The other problem seemed simpler. Access 2007 is a dud, and the rest of Office 2007 is nothing to write home about. It was time to revert a Windows 2003 server to Office 2003.

Easy, I thought. Just uninstall, restart to be safe, install Office 2003 Pro and then apply Office SP 3.

Wrong. I was getting "MAPI32.DLL is corrupt or the wrong version" error messages.

I hate those. They bring back bad memories of running Outlook and Eudora in the old days. MAPI32.DLL was one of Microsoft's tools to kill the competition.

I followed the old trick of locating and renaming MAPI32.DLL. No joy.

Turns out the error message is a fraud. The real problem is another file (emphases mine)

2. Locate and then open the following folder on your computer:
C:\Program Files\Common Files\System\Msmapi\1033
3. Right-click the MSMapi32.dll file, and then click Rename.
Note The file (Msmapi32.dll) that you are renaming differs from the file (Mapi32.dll) that is mentioned in the error message.
4. Type Msmapi32.old, and then press ENTER to rename the file.
5. Start Outlook 2003.

I want to cry. Really, the wrong file name in the error message? Oh, and the kb article is wrong. The bug isn't with the beta version of Office 2007, it's with any version.

That worked, but on Outlook startup I got two messages something like this:

ordinal 7867 cannot be found in mso.dll

Try googling on that one! Nothing I could find.

Outlook then said some app was messing it up and offered to repair the problem. That worked.

Now to go back to spend the rest of my day trying to restore my primary XP workstation. So much for my planned vacation day tomorrow.

People used to wonder why I didn't like Microsoft products. I don't get those questions any more. I read recently that some preposterous number of IT execs are actually considering replacing some of their XP machines with OS X or Linux. I assume they're venting and bluffing, that seem a true mission impossible.

On the other hand, if I were doing a small business startup, I'd be building around OS X workstations running XP in a VM. Use OS X whenever possible, but have XP around to run Office 2003 and any vertical apps that are essential. Whenever XP misbehaves, just delete the VM and stick in a new one.

PS. I checked what happened to the original MAPI32.DLL I'd pointlessly renamed. It was dated 3/25/2003. A new one was created of a slightly different size dated 2/17/2007. I also found yet another MAPI32.DLL dated 12/10/2002. It's not too early for a drink is it?

Update 1/4/07: Despite the above, I still couldn't SEND email. I use Outlook primarily from my laptop, so I let this problem fester for a while. Today I removed my Exchange configuration from that instance of Outlook and deleted an old pst file I was using. I then restored the Exchange connection. Now I can send, but I notice that 'cached exchange mode' is no longer available.

Kindle: DRM only - no PDFs

The obvious knock on Amazon's Kindle is the DRM. If Amazon goes away, so do your books.

This isn't that big a deal for me. We long ago ran out of room for books, most books I buy I give away. I only keep a few, and those I could continue to buy as paper books.

Most of my books are ephemera. I'd need a house for books alone if I kept them all.

The bigger objection, for me, is that the Kindle can't read PDFs or any other eBook format:

Daring Fireball: DUM

...With iPods, while the iTunes Store is the only source for DRM-protected content that iPods support, you can easily fill your iPod with any popular non-DRM audio format other than WMA. Kindle supports a few other formats than its proprietary .azw, but the only way to use it for its main purpose — as a digital reader for popular mainstream books — is via its own proprietary DRM-protected format. I.e., Kindle actually is what ignorant critics have claimed regarding the iPod: a device designed to lock you in to a single provider of both hardware and digital content. You can easily and happily use an iPod without ever buying anything from the iTunes Store; without Amazon’s DRM-protected content, a Kindle is the world’s worst handheld computer...

I agree with DF. More than the DRM, it's the closure to any other format that marks this as a gift horse in need of dental inspection.

Update 11/19/07: DF might have been unfair. It's true they don't do PDF (a big negative), but Kindle can accept .DOC, txt and a few other formats.

On the other hand, you can't use it during takeoff and landing, or when you're stranded on the runway. It's electronic, remember? This alone would rule out the Kindle as a travel companion. Back to the paperback.

Costco: where Apple's discontinued iPods go

TUAW also reports they have pretty good warranty service:

5 reasons to love Costco during the gift-giving season - The Unofficial Apple Weblog (TUAW):

...Their slightly out-of-date iPods. Costco provides a reliable resource for anyone looking to buy older-generation iPods. They clearance them out with excellent prices and good availability. Costco currently carries iPod Nanos and Videos (which still work with free video out!), as well as the newer Classics, and Touches...

Microsoft's free memory test utility

I had no idea Microsoft provided this free memory test utility. I guess I'm too much in the OS X world these days. Many thanks to "enthusiast" for the pointer to this a set of similar test utilities.

Microsoft Online Crash Analysis - windiag

The Windows Memory Diagnostic tests the Random Access Memory (RAM) on your computer for errors. The diagnostic includes a comprehensive set of memory tests. If you are experiencing problems while running Windows, you can use the diagnostic to determine whether the problems are caused by failing hardware, such as RAM or the memory system of your motherboard. Windows Memory Diagnostic is designed to be easy and fast. On most configurations, you can download the diagnostic, read the documentation, run the test and complete the first test pass in less than 30 minutes.

To run Windows Memory Diagnostic, you must reboot your computer with the disk or CD-ROM on which you installed Windows Memory Diagnostic in the drive. After the reboot, Windows Memory Diagnostic will load and its interface will appear. After loading, the first test pass will begin, using the default standard test suite, and continue until complete, unless Windows Memory Diagnostic is either paused or exited. Once the first test pass is complete, Windows Memory Diagnostic will begin a second test pass using the same settings as before. Windows Memory Diagnostic will continue to run test passes until you exit...

I'm looking at this because my "possessed" (really, it is) corporate Dell Latitude (XP SP2 +) just gave me an error message on a huge file copy that was supposed have been fixed in Windows 2000:

You May Not Be Able to Copy Large Files on Computers That Are Running Windows NT 4.0 or Windows 2000

...Cannot copy [filename]: Insufficient system resources exist to complete the requested service...

Yes, this could be due some mysterious corporate monitoring software; many corporations are layering loads of cr*p atop an already unstable XP/antivirus environment, thereby taking XP into new realms of emergent behavior.

My money though is on flaky hardware. I'll try that Windiag and the Dell test suite that comes with their restore DVD.