Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
For those who've enabled dev mode for modified kexts (Trim enabler, continuity activation, etc.), is it safe to update as is or must I restore the original kexts first?

Since I never got a response to this, I took the plunge and ran the update using the downloadable image file. (worst case scenario would be to go into recovery and use terminal to re-enable dev mode)

Other than having to re-enable Continuity and Trim, no issues. So the update is safe as it does not re-enable Yosemite's kext verification mechanism.
 
Yep. I have a desktop PC running Windows 8.1, and I stuff just about every HDD I can find in that thing. I use it to store all my media files in HD, which I then stream to various devices throughout the house.

In Mavericks, SMB file sharing was a mess. The connection was unstable and transfer speeds were slow and inconsistent. Often times the connection would drop mid-transfer. With Yosemite, it's now working great -- speed is respectable, and the connection is responsive, stable and secure.

I am interested in Windows performance connecting to a share on Yosemite where reads and writes are required from Windows. Mac connecting to a Windows share is not a problem.
 
hahahah. dude face it your machine is busted. just because people have faster machines than you don't get bent.

Boot time between Mavericks and Yosemite is identical for me on my 11' MBP on SSD: 7 to 8 seconds...every...single...time...

The boot time and shutdown time for my rMBP mid 2012 is jut absolutely fine.

Mac mini 2012 also have the same boot and shutdown time.

Mac Mini mid 2011-now takes about 3 minutes to boot up, with this line across the screen (progress bar), took about 20 seconds to boot up before Yosemite infested my machine
 
I still have this problem with older TM backups. when I try to access them TM just sits there spinning for ages and nothing happens.

I filed a bug report with Apple about TM still being broken and they actually responded. They asked me to grab some logs while reproducing the issue (inability to browse the backups).

Hopefully it'll get fixed soon.
 
I am interested in Windows performance connecting to a share on Yosemite where reads and writes are required from Windows. Mac connecting to a Windows share is not a problem.

Yep, I have it set up both ways. In my experience, file transfers are actually faster when you initiate from Windows to OS X. So, you're all good.
 
After difficulty installing 10.10 (it froze) and reverting to Mavericks, I thought waiting until 10.10.1 or 10.10.2 might be a smart thing to do. The more I read the more I'm wondering whether I should just skip Yosemite and be happy with a relatively stable Mavericks. It seems that there are many unhappy Yosemite campers.
 
It's making my 2011 27" imac with 3.4ghz i7, 256SSD and 16GB ram which previously behaved like a supercomputer that just munched through any task I threw at it behave like a seven year old G5. I'm not impressed so far. Mavericks and every other system back to Snow Leopard was super fast on it. Not this - opening windows animation is stuttering down to like 2 frames, Safari and itunes both feel around 10-20% slower too.

I quite like the look of it though.
 
Usability or GTFO! Earth to Apple. Can you hear us?

On which planet is it good design to make a text field so vague, so indistinct as this?

attachment.php


Apple, GTFO. Really, GTFO. Or at least, get whoever is at the driving seat out of that ****ing bulldozer.

Mavericks is so much clearer:

attachment.php


should I update?

still on mavericks … is this update ok to try?
thanks!

Yosemite is OK to try, but be prepared to erase stuff then restore from a backup of Mavericks.
 

Attachments

  • Screen Shot 2014-11-20 at 22.10.55.png
    Screen Shot 2014-11-20 at 22.10.55.png
    66.7 KB · Views: 1,101
  • Screen Shot 2014-11-20 at 22.11.42.png
    Screen Shot 2014-11-20 at 22.11.42.png
    17.3 KB · Views: 665
  • 2014-11-20 23-47-10 screenshot.png
    2014-11-20 23-47-10 screenshot.png
    19 KB · Views: 670
  • thank you.png
    thank you.png
    99.4 KB · Views: 1,151
Last edited:
I bit the bullet last night and installed 10.10.1 and, basically, don't notice much of a difference either way, positive or negative. I wasn't having any real problems beforehand so I wasn't looking for any particular fix; I was afraid it might break something, but so far, so good.
 
Yep, I have it set up both ways. In my experience, file transfers are actually faster when you initiate from Windows to OS X. So, you're all good.
Well, not all good here.

I installed the 10.10.1 update and still the same problem which is: Using the JRiver media app on Win7 with media files on Mac Pro 10.10.1, Windows can connect to the Mac share just fine and pull media files for streaming. However, when TV recording is enabled (recording to the Mac share) at the same time as playing an audio file audio stops and there are also errors writing tags to the Mac share. Doesn't happen on Mavericks; also to even get this to work under Mavericks I have had to disable smb2/3 in Windows; even that doesn't work under Yosemite. So either it is a local configuration problem with my system or Apple's SMB implementation under Yosemite can't perform simultaneous reads and writes. Try this on your system and see if you get the same results.
 
