And I ran into the same issues other folks have reported re: migrating data from Palm to iPhone. It was such a hassle, and I'm a software architect, that I wrote up a guide on how to do it.

Hope this helps other people: http://edweirdo.blogspot.com/2009/05/palm-to-iphone-migration-guide.html

My wife and I have been working on on this for a couple days now actually. I ended up importing my contacts into Google Contacts and syncing from there. However, the export/import process was not smooth and I ended up manually entering a bunch of contacts that simply didn't transfer. My wife moved her calendar and contacts from palm into outlook.

For the calendar, she exported from palm in the dba format (which outlook doesn't support), imported the file into yahoo, which then let her export as a csv file. The import into outlook worked okay but she had a bit of cleanup there too (all of her time-based event imported, but none of her date-based events, like birthdays). For contacts she exported as csv and did a ton of cleanup and reformatting in excel before importing into outlook. Once she had a consistent set of data columns in excel, the import into outlook as pretty smooth. Her biggest problem was, in palm, her contact phone numbers (home, work, etc) weren't in the same order for every contact. I think she ended up exporting/importing business contacts separately from personal contacts to alleviate that a little.

Hope that gives you something to work with...

Apple may have got a lot of things right on the iPhone but why do they think it's acceptable to treat something as simple as a battery change as a major service task.

I'll be using my Treo a while longer.

Hope it'll work out for you!

Kind Regards, Jet

I feel people have turned a blind eye to Windows Mobile's clumsiness and slowness. Multitasking is nice, but not really necessary. I was contemplating getting a Treo 750... but after playing with the device for an hour, I gave up and could not convince myself to buy it. I am sticking with my Treo 680.

No, iPhone can't do that but just about any other mobile platform can. So that's hardly a compelling argument to keep PalmOS around.

Talk to me when I can use the iphone to manage my grocery list, maintain my home library card catalogue, my password database and my automotive maintenance and gas logbook.

Palm once dominated this industry. Developers once eagerly flocked to Palm's developer tent to write applications for their platform. Today they are a mere shadow of their former self. They've lost their developer base. Most of the support and development happening on PalmOS today is inertial efforts from existing products.

New development isn't happening, and most of the installed based has migrated to other platforms, particularly Windows Mobile.

When the new platform ships Palm will be starting from a zero sum position. Whether or not developers embrace this OS remains to be seen, and since it will be backward compatible with Garnet applications, developers may see no reason to port their apps to the new framework.

The pressure on Palm to innovative and "wow" the market is great, and judging from the company's recent efforts, namely the Foolio, I don't see them delivering. The idealist in me wants to believe Palm will surprises us all and build a new operating system like no other, but reality and past experience paints a different picture.

And now that Apple has entered this market with an iconic product, the outlook appears even more bleak.

I hope for our sake that Palm does innovate. This industry needs competition. The question is whether Palm can compete with the industry.

I'm keeping my fingers crossed.

And irrelevance is at least somewhat subjective; while I agree that Palm OS is more than a little dated now, I haven't yet seen a device I would even seriously consider as a replacement for my Treo.

I'll have to go back and reread what Colligan said in the conference call--it sounded like he was talking about devices shipping in 2008.

Either way the damage has been done, the platform has faded into irrelevance.