So, despite wanting to get my copy of Leopard on the day of release (sad Mac fanboy that I am), I waited some days to install it. Some of these were because my offsite backup was offsite, and I didn’t realise its power supply and cable were also offsite
Anyway, I began the upgrade process by upgrading a PowerPC PowerBook G4 which already had a developer pre-release copy of Leopard installed. Reassuringly this installation failed, leaving the machine in an unusable state.
Buoyed with enthusiasm by this experience (well, ok it’s somewhat traditional for the release build to fail to install over a developer build), I proceeded.
Having by this time got the first bug reports on Macintouch and news of the Keychain/login update I cautiously turned on auto-login on my machine so that I didn’t need the password to get in (theoretically). I also downloaded the update. I backed up my Intel machine and ran the Leopard installer. I bravely selected the ‘Upgrade’ option rather than ‘Archive and Install’, but I was feeling lucky and wielding a backup.
The machine rebooted (alas I did it overnight so I missed the install movie) and I was in Leopard.
So, fire up Safari and… no network. Bummer.
Install the login/keychain update and reboot. Well, at least the network has come back!
So, what to do? Check out the new Finder features. Launch some Apps. Upgrade some Apps that report upgrades are available. Try AppleWorks, which quits on launch (with the recent items panel open). Eventually this is resolved some days later when I read on Macintouch that the AppleWorks Users Group suggest:
1. Quit AppleWorks and switch to the Finder.
Delete the Recent Items folder at Macintosh HD > Users > yourname > Documents > AppleWorks User Data > Starting Points.
2. Re-launch AppleWorks. AppleWorks will create a new (and empty) Recent Items folder and should then run reliably under Leopard.
Other things I noticed: