Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I think it's more along the lines of "They're the biggest company in the world, they can afford to beta test their software to make sure it doesn't have common, show stopping bugs".

I sure wouldn't classiify this as 'show stopping'. It only impacted those running out of date versions of the operating system, and it was quickly fixed. The vast majority of Snow Leopard users likely did not even install the buggy update yet, especially since they haven't even taken the time to upgrade to Lion yet.

Early adopters need to know that they always sholder the biggest risks. Those that have been around the block a few times know that it's generally a bad idea to be on the bleeding edge of anything new. Patience is a virtue. Let the other guy take the risks and work out the bugs before you jump onboard. Those that live with 'perfection' expectations will always live in constant misery.
 
What scale? A few people had problems, not everyone. I didn't on any of my machines, neither did my parents, sister, her husband, friends, etc.

If it was so wide spread I'm sure one of them would have had an issue.

Again, testing cannot catch everything, this is common sense in the software development world I don't know why it isn't in the consumer world.

Not to mention everyone is making way too big of deal over it. It was fixed in 24 hours, please find me some other company that is that quick with a patch. You'd be very hard pressed to.

Yeah, the only other major software vendor (which actually pushes out far more patches to a far greater user base with a far wider diaspora of hardware/software configurations, all on a relatively fixed schedule) gets into such a situation extremely often. Oh wait, that isn't true at all....

Though I shouldn't be complaining, the delta upgrade installed flawlessly for me.
 
I never applied the Delta update and went straight to the Combo update, and since then on awaking from sleep my iMac does not automatically connect to the 5GHz net. Before, it was fine. Go figure.:confused:

Yeah, I applied the Combo, without the Delta. 5GHz wifi problems unchanged. Cisco E4200 router.

I hope my mother didn't apply the delta.
 
Yeah, the only other major software vendor (which actually pushes out far more patches to a far greater user base with a far wider diaspora of hardware/software configurations, all on a relatively fixed schedule) gets into such a situation extremely often. Oh wait, that isn't true at all....

Though I shouldn't be complaining, the delta upgrade installed flawlessly for me.

I'm assuming you are referring to Microsoft. If you think their patches don't fix previous patches mistakes you must never read any release notes.

I work fixing Windows desktops and servers. We have to read everything every time patches roll out for Windows 7 (which is constant). I assure you its not a flawless process each time, far from it actually.
 
Because it includes the full version of any files changed - that is always going to be a more reliable version of the software - if the binary files have got corrupted on your machine somehow, either because your hard drive has been slightly damaged or because you installed some software that changed the version of the file then only changing the changed parts of the binary file will be risky - and there is no good way to guarantee that that is OK.
If 10.7.1 changed 100 files, its download contained 100 files. If 10.7.2 and 10.7.3 changed again 100 files each, their downloads contained again 100 files each. The combo update (for 10.7.3) thus contains 300 files (or likely less because some files that got changed in 10.7.3 also got changed in 10.7.2 or 10.7.1). You are just replacing a larger number of files. It is not that the 10.7.3 delta update contained partial files and the combo contains full files, it just contains more files.

Of course, as I said before and you also refer to here as wel, if somehow some of the files 10.7.1 and 10.7.2 changed got corrupted locally, the combo update can fix them. It is as I said, a (very) partial re-install of the OS.
 
The patch is running the combo update. It's a fix. Why release another fix when there's already one?


By that logic, why even release a delta when there's a combo?

Plus, last time I checked "patches" weren't exactly 1.4 GB in size. No, this is not a patch, it's a nuclear option of fixing the problem. I also find it interesting they released the faulty update at the same time as its "patch". They must've been able to foresee their screw up.
 
I sure wouldn't classiify this as 'show stopping'. It only impacted those running out of date versions of the operating system, and it was quickly fixed. The vast majority of Snow Leopard users likely did not even install the buggy update yet, especially since they haven't even taken the time to upgrade to Lion yet.

