Personally, I would consider Lion the worst release of OSX of all time.
It contained nothing useful, and instead we got clutter like social media integration, an intrusive notification centre
Notification centre was Mountain Lion.
Personally, I would consider Lion the worst release of OSX of all time.
It contained nothing useful, and instead we got clutter like social media integration, an intrusive notification centre
"Apple support representatives have instructed users to remove excess preferred networks in the Network section of System Preferences"
Yeah, because that makes my life so much easier when travelling with my laptops through multiple networks everyday....
Notification centre was Mountain Lion.
Did you not notice that Apple completely controls the ecosystem? Give M$ credit. They have to support thousands of hardware products with their OS. Considering that fact makes Apple look silly in comparison. And don't get me started on supporting them on a Windows network with real security. They make consumer products not designed for enterprise use.
Why do you think the Apple sales reps avoid IT like the plague and try to sell directly to end users?
Good luck with Windows 8.2/9/10 (release is towards the end of next year), it is still a mess (running the technical preview at home) and definitely not like OS X...
As an FYI, you can run Mavericks on your Mac Pro 1,1 now, as some dedicated folks (some on these forums) have figured out how to do this relatively easily. But I know what you're saying...hardware has to get upgraded at some point and Apple is selling sealed iThings for the most part now.
Hi ---
I don't know why MacRumors keep portraying this a WiFi Problem.
No one complains about loosing their WLAN. They loose their Internet Connect as in possibility to resolve DNS. Thats it.
WIFI works great. If it would be a WIFI issue people would loose their WLAN all the time. This is NOT a WIFI Problem.
In fact as the problem appears the user ARE connected to their WLAN.
Aside from that, you also get this problem when connecting an ethernet cable to the router. It is a DNS Issue, somehow.
Apple should have waited. Before releasing.
You didn't really get it right there...![]()
Yosemite...yuck..
The worst version of OSX in recent years.
after fresh installing Yosemite with much enthusiasm..I re-installed Mavricks on my 2014 rMBP.
Mavricks is more reliable,much faster,much much better looking.and doesn't eat and wastetoo much Ram like Yosemite.
It is mind boggling to me that this was either:
- not detected in QC
- detected in QC and subsequently decided to be a non-showstopper at some management level
It's hard to believe that it was not detected in QC, which leaves the second option. Given the pressure/expectations from the market that seems much more probable.
It is really sad and unbelievable that it does not draw even more attention.
I have a late 2013 maxed out 27" iMac. No wifi issues on Mavericks and none on the initial Yosemite release. But with the 10.10.1 update I'm now having to turn off wifi on my iMac randomly and turn it back on as I lose the connection.
Not only are they not correcting the issue with wifi but they are now causing it on some machines.
It was probably detected. And assessed. Like This:
There is a probability that 20% of all users installing 10.10 are going to suffer from not being able to access the internet.
Great news... That means 80% are going to be able to access the internet. Lets release. And deal with the 20% instead of dealing with the 80% by not releasing...
In War, I believe, this is referred to as collateral damage.
I posted this elsewhere also. I had massive similar issues on Mavericks with disconnecting wifi on a Mac Pro and MBP but got this fixed after a chat with a very savvy 2nd line Apple Support rep. I'd been through 3 peeps at Apple before plus eons of time wasted with BT Support.
Anyway long story short was that enabling two wifi networks (2.4ghz and 5ghz) at the same time with the same credentials - network name and password - (as instructed by BT I might add!) was causing the issue. Changing the name of the 5ghz network cured this problem immediately and I have had absolutely zero issues since, even after installing Yosemite.
Try this, it might just work for you as it did for me.