I have a 2002 G4 iMac, which came with Jaguar. After doing an Erase and Install with Tiger, I found that the Software Restore application didn't work for some of my applications. Apple says that if you want to install iMovie, iDVD, iPhoto, Classic, or the programs that came on your Mac, you have to go back to 10.2 and reinstall, then upgrade.
However, by using TinkerTool, you can avoid that. Go to the Finder tab in TinkerTool and select "Show hidden and system files." Then on each of your 10.2 Software Restore disks, go to the .images folder. You'll find a folder of .dmg files, which contain the applications. After mounting, just drag the files inside to the correct folders, and then you have your applications.
I didn't find iPhoto or iMovie on my Software Restore disks, but I found them as a (non-hidden) pkg file in my Jaguar Install Disk 2, called Additional Applications.pkg. Double click, and there they are on your hard drive. I'd recommend resetting the Finder to pre-TinkerTool state, using the Reset tab in TinkerTool, and then restarting.
I just installed Tiger yesterday and choose the "Save the previous system" install (thus, not a regular upgrade). After doing this, you may want to "reclaim" some space used by the "Previous System" folder.
Some files which are kept and are most likely worthless and can be easily erased are the old swap files. In my case, they were using 1GB of drive space. Here's how to get rid of them in the Terminal:
$ cd /Previous\ Systems.localized/Previous\ System\ 1/private/var
$ rm -rf vm
You can probably also delete these without any fears:
In Tiger, the OS's Installer is now queue-able. Under Panther, if you were installing an application with Apple's installer and tried to launch another install, it would give a message dialog and stop.
In Tiger, it goes through configuration, and when you click the Install button, it gives a message stating that it will wait for the current install to complete first. You can set up multiple installs and they will go in order.
[robg adds: Correction -- as noted in the comments, this worked in 10.3, too.]
This isn't really a hint, but I was thrilled to see it when I did. I haven't seen anyone else mention it, so I will: When booting from the 10.4 DVD, one of the tools available (along with Disk Utility, etc) is the Terminal!
Since Apple's made things trickier for using single-user-mode for anything much more than cp or rm, it's nice to have a Terminal available, along with Disk Utility, while you're working on a sick machine.
[robg adds: I only happened to notice this because I needed to use Disk Utility while booted from the DVD, so I figure it's worth a mention...]
The installer for Adobe Creative Suite 2 (CS2) fails with a warning if your Mac has less than 384 MB of RAM. Although the CS2 apps will run slower than intended on Macs with less RAM, the minimum can easily be changed to any amount by changing one line in one file. To begin, insert disc one of CS2 and then launch Disk Utility. From the File menu, create a new disk image from "Adobe Creative Suite Disk 1." Important: Make sure under the Image Format drop-down menu, you choose "read/write," and under Encryption you choose "none". After Disk Utility is finished creating the new image file, you can quit it. Next, double-click your newly created disk image to mount it.
Once mounted, control-click on the Adobe Installer and choose "Show Package Contents." Navigate to /Volumes: Adobe Creative Suite Disk 1: Adobe Installer.app: Contents: Resources: ACS-en_US.ami: Contents: Resources. Along the way, you'll have to control-click and "Show Package Contents" on ACS-en_US.ami. The file we'll be editing is named ami.plist.
I pre-ordered Tiger without fully realizing that it only shipped in DVD format. It lists compatible systems as G3, G4, and G5, but does not list a DVD-ROM as a system requirement. Even on the side of the box. To get around this, I utilized Mac OS X Server 10.3 and NetBoot. (Yes, I have a server at my house because I am truly a geek).
I created a "New Install" image of the Tiger DVD and was able to boot my iMac from the network and install Tiger. Creating the NetBoot image is simple; the Image Utility practically walks you through the necessary steps. I connected a generic DVD-ROM through the USB port, and after a good amount of time, it read the full DVD and made an image. In order to serve the NetBoot image, the server must be running DHCP, AFP, and NetBoot. After the prevoius listed services are configured and running, the image must be activated and marked as default, so that a Mac booting up will latch on to it.
When booting up a network compatible Mac -- I'm not sure where there may be a full list of these, but my Flower Power iMac worked -- holding down the N key after the system startup tone will force the computer to attempt to boot from the server's default NetBoot image. Without DHCP and AFP working, this will fail and you will be left with the flashing "network" icon and a question mark. If it does latch on to that NetBoot image, you'll see the Tiger installer starting up as if you had a bootable DVD-ROM drive in your old computer.
There are lots of variables to this solution that are outside of my submission, such as how to properly configure DHCP, AFP, and the details of the NetBoot service. There are also physical obstructions to consider such as hub or switch connectivity, or simply using a crossover cable, or the simple fact that 99 out of 100 home users don't have direct access to Mac OS X Server! Not a perfect solution, but it worked for me.
Just a quick heads-up ... I had organized my pre-installed Apple applications (Safari, Mail and iChat in a folder called Communications, etc.). When I installed Tiger using "Archive and Install," it did not replace the old apps with their new versions; instead, it put the new apps in the default location (Applications) and left my old apps behind. Launching from the Dock loaded the old versions, so I had to dig around and trash all the old apps.
So, just a warning: if you muck with your Applications folder, you might want to put everything back in place before installing Tiger.
[robg adds: This comes up with every major update (and some minor ones), it seems, so I figured it was worth repeating the caution. This is one reason why I've simply stopped trying to arrange the Apple-provided applications: I let them live where they want to live. Yes, there are ways around the issue using symbolic links, but I decided it wasn't worth the hassles. Every other program I own is installed on a separate Applications partition (barring a few recalcitrant subjects who refuse to run if they're not in /Applications), but I leave the Apple stuff alone.]
This is more like an un-hint. Previously, I had set up a mirrored RAID array per this hint. It all seemed to be working so well, until I tried installing Tiger. The Tiger installer had major issues when attempting to verify the installation disk (my RAID drive). Although well-warned, I did not have a backup (who needs one with a RAID 0 array?).
The fix is pretty straightforward, but somewhat tedious. After the Tiger installer lets you know that everything is hosed, power down the computer. One at a time, disconnect one of the drives and attempt to boot off the still-connected drive. In my case, one drive would boot and was shown in Disk Utility as a "degraded" RAID drive. The other drive would not boot at all.
Pay very close attention to which one is the "good" drive. Confusingly, Disk Utility shows the unbootable drive as the drive in the RAID set and the bootable drive as on a separate volume. The only information that seemed to make sense was the disk location info which tells you whether the drive is in the upper or lower bay.
Once you are satisfied that you know which disk is which, erase the unbootable disk. Then use Carbon Copy Cloner to clone your "degraded RAID disk" to your newly initialized disk. When that is done, boot up on the newly cloned disk, delete the RAID set, then clone back. In my case, just to be sure, I first verified I could boot off the newly created disk, then I unplugged my newly initialized-and-cloned disk, and booted off the Tiger install disk. From there, I deleted the RAID set and re-initialized the drive.
There's some morals here, I'm sure. In my case, I plan to pay better attention to the numerous warnings about attempting unsupported hacks.
The first machine I tried to install my shiny new copy of Tiger onto was my Powerbook G3 Lombard (Bronze Keyboard). That's when I found out that Apple decided to remove my laptop from the list of supported installs.
Now I had only three options: (1) stay with OSX 10.3.9, (2) wait for XPostFacto to support Tiger, or (3) find a workaround. I chose door number three..
I had just spent a large chunk of money on new memory and a larger hard drive only to find out that Apple's newest OS won't work. Some internet searching proved that the pre-releases of Tiger did work with the Lombard Powerbooks, so my belief was that Apple just changed the installer to exclude my favorite computer. I was correct. Here is how I was able to install OSX 10.4 on my Powerbook G3 Lombard.
Attach an external hard drive to the laptop (I have a PCMCIA firewire card so I used a firewire drive, but I imagine a USB drive would work, too.)
I actually tested this to see what would happen. I have a G3 tower with only a CD drive, and I also have a G4notebook with DVD drive. I put the G3 tower into target disk mode (boot with the 'T' key held down), and I then attached the FireWire cable between the two computers, inserted the Tiger DVD, and ran the installer.
The computer rebooted and I installed 10.4 on to the startup drive for the G3. It actually worked ... and 10.4 tried to boot from the G3 hard drive. I shut down my G4 PowerBook and rebooted the G3.