Early adopters need to know that they always sholder the biggest risks. Those that have been around the block a few times know that it's generally a bad idea to be on the bleeding edge of anything new. Patience is a virtue. Let the other guy take the risks and work out the bugs before you jump onboard. Those that live with 'perfection' expectations will always live in constant misery.

The fact that those updates was not installed should also speak some volumes about Apple users and Apple's default setting for updates. The volumes is not good.

MS learned its lesson the hard with the MSBlaster worm mess. MSBlaster used a patch security hole that was months old and it was exploiting the fact people were very bad at updating and MS default setting was just download and notify you they were ready. The notification was just an icon in the task bar by the clock.

MS changed its default settings in XP SP2 to download and install Automatically. Default time is around 2-3AM for the installs. It will reboot the system and load everything back up exactly was it was. This greatly reduced MS problems of people not updating and honestly is the best setting for default.
 
You obviously have never developed software. Again, like I said, this was tested to the best of Apples ability before release, just like EVERY major software company does but not ever bug can be found until the release is out in the wild.

And, again, the turn around time for a fix was phenomenal. Yes, a mistake happened but they fixed it extremely fast.

and you have obviously never developed software for the single richest company in the USA (which happens to be a computing software and hardware company)...If anyone has the resources to get it right, or closer to right than it has been lately, it is Apple. Truth is, apple is not-so-slowly becoming a tablet and phone company that does not give two *****s for their Mac line of computing devices any longer.

Two words: Bertrand Serlot!
 
I think the real issue is getting the security patches fixed and working.

"http://support.apple.com/kb/HT5130"

(Feel free to laugh, as it's only an opinion)

To me, it looks like possibly a Foxconn employee is making a little extra on the side. The embedded, malicious code in SSL, music, videos and picture formats seems like the "Virus Designers" have finally decided to work another platform, besides PC.

While the integration of your iPhone, home computer (two or more independent networks,) and tossing everything up to the cloud may be a marvel of modern technology, I believe someone is in complete lack of "brilliance," in jumping on the bandwagon and not expecting serious security issues.

The larger the OS platform (iOS or X,) gets, more targets and frequency of bad things are bound to occur, and it's going to take a long time to get ironed out.

This is more serious than a patch for your graphics drivers.
 
What happened to the age-old maxim that you should not install any system update for at least one week after release to see if others have problems? I saw the news that the 10.7.3 update was released, and I immediately marked my calendar to install it one week later. ;)
 
You obviously have never developed software. Again, like I said, this was tested to the best of Apples ability before release, just like EVERY major software company does but not ever bug can be found until the release is out in the wild.

And, again, the turn around time for a fix was phenomenal. Yes, a mistake happened but they fixed it extremely fast.

come on even you have to agree that Apple QA on this patch was a joke. This something the automatic testing procedures should of caught. It is not like it was some minor thing that is hard to find. This was a huge deal and what it points to is Apple rushed it out the door instead of vetting it threw QA.

Now lets face it many times it is QA and testing that suffer for any delays before hand but still this should of been caught in basic QA. Apple jumped on a fix because it was a huge embarrassment for them
 
I sure wouldn't classiify this as 'show stopping'. It only impacted those running out of date versions of the operating system, and it was quickly fixed. The vast majority of Snow Leopard users likely did not even install the buggy update yet, especially since they haven't even taken the time to upgrade to Lion yet.

Early adopters need to know that they always sholder the biggest risks. Those that have been around the block a few times know that it's generally a bad idea to be on the bleeding edge of anything new. Patience is a virtue. Let the other guy take the risks and work out the bugs before you jump onboard. Those that live with 'perfection' expectations will always live in constant misery.

Whoa buddy, I don't think you could be more wrong. Time to step out of the RDF and understand what happened:

1) The Core UI error happened on fully patched machines running Lion
2) The rosetta error also happened on fully patched, fully supported machines.

On one hand, you state that "It only impacted those running out of date versions of the operating system". A few sentences later, you state "Early adopters need to know that they always sholder the biggest risks... Patience is a virtue." So which is it? Should everyone be an early adopter and run Lion, or choose to run a more stable OS and keep Snow Leopard?
 
