Time Machine and Snow Leopard installation problem

I'm trying to install Snow Leopard, but keep getting an error saying that my hard drive is used for time machin back ups. I have unplugged my external device, turned off time machine, yet this keeps happening. What am I doing wrong? I have been able to install Leopard on the computers that I haven't used time machine.

BusyChris18 wrote:
1) Do I have to do anything special with Time Machine BEFORE I install SL? I have been doing regular backups with TM.
Do a "final" backup and turn TM off.
2) should Time machine disc be off/disconnected when I do the install?
It's safest to eject and disconnect it, "just in case."
3) After I reconnect TM disc after SL install, do I have to "migrate" stuff from TM? OR will it just do a new backup and work like normal from that point forward.
If you do the normal install, there's no migration needed. 99.9 % of everything will be fine. In some rare cases of 3rd-party apps putting things in unusual places, there may be a problem, and you may need to re-enter some 3rd-party app purchase codes.
If you erase the drive, then install SL, then yes, of course, you'll have to transfer your data. There should be no reason to do that, but some folks seem to do it out of habit. If you do that, when your Mac boots up again, you can transfer your data from the TM backups. And if you do that, I'd strongly recommend making a separate full backup on a second external drive, again "just in case," preferably a "bootable clone." CarbonCopyCloner and SuperDuper are the most common. (There was a post here just last week where someone did this, the restore got to 99%, then BAM! the TM disk failed.)
TM backups should just continue normally, although there will almost certainly be a long "Calculating Changes" phase (used to be called "Preparing"). And they've added a progress bar, which doesn't seem to be particularly accurate.
However, it may try a new, full backup. If it does, cancel the backup and do a Restart. That may reset whatever confused it. If not, there's nothing you can do to prevent it.
4) Will I be able to access files that were backuped when I have just Leopard?
Yes.

