Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases Mac OS X 10.5.7 and Safari Updates
- Thread starter Doctor Q
- Start date
- Sort by reaction score
Is it fine to install the combo even after the normal? Or is that overkill/will waste memory
It's hard to say. Here is what I do anytime I'm doing an OS update.
1) Time machine backup
2) Download Combo update from Apples site.
3) Run disk verify /repair
4) Check permissions and repair if needed.
5) Shutdown machine
6) Disconnect all peripherals (except ones you need like keyboard, mouse, etc.)
7) Restart machine
8) Install update
9) check permissions again (there were a few errors after 10.5.7 install)
10) Reconnect peripherals one at a time.
11) Check for any other software updates after the OS update (like Safari beta this time)
I've never had an issue at all. It might be fine if I just installed without doing any of this, but I like to be sure the machine is in good condition before I start. If the disk has errors, it's possible to have install problems. Having external devices attached can cause a hick-up too.
anyone noticed how since after the update bluetooth cant be turned off.
for me the option is greyed out...wierd
for me the option is greyed out...wierd
Updating from 10.5.6 to 10.5.7 was very smooth for me on my late 2007 24" iMac. I haven't updated my Macbook Pro yet. I'll do that the next time I take it out and use it (the Macbook Pro, that is).
Two systems updated just now. My mini locked when installing safari, rebooted, reinstalled safari, bada bing.
The Imac had zero issues.
Used the combo for both though, just in case.
The Imac had zero issues.
Used the combo for both though, just in case.
System Preferences Bar
Hmmm. After installing the combo update, I have an issue where the System Preferences window (after I enter any preference pane), loses all of its buttons in the top bar. If I randomly click where I believe a button is, it returns and works.
I've seen that behavior in the menu bar before, but never in a window bar. And never consistently like this.
Hmmm. After installing the combo update, I have an issue where the System Preferences window (after I enter any preference pane), loses all of its buttons in the top bar. If I randomly click where I believe a button is, it returns and works.
I've seen that behavior in the menu bar before, but never in a window bar. And never consistently like this.
i just noticed that with my new Mac Pro I didn't get the new energy Saver icon until I used the combo update.
I let SU do its thing in the background and installed the update last night (200-odd MB version). After the usual dual-reboot, I have no problems.
I don't have the new energy saver icon, however. Odd. Any way to have that pop up without going through the hassle of installing the combo? Everything's working fine so I have no interest in re-installing, this is just a curiosity.
It will have no adverse effects. Also, you can uninstall developer tools after. I'm not sure about the flickering. I don't think I've ever experienced that before.
Good luck. It should work. I used this method to stop horizontal tearing in Safari.
I don't know how to explain it but when I scroll in safari or mail the screen flickers a bit, maybe it tearing, But I'm not really sure what screen tearing is.
It only occurs when using the 9400m and when I am not connected to my 24 inch Apple LED display.
Its almost as if it can't keep up with the speed of the scrolling. There are lots of post about this but there doesn't seem to be any resolution.
I tried the developer tool thing, and assuming I did it right it didn't work for this. Any way to verify the force sync actually stuck?
Hmm... That doesn't sound like screen tearing to me. The Quartz Debug trick probably won't work for that. It only cures screen tearing.
Well that sucks, any one got any remedies for the flicker while scrolling when using the 9400m???
I dig the new CF lamp image.
I got the update from Apple instead of S.U. since I got the corruption error also.
Update went smooth then for my C2D 2.33 20" iMac.
I got the update from Apple instead of S.U. since I got the corruption error also.
Update went smooth then for my C2D 2.33 20" iMac.
bluetooth gone.
i spoke too soon with my update success story.
the 10.5.7 update has made my santa rosa macbook pro forget that it has bluetooth installed. the menu is gone, the bluetooth tab of "keyboard & mouse" in system preferences is gone, and selecting bluetooth in the apple profiler simply says "no information found."
anyone have a fix?
i spoke too soon with my update success story.
the 10.5.7 update has made my santa rosa macbook pro forget that it has bluetooth installed. the menu is gone, the bluetooth tab of "keyboard & mouse" in system preferences is gone, and selecting bluetooth in the apple profiler simply says "no information found."
anyone have a fix?
Just my observation
I went Mac back in Panther. Started reading the Apple forums right away. Panther was brand new.
Since Panther, and Tiger, and now Leopard, it seems Apple has followed a horrific predictable pattern.
In a nutshell, it's this: The first 3-4 releases of any OS are bugridden and unreliable, and give early adopters fits.
Round about the middle releases, X.X.5 to X.X.6, they get stable. Finally.
Then the following releases are all nightmares, UNTIL THE VERY FINAL RELEASE, which usually comes extremely close to the release of the new OS.
Now, whether you want to blame this on Apple rushing in all sorts of hooks for the new OS in the old OS, or absolute malfeasance (screwing up the later releases on purpose to make more people buy the new untried unreliable versions when they first hit the market) the conclusions are the same:
1. STAY AWAY FROM ANY NEW OS RELEASE until midterm. This is an absolute must.
2. STAY AWAY FROM ANY NEW OS UPDATE until the very final version is released. Ignore everything after the stable midterm release until the final version is released.
3. Then STAY ON THIS VERSION until the new version is at midterm.
If you follow this procedure, as I have from the very beginning, you'll avoid being an unpaid beta-tester for Apple. With the accompanying disastrous consequences.
As for me personally, I'm still not even remotely interested in Leopard, yet. In fact, I probably won't bite the bullet on it until Snow Leopard is released and I can be assured they've gotten out all the bugs out of Leopard and the pre-Snow Leopard disaster releases (like THIS one) are finished.
This strategy also makes sure that all 3rd party drivers have been caught up as well.
For what it's worth.
P.S. I'm not even running Spotlight via Spotless, so in that way I'm still on Panther, even though I'm on 10.4.11. My hard drives thank me.
I went Mac back in Panther. Started reading the Apple forums right away. Panther was brand new.
Since Panther, and Tiger, and now Leopard, it seems Apple has followed a horrific predictable pattern.
In a nutshell, it's this: The first 3-4 releases of any OS are bugridden and unreliable, and give early adopters fits.
Round about the middle releases, X.X.5 to X.X.6, they get stable. Finally.
Then the following releases are all nightmares, UNTIL THE VERY FINAL RELEASE, which usually comes extremely close to the release of the new OS.
Now, whether you want to blame this on Apple rushing in all sorts of hooks for the new OS in the old OS, or absolute malfeasance (screwing up the later releases on purpose to make more people buy the new untried unreliable versions when they first hit the market) the conclusions are the same:
1. STAY AWAY FROM ANY NEW OS RELEASE until midterm. This is an absolute must.
2. STAY AWAY FROM ANY NEW OS UPDATE until the very final version is released. Ignore everything after the stable midterm release until the final version is released.
3. Then STAY ON THIS VERSION until the new version is at midterm.
If you follow this procedure, as I have from the very beginning, you'll avoid being an unpaid beta-tester for Apple. With the accompanying disastrous consequences.
As for me personally, I'm still not even remotely interested in Leopard, yet. In fact, I probably won't bite the bullet on it until Snow Leopard is released and I can be assured they've gotten out all the bugs out of Leopard and the pre-Snow Leopard disaster releases (like THIS one) are finished.
This strategy also makes sure that all 3rd party drivers have been caught up as well.
For what it's worth.
P.S. I'm not even running Spotlight via Spotless, so in that way I'm still on Panther, even though I'm on 10.4.11. My hard drives thank me.