Migration Assistant behavior

I made a clean installation of Snow Leopard on an external partitions to eliminate a persistant corruption and some old applications, but Migration Assistant did not behave the way expected. Since I only wanted to save my Users folders, I did not select Applications or Settings (only Users). But Migration Assistant brought over all the applications from the internal disk that I did not want to see again anyway. However, the firmware update that was previously rejected over and over (the persistant corruption) was successfully installed this time. Now the optical drive is quiet when the computer wakes up from sleep. I'll clean install again if I can figure out how to exclude old applications.

Stupid Migration Assistant.
Next time, use a regular storage drive for your Users folders, then erase and install OS X, then programs from fresh sources, then files from backup.
Read my post here, it will bring you up to speed.
https://discussions.apple.com/message/16276201#16276201

Similar Messages

  • Problem with Lion upgrade after running Migration Assistant

    I have a MacBook Pro that I purchased earlier this year.  I bought a new MacBook Air yesterday. 
    I used Migration Assistant to migrate some of my data/settings from my old MacBook Pro to the new MacBook Air.  After the migration, all of my original data was still available on the MacBook Pro (good as I wanted to keep a copy on the MacBook Pro and not all data was migrated).  The new MacBook Air received all the right data and is working well.
    I then purchased a Lion upgrade for my MacBook Pro and started the installation process.  The installation process seemed to be going fine, but the MacBook Pro eventually hung.  I let it "run" overnight hoping that it would finish the process, but the machine was still hanging a day later.  I forced the MacBook Pro to shut down using the power button.  Now, when I restart the MacBook Pro, I get the "Mac OS X Utilities" screen asking if I want to Restore from Time Machine Backup, Reinstall Mac OS X, Get Help Online, or Disk Utility.  Does this mean my data is not longer available on the MacBook Pro?  Also, I do/did have the MacBook Pro connected to a Time Machine and it had up-to-date backups at the time I ran Migration Assistant.  However, I noticed that after running Migration Assistant, the MacBook Pro was complaining that it was no longer connect to the Time Machine. 
    My instinct tells me that I should attempt to restore the MacBook Pro using the Time Machine backup, but I'm wondering if it might be able to revive the MacBook Pro without having to take that step.  Or, maybe I should select the "Reinstall Mac OS X" option first?  Any ideas?
    If I need to use the Time Machine backup, do I need to do anything special given the post Migration Assistant behavior I described above?
    Thanks for any advice!

    How can I fool Time Machine into using the original Backup Folder and just doing an incremental backup?
    You can't. after using MA on it you have to start a new backup sequence. you can change computer name in Sharing preferences to anything you like but it won't affect TM backups.

  • Migration Assistant failure - intriguing behavior

    I'm now on my third attempt to run Migration Assistant to reinstall my user account files. On the second attempt, I watched as Migration Assistant copied the files (from Desktop down to Pictures), and then sat horrified as the files quickly disappeared from the screen (in reverse order of how they appeared).
    A little background. This is on a PowerMac G5 running 10.4.10 (the 10.4.10 update may be the reason for this reinstall and restore, btw). A clean install was required b/c the Volume Bitmap could not be repaired. I used Disk Utility to image the hard drive to a external firewire, which I'm using w/ the Migration Assistant.
    The Applications and the Networking Settings were migrated w/o incident, but the user folder was no where to be found after the migration. Observation revealed the mysterious deletion of files.
    Any ideas why this may have occured? I know I can copy the files manually at this point, but I'm truly intrigued by this behavior.
    Many thanks for any ideas you may be able to provide.
    -Val
    PowerMac G5 Duo Mac OS X (10.4.10)

    I used Disk Utility to image the hard drive to a external firewire
    Did you create an image or did you use the restore option? Can you boot with the FWHD? If so, then I suggest that you do another erase & install, but after booting with the install disk, entering your language, select Utilities->Disk Utility and repair the FWHD and repair permissions, quit DU, select Window->Show Log->Show everything, continue the installation, and watch the log while the installation progresses to see what's going on.

  • Migration Assistant can't see my USB ext HD for Time Machine!

    Here is a question for Pondini!
    I've read through many of the threads here, including Pondini's tutorials on how to set-up Time Machine, use Migration Assistant, etc. Alas, I'm not a technical person and have hit a wall.
    Here's the scenario:
    Last week my iMac running Mountain Lion crashed. The hard drive was initially "repaired" using Recovery, erasing all data then restoring the drive from Time Machine backups stored on a Hitachi 2TB Touro USB3 external HD. But soon after the system froze again and a 2nd restore did not work. I concluded that my almost 5 year old HD was gone.
    Where I stand now is that the iMac's HD has been replaced with a new one which came preinstalled with Snow Leopard. I absolutely want (need!) to restored my Mac from Time Machine to get back all my settings and info.
    During the iMac first boot Setup Assistant did NOT see the external hard drive even though they are connected properly. (Note: My older iMac is undoubtedly USB2 but the external HD is backwards-compatible USB3. THAT is the connection, from the external HD directly into the back of the Mac. It is mounted on my desktop and files can be accessed through Finder.) So I then proceeded to set-up my "new" computer with basic settings, which is how I came to see my external HD was properly mounted and connected. I also upgraded the OS on this new HD to Mountain Lion so it would be the same as my most recent Time Machine back-ups.
    Since then I have tried using Migration Assistant to migrate from Time Machine on my external drive but it still does not recognize any drives - Migration Assistant just searches endlessly for other computers. Argh! I've tried all the tips I've read in these forums and none have helped. I scanned my external drive for errors using disk utility but none were found.
    On my external drive there is a folder in the root called Backups.backupdb. Double-clicking it simply opens the folder in Finder, to reveal folders with names familiar to me - the previous HDs computer name, then a bunch of dated folders within that, including a lone file called 2012-08-17-062839.inProgress. I suppose my HD may have died while backing up to Time Machine.
    WHAT do I do?
    Let's say the worst case scenario is that I cannot use these Time Machine backups. Is there any way to root through them for data I can hand-copy to my iMac's new internal drive? It would be grueling but at least it's something. How can I retrieve years of email? Luckily photos, music, videos, etc were backed up manually into a separate folder (also in the root of my external drive).
    THANK YOU!!
    Danielle

    This happened to me after hard drive replacement under the Seagate Drive Recall at the local Apple Store. Here's what I learned from the process:
    I Wagged the Mac home, fired it up (with naked OS installed at the Apple Store), and it wouldn't see my Time Machine drive with Setup Assistant - not on firewire 800 nor USB. Just a grey spinner that lasts forever. When I try just continuing anyway, it offers me something that looks plausible, but then puts up a dialog about duplicate user name, and no matter what I enter, it always says "that user already exists". So I think - maybe Migration Assistant. Complete the setup, create an account, watch the nice welcome movie. BAM - there's my Time Machine drive on the desktop. OK - it has to work . . . but no. Same behavior in Migration Assistant, plus the new OS offers to start making backups on my Time Machine disk - it's not recognizing it at all.
    So - back to the Apple Store - let the genius figure it out. It turns out there are multiple problems. First, the "genius" who imaged my new machine picked 10.7.2 but my machine had 10.7.5 - turns out, it's not enough just to have right cat. Even a point release older OS may not recognize a newer Time Machine drive. The guy at the desk said "We have images of everything but the 10.7.2 has free iLife in it, so they like to use that one". What the heck? They don't image what you had originally as a matter of sane process?
    Having figured that out, we re-image 10.7.5 at the store thinking we've fixed it. But no - Setup Assistant still won't see the Time Machine drive. Not on USB, not on Firewire. Not in a box, not with a fox.
    So here's the second trick - newer machines have a recovery partion. see: http://www.apple.com/osx/recovery/  Boot with the option key held down, pick that partition, then you'll get a "system restore" option, to restore your whole system from a Time Machine backup. My drive was recognized by the recovery partition restore process when neither Setup nor Migration Assistant would. Obviously, there's something broken in Setup/Migration Assistant.
    Takeaway:
    - if you're getting a drive replaced by Apple, make sure they image *exactly* the same OS you had
    - if Setup Assistant fails, use the recovery partition for system restore
    - Use Recovery Disk Assistant http://support.apple.com/kb/DL1433 to make yourself a recovery thumb drive just in case. With Apple's new "no media" approach to the OS, you're hosed without it.

  • FileVault 2 and Migration Assistant

    Genius at Apple store suggested transfering all my data from my laptop with VF2 turned on (turned it on when I first got it and before putting any data on the SSD) to a new laptop during the set-up prompts when the laptop is first turned on. We did this with a Thunderbolt cable.
    But I wasn't able to turn on VF2 on the new laptop until after the set-up was completed.
    This means my data was transfered to the new laptop SSD unencrypted. So if I turn on VF2 now, the data was written to the SSD already.
    1) What are the chances it could be recovered off the SSD itself if stolen or whatever? I have ALL my password stored in a Secure Note in my Keychain.
    I should not have listened. I should have finished the set-up, then turned on VF2 on the new laptop and then only transfer the data over using Migration Assistant. sigh....
    2) Also does the Migration Assistant actually clone the drive from the previous machine onto the new one?
    Clone is not the right word, I am trying to determine whether it transfers 100% of my contents?
    I am asking because I am seeing Max OS X (Mavericks) is reusing most of my settings from my old machine but my printers for instance didn't trasnfer over nor did my settings for the Notification Center. Perhaps that's a bug/ unintended behavior and those should have transfered over also.
    Thank you in advance for addressing 1) and 2) for me.

    In that situation you would get another machine, connect the encrypted TM disk, restart holding down 'command' and 'r' to get into the recovery disk. You install the OS from the recovery partition, then restore from the encrypted TM so long as you have the FV2 password to unlock the disk.

  • Migration Assistant in Lion won't recognize Time Machine backup from Snow Leopard

    I just got an iMac with Lion. I am trying to use the Migration Assistant to move my files/apps etc from a Time Machine backup to the new computer.  The MA will not recognize the backup drive - (external firewire 800).  I can see the backup drive on my desktop but it does not show up as an option to choose in the Migration Assistant.  Any idea what might be wrong.  The backup is from an iMac running Snow Leopard and all the system software was last updated on Dec 9th. It think it is as current as I could get with Snow Leopard. Any ideas what is wrong? 
    Thanks,
    Chad

    This happened to me after hard drive replacement under the Seagate Drive Recall at the local Apple Store. Here's what I learned from the process:
    I Wagged the Mac home, fired it up (with naked OS installed at the Apple Store), and it wouldn't see my Time Machine drive with Setup Assistant - not on firewire 800 nor USB. Just a grey spinner that lasts forever. When I try just continuing anyway, it offers me something that looks plausible, but then puts up a dialog about duplicate user name, and no matter what I enter, it always says "that user already exists". So I think - maybe Migration Assistant. Complete the setup, create an account, watch the nice welcome movie. BAM - there's my Time Machine drive on the desktop. OK - it has to work . . . but no. Same behavior in Migration Assistant, plus the new OS offers to start making backups on my Time Machine disk - it's not recognizing it at all.
    So - back to the Apple Store - let the genius figure it out. It turns out there are multiple problems. First, the "genius" who imaged my new machine picked 10.7.2 but my machine had 10.7.5 - turns out, it's not enough just to have right cat. Even a point release older OS may not recognize a newer Time Machine drive. The guy at the desk said "We have images of everything but the 10.7.2 has free iLife in it, so they like to use that one". What the heck? They don't image what you had originally as a matter of sane process?
    Having figured that out, we re-image 10.7.5 at the store thinking we've fixed it. But no - Setup Assistant still won't see the Time Machine drive. Not on USB, not on Firewire. Not in a box, not with a fox.
    So here's the second trick - newer machines have a recovery partion. see: http://www.apple.com/osx/recovery/  Boot with the option key held down, pick that partition, then you'll get a "system restore" option, to restore your whole system from a Time Machine backup. My drive was recognized by the recovery partition restore process when neither Setup nor Migration Assistant would. Obviously, there's something broken in Setup/Migration Assistant.
    Takeaway:
    - if you're getting a drive replaced by Apple, make sure they image *exactly* the same OS
    - if Setup Assistant fails, use the recovery partition for system restore
    - Use Recovery Disk Assistant http://support.apple.com/kb/DL1433 NOW to make yourself a recovery thumb drive just in case. With Apple's new "no media" approach to the OS, you're hosed without it.

  • Cannot see latest Time Machine backup in Recovery, Setup Assistant, Migration Assistant

    I was experiencing really slow HD response, and so chose to boot into the Recovery HD and run Disk First Aid.  Disk First Aid said there was an issue and recommended a I backup and reformat the drive and reinstall.  So I rebooted into my main drive, made sure Time Machine had done a backup of the latest files.  Then rebooted into Recovery HD.  Reformated the HD in Disk First Aid.  Then went to Restore from Time Machine Backup.  Under that heading it would only let me restore a system from 6 months ago.  I want restore the latest backup that I verified it had run.  So then I decided to Reinstall the OS and hope that Setup Assistant would see the latest update.  It didn't even see the drive to recover from.  So I skipped it and then hoped Migration Assistant would recognize it.  Migration Assistant recognized the backup drive (Time Capsule) but then wouldn't recognize the specific backup for this machine.  It only saw the backup of a different computer on my network.  So what's going on?  Why won't my computer restore from the latest backup?  Am I going to have to manually restore?  Which would suck considering the number of apps I am going to have to reinstall.  Any help on this issue would be much appreciated.  I am running 10.8.3 on a 2009 13" MacBook Pro w/ 8 GB RAM and a 500GB HD.

    Thank you for your response!
    Thinking out loud:
    Both external LaCie's were were subject to a veriy and repairt process with no errors were found.
    They both mount on the iMac desktop with no problems.
    TM bu's to the LaCie's appear to operate correctly.
    I can easliy and quickely move content to and from them at will.
    Evidence seems to suggest that when entering Migration Assistant(MA), the automatic process of closing all applications save MA, seems to break the iMac<> LaCie connection. Could this be a good lead?
    PONDINI
    "You posted that TM was set to back up only to the LaCies  but the sample you posted below shows a sparsebundle on the TC.  Please clarify."
    LMISES
    My error: That is an old MacBook TM backup(bu)
    PONDINI
    "What were you running before?"
    LMISES
    10.8.3.
    PONDINI
    "Are you sure?  Many folks see what they think is their internal HD, but it's really their backups.  What confuses them is, it shows the Computer and disk name that were backed-up, not the name of the drive the backups are on."
    LMISES
    Please see the screen shot below of what Migration Assistant(MA) presents:
    PONDINI
    "Ordinarily, it's done by excluding the System folder via TM Preferences > Options.  That puts up a prompt, and if confirmed sets an indicator in the .plist that controls backups.  We do have a very few reports of it getting set some other way, mostly on Mountain Lion, but have no idea how."
    LMISES
    Thank you. In my view this is very significant as this behavior, it now appears for me, leaves MA as the only option. Not to value MA vs Recovery objectivly, rather, there are benefits exclusive to each process. As I sit now however, MA fails to recongnise not only the TM bu's residing on both LaCie's; MA fails to recongnise the LaCie's as hardware. 
    PONDINI
    "What's in the sparse bundle on your Time Capsule (in the "Data" folder)?     Double-click the sparsebundle to mount it;  then the "Time Machine Backups" disk image should appear in your Finder sidebar.  Double-click that to open it.  Inside it should be aBackups.backupdb folder just like the ones on your LaCie drives, with similar contents."
    LMISES
    The following screen shots are of the "Data" folder.

  • HT4889 Migration assistant doesn't see my 3TB Time machine it just keeps looking for other computers

    I just did a clean install of Mountain Lion on my iMac and Migration Assistant doesn't seem to see my 3TB Time Machine.  It continuously looks for other computers, and nothing else.  I know the files work because I loaded it on my other MBP and it sees them just fine?  am I just inpatient or is something wrong?

    This happened to me after hard drive replacement under the Seagate Drive Recall at the local Apple Store. Here's what I learned from the process:
    I Wagged the Mac home, fired it up (with naked OS installed at the Apple Store), and it wouldn't see my Time Machine drive with Setup Assistant - not on firewire 800 nor USB. Just a grey spinner that lasts forever. When I try just continuing anyway, it offers me something that looks plausible, but then puts up a dialog about duplicate user name, and no matter what I enter, it always says "that user already exists". So I think - maybe Migration Assistant. Complete the setup, create an account, watch the nice welcome movie. BAM - there's my Time Machine drive on the desktop. OK - it has to work . . . but no. Same behavior in Migration Assistant, plus the new OS offers to start making backups on my Time Machine disk - it's not recognizing it at all.
    So - back to the Apple Store - let the genius figure it out. It turns out there are multiple problems. First, the "genius" who imaged my new machine picked 10.7.2 but my machine had 10.7.5 - turns out, it's not enough just to have right cat. Even a point release older OS may not recognize a newer Time Machine drive. The guy at the desk said "We have images of everything but the 10.7.2 has free iLife in it, so they like to use that one". What the heck? They don't image what you had originally as a matter of sane process?
    Having figured that out, we re-image 10.7.5 at the store thinking we've fixed it. But no - Setup Assistant still won't see the Time Machine drive. Not on USB, not on Firewire. Not in a box, not with a fox.
    So here's the second trick - newer machines have a recovery partion. see: http://www.apple.com/osx/recovery/  Boot with the option key held down, pick that partition, then you'll get a "system restore" option, to restore your whole system from a Time Machine backup. My drive was recognized by the recovery partition restore process when neither Setup nor Migration Assistant would. Obviously, there's something broken in Setup/Migration Assistant.
    Takeaway:
    - if you're getting a drive replaced by Apple, make sure they image *exactly* the same OS
    - if Setup Assistant fails, use the recovery partition for system restore
    - Use Recovery Disk Assistant http://support.apple.com/kb/DL1433 NOW to make yourself a recovery thumb drive just in case. With Apple's new "no media" approach to the OS, you're hosed without it.

  • If Migration Assistant hangs up in the middle of the migrating process what should I do?

    What is the Migration Assistant's default behavior in Lion? About 3/4 of the way through a 10 hr. process of file migration from my old PC to my new Mac Mini the Migration Assistant has hung up on me.I am scared to close it out and start over for the fear that I will have to transfer the whole lot of files all over again. If I do close it out and begin the process again will the migration assistant pick up where it left off or will it indeed start from scratch from the very beginning?

    Kamath,
    If the channel is inactive , it will error out in Integration Engine itself, so u can restart those messages manually.
    Also, lets say the receiver system is not reachable(example JDBC), then what happens? You can find those messages in
    http://host:port/MessagingSystem/monitor/monitor.jsp . In the window left frame choose Received Messages , in the right frame choose Status Not Delivered. Change the time frame and click tab(there is no enter) , u can find list of messages. Now for each message u can find two options Delete, Re-Deliver ,click on Re-Deliver the message, it will go thru.
    raj.

  • Trackpad gestures not working after migration assistant

    I just got a new 13" macbook pro for my wife.  I initially created an admin account for myself and everything seemed fine.  Then I ran the migration assistant to import my wife's account from her old macbook (~3 years old, running snow leopard).  Now some trackpad gestures, like the 2 finger scroll, don't work in her account.  Some do, like pinching and unpinching to zoom.
    I've tried turning all the gestures off in preferences, then turning them back on again, but to no avail - 2 finger scroll doesn't want to work.
    It seems like it must be some old trackpad settings that are overriding the new - her old macbook had the button and did not do gestures.  But I don't know how to get rid of any imported trackpad settings so it will go back to default behavior.

    Same thing happen to me. Had to go into iTunes folder and use old iTL file to get iTunes to open again. But after I did that my iPhone now isn't being recognized by iTunes and it wants me to wipe it. I also can't update to iTunes 11...I'm stuck on 10. It says I should update when I manually check for update but the store says there is nothing for me to download. This is so frustrating.

  • Migration Assistant works...once

    Got a new Macbook Pro, and need to transfer my accounts from my old one (2012 era). Ran Migration Assistant, it demanded I update the old one's OS; done. Ran it again, discovered that transferring files over wireless was a dumb idea (44 hours to transfer everything!). Bought a Thunderbolt cable, ran it again, this time forgot to prune down what to copy (since the old lappy's HDD won't fit in the new one's SSD). Migration Assistant says it was successful, but my account wasn't transferred, and now when I try to re-run it, it gets stuck on "looking for source". I'm guessing it's refusing to "see" the old laptop because it thinks it's already transferred info off of it?
    I can mount the old laptop's drive in Target Disk Mode, in which case it shows up in Migration Assistant. But when given the choice of what to copy off of the drive, the "Documents & Data" section doesn't include my user account; just 0KB worth of "Other files and folders"!
    My data is *right there*. How do I convince Migration Assistant to see it?

    Okay, after further investigation, I turned up this article:
    http://www.hardturm.ch/luz/2014/02/fixing-os-x-10-9-mavericks-migration-from-ext ernal-volume/
    Which explains why Migration Assistant wasn't able to see anything when the old laptop was mounted in Target Disk Mode. Incidentally, this behavior is *deplorable*. Who thought it would be a good idea to unmount external drives before running Migration Assistant?
    Anyway, I'm now finally managing to transfer data over. In another five hours I'll be able to see if it actually worked!

  • Migration Assistant appears to crash

    I've read through several postings around these forums, as well as on other sites, and I'm at a loss right now.
    Source: 2009 iMac 24" running Mac OS X 10.9.3
    Target: Late 2013 iMac 27" running Mac OS X 10.9.3 (delivered today, shipped by Apple two days ago)
    Source and Target are booted, logged in with an Admin user account, and connected with Wired Ethernet (although the behavior noted occurs over WiFi as well).
    Running Migration Assistant on both machines, selecting From Another Mac on the Target, and To Another Mac on the Source.
    After a few minutes, usually between 5-10 but occasionally ~15, the Migration Assistant on the Source appears to crash, and the login window reappears. Just after, the same thing happens on the Target. The Target remains unchanged, and it is clear that no migration has taken place.
    It has continued this behavior despite having done a permissions repair on both target and source. Verify Disk on each machine showed each disk to appear to be Ok.
    Behavior is identical whether selecting all user accounts on the Source, or only one. A search through Console for "Migration" revealed only references to the app not being able to be foregrounded.
    At the moment I do not have a Thunderbolt/FW cable to connect the two together, so that option has not been tried yet (and, for the same reason, haven't been able to test Target Disk mode).
    What other things am I missing, or could I try?

    Bacil wrote:
    Running Migration Assistant on both machines, selecting From Another Mac on the Target, and To Another Mac on the Source.
    Only open and run Migration Assistant on the new machine.
    see > OS X: How to migrate data from another Mac using Mavericks

  • Can I stop migration assistant on my new MacBook pro midway through? What would happen?

    I started migration assistant on my brand new MacBook pro last night and I need to take one of the computers today, either my old dell laptop or the MacBook. Can I stop migration assistant? If so what would happen?

    Link for Download & Install & Setup & Activation problems may help
    -Chat http://www.adobe.com/support/download-install/supportinfo/
    OR
    Some download & install troubleshooting links
    -Comodo Security kills download http://forums.adobe.com/thread/1460361?tstart=0
    -http://helpx.adobe.com/x-productkb/policy-pricing/activation-network-issues.html
    -http://helpx.adobe.com/creative-cloud/kb/error-downloading-cc-apps.html
    -http://forums.adobe.com/community/download_install_setup
    -http://helpx.adobe.com/creative-cloud/kb/troubleshoot-cc-installation-download.html
    -http://helpx.adobe.com/x-productkb/global/errors-or-unexpected-behavior-websites.html
    -http://helpx.adobe.com/creative-cloud/kb/unknown-server-error-launching-cc.html
    -Server won't connect https://forums.adobe.com/thread/1233088
    -AND JUST FOR MAC USERS - Some 10.9.3 links
    -Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
    -more Mac 10.9.3 https://forums.adobe.com/thread/1491469
    -Enable Mac Root User https://forums.adobe.com/thread/1156604
    -more Root User http://forums.adobe.com/thread/879931
    -and more root user http://forums.adobe.com/thread/940869?tstart=0

  • After a Lion clean install, how do I retrieve my data from external back-up? Following Apple advice for use of Migration Assistant did not work creating similar issues leading to clean install.

    After a Lion clean install, how do I retrieve my data from external hard drive?
    Following Apple advice I used Migration Assistant which crashed new system twice which is why I had to clean install Lion in the first place.
    Is there a sure way of doing it?
    I have only a few programs that I will have to install myself and that should not be a problem.
    I just want my data, music and photos back where I can use them.

    Time machine backups. I went to migration assistant a few hours ago and limited my selection to "users", no need for applications, settings and other files.  Stuff started moving over at a fast pace but has now seemed to stall.
    I will let it run overnight as there are lots of songs and photos as well as a few movies.
    If that does not work, then I will go into TM and try restore. I have restored some things in the past such a mail files and it has worked well. 
    The Apple fellow at the store told me to go right into TM, he may have had a point. I'll get it eventually.

  • I transferred data from my external hard drive to my restored Mac Book Pro via migration assistant and now my external hard drive in time capsule has red minus signs. How do I get rid of that without getting rid of any of my data?

    I used Migration Assistant to transfer my data from my external hard drive via Time Capsule to my restored Mac Book Pro. When I now go into Time Capsule I there are red minus signs in the corner of all the folders that are contained in my back up. How do I get rid of this and access my previous back-ups?

    Select the drive and Finder > Get info and at the bottom "ignore permissions on this volume"
    You can copy the files, but the ownership on the files still belongs to the other user account, once your done copying, then perform a #6 Reset Users Permissions and that will set all the ownership to that account.
    ..Step by Step to fix your Mac
    Another method is to copy the entire folder, then change it's permissions.

Maybe you are looking for

  • Does the sequence of Insert/Update matter?

    Dear friends I wanted to know whether there is any difference in results if I change the sequence of Insert/Update statements. For example, if I'm inserting / updating records in a table, normally I write my code as below <code> Begin Insert Into Tab

  • Textedit will not open at all. Why won't it open?

    My Textedit application will not open at all. I double click it in the applications folder and it seems like it will open up but it doesn't. Previous textedit documents will not open either. The application itself is not working. Is there a way to fi

  • Can I run Photoshop CS4 and CS5 on the same system?

    I read somewhere a zillion years ago (right?) that you coould run CS4 and CS5 on the same system but at the time I wasn't even considering it. Run on the same system - not ness to run at the same time Or should I install it on a seperate drive (boota

  • Galaxy S3 won't connect to DI-624 router

    Just bought a new Samsung Galaxy S3 but when I got home found that it would not connect to my Verizon-provided home router (DI-624).  Signal strength is great; it sees the network and tries to connect, but always fails to get an IP address (DHCP is e

  • Cmd.ExecuteNonQuery() doesn't execute

    Hi, I have this code 1; j++)/ Console.WriteLine(@"Please enter" + fields[j]); switch (types[j]) case "int": cmd.Parameters.Add("@inputs" + j, SqlDbType.Int); break; case "float": cmd.Parameters.Add("@inputs" + j, SqlDbType.Float); break; default: cmd