Face Time on Macbook (Snow Leopard)

My Daughter is using a Macbook Mid 2009 running Snow Leopard (Lion not reccommended)
Face time 1.0.2 was running fine until everyone she contacts upgraded to Face Time 2.0 now the Face Time window opens but will not connect.
when she calls out nothing happens!
App store says her software is up to date and will not allow her to up grade to Face Time 2.0.
any ideas ??
Thanks
Ian

While we all have MacBooks in this forum not all of us use FaceTime. There's a FaceTime Support Community where everybody uses FaceTime. You should also post this question there to increase your chances of getting an answer. https://discussions.apple.com/community/mac_app_store/facetime_for_mac

Similar Messages

FACE TIME with new Snow Leopard

I am currrently running Leopard 10.5.8 right now and i tried to download FaceTime on my computer...but found out that it doesn't work....because you need to upgrade to Snow Leopard?... so if i get the upgrade.... will it install smoothly? and let me run FaceTime with friends from over seas (Asia) without any problems?...Any issues with FaceTime and running the new Snow Leopard?... I need all the info before running out and buying the upgrade...thanks

Hi,
It is Intel Only (As In only works with Snow Leopard).
Reports here vary mainly because people come here looking for help so it is a some what distorted view. (we never get to here from people who had no issue setting it up).
Some have reported issues trying so set up "accounts" using Apple IDs they already use elsewhere.
This may centre around the issue of using one Email address as th ID/Account emails and using another for people to Call (it's a bit like an Alias situation).
Search for "Facetime" in the iSight Forum
Same for the "Using Snow Leopard" Forum
This is where most have been posted.
8:41 PM Monday; November 29, 2010
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"

Macbook, Snow Leopard 10.6.8 Since the last software update Safari 5.1 will not save history. Prefs. are set correctly, reset has been done, appropriage plist has been trashed, now Saf. 5.1 has been re-installed. Still dumps history every time

Macbook, Snow Leopard 10.6.8. Safari 5.1.1
Since the last software update, Safari will not save bookmarks history.
Prefs. are set correctly, Cache has been dumped, reset done, appropriate .plist trashed, and finally an uninstall and clean install done
with 5.1.1 download from the Apple support site.
The problem still exists, making me very suspicious that this is a bug.
Any solutions? Let's hear 'em.

M. Davis:
Thank you for your kind and prompt solution. It is a winner.
Problem solved, again many thanks and a very fine evening/day wherever you
may be.
~Very best.
cwxpro

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.

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.

I deleted my Mail app sometime back. I reinstalled it again, today, on my Macbook Snow Leopard Mac OS but when I try launching Mail, it says ' You have Mail version 4.0(1075/1085). It can't be used on Mac OS X version 10.6.8(Build 10K549)",

I deleted my Mail app sometime back. I reinstalled it again, today, on my Macbook Snow Leopard Mac OS but when I try launching Mail, it says ' You have Mail version 4.0(1075/1085). It can't be used on Mac OS X version 10.6.8(Build 10K549)",

The Mail version for your machine is 4.6 (1085) You can get it via the Combo updater. Mac OS X 10.6.8 Update Combo v1.1
Then follow with software updates to pick up the most recent security and iTunes updates.

While transferring photos from iPhone 4S (iOs 7.1.1) to iPhoto '09 (8.1.2) on Macbook (Snow Leopard 10.6.8), their geolocation does not pass along.

While transferring photos from iPhone 4S (iOs 7.1.1) to iPhoto '09 (8.1.2) on Macbook (Snow Leopard 10.6.8), their geolocation does not pass along.

How are you transferring the photos? In the iphoto preferences is look up loations st to automatically?
LN

HT3910 Can I use Mac OS version 10.5.6 to install on MacBook Snow Leopard version 10.6.8?

Can I use Mac OS X Install DVD and Application DVD, both version 10.5.6 to install on MacBook Snow Leopard version 10.6.8?
Thank you

Only if those disks are the ones which shipped with the computer. Retail packages never came with an Applications disk. If they are, install them onto a blank partition or drive.
(67924)

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.

TS4268 how to change apple id on face time using macbook air

how to change apple id on face time using macbook air

coolguy1981 wrote:
How can u format the hard drive since I am using the MBA. Formatting will delete also the recovery space and how to start with new installation? This is not going to work.
No, that's not true. This is one of the 'benefits' of Lion (if you want to see it that way). The OS is on a separate partition and you can reinstall the OS without another physical drive.
What you do is reboot the computer while holding down the 'option' key. From the list of disks that show up (you can release the 'option' key now), choose 'Recovery HD'.
When you get to what looks like a Desktop, choose 'Reinstall OS X Lion'. Shortly after this, you will get asked for your Apple ID. Put your own Apple ID in the box and everything should proceed smoothly from there.

Struggling to restore from Time Machine (2007 MacBook; Snow Leopard)

The hard drive failed on my 2007 MacBook. I had it replaced and the shop also installed Snow Leopard (this was what I was using prior to the fail).
I tried a restore from Time Machine and while a huge chunk of my new hard drive disappeared, I couldn't locate the files. I have since found them in the hidden /Volumes folder.
I have also learned that to do a full restore, I should have used my Snow Leopard install disk alongside the drive with Time Machine backups.
So...
1. Should I delete the restored file in the /Volumes folder and start again using the Snow Leopard install disk?
2. I want to upgrade to Lion (this is the furthest I can go with this MacBook). Can I do step 1 using a Lion install disk even though the Time Machine backup was created in Snow Leopard? (Confession: I'm not sure where my Snow Leopard disk is and I'm trying to avoid going through cupboards and boxes to find it)
3. is it laborious and risky to try to restore everything manually from the /Volumes folder? Where do I start if I decide on this route?
Thanks in advance for any advice.

I would try recovering the files manually first. If the result is unsatisfactory, then I'd boot up using the Snow Leopard DVD, run Disk Utility/Repair disk, erase and reformat the drive, and then install Snow Leopard. Reboot normally, and use Setup Assistant to restore from Time Machine. Completely update to 10.6.8 and then consider if you want to upgrade to Lion. There are no Lion disks - it is a download.
10.6.8 Combo Updater

An old macbook running 10.6.8 was restored using Time Machine then Snow Leopard was reinstalled and updated to 10.6.8. Now the machine is slow and repair disc permissions results in a cancelled by user message.

Our old macbook was getting a gray screen with flashing ? on bootup. Eventually I restored it using Time Machine then decided to reinstall Snow Leopard since it would not boot. Machine now boots but is slow. Ran repair disc and tried to run repair disc permissions but got a message that it was cancelled by user.
This machine is at least 6 years old and I just want to limp it along until I can afford to replace it in the spring.

You may be smelling it because with the new OS the processor is having to work harder causing it to get hotter then it would with the other OS. I can't say there is nothing wrong, but what could be happening is just that, it's getting hotter so the fan is spinning faster and moving more air so you are getting more of the smell then you would before. I would still continue to back it up, and take it to the Apple Store at a Genius Bar and have them look at it to make sure. Was the computer ever in a smoky environment??

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

Time Machine in Snow Leopard much better but still problematic

I've found Time Machine backups to a Time Capsule to be much faster under Snow Leopard than under previous versions of the OS, and I've found that TM seems to avoid some of the extra backups that always seemed to get scheduled:
Jan 8 11:27:01 Musa [0x0-0x188188].backupd-helper[3527]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
Jan 10 20:33:34 Musa com.apple.backupd-auto[14230]: Not starting scheduled Time Machine backup - less than 10 minutes since last backup completed.
But the question is, why would Time Machine try to backup less than 60 or 10 minutes after the last backup in the first place?
In addition, TM doesn't always avoid the extra, unnecessary backup:
Jan 11 07:01:29 Musa com.apple.backupd[14508]: Starting standard backup
Jan 11 07:01:29 Musa com.apple.backupd[14508]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:01:37 Musa com.apple.backupd[14508]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:01:39 Musa com.apple.backupd[14508]: Disk image /Volumes/odysseus/Musa.sparsebundle mounted at: /Volumes/Time Machine Backups
Jan 11 07:01:39 Musa com.apple.backupd[14508]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Jan 11 07:01:51 Musa com.apple.backupd[14508]: No pre-backup thinning needed: 1.07 GB requested (including padding), 331.17 GB available
Jan 11 07:03:08 Musa com.apple.backupd[14508]: Copied 9532 files (60.6 MB) from volume Gigas.
Jan 11 07:03:08 Musa com.apple.backupd[14508]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:03:18 Musa com.apple.backupd[14508]: Copied 734 files (201 KB) from volume Gigas.
Jan 11 07:03:19 Musa com.apple.backupd[14508]: Starting post-backup thinning
Jan 11 07:03:19 Musa com.apple.backupd[14508]: No post-back up thinning needed: no expired backups exist
Jan 11 07:03:19 Musa com.apple.backupd[14508]: Backup completed successfully.
Jan 11 07:03:23 Musa com.apple.backupd[14508]: Ejected Time Machine disk image.
Jan 11 07:03:23 Musa com.apple.backupd[14508]: Ejected Time Machine network volume.'
11 minutes later:
Jan 11 07:14:52 Musa com.apple.backupd[14563]: Starting standard backup
Jan 11 07:14:52 Musa com.apple.backupd[14563]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:15:00 Musa com.apple.backupd[14563]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
Jan 11 07:15:04 Musa com.apple.backupd[14563]: Disk image /Volumes/odysseus/Musa.sparsebundle mounted at: /Volumes/Time Machine Backups
Jan 11 07:15:05 Musa com.apple.backupd[14563]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
Jan 11 07:15:32 Musa com.apple.backupd[14563]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:16:30 Musa com.apple.backupd[14563]: Copied 8407 files (1.4 MB) from volume Gigas.
Jan 11 07:16:30 Musa com.apple.backupd[14563]: No pre-backup thinning needed: 1.00 GB requested (including padding), 331.17 GB available
Jan 11 07:16:38 Musa com.apple.backupd[14563]: Copied 510 files (53 KB) from volume Gigas.
Jan 11 07:16:40 Musa com.apple.backupd[14563]: Starting post-backup thinning
Jan 11 07:16:40 Musa com.apple.backupd[14563]: No post-back up thinning needed: no expired backups exist
Jan 11 07:16:40 Musa com.apple.backupd[14563]: Backup completed successfully.
Jan 11 07:16:43 Musa com.apple.backupd[14563]: Ejected Time Machine disk image.
Jan 11 07:16:44 Musa com.apple.backupd[14563]: Ejected Time Machine network volume.
These were the first two backups that occurred after my MacBook Pro had been sleeping all night. Why does another backup happen so soon?

odysseus wrote:
I've found Time Machine backups to a Time Capsule to be much faster under Snow Leopard than under previous versions of the OS, and I've found that TM seems to avoid some of the extra backups that always seemed to get scheduled:
Jan 8 11:27:01 Musa [0x0-0x188188].backupd-helper[3527]: Not starting Time Machine backup after wake - less than 60 minutes since last backup completed.
When OSX wakes from sleep, Time Machine immediately checks to see if a backup is needed. Since one was done less than an hour before, it doesn't do another one. This message is just telling you why it didn't do a backup upon wake. (Under Leopard, it would do one automatically, which some folks complained about. So Apple changed it.)
Jan 10 20:33:34 Musa com.apple.backupd-auto[14230]: Not starting scheduled Time Machine backup - less than 10 minutes since last backup completed.
Most likely, you did a manual backup a few minutes before this. That does not re-set the schedule; but when the next scheduled backup time arrives, TM checks, and if less than 10 minutes has elapsed, resets the schedule and tells you why it didn't do the scheduled backup. Another thing foks complained about under Leopard that Apple changed.

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.

Face Time on Macbook (Snow Leopard)

Similar Messages

Maybe you are looking for