So, Oracle Calendar sync worked more-or-less OK for me under Windows with my old Palm. So let’s try it out on the Mac, with the E2. Should work fine, right? Wrong. Everything installed correctly. Configured stuff, without a hitch. Attempted to hotsync. Barfage. Some sort of “database full” error or somesuch. Google. Turns out the MacOS Oracle Calendar sync stuff won’t work with the E2’s flash memory. Oracle promises an update “real soon now”. ETA on the update is second quarter 2005. It’s now November 2005. Guess I shouldn’t hold my breath, huh?
I subsequently spent a couple hours in broken-conduit-reinstall-palm-desktop hell trying to eradicate the non-functional Oracle Calendar conduits from the Mac. For future reference: After clean install of Palm Desktop, go to
/Library/Application Support/Palm HotSync/Conduits. Back up all conduits. Restore them by copying the backups back into this directory. If HotSync complains about “duplicate conduits”, follow the prompts and HotSync again, repeat as necessary until the problem goes away. Once I figured that out, I could restore my conduits whenever I wanted to without having to reinstall Palm Desktop.
So it looks like I’m going to have to actually switch on the brain here and figure out a new calendaring solution. Or, I could wait for Oracle to release a Mac Sync client that works with the E2. In the meantime I could use my Windows box to sync. But, I don’t want to sync with my Windows box, I want to use my laptop. And truth be told, if I can find an acceptable solution that doesn’t rely on the Oracle calendar sync client, I’d be more than happy. Seems like I need to step back, decide just what it is I want to accomplish, and then figure out the best way to do it.