Safari load times slower under Snow Leopard?

Has something recently changed?
Safari used to be very snappy- suddenly pages are taking forever to load.
The first days I ran SL- all seemed fine.
The last few days- major hang-ups.
I have three machines and it happening across the board.

Greetings,
It's probably the Top Sites and Cover Flow features caching all those web pages; that can slow things down quite a bit. And if you don't clear your History before you quit every day, that cache just keeps getting larger. You might want to consider disabling those features and removing their cache of web page preview images.

Similar Messages

  • 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.

  • Is Time Machine under Snow Leopard faster only for the initial backup?

    A few days ago, I upgraded to Snow Leopard -- via clean install, manual reinstallation of apps, etc. So understandably, the first Time Machine backup to a preexisting store on an original 500 GB Time Capsule is going to be huge and take a long time. Apple claims that TM is 40% faster on the initial backup, but are there speed improvements as well? I was surprised by the slowness; I started it before going to bed, and it wasn't nearly done when I woke up:
    http://support.apple.com/kb/HT1770
    Jan 6 01:29:52 Musa com.apple.backupd[438]: Copied 8.3 GB of 59.3 GB, 9299 of 250057 items
    Jan 6 02:29:52 Musa com.apple.backupd[438]: Copied 9.6 GB of 59.3 GB, 35209 of 250057 items
    Jan 6 03:29:52 Musa com.apple.backupd[438]: Copied 11.5 GB of 59.3 GB, 48441 of 250057 items
    Jan 6 04:29:52 Musa com.apple.backupd[438]: Copied 12.9 GB of 59.3 GB, 109846 of 250057 items
    Jan 6 05:29:53 Musa com.apple.backupd[438]: Copied 17.4 GB of 59.3 GB, 140388 of 250057 items
    Jan 6 06:29:54 Musa com.apple.backupd[438]: Copied 26.1 GB of 59.3 GB, 151723 of 250057 items
    Jan 6 07:29:54 Musa com.apple.backupd[438]: Copied 36.9 GB of 59.3 GB, 167431 of 250057 items
    Jan 6 08:20:04 Musa com.apple.backupd[438]: Copied 219433 files (38.0 GB) from volume Gigas.
    The throughput rate is quite variable, but at its best, it's only about 2.7 MB/sec. Is that to be expected, or would I have to start a new backup to see speed improvements?

    Kappy wrote:
    i'd say you are concerned over nothing.
    Not sure I agree. Look at this system.log output:
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 19:54:22 Musa com.apple.backupd[7571]: Attempting to mount network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:30 Musa com.apple.backupd[7571]: Mounted network destination using URL: afp://odysseus@Time%20Capsule.afpovertcp.tcp.local/odysseus
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 19:54:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 19:54:42 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Compacting storage: 72.07 GB requested (including padding), 58.36 GB available before compacting
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:00:50 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:00:53 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:01:12 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:01:14 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:01:20 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:07:26 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.36 GB available
    Jan 6 20:10:46 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-03-131536: 58.42 GB now available
    Jan 6 20:12:10 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-094152: 58.52 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-073331: 58.57 GB now available
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:13:02 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:13:08 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:13:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:13:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:13:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:19:36 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 58.57 GB available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2010-01-04-071252: 58.58 GB now available
    Jan 6 20:20:38 Musa com.apple.backupd[7571]: Removed all 1 expired backups, more space is needed - deleting oldest backups to make room
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-07-31-231155: 60.81 GB now available
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Deleted 2 backups: oldest backup is now Aug 15, 2009
    Jan 6 20:25:17 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:25:20 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:25:24 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:26:39 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:26:41 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:26:49 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.07 GB requested (including padding), 60.81 GB available
    Jan 6 20:32:46 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-15-182619: 65.12 GB now available
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Aug 25, 2009
    Jan 6 20:47:38 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 20:47:41 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 20:47:47 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 20:49:36 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 20:49:38 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 20:49:46 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 65.12 GB available
    Jan 6 20:55:48 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-08-25-185228: 67.32 GB now available
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 1, 2009
    Jan 6 21:05:11 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:05:13 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:05:22 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:06:45 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:06:48 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:06:57 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 67.32 GB available
    Jan 6 21:12:57 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-01-060212: 69.89 GB now available
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Deleted 1 backups: oldest backup is now Sep 8, 2009
    Jan 6 21:25:51 Musa com.apple.backupd[7571]: Stopping backup.
    Jan 6 21:25:53 Musa com.apple.backupd[7571]: Backup canceled.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Ejected Time Machine disk image.
    Jan 6 21:26:00 Musa com.apple.backupd[7571]: Compacting backup disk image to recover free space
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Completed backup disk image compaction
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Starting standard backup
    Jan 6 21:27:30 Musa com.apple.backupd[7571]: Network destination already mounted at: /Volumes/odysseus
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Disk image /Volumes/odysseus/Musa_002332d5c37e.sparsebundle mounted at: /Volumes/Backup of Musa
    Jan 6 21:27:33 Musa com.apple.backupd[7571]: Backing up to: /Volumes/Backup of Musa/Backups.backupdb
    Jan 6 21:27:41 Musa com.apple.backupd[7571]: Node requires deep traversal:/ reason:must scan subdirs|
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: Starting pre-backup thinning: 72.06 GB requested (including padding), 69.89 GB available
    Jan 6 21:33:37 Musa com.apple.backupd[7571]: No expired backups exist - deleting oldest backups to make room
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Deleted backup /Volumes/Backup of Musa/Backups.backupdb/Musa/2009-09-08-081225: 72.34 GB now available
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Pre-backup thinning completed successfully: 1 backups were deleted
    Jan 6 21:45:33 Musa com.apple.backupd[7571]: Backup date range was shortened: oldest backup is now Sep 15, 2009

  • Library Fonts not loading in CS3 under Snow Leopard

    I just noticed this: Most of the fonts in the HD/Library/Fonts folder are not being read by CS3 applications. This includes old favorites like Verdana, Trebuchet, Arno Pro, etc. These fonts are being read by Apple apps like Pages and Text edit. Anyone else having this issue?
    I think a solve would be for me to have my Font Management application load these fonts.
    Details:
    I installed Snow Leopard on a freshly erased drive. Updated to 10.6.1. Installed CS3 Design Premium. Ran the Adobe updates (which was much more difficult than it should have been!)
    Thoughts, ideas, suggestions?

    CS 4 and Cs 3 they load as expected on my Mac Pro? Tr resetting the preferences.

  • PS CS4 seems to run slow under Snow Leopard...

    Hello, this is my first post at the forums.  I just did some tests and am a bit baffled. 
    Scenario:
    Computer 1:
    - New Mac Pro quad xeon running snow leopard and PS extended 10.0.1, 6 gigs of ram with only photoshop running
    - opened a 52"x52" 300 dpi image.
    - cropped image and the cropping took a bit longer than I hoped for maybe about 3-4 min.
    Computer 2:
    - Imac Intel core 2 duo with 2 gigs of ram with PS and AI and other apps running
    - opened same image
    - cropping was faster than the Mac pro.... took about 2-3 min
    Any thoughts?
    Another Scenario:
    Computer 1:
    - New Mac Pro quad xeon running snow leopard and PS extended 10.0.1, 6 gigs of ram with only photoshop running
    - opened a 2.8 gig 300 dpi image.
    - cropped image and got a message saying operation can't be done because out of ram
    Computer 2:
    - Quad g5 6 gigs or ram
    - opened same file
    - was able to crop but it took a while.
    Any thoughts?
    I wanted to see if it's the OS or the Machine but I tried to install 10.5 in the new mac pro and it won't let me.
    Just wanted to share been looking around for any info about app speeds.
    - Nico

    Oops I meant 11.0.1 also to clarify the one running on the imac is PS CS4 standard not extended but the one running on the G5 and Mac pro is Extended.

  • Can Time Machine under Snow Leopard (10.6) backup to a wired drive?

    I have just upgraded to 10.6 and when I try to run Time Machine the wired drive I was using is not visible. So I run Time Machine Setup and it only offers me the ability to setup wireless drives via AirPort. I don't have a wireless hard drive... What am I doing wrong?

    Hi, and welcome to the forums.
    Check the TM drive's *Partition Map Scheme* and Format via the instructions in item #C1 of the Time Machine - Troubleshooting *User Tip.*

  • TIme machine backup made under snow leopard to be used in leopard

    Hi I have just down-graded back to leopard from snow leopard due to problems i was encountering. Prior to re-installing leopard OS10.5 I made a backup of my hard drive with time machine under snow leopard 10.6. now i have tried to restore this hard drive back-up once i had succesfully re-installed leopard 10.5 but it wont allow me. is there any way around this? do the back-ups have to be from same operating systems. any advice much appreciated

    willouk2 wrote:
    What I wanted to acheive was for my macbook to look the same to when before i installed snow leopard, as in with all files in place, apps, desktop etc! so having made a time machine backup in 10.6 I Inserted Leopard disk OSX 10.5, held down the C key and rebooted, formatted HDD, installed Leopard
    There's no point to installing OSX, then restoring +*your entire system+* from backups: "your entire system" includes OSX. The first thing it does (as you're warned on the screen) is erase the HD.
    The message you got was apparently the Leopard installer (on the disc) saying you can't use it to restore a complete Snow Leopard system. But if it had, you'd have been back on SL.
    If you don't have a backup from Leopard, you can't make your system look exactly like it was under SL but with a Leopard version of OSX. Even getting close won't be easy: you no doubt have many files that were created in SL, or upgraded by SL. They're not compatible with Leopard; OSX and Leopard apps may not work right, if at all, with them.
    At this point, you've got two options:
    First (and almost certainly best) is to restore your entire system to the way it was at the time of the backup (by using the Snow Leopard install disc). Then fix whatever problems you were having.
    If you really want to go back, do an Erase and Install of Leopard. When it boots up, and asks if you already have a Mac and want to "transfer" data from it, say no. Set up your first user, etc,. Then download and install the "combo" update to get back to 10.5.8. Info and download available at: http://support.apple.com/downloads/MacOS_X_10_5_8_ComboUpdate Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
    Then reinstall all apps that came with installers (and are compatible with Leopard) from the original discs.
    You'll have to set up all your email accounts, passwords, and other preferences and settings.
    Then you might be able to selectively restore some things from your Snow Leopard backup, but be aware that you may be restoring incompatible versions of files. The behavior of OSX and your apps will be unpredictable at best.

  • Will it work to recover from a Time machine data backed up under Snow Leopard?

    Hello,
    Mine a Mac Book Air that has 2.13 GHz Intel Core 2 Duo and RAM: 2GB 1067 MHz DDR3.
    I have time machine back up on an external HD.
    Once I install the Lion os, would I be able to use the backed up data under Snow Leopard to an external HD if any eventualities on a later date? Data such as photos in Aperture library or folders with Mac version of Windows Office 2008.
    [The time mechine backed up data was under Snow Leopard and my Mac Book Air now has the Lion OS]
    I understand as soon as I upgraded to Lion I should create a new back up with time mechine but in case if that is not done......
    I hope your understand What I mean..
    Regards

    What you propose should work.  There could be problems with data for applications such as Mail where the application version and format of the data changed in Lion.

  • Under Snow Leopard I used a WD My World NAS to back up my Mac Pro (Mid 2010). When I upgraded to Lion I am unable to access the backup because the NAS does not yet support AFP. I have now bought a Time Capsule and want to transfer the old backup onto it.

    Under Snow Leopard I used a WD My World NAS to back up my Mac Pro (Mid 2010). When I upgraded to Lion I am unable to access the backup because the NAS does not yet support AFP. I have now bought a Time Capsule and want to transfer the old backup onto it.
    How can I recover the NAS back up to put on my new Time Machine.
    Talking to Apple Support Adviser was a waste of time on case number 239647273
    Any thoughts or pointers?

    Keep the old OS around and just kick the tires and test new OS. Apple has a history and habit of breaking support in things like this.
    You can use TimeMachine as one level of backup, and even there there were changes with Lion, I would always recommend foremost backup clones of every volume. And clone (SuperDuper etc) can be stored on something like HP NAS Media Server which also was supporting TimeMachine, iTunes - until Apple made that harder and more their own proprietary format.
    Apple AirPort Time Capsule Support
    Lion Communities
    Cloning as a Backup Strategy
    Rather than "upgrade" I would clone the system, and do a clean install, then allow Setup Assistant to import your files.
    Others who are asking the same question:
    http://www.bing.com/search?q=mac+os+x+lion+WD+My+World+NAS

  • HP OfficeJet Pro 8500 Wireless second paper tray under Snow Leopard

    He there, I have a strange problem with the second (extra) paper tray from the Office Jet Pro 8500. I have setup the tray and activated the option on the driver page on the computers, but no results. No paper is loaded from the tray and there is an error that no paper is loaded in the machine. The printer is connected via ethernet (and a time machine) and I am running snow leopard on all the machines that are connected to the printer. I have installed the latest drivers from Apple and from HP. I know that the paper tray is working, because when I make a copy on the machine localy and force him to use papertray number 2, then there is no problem.
    Does anybody have the same problem?? Thanks

    I also just tried connecting my 8500 wireless printer directly via usb and then downloading the HP printer drivers from Apple downloads and reinstalling.
    The install hangs nearly forever on the final step, but eventually says the driver install was successful. However, then when connected via usb, I am unable to print. Printing works when you reconnect via the wireless on the 8500.
    So connecting via usb and reinstalling HP printer drivers does not solve the issue. And it's puzzling, because the list of supported printers under Snow Leopard lists the Officejet Pro8500 Wireless as supporting both printing and scanning.
    Somebody has it wrong.
    If this scanning problem continues very long, I may be forced to uninstall Snow Leopard, because my printer is brand new.

  • Font problem with MX under Snow Leopard

    Anybody know what might cause an app built with Director MX not to display an installed (not embedded) custom font under Snow Leopard?
    The program was built quite some time ago but was tested under previous Mac OS X.x versions and worked fine. What might have changed that could cause this problem?
    Complicating this is that I don't have Snow Leopard myself to test it directly, but here's what I do know:
    The font is definitely installed and available to other apps.
    Everything else about the app works fine.

    I noticed the same jumbled text problem.
    When I went to look at Font Book, I see that those fonts are no longer installed. It must've happened when I loaded Snow Leopard last weekend.
    Anyway, I went to reinstall fonts, and I see I've got a bunch that got uninstalled. But when I try to reinstall them, like Calisto and Caligula to name the first couple I tried, Font Book reports that there were serious errors when trying to load them.
    Does anyone have insights into the vague message: "System Validation" as the serious problem? I don't see a way to get more details about the problem than that.

  • Why is Safari running so slow under Mountain Lion?

    Why is Safari running so slow under Mountain Lion?

    I have other mac's on my home network that are still running Snow Leopard and the are performing well. I wanted to use the iCloud so I upgraded and instantly started experiencing the slow down, to the point of ridiculousness. Other function are mixed some normal speed, others a day on the beach with the spinning ball. Firefox is at full speed, good thought, haven't checked Chrome yet.
    Last night and hooked into a projection unit that adjusted my screen resolution for a presentation and after the event my Mac reset back to the normal settings and Safari launched and is running normal speeds so far. In the past there have been issues with performance speeds and certain resolutions, has anyone had similar luck or is this a fluke?

  • Front Row Incorrectly Reads iTunes Metadata under Snow Leopard?

    There is a serious problem with Front Row under Snow Leopard. The program is unable to correctly read the TV metadata from iTunes and does not correctly filter/organize the data. TV episode/season/title data is not read resulting in a completely disorganized library. All files are viewd as "movies" whether they have been tagged as TV shows or not. I had a sizable libray of videos that was perfectly organized under Tiger. Under Snow Leopard my entire database has been blown up- most TV shows appear as "Untitled". I'm sure they are MacMini users who have integrated their computers into their media playback systema s I have and am hoping Apple will provide a fix for this issue which totally undercuts one of the main reasons for integrating the Mini into one's home theatre system. Does any have a fix or simple work around. Come on Apple-- don't turn into Microsoft on me!

    I recently purchased a used iMac (from 2006), that the previous owner had upgraded to Snow Leopard. I already have a MacBook Pro. To explain, I purchased the iMac to set it up as a media center computer, connected to my external hard drive and synced with AppleTV. I used Migration Assistant to move my files onto the iMac, but Front Row is now showing all the errors you described.
    1. It is VERY slow to open. Clicking Menu on the remote, and you wait 15 seconds or more for Front Row to open.
    2. Even though iTunes is directed to my external hard drive, Front Row shows Source as my Macbook Pro.
    3. TV shows are out of order. On my Macbook Pro (10.5.8) all shows are listed from first to last, from top to bottom. On the iMac (10.6.4) they are listed last to first, top to bottom.
    4. Some TV shows that are clearly in iTunes (purchased from iTunes) do not appear in Front Row at all.
    5. The unwatched content blue dot remains even after watching something all the way through to the end. After watching them in Front Row, iTunes does not show them as watched either, but instead has the half blue dot, as if they were unfinished.
    6. iTunes is also badly affected: I now have a large number of TV shows in the Movies section, and attempts to reorganize them in the folders on the external where they are store fails. It's a complete mess, and it seems like its deliberate that we cannot reorganize it ourselves.
    So what used to be a very lovely program has become a horribly messy, PC like, application. Which made the whole point of setting up a special computer just for media a total waste of time and money with Snow Leopard installed.
    If a fix is not forthcoming, I'm probably going to uninstall Snow Leopard, and reinstall Leopard. Everything worked fine there for me.

  • 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.

  • 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.

Maybe you are looking for