Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Installed fine, but in an hour beachballs for like 30 seconds on one safari tab open once.
Then a minute ago just froze.
My christmas gift is going back I guess.
Late 2013 13' 2.4/8/256
 
Although I have no scientific proof, this release feels way faster on my '08 iMac than .0 and the last beta. Not sure if they've been messing with anything under the hood but I'm getting far less disk access pauses.
 
Main build number is 13B42.

Build number for late 2013 macbook pros is 13B3116

A full installer is also now available on the mas.

I'm curious how they come up with the build numbers on the "special" builds. So, 13B42 should be the 42nd build of 10.9("13").1("B"), just like 10.9.0 was 13A603 and the 603rd build of 10.9.0.

I have a 2013 rMBP that came with 13A2093 (2093rd build of 10.9.0?) and is now running 13B3116 (3116th build of 10.9.1?). All of the leaked Mac Pro benchmarks show 13A4023 (4023rd build of 10.9.0?), as far back as Sept 27th - but that build is much further along numerically than the released build for the rMBP leaked on Oct. 23rd!

Anyone who understands how this works, please chime in.
 
I hope this fixes that problem that only I experienced. You know, the really obscure one. Yes, the one I whined about in random places all over the forum to make it look like more people besides me had it.
Yeah Apple, FIX IT!! Even though I should know by now that you don't even read this forum and i'd be better off using your feedback form instead!!
Apple teh suxx0rs! When is 10.9.2 coming out?? OMG!! Im going to hurl my Mac out of a window and get a cheap and nasty plasticy Android device I swear!!
 
10.9.1 - Anybody else having trouble with their magic mouse no longer being a trackpad for scrolling, etc? Worked great in 10.9....zip in 10.9.1....


Edit:
Never mind - another reboot and things are back to normal with the magic mouse....
 
Last edited:
Ever since installing Mavericks my early 2008 Mac Pro goes nuts if I try doing anything involving an external drive (i.e. setting up a new Aperture vault, loading photos from a USB card reader).

That's really strange. I have a 2010 iMac and have had the opposite experience: my external drives are now far more stable than they ever were under 10.8.
 
Bootable USB for 10.9.1

Here is how to make a bootable USB installer for 10.9.1:

Your 8 GB USB drive should be called Untitled and formatted as Mac OS Extended (Journaled). The full installer available on the mac app store should be called Install OS X Mavericks.app and should be in your Applications folder after you download it.

Run this in terminal and wait about 20 minutes:

sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction

You should see something like this:

Erasing Disk: 0%... 10%... 20%... 100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

You can then boot up from the USB by holding down the option key, then install 10.9.1 from the USB.

Note that this will also install a recovery partition.
 
Is anyone else hanging on "less than a minute remaining"? Mine has been like for almost an hour. Wtf?

I'm on a late 2013 15 inch rMBP btw.
 
Will I be able to buy songs from itunes again? I haven't been able to for weeks.
Also, why the hell did Apple take away the option to buy all songs from your wishlist at once?
 
Here is how to make a bootable USB installer for 10.9.1:

Your 8 GB USB drive should be called Untitled and formatted as Mac OS Extended (Journaled). The full installer available on the mac app store should be called Install OS X Mavericks.app and should be in your Applications folder after you download it.

Run this in terminal and wait about 20 minutes:

sudo /Applications/Install\ OS\ X\ Mavericks.app/Contents/Resources/createinstallmedia --volume /Volumes/Untitled --applicationpath /Applications/Install\ OS\ X\ Mavericks.app --nointeraction

You should see something like this:

Erasing Disk: 0%... 10%... 20%... 100%...
Copying installer files to disk...
Copy complete.
Making disk bootable...
Copying boot files...
Copy complete.
Done.

You can then boot up from the USB by holding down the option key, then install 10.9.1 from the USB.

Note that this will also install a recovery partition.

Oh whew! That'll save me the trouble of not googling it anyways.
 