come on even you have to agree that Apple QA on this patch was a joke. This something the automatic testing procedures should of caught. It is not like it was some minor thing that is hard to find. This was a huge deal and what it points to is Apple rushed it out the door instead of vetting it threw QA.

Now lets face it many times it is QA and testing that suffer for any delays before hand but still this should of been caught in basic QA. Apple jumped on a fix because it was a huge embarrassment for them

I honestly don't think this is near as big an issue as everyone things it is. I run rosetta apps and had no problem, not one single person I know had a problem either and I'm willing to bet almost everyone on this forum didn't have a problem.

Mistakes happen and it was fixed in roughly 24 hours so I really don't see why everyone is making a big deal about it.
 
I'm assuming you are referring to Microsoft. If you think their patches don't fix previous patches mistakes you must never read any release notes.

I work fixing Windows desktops and servers. We have to read everything every time patches roll out for Windows 7 (which is constant). I assure you its not a flawless process each time, far from it actually.

Wait I think you're misreading what I actually wrote. I was referring to a situation like *this*, with this virtually show-stopping bug that some people were getting in everyday usage.

I did not say Microsoft makes no mistakes- indeed, they seemed to have pulled the patch that was supposed to improve Bulldozer performance as it apparently decreased performance slightly. They didn't pull it though because it totally broke Windows for a subset of users...

And I believe the sheer number of updates that are pushed out and installed, with nary a hitch or complaint from a vast array of users, demonstrates that the update process is perhaps as flawless as is achievable. Now what all these patches imply about the underlying vulnerabilities in Windows is a different story :/
 
Wait I think you're misreading what I actually wrote. I was referring to a situation like *this*, with this virtually show-stopping bug that some people were getting in everyday usage.

I did not say Microsoft makes no mistakes- indeed, they seemed to have pulled the patch that was supposed to improve Bulldozer performance as it apparently decreased performance slightly. They didn't pull it though because it totally broke Windows for a subset of users...

And I believe the sheer number of updates that are pushed out and installed, with nary a hitch or complaint from a vast array of users, demonstrates that the update process is perhaps as flawless as is achievable. Now what all these patches imply about the underlying vulnerabilities in Windows is a different story :/

My apologies! I see what you are saying now. :eek::eek::eek:
 
MS changed its default settings in XP SP2 to download and install Automatically. Default time is around 2-3AM for the installs. It will reboot the system and load everything back up exactly was it was. This greatly reduced MS problems of people not updating and honestly is the best setting for default.

Reboots the system, yes. Loads everything back up exactly blahblah, fscking no. That's why it is much less than ideal.
 
My system was hosed by this update. Only time machine restore resolved my machine working at all. Luckily recovered all my data.
My biggest FO is this, how can apple really not be able to test the updates on all their compatible machines, it's not as if they have to try and guess whose exotic third party hardware to support? They sell these machines on the basis that they make the hardware and the software, so it just works. The lion OSX is even limited to c2d machines, so that's what? 3 gens of iMac, 2/3 minis and a couple mac pros, half a dozen laptops. It' not [satire]rocket surgery[/satire] ffs!
 
The vast majority of Snow Leopard users likely did not even install the buggy update yet, especially since they haven't even taken the time to upgrade to Lion yet.

weasel words!

There's quite a few users who continue to use Rosetta for a variety of pretty good reasons - the least of which is 'not taking the time'!
https://forums.macrumors.com/threads/1318672/

They've made the judgement that the features/functionality of Lion do not out weigh the cost/time/technical issues involved with the upgrade. Apple clearly recognises SL is not all that 'out of date' - otherwise they wouldn't have released a security update for SL. I don't recall there being one for Panther, Tiger?

Those who did install the update were not expecting extra features or functionality but a security update and I for one, am pleased that Apple continues to release them.

I would however, hope that Apple continues to take as much care over them as any other of their products. Thankfully the fix was provided pretty promptly but long enough for some users to start implementing time-consuming solutions such as reinstalling SL, then updating to the latest version pre-bug, etc. Possibly Apple's initial denial of the problem would encourage people to feel they were on their own in solving it?
 