Similar Messages

  • TIme Machine and Snow Leopard

    I'm getting a problem. I updated to SL last week, backed up before I updated just in case. The update went without a hitch.
    I went to do a weekly backup using Time Machine (I had turned off automatic backup under 10.5.x as it was taking over the machine and stopping me working), but could not get it to go past 40Mb before it stalled. This has happenned constantly. When I look at Timemachine none of the previous back-up records are there, and my Finder now seems to crash too.
    I am getting really fed up with Time Machine. It is nearly as bad as a Windows experience, and now with this new OS upgrade it will not work at all.
    I'd appreciate some word from Apple admitting to a problem.

    Philip Grifffiths wrote:
    I'm getting a problem. I updated to SL last week, backed up before I updated just in case. The update went without a hitch.
    I went to do a weekly backup using Time Machine (I had turned off automatic backup under 10.5.x as it was taking over the machine and stopping me working), but could not get it to go past 40Mb before it stalled. This has happenned constantly. When I look at Timemachine none of the previous back-up records are there, and my Finder now seems to crash too.
    Start with the Time Machine - Troubleshooting *User Tip.*
    It will show you how to locate the message(s) that describe the problem, then help you fix it.
    If that doesn't help, post back with details, including all the messages, your setup (especially the destination for the backups), what you've done, and the results.
    It sounds like you were having problems on Leopard, too, so it's unclear just what started when.
    I am getting really fed up with Time Machine. It is nearly as bad as a Windows experience, and now with this new OS upgrade it will not work at all.
    I'd appreciate some word from Apple admitting to a problem.
    Then you need to talk to Apple, not us: this is a user-to-user forum. Call AppleCare, and be sure to tell them what you've done to diagnose and solve your problem, since it doesn't appear to be widespread.

  • Mail, Time Machine and Snow Leopard

    When I upgraded to Snow Leopard (fresh install), I exported my Address Book to a backup file. After the upgrade, I imported the backup to Address Book and all was well. However, I see that time machine freezes when looking for Address Book history within Time Machine. I see many days of backups for AB, but TM won't let me move back in time to see them. Also, when looking at AB in TM, I can't exit TM. It basically freezes. This only happens with the Address Book and TM.
    Any solutions?

    Here is the log:
    2/2/10 1:04:30 PM com.apple.backupd[432] Network destination already mounted at: /Volumes/MyBook
    2/2/10 1:04:31 PM com.apple.backupd[432] Disk image /Volumes/MyBook/R.sparsebundle mounted at: /Volumes/Time Machine Backups
    2/2/10 1:04:32 PM mdworker[364] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
    2/2/10 1:04:33 PM Address Book[391] * -[NSCFString substringWithRange:]: Range or index out of bounds
    2/2/10 1:04:35 PM Address Book[391] CoreAnimation: ignoring exception: * -[NSCFString substringWithRange:]: Range or index out of bounds
    2/2/10 1:04:52 PM Address Book[391] * -[NSCFString substringWithRange:]: Range or index out of bounds

  • HT1277 Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

    Mail has gone crazy. Header's and messages are mixed up. New Mac Book Pro. Migrated files from Time machine running snow leopard. Reinstall or new computer needed?

    Ok; I'm not sure what you're doing.    36 hours is rather long.  Seems like a new migration.  Not what I intended.
    Here's what I intended: from the newly-migrated and apparently-corrupt environment, create a new user, not related to any existing user, nor any migration-created user, or any other user for that matter.  That is, use  > System Preferences > Users and Groups, authenticate yourself by clicking on the padlock, and then click the + and create a wholly new user.  Then log in under that user and establish the mail access.
    36 hours?  I'm wondering if there's an error or an exceedingly slow network here?  Or a really, really slow disk?  Or a sick backup?  (WiFi isn't the path I'd usually choose, either.)
    Failing the attempted second migration, I'd try a different tactic.  Does your existing (old) system work?   If so, I'd bypass the backup and connect an external (scratch) USB disk drive to the (old) sstem and then boot and use Disk Utility booted from the installer DVD disk or boot and use Disk Utility from the recovery partition or booted from a recovery partition created on some other external storage (details here vary by the OS X version and what hardware you have), and perform a full-disk backup of your original internal disk to (scratch) external storage.  (Make sure you get the source and target disks chosen correctly here; copying the wrong way — from the scratch disk to your existing disk — will clobber your data!)  In esssence, this will clone your existing boot disk.  Then dismount the (formerly-scratch) external disk, transfer it over to the new system, and use it as the source of the migration, by performing a fresh OS X installation on the new system.
    Target Disk Mode is also sometimes an option for accessing the disk for a migration, but that requires the right cable, and requires systems that have the same external connection; newer MacBook Pro systems use Thunderbolt for this, and older systems tend to use FireWire.  And I'm guessing you don't have compatible hardware.
    The details here can and do vary by your OS X versions and your particular Mac systems — if you'll identify the specific models and hardware, somebody might be able to better tailor the above (fairly generic) sequence to your particular configuration.

  • Backing up an encrypted drive with Time Machine under Snow Leopard

    In a nutshell, my question is “Can I back up an encrypted drive using Time Machine under Snow Leopard, and if so, how do I access its data from a previous day?”
    I have a 1Tb USB drive connected to my MacBook, which runs Snow Leopard. The drive is formatted as Mac OS Extended (Journaled). This drive is included in the drives that Time Machine backs up. I used Disk Utility to create an encrypted drive on the USB drive (998Gb), also formatted as Mac OS Extended (Journaled). The encrypted drive is not on TimeMachine’s list of excluded files/drives.
    When I go into Time Machine, I can see the USB drive and the encrypted drive in the side bar. I can access the files on the encrypted drive as long as I’m looking at how it stands now. But if I move backward in time, the encrypted drive is grayed out and inaccessible.  If I click on the USB drive, I get a window that tells me it is 75.9Gb in size, and nothing else is available to me.
    When I open the back-up drive in Finder and navigate to Backups.backupdb > macbook name > some date and time, I see my MacBook’s hard drive and the USB drive. The encrypted drive is not shown. When I click on the USB drive, I see an entry for drivename.sparsebundle. When I click on that I’m prompted for the password for the encrypted drive. When I enter it, I get a warning telling me that the disk image could not be opened and that the encrypted drive has no mountable file systems.
    Is my encrypted drive really be backed-up and if so, how do I access the backed-up data? 

    Having received a bunch of views but no replies over the last 5 days, I decided to venture into my local Apple store and ask this same question. The response I got from the geniuses was that you can't get a reliable back-up of an encrypted drive using Time Machine under Snow Leopard. So, my only alternative is to copy the encrypted drive's contents elsewhere, unencrypt the drive, and then copy the contents back. This is what I expected, but not what I wanted to hear.

  • Transfer time machine data (snow leopard) to new mb air (lion)

    MB Pro died. How do I transfer external Time Machine backup (Snow Leopard) to new MB Air (Lion)?

    Your best bet, by far, is to use Setup Assistant when your new Mac first starts up, to transfer your 3rd-party apps, user accounts, data, settings, etc. from the backups.  See Using Setup Assistant on Lion for detailed instuctions.
    If the backups are on a Time Capsule, get a USB-to-Ethernet connector, so you can do this via Ethernet -- it's 2-3 times faster, and much more reliable, than WIFIl.

  • Time Capsule And Snow Leopard - Problems Accessing Files / Folders

    Hi all,
    I am having a problem accessing the time capsule drive and my networked Macs drop boxes etc from the finder. They were working fine, possibly before 10.6.1 and are very intermittent at the moment. If I goto 'go' then 'network', it shows all connected devices fine however accessing them seems to be sketchy. For example, from my Mac Pro upstairs, I can see the time capsule and macbook fine, I can connect to them fine, even screen share with no problems, however when I try to access the drop box, or anything at folder level, I get a spinning type icon in the lower right of the finder by the new zoom bar that just keeps spinning and nothing happens. I have this problem accessing the 'data' folder on my time capsule from both the Mac Pro and the MacBook unless I access it from the drive it mounts on the desktop, I get straight in that way! It's quite infuriating really. Anyone else having this problem? Just to update, I have both Macs connected to the time capsule for time machine and backups are working fine. It would seem that you do eventually get into the folder you try to access, but takes forever for some reason.
    Cheers.
    Message was edited by: Judda

    I couldn't access files on a drive attached to my TC recently, and I fixed the problem by repairing permissions on my main hard drive (the one in my computer.) This option is in Disk Utility. Not sure if that will work for you but it's worth a shot, it doesn't hurt anything! A lot of people recommend repairing permissions every time you update your operating system.

  • Time Machine on Snow Leopard just doesn't work.

    So I've had huge nightmares over the past few days over Time Machine.
    So I've always been a big proponent of Time Machine. I always tell everyone that you NEED a backup solution, and while Time Machine may not be the be all and end all, it's a great starter solution for those that don't want any fuss.
    But perhaps not anymore.
    It just works, right? Well apparently not.
    So a little while ago I performed a Time Machine-assisted hard drive swap for a MacBook (not mine). That is, I install a new drive, boot from SL DVD, perform a HD wipe, then restore from Time Machine. It seemed to go well.
    Fast forward to more recently, I went on a trip overseas (Taiwan). While there, I obviously took a lot of photos, and it became that time again - purchase a new hard drive with more capacity for my MacBook Pro! HD were a little cheaper where I visited, so I not only bought a new drive for my MBP, but also a new drive for my wife's MB, as well as new external drives to upgrade our Time Machine drives.
    While I was there, I decided to update my own Time Machine first - following the instructions from Apple's own knowledge base on the matter:
    http://support.apple.com/kb/HT1427
    I transferred my existing backups to the new drive to continue my Time Machine. I didn't notice any problem at the time.
    Then I returned to my home country (New Zealand). First thing I did when I got back was to perform the Time Machine-assisted HD swap after making sure the OS were up-to-date as were their respective backups, on both my own MBP and my wife's MacBook.
    That's when the troubles started.
    First off, I noticed that a few images from my Aperture Library were missing. The album data and everything were there, but the actual files were not. They also did not exist anywhere on the Time Machine drive and as such never made it over to the new HD. Weird, I thought. They were there, clear as day on my original drive. They simply weren't backed up.
    Now I'm aware of a few TM niggles, such as the false backups after verifying a disk, but I hadn't done that.
    The second issue was much more major. My Wife's MB would be endlessly stuck on the white boot screen with the grey Apple logo. As it turns out, it's exactly this issue here:
    https://discussions.apple.com/thread/2738620?threadID=2738620&tstart=74
    In short, the fresh Time Machine backups I made before transferring to the new HD showed no sign of updating the /System/Library/Framework/Security.framework/Versions/A/Security package, which is REQUIRED for the Mac to boot into 10.6.7 (it had an old one from before).
    Great, I thought, but maybe I can fix that by installing a fresh 10.6.7 combo update on the MB via target disk mode.
    No dice. On trying, it goes all the way to the end, and then fails installation. I had to resort to copying over the correct, more recent security package just to get it to boot.
    After booting, what to do? Who knows what other files Time Machine failed to update, and what consequences they would have. After putting back the original security package, I tried updating 10.6.7 again. Nope, no dmgs would open - i HAD to use the new Security package for anything to open. Fair enough, but even with that, the installation would inevitably fail.
    Problem with the package? Nope. Tried a fresh download, and checked the SHA and everything.
    Time to do some blitzing. I pulled out my trusty Snow Leopard DVD and did a reinstall on top. That's gotta get my problem, right? Well, nope. After resetting to 10.6.0, the 10.6.7 combo updater STILL failed on installation. Furthermore, the updater no longer worked on MY MBP either.
    What gives?
    As it turns out, it was related to this:
    https://discussions.apple.com/message/11317470?messageID=11317470
    In short, some files had the user immutable flag switched on, preventing changes from being made to those files (manifests as a little lock icon on the file icon). They included (and I'm sure not limited to) the Acknowledgement.rtfs in /Library/Documentation/, as well as a majority of the fonts in /Library/Fonts.
    Checking back in the backup drives, it was clear that Time Machine was the culprit - instances of those files in the backups were also locked. When did that happen? Looking back, it looks like it happened when I transferred the backups from one Time Machine drive to another. But it wasn't all at once - in the first backup on one drive, one of the Acknowledgement.rtf files was locked, and the other one wasn't, but in the second onwards, both were. It was clear that Time Machine seemed to be doing it to those files. Which files and why? I have no idea.
    So removing the uchg flag with "sudo chflags -R nouchg /" in terminal finally allowed me to apply the 10.6.7 combo update without failure.
    So were the troubles over then?
    Nope.
    While checking if everything was fine, I noticed iPhoto on the MB had all the thumbs missing - after rebuilding, they weren't back, and only a .plist trashing fixed it (I consider this pretty normal - probably looking for the files on the old UUID drive or something).
    But what gives? ALL the photos taken on the trip were gone! Not just the thumbs - the actual files were missing from the iPhoto Library! The data in the albums existed, just the actual files, just like my instance in Aperture on my own MBP.
    Checked the Time Machine - again, it was clear Time Machine had completely stuffed up - the files were nowhere to be found on the Time Machine drive.
    So currently, I've returned the original internal drive to the MacBook, performing a FRESH on new reformatted disk Time MAchine, and will use THAT to restore.
    Nightmares, indeed. It's several days of work doing all the restores, considering I have limited drives to work with. And yes, rest-assured, I was doing enough permission repairs, and PRAM resets to ensure they weren't issues.
    It occurs to me there are several faults with the most recent version of Time Machine (maybe 10.6.6 or something as that's when people had some of the issues above):
    1) At some point in time, Time Machine may not update a necessary Security package (and probably other files too - I believe the files around it were also not updated), meaning that if you use that Time Machine to restore, the outdated package will cause your computer to fail to boot.
    2) Transferring your backups to a new destination Time Machine drive may cause certain files to become user immutable or 'locked', with one consequence being you cannot update the OS.
    3) Time Machine may fail to backup image files with the Aperture or iPhoto Library. Trying to remember back, I *think* this may be related to the fact that we changed time zones, as the unupdated image files were after the zones were changed. Strangely, every other file within the Library packages were updated, as album data was updated - just not the actual image files and folders.
    Conclusion? I no longer trust Time Machine. The basic foundation of a backup service is that you trust it to do what it's supposed to do. After all this, how can I?
    You might think they are isolated incidents, but they were occurring on two Macs that I have, and they same errors can be found in others.I think I have detailed some root causes, but who really knows.
    At any rate you should keep an eye on at least these files I have detailed. Would love to hear Pondini on the matter, as I know he knows a lot about Time Machine.

    Someone has suggested just installing Snow Leopard on the machine. Will that work?
    If you can find a copy of the workstation version of Snow Leopard shipped with the same model of Mac mini, yes. Apple has not, to my knowledge, shipped a retail version of Snow Leopard new enough to boot your mini.
    I've also heard there is a way to install SL while connected to my old Powerbook in order to suck the entire old drive onto the new machine in an operable manner. Is this accurate, and can this be done if my old machine is the Powerbook on the old apple chip when the new machine is intel based
    No, it's not accurate. The OS on your PowerBook will not boot your mini.
    what are the differences between the single pack and the family pack?
    If you mean single and family pack of Mac OS X, the single pack is licensed for installation on one computer only, while the family pack is licensed for installation on up to five Macs.
    Regards.
    Message was edited by: Dave Sawyer

  • Corrupted user account on Time Machine- recovered Snow Leopard

    After changing the hard disk on my macbook and recovering my user account on afresh Snow Leopard installation, it seems the account got corrupted and now I can't repair permissions and some programs aren't working properly (Manga Studio can't export images, for example)...
    Is there any way to fix this besides reinstalling everything and creating a new user (which would mean losing all my mail messages and keychain info)? Is there a proper way to backup (at least) the keychain info?

    Carlos CD wrote:
    I used the setup assistant, so there wasn't another user account when geting the old one from Time Machine
    Rats.  I was hoping it was the other way, which we could probably fix fairly easily.
    There are a couple of possibilities:
    The backups might be corrupted.  You might want to try repairing them, per #A5 in Time Machine - Troubleshooting.
    If that finds and fixes things, a full system restore (per #14 in Time Machine - Frequently Asked Questions) might solve the problems.
    If not, why did you replace the HD?  If it was failing, it might have corrupted some things, and the damage got backed up.  So Setup Assistant would have brought the damage right back.  A possible fix for that would be to do a full system restore from the backups, but select an earlier one (Setup Assistant doesn't give you a choice -- it automatically uses the latest one).
    Oh, and I'm really sorry if I'm a bit vague on the details: I'm an absolute noob!
    Not a problem.  Nobody was born knowing all this stuff! 

  • Time Machine to Snow Leopard not working

    Ok, so this issue appears to be multi-faceted so please bear with me as I try to fully explain what's happening.
    I have a mid-2009 Macbook Pro with OSX 10.6.8, and I decided to give Yosemite a try since it was free. Before upgrading, I did a Time Machine backup on an external 500GB WD drive in case I wanted to switch back to Snow Leopard.
    I did the upgrade, but wasn't very pleased with the results. Seeing as how the computer was older I figured it would slow down a touch, but what broke the deal was when I tried to run After Effects and had plugins - that never gave me trouble before - crashing. I decided to restore from Time Machine and rebooted into Recovery Mode. However, by accident I selected the External Drive with the backups as my boot disk. I quickly rebooted AGAIN and selected the Recovery drive, but the TM drive wasn't showing up when I tried to access it for the backup.
    I rebooted back to Yosemite and found that the drive was not mounting despite lighting up and making spinny sounds. Disk Utility could see it but was unable to repair, so I used DiskWarrior instead. Everything seemed to work out ok and the drive was reading on my desktop as a TM backup. I rebooted AGAIN to recovery mode, selected the appropriate backup, and let the computer do it's work overnight.
    When I woke up in the morning and checked in on it, I got an error message saying that the restoration had FAILED at some point along the way. I tried to reboot normally, but the grey screen of death would appear after a few seconds and I'd have to shut down.
    I went back to Recovery mode, tried to access the TM drive, but once again it was not showing up! So I reinstalled Yosemite and was able to login to my desktop. The TM drive was still showing up, and according to a reinstalled DiskWarrior the drive was fine. I rebooted in Recovery, selected the TM backup, and it only took about 20 minutes before the restoration failed! This time the computer appeared to be wiped clean, with no OS.
    Fortunately I still had my Snow Leopard install DVD, so I managed to reinstall it from there. However, now I CANNOT login. My username shows up but the password I've used for FOUR YEARS is constantly rejected. I can't even login to the GUEST account!
    If you've made it this far, PLEASE HELP!!!!

    Pondini - I have an issue too. And so I went to the troubleshooting tips you listed here and was not able to find a solution. Specifically, I don't get a message. I plain ole don't get nothing. After I installed Snow my first backup failed. Funny thing is the backup on my wifes computer also failed. She does not have an Intel Mac. It's a PowerBook G4. Hence no Snow Leopard there. I have a iMac 24 Aluminum. My Time Capsule backup worked fine until Snow. My TC is wired via ethernet. There is no latest date. When Time Machine backup starts the TM preference pane says it's "Making disk available" Something to that effect. And that's where it stays. If I then try to do anything with the preference panel - like close it - I find out the Preferences are not responding. So I force quit. I try to stop Time Machine backups and it's no good. The TM indicator - that little backwards running clock - in the menu bar just keeps on it's merry little way. The only way to stop it - shutdown. Strange thing is shutdown then refuses to - well, shutdown. I end up having to hold the power button for 5 seconds. I don't get error messages. I get nothing indicating what may be causing this problem. I have been searching these and other forums looking for an answer. I had hoped the user tips you listed would have a solution, but, alas, no. I deleted the timemachine plist in the "higher" library. No luck. I have powered down everything. No luck. Those were two ideas I saw that said they worked. So where do I go from here? Where do I look for error messages that will point me in the right direction? I'd appreciate any help from anybody.

  • Restoring from time machine in snow leopard

    I recently sold an iMac on ebay. It was an iMac 10,1 with OSX 10.8.4 I purchased the Snow leopard discs from apple and rebooted the computer using those...
    The buyer recently sent me a message on ebay saying this:
    "I have been trying to restore my backup via Time Machine, and the instructions tell me when the Installer disc opens to click on Utilities, then choose Restore System from Backup.  But when I click on Utilities, it asks me to Restart, everytime.  Do you know if I am doing something wrong?"
    Can someone hepl me/him?

    Instead of restoring his/her backup from the OS X disc, install Mac OS X. After installing Mac OS X, it will ask you to restore files, so follow the steps

  • When I try to enter a time machine with Snow Leopard backups Lion I get an error code -6584 ... how to fix?

    Hi.
    I had a first gen time machine with backups all on Snow Leopard.
    This died (power supply), and I bought a new time capsule, because to fix the old one would cost nearly the same amount.
    Since, I have started using Lion, and backed up onto my new time capsule in Lion.
    Unfortunately, there was a file I deleted that I really need for a Logic Audio project, that is only present on the old time capsule.
    I got the old time capsule fixed, so it powers up. I even extended my current wireless network with it. I can see inside it -- all the data that I dragged onto its HD in the past is present, and the "Sparse Bundle" containing the data for the time capsule save-states is present too.
    Now, when I try to "Enter" my old time capsule, I get this error message:
    I tried entering the time machine via WiFi and via ethernet, to no avail.
    Can anyone help me to access these old save states on my old "snow leopard" time capsule?
    I was thinking maybe I need to try to access it from a machine with Snow Leopard?
    Please help.
    Thanks in advance.
    JM

    I have the same issue. Does anybody know why this has happened

  • Recent Time Machine and Airport Leopard update causes Kernel panic

    I had 15 iMac's in a classroom that were all updated to the new Leopard update for Time Machine and Airport. When they restarted, they all gave a kernel panic error. Successive restarts continue with the screen starting with the kernel panic error message and asking for a shutdown.
    I am extremely sure that it had to be those updates because they were all fine before that. I doubt 30 pieces of RAM could have gone kaput all at once. Since we have a dual boot setup, if I press the alt key when I restart, I can boot into the Windows side without any problems.
    If somebody has had a similar problem and found a way to do something about the kernel error, please let me know. Thanks in advance. I did the usual zapping RAM and stuff. It didn't help.

    More information - from the crash report:
    Tue Mar 25 11:23:14 2008
    panic(cpu 6 caller 0x001A8C8A): Kernel trap at 0x004095b9, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x00000018, CR3: 0x00d7b000, CR4: 0x00000660
    EAX: 0x00000000, EBX: 0x0bb2c200, ECX: 0x00000000, EDX: 0x0c0915a0
    CR2: 0x00000018, EBP: 0x82ffbcc8, ESI: 0x0c09de00, EDI: 0x0c09bfa0
    EFL: 0x00010206, EIP: 0x004095b9, CS: 0x00000008, DS: 0x00000010
    Error code: 0x00000000
    Backtrace, Format - Frame : Return Address (4 potential args on stack)
    0x82ffbad8 : 0x12b0f7 (0x4581f4 0x82ffbb0c 0x133230 0x0)
    0x82ffbb28 : 0x1a8c8a (0x461720 0x4095b9 0xe 0x460ed0)
    0x82ffbc08 : 0x19ece5 (0x82ffbc20 0x1 0x82ffbcc8 0x4095b9)
    0x82ffbc18 : 0x4095b9 (0xe 0x10048 0xbbb0010 0x3e0010)
    0x82ffbcc8 : 0x40960c (0xc09de00 0xbbdf900 0x1 0xc09de00)
    0x82ffbce8 : 0x40d648 (0xc09de00 0xc09dd00 0x0 0x3ea76c)
    0x82ffbd38 : 0x40d7fb (0xc09dd00 0x4 0x0 0xb6dde00)
    0x82ffbd58 : 0x84047d77 (0xc09dd00 0xc09dd00 0xbda3760 0x11a1d4)
    0x82ffbdc8 : 0x8404bf21 (0xbb2c200 0x82ffbdfc 0x82ffbdf8 0xbb2c200)
    0x82ffbe08 : 0x8404c236 (0xbb2c200 0x0 0x0 0xbb2c200)
    0x82ffbe28 : 0x8404c2ba (0xbb2c200 0x840555a0 0x0 0x0)
    0x82ffbe48 : 0x40fd82 (0xbb2c200 0xbbdf900 0x1 0x3ea740)
    0x82ffbea8 : 0x411c17 (0xbbdf900 0xbb2c200 0xbbead40 0xbb46300)
    0x82ffbf28 : 0x41147b (0xbbdf900 0xbbb66c0 0x0 0xffffffff)
    0x82ffbf78 : 0x4100f7 (0xbbdf900 0x0 0x82ffbfac 0x1)
    0x82ffbfc8 : 0x19eadc (0xbbddb40 0x0 0x1a20b5 0xb9445d0)
    Backtrace terminated-invalid frame pointer 0
    Kernel loadable modules in backtrace (with dependencies):
    com.faronics.driver.DFXDriver(4.0.1f23)@0x84046000->0x8405afff
    dependency: com.apple.iokit.IOUSBFamily(3.0.8)@0x83483000
    dependency: com.apple.iokit.IOStorageFamily(1.5.2)@0x8375f000
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    9C7010
    Kernel version:
    Darwin Kernel Version 9.2.2: Tue Mar 4 21:17:34 PST 2008; root:xnu-1228.4.31~1/RELEASE_I386
    System model name: MacPro2,1 (Mac-F4208DA9)

  • Snow Leopard Installation problems

    What can I do if the Snow Leopard installation isn't completed, returning message " Installer couldn't replace system documents"?
    I tried once, and system returned me the message above. So I restarted and tried installation again, but first I formatted the HD with the Mac os x Journaled file system. the I retried, but the installation didn't go to an end, returning the same message.
    I'm stucked with a 2009 Macbook Pro. Before I tried installation, suddenly stopped working, booting it with no success, ending with a white wide screen.
    Any ideas?
    Many Thanks.
    Ricky

    Oh, it was the +File Open+ dialog, not a web browser window, is that correct?
    Since you installed Snow Leopard as an upgrade over your existing system, and logged in to your existing user account, you may have had a +Login Item+ (processes that start and run at login) that needs to use "Events.app" (or maybe Events.app itself was the Login Item).
    If you log out and log in, that message should pop up again, if it is related to a Login Item.
    To see your Login Items, go to System Preferences Accounts pane +Login Items+ tab. The list you see are your Login Items. If you see anything that you no longer need, you should remove it. Look for something that may be related to this "Events.app" process.

  • Problem with Time Machine, running Snow Leopard

    Hi all,
    Last week I had a new hard drive fitted into my iMac 8,1, after which Snow Leopard was reloaded (10.6.3 from the disc, updated to 10.6.8), followed by the restoration of data via Time Machine from my external hard drive. Whilst my Mac is now running beautifully, I am having problems backing up with Time Machine.
    When I run a backup, it prepares about 100,000 items, then starts to backup, usually about 650mb. It crawls along in kb until it gets to about 1mb, then jumps quickly to the end, but then it adds extra mb on the end. Then it suddenly starts again "preparing x items....." and off it goes again.
    I have tried repairing the backup disc, and it appears to be ok. I even erased it and started again. Time Machine did a full backup (139gb) in about 2 hours, then immediately added another 640mb at the end - strange, but I do at least have a full backup from yesterday. But now, everytime I run backup, it looks for the same sort of figure (650-700mb) and then goes round in circles.
    Any help would be very much appreciated!
    Thanks, David

    Hi Eric
    Thank you for your reply.  Here are the screenshots for each change:
    Having prepared about 95,000 items, the backup of 612mb begins
    14 minutes later a message appears
    Another 3 minutes and another message. You will see from this screenshot that the backup figure has changed to 613.1mb
    Another 30 seconds and it all begins again....
    And finally, 7 more minutes pass, another 96,000 items are prepared, and another 604.8mb backup begins.
    I might add, that between posting this morning, and your reply, I also went into disk utility, chose the top leve of the external drive, clicked on the partition tab, charged current to 1 partition, renamed the drive, erased it, and did a full back up of 139GB. After 137GB it started again, looked for 602mb, backed them up and finished the backup, which is why TM states that the last back up was at 18:16 today.
    Thanks again
    David

Maybe you are looking for