Very Mature Answer!

Every time you get a (2) in the name, the Apple TV disconnects itself from AirPlay list. It happens every second. So, it not working as Apple advertize. Practically impossible to use it.

Now I undertand when people says that in sites like this there are trolls just waiting to mock every people. When people has nothing good to say, they better keep their mouth shut. Ugh!

Clearly you're living in your 'own' world.
 
hahahah. dude face it your machine is busted. just because people have faster machines than you don't get bent.

Boot time between Mavericks and Yosemite is identical for me on my 11' MBP on SSD: 7 to 8 seconds...every...single...time...

Typical fanboy response which I thought about just disregarding, but considering the the Yosemite complaints are finally mounting to reach critical mass, I'll respond.

Only a fanboy would say what you just said. I have a $5000 tricked out late model Mac Pro with high end graphics and Yosemite makes it run like crap. I'll sooner downgrade to a previous OS than buy another machine and it appears a lot of people are considering following my lead.

The cool things that Yosemite offers aren't even compatible with newer Macs than mine, so why would I want to slow my Mac down to slower than an iPhone just for them?
 
On which planet is it good design to make a text field so vague, so indistinct as this?

Image

Apple, GTFO. Really, GTFO. Or at least, get whoever is at the driving seat out of that ****ing bulldozer.

Mavericks is so much clearer:

Image



Yosemite is OK to try, but be prepared to erase stuff then restore from a backup of Mavericks.

Seeing that Mavericks Safari screenshot makes me miss it even more. Look at the difference! Having the forward/reverse arrows on the same line as the minimize/close buttons is idiotic and I really miss the longer bar to enter website http
One thing I can say for sure-Jony Ive sucks at software design.
 
I have trouble with changing, even deleting, partitions on external drives in disk utility. A simple function. That is not acceptable. I still advice people stay away from this POS.

Again, you have a problem with Yosemite. The vast majority of people are not likely to experience the same issue that you're seeing. One thing not working right for you doesn't negate the fact that Yosemite works well for most people.
 
That may be, but it is just one example of the wonkiness that is yosemete. Wifi problems is a show-stopper for me, and it is affecting many others.
 
That may be, but it is just one example of the wonkiness that is yosemete. Wifi problems is a show-stopper for me, and it is affecting many others.

What is a showstopper for you, is a non-issue for me. I'm on 10.10.1, and have experienced absolutely ZERO problems. No WiFi problems. In fact, I haven't had a problem with my mid-2011 MBA since I bought it. That's from Lion to Mavericks to Yosemite.

You're only calling it a POS because you are having problems with it. Others are not, so if I didn't know that the WiFi problem may be hardware related, I'd call your put all of your issues down to PEBKAC.

BL.
 
It's software. It's confirmed to be a problem with software. Other operating systems, even non-Mac, connect just fine. This behavior began with Yosemite.

Don't dismiss this as user error. Many of us have done our due diligence. As you can see, not all machines are affected, and while users reporting problems are the minority, it is still a sizable minority. The only unifying element is Yosemite.
 
BS. On work i had a 4 gb iMac with mountain lion. It didn't ran very fast, but it ran just fine. If Yosemite doesn't run well with 8 gb, it's just a bad os.

It runs fine on my MBA with 4GB of ram...

Other than some wifi issues which aren't related to ram
 
It's software. It's confirmed to be a problem with software. Other operating systems, even non-Mac, connect just fine. This behavior began with Yosemite.

If it were software, wouldn't all users be impacted by it? After all, we are all using the same software, yet on my MBA, I am not having any such problem. Many others also are not having that problem.

Additionally, there were people in this forum (and IIRC, in this very thread) who were reporting that they had this problem with Mavericks as well. If that turns out to be true, that would effectively eliminate the software, leaving it to either the hardware, or the version of the driver used to run the hardware.

Don't dismiss this as user error. Many of us have done our due diligence. As you can see, not all machines are affected, and while users reporting problems are the minority, it is still a sizable minority. The only unifying element is Yosemite.

See the above.

BL.
 
Anyone know if it fixes Time Machine browsing?

According to the release notes it should:

Resolves an issue that might prevent Time Machine from displaying older backups

"might prevent" vs. "prevents".

The way this is worded, they found a bug that under very particular circumstances prevents you from browsing older backups, but many people will never have these circumstances on their Mac and will never notice it.
 
Has anyone else noticed that when you specify notifications for one of the "hot corners" it doesn't work after the first few uses of the hot corner? If so, is there a fix?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.