Migration Assistant (Tiger -- Leopard)

I just received my new MacBook yesterday...during installation, I was trying to use the Migration Assistant to take data from my older Mac (PowerBook G4 w/ Tiger) using the Firewire mode. After connecting the Macs using the Firewire cable, and then restarting the older Mac in Transfer mode (holding down 'T')...the older Mac has the Firewire display on the screen, but the new MacBook's Migration Assistant says that it cannot find any disks with Mac OS X loaded. I've also tried connecting through the AirPort with the same results. In addition, I tried running Migration Assistant outside of the installation process to see if there was any difference, but no luck.
Is there a known issue with Migration Assistant from Tiger to Leopard? Is there some reason that Leopard's Migration Assistant isn't finding my disks on the older PowerBook G4 (PowerPC)?
Any help would be greatly appreciated.
Thanks
Brad
Message was edited by: shoptb

My father has a new Imac running 10.5. We want to migrate from an old G4 running 10.4. The old machine is not recognized in the attempted firewire transfer in migration assistant (MA). No help is offered in the MA. I then tried migration via ethernet. The OS10.5MA describes settings choices in the old machine's MA that do not exist ("migrate to" choice does not exist in 10.4 MA) - a bug. APPLE ON-LINE SUPPORT WAS STUMPED and they insisted we take BOTH machines into an apple store - a huge burden.
APPLE SUPPORT - LOOK THIS IS AN OBVIOUS BUG, MULTIPLE POSTS, CAN YOU PLEASE PROVIDE ANSWER?
An IT professional recalled a similar case and thought there might be network settings issues. Another possibility is unrelated software interference - e.g. firewalls, backup software, anti-virus. Perhaps a hint about booting into a single user mode might help?
I note that cables and firewire read/write to extrenal drive were all tested separately and worked fine.
-B

Similar Messages

Migration Assistant - Tiger to Lion?

I'm installing a new iMac for a client soon which currently has Snow Leopard on it. I'd like to upgrade them to Lion, but before I do I want to make sure that I won't run into any problems with the Migration Assistant. I believe they are running Tiger on their current Mac... I know there was just a compatibility update for Snow Leopard, but will I run into any problems using it from Tiger to Lion? How far back will Migration Assistant be compatible?

