My apologies to everyone that may get to this thread via my POSTs on others with same issue earlier.
Yes, I chose my wording badly. I just wanted to put some words in my message other than just a link with no explanantion given (as I did on my first). So I just quickly jotted down a few words with few letters.
OBVIOUSLY, the onus is on Apple. This is not a fix be any means, but if works a great workaround for those with an appetitie to do it.
I fear, escepecially since I've read somewhere along the way researching this issue that Apple has known about this issue in pre-releases in Dec. If (BIG IF) true, writing is on the wall this won't get addressed. At least not in any resemblance of an acceptable timeframe by us.
Apple still pushed it though, and unless we work for the company writing the code, we will never know if they did it knowing this was going to happen. (Just 3rd party accounts of posts like this that claim they read it some where).
Only affects 6 year old models? Of which coincedently happens to be the cut off for Mountain Lion. I don't like my odds on a true fix coming any time soon.