HALLELUJAH!
Will we just be able to update our current install or do we need to start over again.
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.
[Guide] Success! Install 10.8 on old unsupported Mac
- Thread starter hackerwayne
- Start date
- Sort by reaction score
HALLELUJAH!
Will we just be able to update our current install or do we need to start over again.
I say again. I won't be implementing 64-bit into 10.8. You're just killing the chances of these stuffs being able to work on 10.9. Yes, i do have X3100 & GMA 950 working on 64-bit. That means all current dropped line up (all 6 families) will run 64-bit MLPF.
----------
Update is possible. But clean install is always recommended.
I need to resolve:
Code:
13.05.13 20:35:22,000 kernel[0]: ERROR: FireWire unable to determine security-mode; defaulting to full-secure.
13.05.13 20:35:22,000 kernel[0]: 32.315915: wlan_vap_create : enter. devhandle=0x5035d658, opmode=IEEE80211_M_STA, flags=0x1there is still no iMessage,
yesterday clover worked just fine, but today I reinstalled it (I pretty sure I used the same settings: UEFI, 64bit graphics driver - this did the trick for the gui yesterday although Clover boots in 32bit uefi mode) but there's (again) no GUI loading until I reach the desktop/login screen...
If your working with clover may you post your config.plist?
and if not are you willing to install clover (I think it run's fine side by side with Chimera/Chameleon) and create a config.plist which works for you (including iMessage)
That would be great.
Anyway: any detailed information how I could solve this would be great.
@Rastafabi
hi i dont use clover but this might help you for imessage fix
http://hackintoshmumbai.blogspot.com.es/2013/04/imessage-fix-with-clover.html
hi i dont use clover but this might help you for imessage fix
http://hackintoshmumbai.blogspot.com.es/2013/04/imessage-fix-with-clover.html
Future?
So, this has been amazing, thanks to everyone who has been a part!
This also begs the question, what's the future? Is there any possibility of work done to 10.9? Or whatever comes next? Or are these Macs finally dead at ML? I'm just curious, it would be awesome to try and get them even further!
Thanks,
Noah Budgor
So, this has been amazing, thanks to everyone who has been a part!
This also begs the question, what's the future? Is there any possibility of work done to 10.9? Or whatever comes next? Or are these Macs finally dead at ML? I'm just curious, it would be awesome to try and get them even further!
Thanks,
Noah Budgor
So, this has been amazing, thanks to everyone who has been a part!
This also begs the question, what's the future? Is there any possibility of work done to 10.9? Or whatever comes next? Or are these Macs finally dead at ML? I'm just curious, it would be awesome to try and get them even further!
Thanks,
Noah Budgor
No one knows, not even Apple. We don't know what requirements 10.9 will have, and Apple doesn't even test 10.9 against these machines. I do find it hilarious that some seem to think Apple is actively trying to shut down utilities like this by coding against them. Apple didn't just arbitrarily say "Hey, lets cut off these machines so they have to upgrade!" They likely looked at the development work involved in making these machine families run 10.8 and decided that the cost and time involved was too great to create a stable, rock solid solution. I know I know, "Look at what these guys did, its possible and Apple didn't do it on purpose!" To which I just need to point to pages upon pages of posts where things are broken, half-functional, or less than perfect. Apple is a company where none of these issues would fly as releasable products to the consumer.
Will 10.9 be modifiable to run on these old machines? Perhaps. Will Apple actively devote resources to stop it? Of course not. Will they create a product that runs best on supported hardware with no regard to how their choices may negatively impact this and other such projects? Of course.
Last edited:
Is there an easy way to Backup the existing install and import it into a clean install? Apps etc?
time machine does that...and then after the clean install you can use the migration assistant
Bonjour is broken, and both of those things rely on it. Theres a fix a few pages back, but supposedly its fixed in 0.3 which should hit fairly soon.
Well, yes I totally agree. I'm just excited for what may come of all this in the future. I certainly have no money/plans to spend on a new Mac, mine was given to my by my uncle! (lucky guy with a rMBP), so it's cool to see how much you can get out of these machines. Sure, it's no gamer, but it runs everything very well, even on 'unsupported' ML. Here's to a bright future, whatever it may hold for all our older Macs!
Excuse me dude? Did you see what i posted? If you refuse to follow what we plan then please leave the thread and discuss this else where. Most importantly, don't use our files.
----------
So, this has been amazing, thanks to everyone who has been a part!
This also begs the question, what's the future? Is there any possibility of work done to 10.9? Or whatever comes next? Or are these Macs finally dead at ML? I'm just curious, it would be awesome to try and get them even further!
Thanks,
Noah Budgor
Sure, some ppl like Rastafabi just killing the chances of MLPF 64 being able to work on 10.9.
Excuse me, but this is a public forum and "your" files are Apple's intellectual property. I'm all for hacking and modding things, but don't act like you coded a driver yourself or something like that. If YOU don't like people hacking and modding your hacked and modded files, don't release to the public. And I fail to see how any of this is going to "kill" the chances of 10.9 working; its a little ridiculous to think Apple gives a rats behind what you're doing, let alone that they would use development man-hours to block your method. If it does break, its because they developed with no regard to what you were doing, not some "grudge."
I'm sorry! I never meant to offend you in any way. I'm trying to support you and everyone who want to get the best out of his/her old machine. If you don't want me to do this, fine - I will stop as I am depended on the work you and MLforAll have done.
Anyway, I don't know in which way I'm killing any chance in any way as I'm not doing anything else than turning my MacBook into an Hackintosh build up on MLPF, having in mind to improve things that weren't done/couldn't be done right now.
You might remember I gave instructions for restoring the RecoveryHD, just to give an example that I attend to be productive.
Well. As it seems your not fine with that... So I will stop, as I want this thread to be focused on developing/modding instead of arguing
Concerning 10.9 I think we (sorry, YOU) won't have a chance, as it's time for Apple to switch to OpenGL4 (and most of our chipsets just aren't capable) - although I still hope they won't...
----
@Senseotech: Thanks for defending me.
Ummm
Not to be a big meanie or anything but how do you know what Apple thinks at all and that they are not watching all this and trying to stop it? I have seen Apple do that very thing before and am sure they do it again. I completely see what Wayne is saying and would rather wait then ruin the chances of things working in the future.
Not to be a big meanie or anything but how do you know what Apple thinks at all and that they are not watching all this and trying to stop it? I have seen Apple do that very thing before and am sure they do it again. I completely see what Wayne is saying and would rather wait then ruin the chances of things working in the future.
Really, when has this happened? And don't say jail breaking, as that's an entirely different thing. Those are major security exploits that would be negligent for apple not to fix; this is not that. If anything, the team on the OS X side has embraced hacking and modding. Every version of OS X gets easier to hackintosh, which is arguably more detrimental to Apple than this is.
Last edited:
60 gb ssd primary - how?
My MacBook Pro from 2006 has a 60 GB primary HD with 40 GB taken up by Lion. My secondary is 250 GB. Is there anyway to install ML using MLPostFactor. I have the Mountain Lion.app in my Apllications folder. I'm pretty new to this, but have spent hours trying to get this puppy to take ML.
Thanks
My MacBook Pro from 2006 has a 60 GB primary HD with 40 GB taken up by Lion. My secondary is 250 GB. Is there anyway to install ML using MLPostFactor. I have the Mountain Lion.app in my Apllications folder. I'm pretty new to this, but have spent hours trying to get this puppy to take ML.
Thanks
Its not that im preventing/don't like people from modding my files, I've made my statement above. If you don't like it, fine. You fail to see how its gonna kill chances of 10.9 working. Fine. Your problem, not mine.
And i do not want to argue further. I'm pretty sure you're using my modded files as well. So if you still wanna argue, I rather you format your Mac, go back to Lion and get lost. I'm not here to argue with all these craps.
I fail to see why Apple would stop using 32-bit kernel, is there any major purpose for that? No? And DP1 still has a 32-bit kernel on it? Isn't that some sort of preventive method to stop it being hacked on older Macs? Like lion? But whatever it is, if that method doesn't work on 10.9, we can always release for 10.8. I don't see why you're so angry anyway.
----------
Follow the guide but install it onto the 250GB instead. You can partition both Install & ML onto 250GB as long as its an internal drive.
Last edited:
Thats the beauty of posting on a public forum you have no ownership over; you have absolutely no say in the discourse. Just like publicly releasing files, you get no say over who uses them or not. This is a forum, where people come to discuss, both positively and not so positively, things. If you can't handle reasonable criticism, you have no business being here, especially not with a holier than thou attitude like you're rocking right now. If you want to control the entire conversation, take it somewhere you have control and can censor to your heart's content. Until then, you're posting on a (mostly) public forum where people can and will continue to provide reasonable critiques.
And I fail to see the reason its going to "kill" a 10.9 workaround because there is no reason. Really, provide a single instance that makes you think Apple is actively monitoring and stifling this project? I provided evidence to back up my claim, you should be expected to do the same.
I already posted it above. Please read. Like I said, why not create your own method and get lost. No one wants to argue here any further. You fail to think that we all have the same motive to make 10.8 run on older Macs. Regardless whether Apple is monitoring this thread, why not wait till 10.9 DP is out and see if the 64-bit could benefit from there? If it doesn't, its not too late to release it for 10.8 anyway. I don't see why you're arguing here.
----------
I don't see your point here.
Your points:
1. Im restricting others use of my files.
- I didn't. All i said was "Don't discuss 64-bit here, wait for 10.9 to be released"
2. You claimed 10.9 won't benefit from this
- Fine mate! Its your opinion. But will it hurt if we see 10.9 DP release first before releasing it for 10.8? Whether or not 10.9 will benefit from this. If it doesn't then release for 10.8. Simple. Don't get my point? Then you should really get lost cuz you're only here to argue.
Yes, removing the 32 bit kernel was a move to kill your project that didn't exist yet and artificially lock out consumers. That's much more plausible than it taking too many internal resources to get running stably and without issue. It took you how long to get it working? And with how's my outstanding issues? If they shipped a product like this, the market would go nuts. So they made the call to cut mountain lion off where they did to make development easier and to deliver a consistent product. If you want to keep thinking they're actively stifling your project, go right ahead. I'm just saying, it's a little silly to think a multimillion dollar global corporation is out to stop you.
Read my last post. Please. I don't know why you're still arguing here.
Omg. Dude, this is a non-profitable project. Did i charge you for it? No? Answer my questions above or shut the f up man.
My problem is with you taking files that aren't yours, modifying them, and then thinking you somehow get to tell others they can't do the same. My problem is with you withholding something you claim is working fine because of an asinine, paranoid worry that Apple will purposely thwart you, and anyone who says otherwise gets met with the reply "stop talking," like you're a six year old.
Edit since you like to do them so much: I never insinuated it was about money. I was using that as an example; apple wouldn't release a product that was as buggy and broken as mountain lion on these machines is. I admire that you've hacked it together to run, but it's cludgy and buggy nonetheless. Did you ever stop and think, "maybe apple had these problems too and decided it wasn't worth it?" That's a much more reasonable, same thought than "they're out to stop me."
Then get lost! Create your own files and post it up here. I'm waiting! People like you makes all the developers thinks twice before contributing to the public.