Patricia W wrote:
I'm attempting to do the same thing from an iMac G4 and I can assure you it does not have a Firewire port and it does run OS X Tiger. I cannot find out how to use Migration Assistant but I can assure you that you can connect your computers via a ethernet cable.
As posted several times here, you cannot use Setup Assistant or Migration Assistant via network from Leopard or earlier to Lion.
But all iMac G4's came with either 1 or 2 F/W 400 ports:
iMac (Flat Panel), iMac (17-inch Flat Panel) - Technical Specifications
iMac (17-inch 1Ghz) - Technical Specifications
iMac (USB 2.0) - Technical Specifications
You'll need a F/W 400 to F/W 800 adapter, or a cable with a F/W 400 plug at one end and a F/W 800 plug at the other. Just so you know what they look like: http://www.amazon.com/elago-FireWire-400-800-Adapter/dp/B002TF0ZDQ/ref=sr_1_1?ie =UTF8&qid=1312562370&sr=8-1
Or, make a "clone" backup of the G4 on an external HD, with the Restore tab of Disk Utility (see #7 in Using Disk Utility), or CarbonCopyCloner or SuperDuper, then connect it to your new Mac.

Problems with Migration Assistant in Leopard-

Hi - I did see someone else with a similar problem, but thought I'd be able to avoid these snafus by migrating between two PPCs. Alas!
I tried to transfer all my files, programs and settings between my used eMac and a second hand iMac G5 I had thought to upgrade to. Migration Assistant seemed to insist that I create a second account in order to proceed with the migration. At first, I thought I'd lost a lot of my programs, but now I see that they are actually there and working in the second account. On the other thread, I read that people with this problem should restore their new or newer machine to its factory settings, then do the migration over. That way, we can avoid setting up two identities for the same person. In my case, the seller of the iMac is sending me an install disc of Leopard. Can I use this to get back to the factory settings, more or less? And how would I do it?
I do know how to do an install-in-place, having done a couple of them. But clearly more is required here. I don't mind messing around with my machines to a degree, but I'm not a techie, really, and I'm also quite cautious generally. My whole life is on the eMac, so my priority is keeping it in good shape while transferring info to the iMac.
What I'd ultimately want to end up with - assuming I decide to upgrade to the iMac - is one administrator account, not two, with access to all my old files, settings and programs and also the newer programs the seller provided. Can I use the Leopard install disc to get there?
Oh - two more things. I cannot open iTunes on the working (second) account on the iMac. Also, none of my mail messages transferred over. Is there a way to get them to transfer?
Thanks very much, and sorry for all the questions!
Mary

I HATE migration assistant! Just spent three hours trying to move stuff from my eMac, and I am now listed as the only user - but I have the same problems I had the first time around, only, this time, it might be worse. None of my files were moved into the current "music", "movies", "documents" folders. In order to find them, I have to dig into the hard drive, find my saved data, and then go to users and documents. Not all of my programs transferred, either, and one or two of them acted odd when they did. The most serious thing is that my novel is again missing on the iMac, and I again had to re-license Scrivener. Only this time it's really gone, all but three chapters. Grrr!
It's a good thing I am a cautious person and had no intention of passing the eMac on unless/until I could really use the iMac. Well, if I can't get my most important files over seamlessly, and if the machine can't access them without a lot of clicking and dragging, the iMac is no use to me.
I know I have a lot of info on the eMac - altogether, close to 8 years of stuff. But there has got to be a way to get it over to the iMac without losing data, programs, passwords, etc. I just don't understand this!
What I did - did an erase and install of Leopard a second time, because, if you don't use setup assistant to migrate, you seem to be stuck with two identities. Then followed the steps and opened the window and turned on a fan behind my computers - and waited, and waited, and waited, waking the iMac up occasionally when it went to sleep. Reinstalling Leopard took less than an hour, but this file transfer took nearly three. And it's a total mess, again. I'm really, really fed up, and am at the point of just sticking with the eMac and lending the iMac to the library. This just shouldn't be so hard!
(And this sort of thing is why I don't like Leopard. ))

What do I use when Migration Assistant reads "you might not be able to transfer using firewire on this computer"?

When using Migration Assistant to transfer from one Mac to another Mac, as soon as I get to the point where it says to connect the firewire to each computer, it says "You might not be able to transfer using Firewire on this computer". What do I use then?

firetruckjanet wrote:
The G5 is running osx 10.4.11, but so is the G4.
I don't know if it's the Tiger or the Leopard.
10.4.x is Tiger; 10.5.x is Leopard.
I've not used the Tiger version of Migration Assistant (just Leopard and later), and there's not much in the way of Apple tech articles for it anymore.
Since the message says "might not," I don't see any reason not to give it a try. At worst, it will fail and perhaps leave a partially-transferred user account on the G5. If that happens, we can deal with it.
I'd make sure the connections are snug and secure, and try it.
Good luck, and keep us posted.
I don't have any backups of the G4 and I don't have an external drive and I don't know anyone who has one.
If your data is important to you, invest in one . . . soon, and start making regular backups. They're not very expensive (some as cheap as $50, good ones perhaps $100). Disk drives fail, especially after a few years, other things go wrong, and even the most careful users make mistakes now and then.

Can I use migration assistant from a mac with leopard to a mac with tiger?

My old mac was upgraded to leopard, (don't ask me why), and I just got a new mac with tiger, although I ordered leopard up to date. Can I use migration assistant to move stuff from the old mac with leopard to the new mac with tiger, or do I have to wait until I get the copy of leopard? Plus, if I move files over now- like through email and/or network connection, and then when I get leopard and archive and install, what happens to my files?

That is correct. You'll need either an ethernet cable or a firwire cable and a firewire to thunderbolt adapter to connect the two macs together. Here's info on Migration/Setup assistant
http://support.apple.com/kb/HT4889?viewlocale=en_US&locale=en_US

Problems using Migration Assistant from Tiger to Snow Leopard

I want to scavenge files and apps from a Power Mac G4 (PowerMac3,5) running Tiger 10.4.11 before I turn it out to pasture. Most of them were migrated years ago to another system and have been updated and upgraded over the years, but a few apps have no modern equivalent. Now I want to do one last "pull" to pick up anything left behind all those years ago, particularly apps for which the install discs are in deep storage at best and possibly discarded.
I'm trying to use Migration Assistant in a nearly virgin Snow Leopard 10.6.8 system (installed fresh from 10.6.3 retail optical disc, updated over the network, lightly tested). It has a single admin account, no other user accounts.
Possible complicating factors: the Snow Leopard system is Server running under Parallels 10.1.4 on Yosemite 10.10.2 on an Early 2008 Mac Pro (MacPro3,1) with third-party USB3 controller in a PCI slot.
At present, I'm using a portable drive with both FW and USB interfaces as an intermediate storage (FW on the G4 to clone the system drive, USB on the Mac Pro to connect it to the virtual machine). SL sees the drive just fine, can copy files from it, and can even run apps from it. Migration Assistant sees the drive and offers to migrate from it.
Two problems:
1. No matter what user(s) I select for migration, Migration Assistant tells me it is a duplicate account. Proposing an account name never used before does not help. As a result, no user files can be migrated. (Obviously, I could copy them in other ways, but I think MA should do a more thorough job.)
2. Migration Assistant offers to migrate absolutely no applications. Even applications that SL will run from the drive cannot be migrated. (Some are PPC apps, but SL will run them via Rosetta. Others are Universal apps.)
Am I expecting too much of Migration Assistant?
Is the Migration Assistant shipped with SL Server (and updated through Software Update) not capable of running under SL Server?
Should SL MA refuse to migrate any applications from a Power Mac, even Universal applications?
Am I missing something obvious?
Is there key information I have omitted?

markwmsn wrote:
...It's not the twenty bucks, it's the principle of the thing.
Not sure what you meant by that statement. Although this "principle" may be more important to you than the twenty bucks, I know that my time is worth more to me than your twenty bucks!
What apps are you using?
markwmsn wrote:
I was able to install Snow Leopard (client) in a partition, and it was able to migrate users and many applications from the G4 clone on the portable drive. Some of the apps even run.
Then I went back to my SL Server virtual machine and tried to migrate FROM the SL client partition. Migration Assistant showed the same symptoms as importing from the clone directly (no apps offered, bogus "dup user" errors). I am forced to conclude that either (a) Migration Assistant 3.0.4/1.1 is broken when run on SL Server or (b) my new SL Server installation is broken. I'm either going to have to boot back and forth to run the old apps or find their installation media and reinstall them in my SL Server virtual machine.
Even worse, I realized that one of the antique programs I still haven't dug everything out of is a Classic application that had to be kludged to survive Y2K!
Thanks again, MIchaelLAX.
Anybody else have any clever ideas?
So, glad to see that Migration Assistant did work for you in Snow Leopard...
More clever ideas:
Install Snow Leopard client in Parallels and use its Migration Assistant:
http://forums.macrumors.com/showthread.php?t=1365439
Here is a recent post I assembled for running Classic apps on Intel Macs:
With the newer Intel Macs, you have to run a Classic emulator such as SheepShaver, which requires you to extract the Mac ROMs from your older Classic Mac and then install Mac OS 9.
A related program is Chubby Bunny, which comes bundled with all of that included (google the term "Classic-On-Intel v 4.0.1 chubby bunny").
More information on SheepShaver:
http://www.emaculation.com/doku.php/sheepshaver_mac_os_x_setup
and
http://www.everymac.com/mac-answers/mac-os-9-classic-support-faq/run-macos-9-on- intel-macs.html
and more information about Chubby Bunny:
http://www.macwindows.com/OS9_on_Intel_Mac.html#092408b
and
http://hackthemac.blogspot.co.uk/2008/08/chubby-bunny-old-virtual-machine.html
Here is the Classic CD-ROM version of RISK II running in SheepShaver on my Lion Mac Mini:
[click on image to enlarge]

"Upgrading" from leopard to tiger.. Migration Assistant cant see 10.5

10.5 runs like a pig on my 12" G4. I re-installed 10.4 onto a new volume and it runs just like it used to. For comparison I had also tried a clean 10.5 and it ran just as slow.
So anyway, what I wanted to do was use the migration assistant to pull my data from 10.5 over to 10.4 but when I point to the 10.5 volume MA doesnt see anything. I suspect maybe this is by design and such a "downgrade" isnt supported.
Has anyone tried this?
My other option is to create a backup of the 10.5 volume then just try an archive+install of 10.4 over the top.
Lets hope 10.6 runs better!

WEll, it;s not that easy Darrin,
Leopard puts things in different places than Tiger did.
Hopefully one of the people that recently posted on how to do it will drop in, because I can't find it!
suspect maybe this is by design and such a "downgrade" isnt supported.
Nope... how would they know what Leopard would do with files when they made Tiger?
My other option is to create a backup of the 10.5 volume then just try an archive+install of 10.4 over the top.
Lots of stuff you have now won't be in the right places.

Migration Assistant Question re Tiger to Leopard

I am planning on updating a friend's Mac Mini from tiger (10.4.9) to Leopard, via the Retail Leopard DVD.
Trying to look for time shortcut here, she has no backup beyond a flash drive, I will bring over an ext FW HD for full user folder data backup at the start of the process.
And I plan to do the Archive and Install with Preserve Settings. (I am too leery of Updating Leopard ontop of Tiger.)
My questions,
(a) Will Leopard ask to run the Migration Assistant after "Archive and Install" -- or does it ask this only after a full Format (erase the HD) Install type?
(b) If I were to run Migration Assistant manually after the Leopard installation, can it pull data from a backup of Just the User folder (and of course sub folders) and the Applications folder -- assuming I was pressed for time and only backed up those to external HD, not taking the longer time to clone the whole disk clone of System, Library, Etc etc)?
Or does Migration Assistant require a fully operating Mac or Cloned HD.
(My guess, based on the reading of Apple's info pages, is that it will only work from a full OS X machine or full clone.
And that it would only pull over user data - as per: http://support.apple.com/kb/HT1554 "can transfer data (including account settings and home folders)")
Any one have any experience with that sort of safe but faster installation?
(I only ask because she (friend) is very time sensitive and does not want to be twiddling thumbs during a full clone of the Tiger (Mac Mini) HD first.... sigh...)
Thx.
Message was edited by: Bruce

BruceTech wrote:
(a) Will Leopard ask to run the Migration Assistant after "Archive and Install"
No. But if you select "Preserve Users and Network Settings", the user home folders will be left undisturbed, so Migration Assistant won't be needed for those things.
It's been a long time since I installed Leopard, but apparently "Archive and Install" will also preserve the Applications folder. It's mainly the System and Library folders that will be affected buy such an installation.

Migration Assistant from Tiger Mac to new Leopard MBP can't see disk

Hi,
I just bought a new MacBook Pro and am trying to migrate from my Tiger-based (10.4.10) dual 1 GHz Mac (mirrored-drive door) desktop machine. The boot drive on the Tiger machine is actually partitioned into an emergency boot drive of a few GB and my main working drive ("Macintosh HD"). When I run Migration Assistant (MA) on my MBP (after connecting the 6-pin Firewire cable and restarting the Tiger Mac in target disk mode), the MBP sees only the emergency boot-up partition and not the main working partition from which I want to migrate.
I tried MA on my MBP connected to a different Mac with no HD partitions, and it sees "Macintosh HD" just fine, so I think all the new hardware is okay as well as the Firewire cable.
Any ideas?
-Eric

Thanks for the info. I do know something about this (being a HW engineer), but I would have thought that the IDE master/slave jumpers would affect all the partitions on the disk. Since my emergency-boot partition is visible, I take that to mean that the IDE master/slave jumper issue is a non-issue for me.
I don't know if this helps, but here's what Disk Utility reports about the disk (not the volumes residing on it):
Name : ST380021A
Type : Disk
Disk Identifier : disk1
Media Name : ST380021A Media
Media Type : Generic
Connection Bus : ATA
Connection Type : Internal
Connection ID : Device 0
Partition Type : Applepartitionscheme
Device Tree : pci2/ata-6@D/@0:0
Writable : Yes
Ejectable : No
Mac OS 9 Drivers Installed : Yes
Location : Internal
Total Capacity : 74.5 GB (80,026,361,856 Bytes)
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 0
Now, onto the partitions which I know less about.
Here's what Disk Utility says about the Macintosh HD partition:
Name : Macintosh HD
Type : Volume
Disk Identifier : disk1s10
Mount Point : /
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : pci2/ata-6@D/@0:10
Writable : Yes
Universal Unique Identifier : E6E9B335-60D0-3F06-97F9-2A9BAC522106
Capacity : 68.4 GB (73,411,137,536 Bytes)
Free Space : 819.5 MB (859,291,648 Bytes)
Used : 67.6 GB (72,546,123,776 Bytes)
Number of Files : 367,638
Number of Folders : 74,198
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 10
Here's what Disk Utility says about my emergency-boot partition:
Name : Clean Boot
Type : Volume
Disk Identifier : disk1s12
Mount Point : /Volumes/Clean Boot
File System : Mac OS Extended (Journaled)
Connection Bus : ATA
Partition Type : Apple_HFS
Device Tree : pci2/ata-6@D/@0:12
Writable : Yes
Universal Unique Identifier : 4A704075-200F-3CCB-B8ED-E7FEEDB655EC
Capacity : 5.9 GB (6,345,846,784 Bytes)
Free Space : 3.8 GB (4,133,232,640 Bytes)
Used : 2.1 GB (2,212,093,952 Bytes)
Number of Files : 76,846
Number of Folders : 19,664
Owners Enabled : Yes
Can Turn Owners Off : Yes
Can Repair Permissions : Yes
Can Be Verified : Yes
Can Be Repaired : Yes
Can Be Formatted : Yes
Bootable : Yes
Supports Journaling : Yes
Journaled : Yes
S.M.A.R.T. Status : Verified
Disk Number : 1
Partition Number : 12
I don't know how to determine from the above what the "first" partition would be. I don't know how to post an attachment here otherwise I'd show a screen shot, but when I got into Disk Utility's partition tab, the emergency-boot partition (called Clean Boot) shows up at the bottom of the space indicating all of the HD's space, and Macintosh HD shows above Clean Boot.
So what are my options? Can I repartition w/o loosing Macintosh HD (I'm willing to loose the other partition Clean Boot)? Any way to change the partition numbers?
I was thinking of cloning Macintosh HD to another HD and then migrating from that. Any experience with that?
Thanks, Eric

Disk Migration from Tiger-based iMac to Leopard MacBook

A friend just bought a new MacBook (with Leopard). She wants to do a disk migration from her G5 iMac (running Tiger). Any issues I should know about when doing this? Or should I upgrade the iMac to Leopard before doing the disk migration?
Thanks for any input!

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 or G4 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 or copying the critical contents to CD and DVD or an external hard drive will work better when moving from PowerPC to Intel Macs.
Basically the instructions you should follow are:
1. Backup your data first. This is vitally important in case you make a mistake or there's some other problem.
2. Connect a Firewire cable between your old Mac and your new Intel Mac.
3. Startup your old Mac in Target Disk Mode.
4. 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.
4. 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 3/12/2008

Why won't Mail.app rules won't migrate, System Tiger to System Leopard?

Hi,
Mail.app rules won't migrate from System Tiger to System Leopard.
Here's what I did:
-- Clean install of System Leopard 10.5.6 onto a new Mac Pro.
-- Used Migration Assistment to move files from System Tiger to System Leopard 10.5.6.
-- Mail.app's rules failed to migrate.
So, I manually finder-copied MessageRules.plist into the proper folder to replace the newly created and empty rules set in System Leopard's mail.app, and afterwards, the rules then showed up in mail's preferences.
However, the "manually migrated" [finder copied] rules won't run.
In order to narrow the scope of the problem, I moved the former System Tiger's mail.app rules to the desktop and allowed mail.app to re-create a new rules plist file, then I created a test rule and it worked.
Questions:
Why won't System Tiger's mail.app rules files migrate to System Leopard, and won't work upon manual migration?
What is the remedy to "properly import" the rules to the new [System Leopard based] mail.app, or to make the manually moved rules plist file work?
For what it's worth I did follow the procedures at
http://discussions.apple.com/thread....9306&tstart=90
in order to make the messages migrate, but that failed to affect the rules.
Thanks much,
Jack

Here's the fix, along with recommendations for Apple programmers.
http://www.macfixitforums.com/ubbthreads.php/topics/463491#Post463491

HT4889 Trying to migrate from Mac-mini Tiger to Mac-mini Lion and Migration Assistant cannot find my Firewire, 400 to 800, "T" disk although it show up in the new Mac's computer folder. Help

Trying to migrate from Mac-mini Tiger to Mac-mini Lion and Migration Assistant cannot find my Firewire, 400 to 800, "T" disk although it shows up in the new Mac's computer folder. It seems that Mac-mini Tiger is as it should be and the firewire cable is OK. Something about the Migration Assistant is being missed, but I have no idea what it is.
Help

Addendum: I read on a post here (http://forums.macrumors.com/showthread.php?t=420169) about removing some kext files in order to trick OSX into thinking that there were no FireWire ports.
I followed the instructions and removed from /System/Library/Extensions/ the following files:
IOFireWireSerialBusProtocolTransport.kext
IOFireWireAVC.kext
IOFireWireFamily.kext
IOFireWireIP.kext
IOFireWireSBP2.kext
I restarted and BAM...Snow Leopard booted crazy fast and the mouse and keyboard worked instantly.
The System Profiler says "No FireWire ports were found."
So this tells me that the FW port is probably the culprit and is messing up the installation.
So how do I hack the Mountain Lion installer and tell it to ignore the FW port, which is obviously quite dead? Or is there something I can do to the Base system that is similar?

Tiger icons migrated to new Leopard notebook

I used the Migration assistant to move my information from my old Powerbook G4 running Tiger, to my new aluminum Macbook running Leopard. The application icons (Mail, iChat, etc.) for Tiger are being used. Is there a way to get the default Leopard icons to replace them? I tried opening the info pane and deleting the icon to try to get to the default, but apparently, the Tiger icons are set as "default".

You might try one of the various cache cleaner tools - start at http://versiontracker.com and search on "cache" some of the hits will be cache cleaning utilities.

New leopard macbook won't see panther macbook os in migration assistant

I just got a brand new MacBook (leopard) but when i try to use migration assistant, i get as far as it waiting for target (MacBook with OS 10.4.11) to restart, which it does with the firewire symbol, but then it tells me i don't have any versions of OS X on there! I have tried a number of times! Any advice?

First off, your naming conventions already put to doubt what you have.
10.4.11 is Tiger, not Panther.
Are you sure the machine you are putting into Target Mode is a MacBook?
If it says Powerbook or iBook on it, don't use it for Migration Assistent
transfer, and instead use this article:
http://discussions.apple.com/thread.jspa?threadID=435350
If it is indeed a MacBook, make sure you Target Disk Mode is set when nothing except power is connected to the MacBook. Target Disk Mode initiation frequently does not work when other cables are connected to the computer.
Message was edited by: a brody

HT4889 Am I wrong or does Migration Assistant not work in Mountain Lion (10.8.2) when migrating from a PowerPC running Tiger (10.4.11)? Apple really needs to get on the ball or face losing people buying their new desktop products.

The title alone speaks to my frustration about this issue.
Used the process that was recommended by Apple to migrate from my "Lampshade" iMac (PPC running 10.4.11) to the new iMac (Intel running 10.8.2) and I got bupkiss...
Just a spinning wheel (not beachball) and no drive recognized using Migration Assistant for both nor when using Target Mode on the iMac running 10.4.11 and Migration Assistant on the iMac running 10.8.2. Which is ironic, or more accurately oxymoronic, since the iMac in Target Mode (10.4.11) is recognized on the desktop of the iMac running 10.8.2 but not in the Migration Assistant. And before you can misdiagnose..it is not the Thunderbolt connection since I have the Apple recommended Thunderbolt to Firewire adapter and also used the Firewire 400 to 800 cable to expedite the transfer.
On a personal note...
I'm not bashing Apple for this...they are "head and shoulders" above the competition in what they do but I've been burned a few times so I feel I can share a small bit of loyal customer advice...I understand your iOS and mobile products hold huge sway in company focus and market-share but I find it a tad unwise to slack on the desktop applications. I don't recall any app for the iPhone/iPad family being made on the iPhone/iPad...only from desktop applications if I recall correctly. And how can I clearly "Move my Mac even further ahead" as your marketing states when I can't even migrate my files from my old Mac to my new one in a simple fashion as per your instructions?
I thank anyone in advance with an answer or even a workaround for this issue and please have a great day.

http://support.apple.com/kb/ht4889
Migration from Mac OS X v10.4 Tiger to OS X Lion
Migration from Mac OS X v10.4 computers to OS X Lion over your Wi-Fi or a wired network is not supported. However, if both Macs are equipped with a FireWire port, you can use Target Disk Mode to transfer your data:
Verify that both Macs are equipped with a FireWire port. Note that different model Macs may have different FireWire connectors, which will require an appropriate cable, such as FireWire 400 to FireWire 800.
On the Mac you want to transfer data from, Restart, and immediately hold the T key.
Wait for the FireWire logo to appear on the screen. If it does not, restart and try again.
Connect both Macs via the FireWire cable.
On the Mac you want to transfer data to, Open the Migration Assistant application.
Select the option "From another Mac, PC, Time Machine backup, or other disk" and click Continue.
Select the option "From a Time Machine backup or other disk" and click Continue.
Select your other Mac's volume, such as "Macintosh HD", from the list, and click Cont
EDIT: Actually I realize you did follow these directions and if your drive is seen on the new Mac it should work. You're entitled to free Apple support with the new purchase, I'd give them a call.

Migration Assistant (Tiger -- Leopard)

Similar Messages

Maybe you are looking for