It seems lighter to me than the one in 10.7.3.
Now when I log out and back in it looks like the old 10.7.3 login background. Only after rebooting from the .7.4 update did it look different. Weird.
It seems lighter to me than the one in 10.7.3.
I'm a noob when it comes to flash issue or anything related to it..but...I thought mac don't use flash? Or am I thinking of something else?
Yes. No word on what changed though. OpenGL extension support did not change.
I just came here to say that.
I like having my own login screen background. The linen one is too... linenny.
Your thinking of iOS. iOS does not allow flash.
Is it just me or is the user sign in background different?
Updated five startup drives on my Mac Pros and one on my MacBook Pro - I have two drives in that machine - but when I updated the second drive, the startup drive, and THE ONLY ONE RUNNING FILEVAULT, I got an error when I tried to verify the drive with disk utility. It said that "Problems were found with the partition map which might prevent booting" and then the red error message "Error: Storage system verify or repair failed."
That's what I though as well. 370mb of data for couple of fixes?
Not to mention those 730mb ones!
Yeah I am trying to find a way around it. When I browse to the folder where the login background is, it shows the customized one I use. I wonder what is overriding it.
Is it just me or is the Automator Icon different now?
Welcome, guinea pigs, to the new Apple.
did anyone else install the update and have more problems?
I did the update, it restarted saying it was installing and validating files then went to the blank loading screen with just the spinning status bar on grey.
After about 30 minutes of this I turned it off and restarted and it "loaded" for about 10 minutes before finally reaching login screen where it proceeded to spin the beach ball for a few minutes before logging in and promptly indexing spotlight again.
Seriously. I understand that Jobs wanted to keep engineers small and tight knit, allowing Apple to move engineers between OS X and iOS departments (OS X engineers were moved to iOS which delayed the release of OS X Leopard twice). However, Apple has grown immensely and it seems departments are becoming strained. I visited a friend who works in Cupertino this Feb, departments haven't grown much in the past five years. Seems demand is surpassing engineering resources. It might behoove Apple to hire more engineers, and slow it down on the iOS and OS X integration.
C'mon Apple, keep focus on what made you a great company, OS X.
Nope. Everything went fine.
Not over here. I've had nothing but problems with Lion and the "geniuses" insist I do a clean install which I did. And it made it a little better.
Now this update has bogged down my laptop, isn't fully installed and I'm having slow downs, frozen start ups, etc after trying to update. Apple needs to get it together.
Is it just me or is the Automator Icon different now?
de-crypted. ran disk utility. original error gone. new one appeared:
Invalid Volume Header @ 0: incorrect block type
Invalid Volume Header @ 479244221953: incorrect block type
disk0s2 is not a CoreStorage volume
booted from Recovery Partition, ran Disk Utility twice on repair. Didn't say it was repairing anything, but it didn't find anything, either.
All came out okay.
Re-booted into startup drive and verified via Disk Utility. All is now well.
Going to re-encrypt and move on with my life.
How about fixing Safari so that it doesn't reload all my tabs even though I have 16 GB of RAM.![]()
Have one setup in the office of Windows users.... its been "fun"
It has been fun for me since Tiger. Yeah...Let me fix that for you:
Ah the scourge of Apple OSX's implementation of SMB
So, the office full of Windows users is having no unexpected problems with CIFS, but the one Apple is having problems.
Wouldn't that lead you to think that the problem is the Apple, and not CIFS?
(I said "unexpected problems", because most NAS protocols will attempt recovery if a connection to storage is down due to network or server failures. This is seen as a 30 to 120 second "hang" by the user, but in fact it is part of the design of the protocol.)