Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OS X Yosemite Beta: First Impressions, Installation Tips, Known Issues, and Bug Fixes
- Thread starter MacRumors
- Start date
- Sort by reaction score
I tend to not notice the system graphics at all... I'm only aware of *content* and I just realized: The system-look gets out of the way and lets me pay attention to what needs my attention.
And that's the way it *should* be!
I like the new look, too 🙂
Running on my ancient MacBook Pro from 2007 (oldest supported laptop). No longer a primary machine, so I figured to give it a whirl. Originally came with 10.4.10. I thought for sure Mavericks was the end for this, but I guess not!
View attachment 482209
View attachment 482210
Current performance seems akin to Mavericks, which isn’t bad. Haven’t noticed any other issues yet.
It's great that Apple is willing to keep the Santa Rosa MBPs chuggin along.
I have one too that I use as a second laptop when testing code, it shipped with 10.4!
Pleasing to see that it is still very usable in mid-2014.
It is a bit of changed beast from the original shipped back in 2007 though as I have:
- Swapped the trackpad for one from the early-2008 that had multi-touch.
- Installed a 3x3:3 450 Mb/s 802.11n wireless card giving AirDrop (AR9380).
- Fitted the Broadcom Bluetooth 2.1 + EDR card that came with the early-2008 MBP.
- Fitted the newer hard disk that came with my 2011 MBP when that was swapped out for a SSD.
- Fitted 4 GB RAM, it came with 2 GB.
tevion5
macrumors 68000
Mavericks was the same though? Loads of performance improvements and no nonsense. Mountain Lion and definitely Lion were buggy and gimmick filled updates.
And for Yosemite, performance on my MacBook Pro 13" from 2011 is far better under the Yosemtie Beta 1 than it is under Mavericks 10.9.4. No bugs, more fluid UI, and faster performance in general tasks. Safari is much faster. Even little things like system settings open noticablly snappier.
Last edited by a moderator:
Crazy Badger
macrumors 65816
Just noticed the preview feature that stopped working in Mavericks (for MKV and AVI files) now works again in Yosemite 😀
blancoBronco
macrumors 6502a
tried to install on my mid 2010 MacBook Pro. completely wrecked my hard drive now. people at the apple store couldn't even do anything to help. they said something about how having a passcode lock on my computer made the installer lock the hard drive beyond my passcode but no one there was exactly sure how or why that happened. HD is not partitioned, cannot quit installer, cannot continue install, do not have a backup of my files from within the past year. besides basically erasing my entire HD and starting fresh, does anyone have any sort of advice?
Yeah, start backing up your hard drive, or use Dropbox. There's really no excuse not to have automated backups these days.
AxoNeuron
macrumors 65816
To no one in particular:
DO NOT install Yosemite on your primary machine if you are not a developer. As a BARE minimum you should have extensive computer troubleshooting experience, TWO backups (preferably one time machine and one disk-image), and also you have a secondary machine or Mavericks partition. I've heard some absolute horror stories, even with Yosemite. Right now, it's much better than the first developer preview release was, but even at DP4 it still has many problems especially with some third party software. For example, my VLC app tells me that my version of OS X is not supported, which is to be expected since VLC wasn't built for Yosemite.
Truly, you're playing with fire if you don't know precisely what you're doing. Especially if you do it without a backup.
The final build will almost unquestionably work with enabling TRIM support for third party SSD's. Looks like what caused this is disabling loading non-standard kext files, so editing the kext containing modified kernel extensions for enabling TRIM would definitely cause a boot failure.
DO NOT install Yosemite on your primary machine if you are not a developer. As a BARE minimum you should have extensive computer troubleshooting experience, TWO backups (preferably one time machine and one disk-image), and also you have a secondary machine or Mavericks partition. I've heard some absolute horror stories, even with Yosemite. Right now, it's much better than the first developer preview release was, but even at DP4 it still has many problems especially with some third party software. For example, my VLC app tells me that my version of OS X is not supported, which is to be expected since VLC wasn't built for Yosemite.
Truly, you're playing with fire if you don't know precisely what you're doing. Especially if you do it without a backup.
The final build will almost unquestionably work with enabling TRIM support for third party SSD's. Looks like what caused this is disabling loading non-standard kext files, so editing the kext containing modified kernel extensions for enabling TRIM would definitely cause a boot failure.
Last edited:
macsforever
macrumors regular
r.harris1
macrumors 68020
It doesn't matter how many exclamation points and capital letters you use, I see no difference in how app expose and mission control work between yosemite and mavericks, at least between my mavericks and yosemite instances. If they work differently between yours, please provide a few screenshots so we can see what you mean, as an exclamation of exactly what you mean hasn't been forthcoming. Just a lot of exclamation points 😉. If there's a bug in the implementation based on how you use it, it would be useful if you could share that bit of information.
macsforever
macrumors regular
I'm sorry I just a beginner and I don't know how to do anything so yes you're right and I'm wrong thank you have a good day. I didn't know there was Apple engineers on MacRumors to give trouble tickets to ha ha Ha.
