Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
The only issue I was having with 10.5 was that Dashboard crashed after my Powerbook awakened from sleep. Sometimes it would crash a couple of times after that. It seems to be ok now. Although, there was one widget I removed before the update that could have been the culprit.
 
I still can't get passed the setup assistant. I did disk repairs from the Leopard DVD but it didn't help. I have no idea what to do. My Macbook is pretty much useless as is.

Does anyone have any suggestions on how to fix this problem? I'm literally going insane and am worried I've totally ruined my mac.

My iBook G4 was doing this, kept rebooting and loading up the setup assistant. I managed to quit the assistant from the menu, which took me back to the login screen. Then I restarted and it installed the update correctly then (installer thingy came up), now it seems to be fine. Thank god.
 
Yep, I was always aware of that tiring waste of time. Yeah, it's irritating if not time consuming to hold down on the mouse button waiting for that whereas Stacks is instant.

Um... so doing less quicker is good... Oh well... some things sometimes just defy logic.
 
...

Specifically, Apple claims that the GeForce FX 5200 GPU used in the 12" powerbook is missing support for a certain unspecified subset of OpenGL, which just so happens to coincide with the specific technique that Apple uses for menu bar translucency.

Personally, if it means a choice between having an opaque menu bar, or having a translucent menu bar that requires dedicated attention from the CPU every time the screen refreshes to work around the GPU's deficiencies, I'd choose the opaque menu bar.
...

Menus have transparency and blur. Those work on the PowerBook 12".
The menu bar has transparency and blur. That does not work on the PowerBook 12".

Now exactly what feature is not supported?
 
Networking problem with SMB shares

>Networking

>Addresses an issue in which Microsoft Windows shared folders may be >read-only when connected via SMB.

well, not on my system it doesn't. I've had this problem ever since upgrading to Leopard: powerpoint files on my windows fileserver keep telling me they are in use by someone else, and have to be saved with a new filename. I was really pleased to read that this issue had been addressed in 10.5.1 - meant I could go back to keeping all my files on the fileserver.

However, I still get the problem after today's 10.5.1 update. Anybody found a fix? It's seriously debilitating when working within a windows/exchange environment.

Bill
 
Updated last night. The update install itself went smoothly.

The firewall now works with Skype, although with the "Set access for specific services and applications" setting, it prompts to "allow incoming connections" for Skype each time that Skype starts up.

I am also able to access shares with read/write permission on my XP PCs (where I set the share to allow users to change files). Actually the only problem with accessing the Windows shares before was getting read only access to the share of the folder that is linked to "My Documents", even if the share was set to allow changes.

Checking the list of fixes, I don't think I was affected by most of them. I am definitely interested in seeing more fixes to the networking. That still seems somewhat flaky, i.e. shared computers consistently showing up in the Sidebar in Finder. Also, I haven't tested this yet, but before the update I was having issues with "Computer name is in use, changed named to..." when I used a different network location other than Automatic.

So far, I'm happy with the update, just wish they fixed some more things. Hopefully, 10.5.2 will really start to solidify Leopard.
 
Uninstall Cisco VPN!

Hi-

I was getting kernel panics to the point where my machine wouldn't boot after installing 10.5.1. It was related to the VPN. I followed the tutorial here, uninstalling the VPN, and it worked. I have a MBP 15" CD 2 GhZ with 1 gigabyte of RAM.
Hmmmm... :apple:
 
I still can't get passed the setup assistant. I did disk repairs from the Leopard DVD but it didn't help. I have no idea what to do. My Macbook is pretty much useless as is.

Does anyone have any suggestions on how to fix this problem? I'm literally going insane and am worried I've totally ruined my mac.

This is the 'fix':

1) Boot into Safe Mode by holding down the shift key upon boot... (wait, wait, wait... it will finally come up)
2) DO NOT LOG IN
3) Hit the back arrow key
4) Then hit the restart button
5) Wait, it will then run/rerun the updates
6) Wait, wait, wait and it will finally restart...

I had this happen to me about a week ago on my iMac, and the fix unfortunately did not work, and I just formatted and reinstalled. I think it has something to do with updates not installing correctly or the user not rebooting immediately when they download an update.
 
They fixed the problem in printing presets which wouldn't save the tray #... This was very important for me..
 
Can anyone tell me if this fix allows Time Machine to be used with external hard drives connected to an Airport Extreme Base Station (AEBS)?

Thanks.
 
Can anyone tell me if this fix allows Time Machine to be used with external hard drives connected to an Airport Extreme Base Station (AEBS)?

Thanks.
Sorry, it doesn't seem like it... (my TM prefs didn't let me change to my mounted Airdisk).

There was a hack somewhere to allow this, but I don't really want to rely on a hack for my backups, so I didn't really make a notice of where I saw it, and wouldn't recommend it anyway... ;)
 
Can anyone tell me if this fix allows Time Machine to be used with external hard drives connected to an Airport Extreme Base Station (AEBS)?

Thanks.

Nope. This release is just bug fixes no new features. However since that feature was removed just before Leopard's release I'm sure they're still working on it. And when they do you'll see it on MacRumors asap - many people want it.

BTW, my SR MPB update went perfectly. It seems to have fixed my bluetooth mouse from stuttering but since it rarely happened I'm not 100% positive yet.
 
I am having an issue with WIFI after applying this update.

Every time I put my Macbook to sleep, upon waking it I have to reenter my network name and password! This never happened with 10.5 for me.

As well Apple didn't fix the annoying external speaker popping sound!
 
Nice quick work by Apple as usual.

I love how people are expecting extra features/options like improvements to Stacks... it's never going to happen. Deal with it (or hack it) :) I've never heard of Apple doing such a thing in minor updates (anything except bug fixes), and improved stack functionality would be a good selling point for 10.6.