hahahahaa

who else thinks this is funny: http://support.apple.com/kb/TS5313?viewlocale=en_US&locale=en_US

OS X Server (Mavericks): Clients cannot connect to VPN service using L2TP
Symptoms

With OS X Server (Mavericks), the VPN service may no longer accept L2TP connections. This can happen if the client and server are behind different network address translation (>NAT) gateways.

Resolution

You can configure and use PPTP instead. Please note that PPTP requires Directory accounts.

Seriously... Problem can't securely connect to my server... Apple's solution well connect using a non-secure method.....
Don't be silly, PPTP can be just as secure as L2TP for all practical purposes.
 
There were definitely some graphics engine fixes in this release. Second Life was nearly unusable on 10.9.0 but it's running great on 10.9.1 so far.

Gonna have to try Team Fortress 2 next to see if it runs even better; THAT actually ran pretty good on 10.9.0.
 
Really could not give a flying ***** about anything associated with Google. Let them rot.

On another note; update done.. now to look out for improvements.
 
Ok.....

so the famous beach update dont have all the nuts and bolts fully oiled....Time to wait before upgrade in production/serious environment....:eek:.....:confused:......


:):apple:
 
I'm curious how they come up with the build numbers on the "special" builds. So, 13B42 should be the 42nd build of 10.9("13").1("B"), just like 10.9.0 was 13A603 and the 603rd build of 10.9.0.

I have a 2013 rMBP that came with 13A2093 (2093rd build of 10.9.0?) and is now running 13B3116 (3116th build of 10.9.1?). All of the leaked Mac Pro benchmarks show 13A4023 (4023rd build of 10.9.0?), as far back as Sept 27th - but that build is much further along numerically than the released build for the rMBP leaked on Oct. 23rd!

Anyone who understands how this works, please chime in.

Special variants (typically model-specific) start at a build number which is some multiple of 1000, with lower build numbers reserved for the common variant. I think that in recent OS X versions, Apple has started special build numbers at 2000, leaving 0-1999 available for the common variant.

Therefore 13A2093 is build 93 of special variant 2 of 10.9.0, 13B3116 is build 116 of special variant 3 of 10.9.1, and 13A4023 is a build 23 of special variant 4 of 10.9.0.

The build number usually gets reset (presumably to 1) each time the major number or minor version letter increases.

The letter usually corresponds to minor versions (e.g. 13A and 13B are 10.9.0 and 10.9.1 respectively), but that isn't always the case. Strictly, the letter increases when the kernel changes: in some minor OS X versions, the kernel doesn't change (so consecutive minor versions have the same letter), and sometimes it jumps more than one letter between minor OS X versions (e.g. 10.7.4 was 11E53, and 10.7.5 was 11G56).

10.6 had an odd pattern: the build numbers of 10.6.1 and later were all in the 500-900 range, and it looks like Apple was using a different internal system to number the builds. The build number for released versions increased from 10.6.0 to 10.6.3 despite kernel version letter increases, then went down slightly in 10.6.4, up again in 10.6.5, down slightly in 10.6.6 and down again in 10.6.8 (10.6.7 was the same kernel version as 10.6.6).

10.4 was a special case, since it had parallel releases for PowerPC and Intel. The Intel builds used build numbers 1000+ or 2000+ while the PowerPC builds used lower numbers, but otherwise the standard rules applied.

For other major versions of OS X, the 10.x.1 and later releases usually have build number in the 1-99 range (sometimes getting up into the 200s) and adjacent versions have unrelated build numbers (unless they have the same kernel version letter, in which case the newer OS X version has a higher build number than the previous version).
 
I've never regretted a software upgrade so much as I have regretted upgrading to Mavericks. Mail went from being a pretty nice email client to a complete disaster. Numbers is broken too. Another upgrade regret. I hope Apple stabilizes Mavericks soon, but right now it is Apple's "Vista" in my book.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.