Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Floating about where? Every developer knows which build they have and which build is the latest one. There's nothing confusing about it unless you are a 5 year old kid.

----------



I think Mavericks will be the buggiest .0 release we've had for a while. I've been using GM since the beginning of october and I never had this many issues with a GM since Leopard. So I really hope .1 will come very soon. One thing amazing about Mavericks is Safari, it really is impressively snappy. No other browser will come close to it in terms of performance on Mac.

Yeah I tried to use firefox, which is my preferred browser on my windows desktop, and I wanted to use it for the firefox sync, but compared to safari in mavericks its like driving a bus vs a ferrari

----------

I hope so. Nobody should blame Apple for doing this, if it is the case.

One thing is for sure anyone who has invested a whole lot of time installing and setting up their new Mavericks install has wasted it. That is, unless you're happy being stuck on 10.9.0 until 10.10 comes out.

It would make no sense for apple to update the GM to "thwart people who torrented it"

Do you guys realize how dumb that sounds? If people could torrent the first GM, then they can obviously also torrent the updated one, it doesn't "disable" anyone. Its just as much of an annoyance to developers as it is to the people who torrented it (developers have had to redownload it from the app store and run the installer, people who torrent it just...torrent the new build instead and run the installer)
 
It would make no sense for apple to update the GM to "thwart people who torrented it"

Absolutely!

Torrent users are free real world guinea pigs for Apple before an official public release. Absolutely no reason for Apple to get difficult with this group of users.

Anyway, 603 installed well directly over my existing 598 without issue. Just have to be patient as it would go "quiet" for periods along the way. Everything came back up and Safari is even smoother. Safari under 598 had tiny but noticeable hiccups here and there but this is very smooth. Also, SW Update has picked up a Camera RAW update that 598 didn't.
 
That might be possible. Obviously I don't have Mavericks yet and I don't have an rMBP - just a regular one, late 2011, so no AppNap experience. The only thing I tried to point out is he/she has a ton of heavy-duty stuff running in the background and doesn't understand why his MBP is sluggish. That's sort of Laptop 101.

He/she might find a marked increase in speed and responsiveness if the person limits background apps manually. Perhaps AppNap should be doing the same thing? Don't know.

Late 2011 MBP too... Looking forward to seeing the difference. But, yeah, I totally agree with your analysis of the problem, I was just wondering if AppNap will help clueless users with problems like that.

Is there a way to limit background apps? I have to admit that I'm a casual user/student who pretty much uses Safari, iTunes, Word, Excel, and Mail.
 
FWIW, I've found this new update very useful. It fixed a nasty crash that occurred with Mail and searching for items in the search bar. I could repeatedly crash mail just by searching for and filtering for attachments, for instance. It appears this build has fixed that bug. Well worth the effort to make sure something like this doesn't slip through.
 
"seed" is tech term for deployment or distribution. They call it "Gold Master" not "Gold master Seed"

This was labeled a GM seed, which they treat as equivalent to what would be called a release candidate elsewhere. This issue has come up before on the developer forum, and that was the information given by an Apple employee. For example, Xcode 4 had both a "GM Seed 1" and a "GM Seed 2".
 
Last edited:
In at least some instances they have called it simply GM or Gold Master.

In any case, this one was labeled a GM seed. There have been multiple GM seeds for products before, so the release of a more recent GM build is not unheard of. If Apple adopted the more conventional term "release candidate", people would probably be less annoyed when they release these newer builds of what people assumed was the final version.
 
Just ran an MD5 Checksum for the InstallESD.dmg that's inside the shared support folder of InstallOSXMavericks.app and got this...
Image

Anyone can confirm if this is legit...btw this came from a torrent that i got for the new build. Also, i checked the .plist and i'm getting build version "13A602" instead of 13A603.

Image

This is the legitimate MD5 - ignore the other FUD.
 
Also, SW Update has picked up a Camera RAW update that 598 didn't.

Apple disabled (at least some downloads in) Software Update for the 598 seed server-side after about 36 hours due to bugs in Software update. Therefore it's unlikely that people with 598 will be able to update to 10.9.1 or download any other updates. All developers who installed 598 will have to install 603 first I think.
 
Mavericks GM Build 13A603
MD5: BFFB7A8E1776E8E748FDB0DA39433FDF
SHA1: CFD9DB706BCA3253BB6667CCC4F16FA9934218D1

I'm pretty sure this is the hash of the entire .dmg.app, not the installesd.dmg file.

The torrent I downloaded was an .app.dmg (DMG file with the Install OS X Mavericks.app inside), and when I ran openssl sha1 on Install OS X Mavericks.app.dmg I got the same sha1 hash you just posted.

I can confirm that the above MD5 and SHA1 are for the "install_osx_mavericks.dmg" file; NOT for the installESD file in the package.

Here are my numbers for the installESD:

MD5: f222952400db8535c03697c3293e168e
SHA1: e804dea01e38f8cd28d6c1b1697487e50898dbe7

And here for the entire DMG:

MD5: bffb7a8e1776e8e748fdb0da39433fdf
SHA1: cfd9db706bca3253bb6667ccc4f16fa9934218d1

My source needs to be double-checked.
 
Last edited:
Floating about where? Every developer knows which build they have and which build is the latest one. There's nothing confusing about it unless you are a 5 year old kid.

But as a developer responding to a bug report, don't you want to make sure that your customer is running the same build that you are?
 
Yay can't wait to have a dozen more compatibility problem for some more useless fancy gimmicks. I mean damn the bugs with Mountain Lion haven't even been fixed.
 
Running the original GM, this is what I get when clicking install mavericks from the app store: http://i.imgur.com/j20SuC5.png

jV7Fqq7.png


Hey now... what are you up to over on Reddit? :D
 
I'm getting this too. I'm on the first GM build though :confused:

Will it just update normally if I click continue without any data wiping?

Probably, I haven't tried it yet myself. But people that manually downloaded the new GM build before it was officially released reported it installed over the first GM just fine.
 
No. It is okay. That's the official method Apple intended, because there is no official way to do a clean install since you have to download it from App Store and install on a mac with a working OS X.

The clean install method is the unofficial method, but preferred by some forummers as they want to make sure no files from the previous operating system are leftover.

Both is fine.

Thanks I was wondering why I kept seeing people say they were doing this clean install.
 
I got the same download as bemiquel, weird since it includes "Developer preview" ?

I'm running on the first GM as well and it didn't bump the build number...
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.