combo update is different than original

The combo update dmg is not the same as the original one posted for 10.7.3.

If you downloaded the combo updater on the initial release day, you may want to download it again. The SHA1 checksums I have are:

Code:
b8322dbd1f7b55bf35aac4122ad2204c51307793  MacOSXUpdCombo10.7.3(1).dmg
07dfce300f6801eb63d9ac13e0bec84e1862a16c  MacOSXUpdCombo10.7.3.dmg

The first one (the one with the 1 in parentheses) is the most recent one and that checksum matches the one posted at http://support.apple.com/kb/DL1484
 
The combo update dmg is not the same as the original one posted for 10.7.3.

If you downloaded the combo updater on the initial release day, you may want to download it again. The SHA1 checksums I have are:

Code:
b8322dbd1f7b55bf35aac4122ad2204c51307793  MacOSXUpdCombo10.7.3(1).dmg
07dfce300f6801eb63d9ac13e0bec84e1862a16c  MacOSXUpdCombo10.7.3.dmg

The first one (the one with the 1 in parentheses) is the most recent one and that checksum matches the one posted at http://support.apple.com/kb/DL1484



Ok so they have updated the combo? I'm wondering if I should run it again.
 
I spoke too soon....All three Macs have now been updated via the combo. All three manifested wifi issues, slow App loading, and spinning beach balls. After the combo....All is well.

Get a grip Apple...IOS is fine, but OSX requires the same attention.

End Of Rant.
 
Do you have any technical explanation why getting the combo updater right is easier than getting the delta updater right? Both represent a delta, just with different reference points. Shouldn't logic tell us that the smaller the delta, the easier it is to get things right?

Nope, there is more jiggery-pokery involved with creating a delta over creating a combo - more things to go wrong especially when it comes to doing binary diffs. This isn't new btw, I've found the same situation happened running Linux where delta updates have become the 'in thing' only to find that in many occasions things can go pear shaped. It is the old story, when it works well it works well but when things go bad they go really badly.

Like I said, it is a few hundred megs difference - just take the extra 10 minutes and download the combo.

Said perfectly. Let this be a lesson learned for everyone, old and new, never download anything but a combo update. This is certainly not the first problem Apple has had with a delta update and certainly won't be the last.

I learned the lesson way back in 2003 when I had my eMac (my first Mac), downloading a combo update via a 56K dial up connection - it wasn't pretty but I learned quickly the perils of relying on a delta update. For me I can't work out the logic of what Apple does - it makes no sense what so ever. Put a combo up, less problems, good experience for end users, positive news stories spreads and great marketing of re-enforcing "Mac's just work" thus a win-win situation. Colour me confused sometimes as to the reason why Apple makes certain decisions that they do.
 
Lion...a mess

I'll set things clear up front :

1. I'm not a software developper but

2. I have enough experience on computers that I know when errors are users ones or softwares ones.


Ever since I updated my 2 Macs with Lion, I'm suffering with stability issues, unresponsive applications and unresponsive OS. Lion is not more stable than my Win XP job Laptop and God knows how I hate Windows. I miss SL so much but unfortunately, if you want to use iCloud, there is no choice of using Lion.

Both my Macs are always updated with the latest patch releases so there is no way that I missed an update. They are always up to date.

Both my Macs have been updated on last Thursday evening using the Combo update. No improvement so far on stability.

Since the update, Time Machine is crawling. Backup was done after the update and took hours to complete. And the worst, yesterday evening, TM started a backup on my MacBook and guess what...bakcup size was 54 GB ??????? I barely used the the MacBook in the last days and it completed the full backup right after Combo update.

I find Apple Quality Control on Softwares is messing a lot lastly. Even the simple iBooks app on iOS. They upgraded to V2 and made a event on this about developping textbooks for schools with publishing companies. Guess what...V2.01 fixed major bug which prevented Textbooks from opening....I mean they should be kidding.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.