Benches Mac desktops

12

Migration from PPC 10.4.11 to iMac 10.6.2 OS 9 ...

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

I am about to use migration assistant to move my old PPC files and apps to a new 27" iMac running 10.6.2. I'd like to do everything, files and apps and settings and I plan on using a firewire cable and target mode.

The old computer is 10 years old...still running great! But when it was new it ran OS 9 and there is a lot of that old stuff still on the computer (OS 9 system, various arcane apps like Conflict Catcher--remember that one?!). Do I need to try to clean those out before I migrate, or will 10.6.2 be smart enough to deal with this?

Thanks!

PS, what an amazing thing this 27 inch iMac is!!

12 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    You'll have to filter them out sooner or later.

    Use CarbonCopeCloner to bring over just what you want and leave them behind or move the lot and weed thru the cruft later - 6 of 1....

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Most likely you do not want your old PPC-only applications. They should be updated to universal binary versions first, if possible, or find replacements that are universal binaries.

    With such a mixed up old system I would be quite careful about migrating anything other than your personal data, files, and folders. Quite a lot of old stuff just isn't compatible any longer and can raise havoc on a new and well functioning system. See the following:

    A Basic Guide for Migrating to Intel-Macs

    If you are migrating a PowerPC system (G3, G4, or G5) to an Intel-Mac be careful what you migrate. Keep in mind that some items that may get transferred will not work on Intel machines and may end up causing your computer's operating system to malfunction.

    Rosetta supports "software that runs on the PowerPC G3, G4, or G5 processor that are built for Mac OS X". This excludes the items that are not universal binaries or simply will not work in Rosetta:

    Classic Environment, and subsequently any Mac OS 9 or earlier applications
    Screensavers written for the PowerPC
    System Preference add-ons
    All Unsanity Haxies
    Browser and other plug-ins
    Contextual Menu Items
    Applications which specifically require the PowerPC G5
    Kernel extensions
    Java applications with JNI (PowerPC) libraries

    See also What Can Be Translated by Rosetta.

    In addition to the above you could also have problems with migrated cache files and/or cache files containing code that is incompatible.

    If you migrate a user folder that contains any of these items, you may find that your Intel-Mac is malfunctioning. It would be wise to take care when migrating your systems from a PowerPC platform to an Intel-Mac platform to assure that you do not migrate these incompatible items.

    If you have problems with applications not working, then completely uninstall said application and reinstall it from scratch. Take great care with Java applications and Java-based Peer-to-Peer applications. Many Java apps will not work on Intel-Macs as they are currently compiled. As of this time Limewire, Cabos, and Acquisition are available as universal binaries. Do not install browser plug-ins such as Flash or Shockwave from downloaded installers unless they are universal binaries. The version of OS X installed on your Intel-Mac comes with special compatible versions of Flash and Shockwave plug-ins for use with your browser.

    The same problem will exist for any hardware drivers such as mouse software unless the drivers have been compiled as universal binaries. For third-party mice the current choices are USB Overdrive or SteerMouse. Contact the developer or manufacturer of your third-party mouse software to find out when a universal binary version will be available.

    Also be careful with some backup utilities and third-party disk repair utilities. Disk Warrior 4.1, TechTool Pro 4.6.1, SuperDuper 2.5, and Drive Genius 2.0.2 work properly on Intel-Macs with Leopard. The same caution may apply to the many "maintenance" utilities that have not yet been converted to universal binaries. Leopard Cache Cleaner, Onyx, TinkerTool System, and Cocktail are now compatible with Leopard.

    Before migrating or installing software on your Intel-Mac check MacFixit's Rosetta Compatibility Index.

    Additional links that will be helpful to new Intel-Mac users:

    Intel In Macs
    Apple Guide to Universal Applications
    MacInTouch List of Compatible Universal Binaries
    MacInTouch List of Rosetta Compatible Applications
    MacUpdate List of Intel-Compatible Software
    Transferring data with Setup Assistant - Migration Assistant FAQ

    Because Migration Assistant isn't the ideal way to migrate from PowerPC to Intel Macs, using Target Disk Mode, copying the critical contents to CD and DVD, an external hard drive, or networking
    will work better when moving from PowerPC to Intel Macs. The initial section below discusses Target Disk Mode. It is then followed by a section which discusses networking with Macs that lack Firewire.

    If both computers support the use of Firewire then you can use the following instructions:

    1. Repair the hard drive and permissions using Disk Utility.

    2. Backup your data. This is vitally important in case you make a mistake or there's some other problem.

    3. Connect a Firewire cable between your old Mac and your new Intel Mac.

    4. Startup your old Mac in Target Disk Mode.

    5. Startup your new Mac for the first time, go through the setup and registration screens, but do NOT migrate data over. Get to your desktop on the new Mac without migrating any new data over.

    If you are not able to use a Firewire connection (for example you have a Late 2008 MacBook that only supports USB:)

    1. Set up a local home network: Creating a small Ethernet Network.

    2. If you have a MacBook Air or Late 2008 MacBook see the following:

    MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- Migration Tips and Tricks;
    MacBook (13-inch, Aluminum, Late 2008) and MacBook Pro (15-inch, Late 2008)- What to do if migration is unsuccessful;
    MacBook Air- Migration Tips and Tricks;
    MacBook Air- Remote Disc, Migration, or Remote Install Mac OS X and wireless 802.11n networks.

    Copy the following items from your old Mac to the new Mac:

    In your /Home/ folder: Documents, Movies, Music, Pictures, and Sites folders.

    In your /Home/Library/ folder:

    /Home/Library/Application Support/AddressBook (copy the whole folder)
    /Home/Library/Application Support/iCal (copy the whole folder)

    Also in /Home/Library/Application Support (copy whatever else you need including folders for any third-party applications)

    /Home/Library/Keychains (copy the whole folder)
    /Home/Library/Mail (copy the whole folder)
    /Home/Library/Preferences/ (copy the whole folder)
    /Home /Library/Calendars (copy the whole folder)
    /Home /Library/iTunes (copy the whole folder)
    /Home /Library/Safari (copy the whole folder)

    If you want cookies:

    /Home/Library/Cookies/Cookies.plist
    /Home/Library/Application Support/WebFoundation/HTTPCookies.plist

    For Entourage users:

    Entourage is in /Home/Documents/Microsoft User Data
    Also in /Home/Library/Preferences/Microsoft

    Credit goes to Macjack for this information.

    If you need to transfer data for other applications please ask the vendor or ask in the Discussions where specific applications store their data.

    5. Once you have transferred what you need restart the new Mac and test to make sure the contents are there for each of the applications.

    Written by Kappy with additional contributions from a brody.
    Revised 1/6/2009

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hmmm. How about if I just don't migrate the apps, and just do everything else?

    also, would it be better to install, say Office 2004 on the new mac before I migrate over all my words files, email etc?

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    This is entirely your choice.

    If you're going to use Snow Leopard or Leopard then I would use Office 2008. However, it doesn't make any difference whether you do that before or after.

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    David52 wrote:
    Do I need to try to clean those out before I migrate, or will 10.6.2 be smart enough to deal with this?

    I suggest that you do not touch anything on your old Mac -- since it is running great now, why change anything on it? I also suggest that you use Migration Assistant to bring everything over (even the OS 9 System Folder if you want) & then decide what migrated items to delete on the new iMac & do that. (I am making one assumption here, that the new iMac currently has much more free space on its drive than the total of all the stuff on the old Mac's drive. If this is not true, you may need to be more selective about what to migrate.)

    I base my advice on the following:

    1. Migration Assistant is smart enough not to migrate versions of apps that already exist on the destination drive, so it will not for instance overwrite the new Snow Leopard Finder or any of the bundled apps like Mail or Address Book with older versions from the old Mac. It also will not overwrite system settings (preference values) with ones from the old Mac that are not appropriate for the new one.

    2. It is very unlikely that Snow Leopard's version of Migration Assistant will migrate anything from a properly configured PPC Mac running an older version of OS X that would play havoc with the new system. For instance, Snow Leopard won't run Classic apps but it just politely tells you that it can't if you try to launch one. Migration Assistant does not migrate caches so that isn't a problem, & even if it did Snow Leopard would recognize that they were "stale" & update or delete them. PPC-only plugins for browsers won't run, but they won't load either, so the worst that can happen is loss of their functionality, not some sort of systemic "havoc." The same is true for kernel extensions & most of the other items in the user-suggested Basic Guide tip: they either won't be migrated or Snow Leopard won't load them.

    3. You may well want to retain at least some PPC-only applications that will run with Rosetta, at least until you can find Universal or Intel-only versions to replace them -- assuming they exist, your budget can immediately support any upgrade costs involved, you use them often enough to justify finding & installing their replacements, & the replacements actually offer something the PPC version running under Rosetta lacks. And while you can't run Classic apps at all, you may even want to temporarily retain some of the items in the old System Folder for reference, which can sometimes help in the quest for replacements.

    4. The manual migration alternative is somewhat tedious to perform, especially if you discover that you haven't copied some items in ~/Library/Application Support (as mentioned in the Tip) or other ~/Library folders required for third party applications & have to go back & do that after you thought you were done. And of course, you might end up copying something that you don't need since it isn't always obvious what supports what unless you contact the vendor or ask in Discussions (as suggested in the Tip). You may also want to migrate ~/Library items not on the Tip's list for other reasons than strictly for application support, such as sounds, preference panes, saved searches, etc. IOW, the list is not comprehensive but more of a minimum suggestion of what most users would want migrated. You should consider all this when deciding if the supposed benefits outweigh the tedium of doing a manual migration.

    5. Of course, using Migration Assistant to migrate everything takes quite a bit of time, but unlike with the manual method you don't have to actively participate in the process so you can let it work away while you do other things. And you will probably find that it is more convenient & efficient to delete unneeded items from your new Mac than to work with both of them. For instance, Snow Leopard's System Profiler will list & sort all your apps, frameworks, & a few other classes of software by kind, so you can see at a glance which are Classic, PPC-only, Universal, or Intel-only. And since the new iMac is undoubtedly much, much faster than your 10 year old PPC one, you won't be waiting for the old one to complete some operation before you can apply the results to the new one.

    6. In short, Apple designed Migration Assistant to make the transition from one Mac to another as painless as possible. While it isn't perfect, it usually works quite well, almost always well enough to avoid any of the vaguely defined "havoc" that the user tip is so concerned about.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ah! Well I really do want to believe! After doing some more research I think I'll give it a shot and do a migration to bring everything over and trust the system to do it right. If I am wrong, well, there will be remedies for that too.

    I understand the 2 extremes of ultra caution (some people recommend always doing an erase and install with a new OS, for example) and some just trust Apple to "do it right". I have found that usually the latter works (unless there is a major fault somewhere....that fine old G4 dual 450 I am still running came with one defective processor!)

    My old HD was 120GB, and I have only 75GB in use, the new one: 1TB! so space is not a problem, nor is the time it would take to cable them up and let it run.

    I'll give it a whirl!

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ok, I'm confused after reading some of the above info.

    Soon I'll have a new MBP. Currently I'm using a PB G4 running 10.4.11.

    Ideally I'd like to migrate:

    - my user settings
    - some of my apps
    - some of my data

    When I first open the new MBP will I be able to migrate my admin user account to the new OS without creating a new account on it?

    Is the above message that tries to say not to auto-migrate mainly concerned with OS 9 items or is it saying migrating any 10.4.11 stuff can cause havoc in 10.6?

    I mainly care about migrating user settings right off the bat. Migrating app and files don't need to be done right away.

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi Lee

    I'll tell you my experience: I did the migration and so far so good. A couple of important things: I used a firewire cable to do it (there seems to be some problems, not huge, doing it over a wireless network), and I did it AFTER I had set up my new computer, and this cause me a bit of chagrin. I had set up my new computer with a new name and had started to play a little bit. But when I did the migration (I did the whole shebang transferring everything), I found that this created an identical copy as an account under the old name. So much for my new naming. But since I do not plan to use the old computer much longer, I guess I'll be OK with the boring old name. I don't know if it matters, but I used my same system password for the new computer.

    All I had to do was Login under the old name and everything was there, and I have not encountered any problem so far. I can see why there is advice out there to do the migration immediately when you set up the new computer for the VERY FIRST TIME, because then it will just recreate everything as it was on the old machine....names etc. Even the desktop picture.

    I think if you migrate right away when you first open the new MBP, you will not have to set a new account or anything up. I think your admin user account will migrate over exactly as you have it set up.

    So far, I haven't seen any havoc to complain about. Good luck, and lucky you!! a new MBP.

  9. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    David52 wrote:
    I think if you migrate right away when you first open the new MBP, you will not have to set a new account or anything up. I think your admin user account will migrate over exactly as you have it set up.

    That is correct. Technically, the first thing you see after the "Welcome" movie is the Setup Assistant. At that point there are no user accounts or system settings so you must immediately either create a new account or migrate at least one account from another Mac, together with that Mac's system settings. Setup Assistant gives you this choice. If you choose to migrate, Setup Assistant in effect runs Migration Assistant as a root user (also known as "superuser" or "system" user) process. Since OS X must have at least one admin user account, if you elect to migrate only non-admin accounts, this process will change the first migrated regular account to admin status.

    Otherwise, it is the same as running Migration Assistant normally from an admin account.

  10. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Ah, thank you!

    That is helpful to me at least, to know what is happening. If I had not migrated my settings over (when I did a "later " migration), would all my stuff have gone into the admin account I had on the new Mac?

    I'm glad that I did it the way I did at any rate. Seems like the settings is the most important stuff to migrate! (i.e. they would be the biggest hassle to reconstitute on a new computer)

    Dave

  11. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    David52 wrote:
    If I had not migrated my settings over (when I did a "later " migration), would all my stuff have gone into the admin account I had on the new Mac?

    I'm not exactly sure what you are asking but Migration Assistant will not merge a migrated account with a preexisting one -- there are too many potential conflicts for it to know (for instance) which user preferences to use. Thus, if you try to migrate a user account with the same name as the one you created on the first startup, it will give you a choice of renaming one of them or disabling that new one (optionally keeping the account's home folder around for future use).

    IOW, each account is a separate entity. Migration Assistant will allow you to copy one from one system to another, or replace one with another, but only one account of each short name can exist on any system.

  12. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    R C-R wrote:

    2. It is very unlikely that Snow Leopard's version of Migration Assistant will migrate anything from a properly configured PPC Mac running an older version of OS X that would play havoc with the new system.

    6. In short, Apple designed Migration Assistant to make the transition from one Mac to another as painless as possible. While it isn't perfect, it usually works quite well, almost always well enough to avoid any of the vaguely defined "havoc" that the user tip is so concerned about.

    After having read the various suggestions pro and con about using Migration Assistant to migrate from ppc to Intel, I decided to go ahead and try migrating everything from my iBook G4 running well with 10.5.8, to my new Mini.

    The first time I booted the Mini, I connected my iBook in FW target disk mode, when requested by Setup Assistant on the Mini. I chose to migrate everything, and the process seemed to go well and took less than an hour to migrate 40gb.

    The very first task I attempted on the Mini after rebooting was pairing my Apple bluetooth keyboard. Unfortunately, I could not launch Bluetooth Setup Assistant, as it would instantly unexpectedly. I discovered that Migration Assistant had migrated the old ppc version. Deleting bluetooth plists then the ppc Bluetooth Setup Assistant did not solve the problem. I connected an old usb keyboard.

    The next task I attempted was adjusting Energy Saver to not sleep the Mini. This also didn't work. I would set the slider to "never sleep" but the Mini would sleep anyway. I rechecked the setting in Energy Saver. The slider was as I set it, but the Mini ignored it.

    I decided not to find out what else was broken, so I did a clean install. I initialized the Mini's disk, re-installed Snow Leopard from dvds, ran Setup Assistant without migrating any files, ran Software Update, and tested the Mini. Both Bluetooth Setup and Energy Saver now work fine.

    I would say 0 for 2 success rate, on the very first couple of system tasks I attempted after running Migration Assistant, met my definition of "havoc.