You need to look back at the history of OSX, apple does add features and options in these minor updates.

With stacks specifically, I don't know if people will get exactly what they want or when it will happen, but I'd be shocked if there are no changes in stacks functionality until 10.6.

I have wondered about people who leave their Macs on for weeks/months at a time, and I wonder - why?

Why sit around and wait for it to boot and for apps and documents to open? Not to mention things like opening up servers, arranging windows etc. I'd probably be more inclined to reboot if there was an option to have the machine remember what was open and restore that state after the reboot.
 
Menus have transparency and blur. Those work on the PowerBook 12".
The menu bar has transparency and blur. That does not work on the PowerBook 12".

Now exactly what feature is not supported?

Hey, don't shoot the messenger! I'm just repeating what I read in Apple's knowledgebase website, and it is disappointingly sparse in technical explanations. I don't have any insider info.

For what it's worth, I have access to both a last-generation 12" Powerbook G4 (nVidia GeForce FX 5200) and a last-generation 12" iBook G4 (ATI Radeon 9550) both running Leopard.

On the iBook, I've confirmed that the menu bar shows up translucent, while on the Powerbook, it does not. This suggests to me that there must be a real issue here.

Apple would have no incentive to go out of its way to artificially limit the G4 Powerbook's menu bar, but not the G4 iBook's. This leads me to believe that, despite outward appearances, the actual transformations used to get the translucency effect in the menus themselves are subtlely different than the transformations used to get the translucency effect in the menu bar, and that the exact transformation being applied to the menu bar is incompatible with the GeForce 5200.

Apparently it is also affecting G5 PowerMacs using a GeForce 5200 graphics card.
 
Hey, didn't mean too shoot you. Tasers work much better. :p

Anyhow, I understand what you're saying. I just really hope they fix it.
 
Damn. Started up a torrent before bed and get up this morning and MBP is dead. The wireless kernel panic is still there. Back to ethernet we go. :( :(

I can understand it not making 10.5.1 but to not fix such a severe problem that must have been reported thousands of times now in 10.5.2 would be bad.
 
Heh heh... yeah but that's what Leopard was, wasn't it?

And not just leopard, in theory any OS update could trash your system. It's good to be conservative but the only way to be truly safe is to never upgrade anything. The downside of that is you'd still be running 10.0 or whatever your computer shipped with.

Personally, I'm willing to take the risk as long as things are backed up. Somebody's always going to have a problem somewhere, as long as those numbers are small I don't worry.

Yep, I was always aware of that tiring waste of time. Yeah, it's irritating if not time consuming to hold down on the mouse button waiting for that whereas Stacks is instant.

So option click and it's instant. Obviously it can't be instant on left click since people don't always want the menu to pop up. It's a bit silly to say that the old dock was slower when that's only the case if you don't take advantage of the features available.
 
Menus have transparency and blur. Those work on the PowerBook 12".
The menu bar has transparency and blur. That does not work on the PowerBook 12".

Now exactly what feature is not supported?

The mistake you're making is in assuming the menus and the menu bar are using the same 'effect'.

Leopard still uses simple resources (small transparent PNGs) to build the actual menus then applies a subtle blur effect. The menu 'bar' no longer has a "resource", it is now built from scratch by the newesh 'CoreUI' layer and is more of a rendered surface, allowing for future support for resolution independence and possibly other fancy stuff (animated movement, animated icons etc.) yet to come. The 'translucence' which is actually done by sampling the wall paper and applying several techniques to it, including some subtle pseudo-3D real-time shading (the 'curved' looking surface), isn't really just "transparency and blur". At all.

On some GPUs that only partly support QuartzGL, all this work just to render the menu and draw everything on it in real-time full-color would require using the CPU fallback mode and just wouldn't be worth the resource use.

I hope this helps explain why your MacBook has less effects on it's Leopard Menu Bar. Maybe in the future the menu bar routines can be optimized to allow supporting more GPUs in real-time with the full set of 'effects' applied. In the meantime this is probably the best compromise while still allowing everything important to work.
 
Way to turn off Transparency...

The mistake you're making is in assuming the menus and the menu bar are using the same 'effect'.

Leopard still uses simple resources (small transparent PNGs) to build the actual menus then applies a subtle blur effect. The menu 'bar' no longer has a "resource", it is now built from scratch by the newesh 'CoreUI' layer and is more of a rendered surface, allowing for future support for resolution independence and possibly other fancy stuff (animated movement, animated icons etc.) yet to come. The 'translucence' which is actually done by sampling the wall paper and applying several techniques to it, including some subtle pseudo-3D real-time shading (the 'curved' looking surface), isn't really just "transparency and blur". At all.

On some GPUs that only partly support QuartzGL, all this work just to render the menu and draw everything on it in real-time full-color would require using the CPU fallback mode and just wouldn't be worth the resource use.

I hope this helps explain why your MacBook has less effects on it's Leopard Menu Bar. Maybe in the future the menu bar routines can be optimized to allow supporting more GPUs in real-time with the full set of 'effects' applied. In the meantime this is probably the best compromise while still allowing everything important to work.

Over on MacHints there is an article on a command to turn off and/or set the level on the menubar...
http://www.macosxhints.com/article.php?story=20071115135215262
 
I hope this helps explain why your MacBook has less effects on it's Leopard Menu Bar. Maybe in the future the menu bar routines can be optimized to allow supporting more GPUs in real-time with the full set of 'effects' applied. In the meantime this is probably the best compromise while still allowing everything important to work.

That's the funny thing, this effect isn't even real-time.

Thanks for your explanation though.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.