personguy

this is fantastic. i'm trying to figure out how to do this on my own before "giving up" and sending you my files i already patched the DSDT that i was using when i finally got ML running out of safe mode. (had to use some common sense when googling the warnings and errors after compile because some of the only solutions were in danish and german websites..) but it compiles fine and i've been using that ever since. however, on my laptop, the battery is suffering majorly when i go without the power supply. normally i get over 6+ hours of regular or even video play+internet youtube etc out of my battery under win 7, but the hackintosh is doing that "losing 1% every minute" thing, so i want to see if i can really get my head around the DSDT and speedstepping and all that. one word of worry, there's nothing in my BIOS that references HPET at all, and i understand this is required to get speedstepping working. anyway, even if i could just fiddle and fudge with the DSDT until all or most of the hardware was recognised through that and i could do away with as many kexts as possible, i'd be a happy camper. so, a quick question: i have the files from the aida64 program, but they're saved in .bin format. how should i proceed to get these in an edit-able state with DSDT patcher? is it as straightforward as just changing the extension? thanks for all the great reading and hard work available in here, btw.

used that guide, with the Extra_ML folder replacing mine, and now have a bit of work cut out for me trying to get my old Extra folder back through Terminal off my usb stick no matter, i don't mind being in terminal. i went against my better judgement on that one, not because you suggested it of course, just because i had a look in the files before using them and everything looked like it wasn't going to fit. no fix file for the 1600x900, and in fact the boot.plist had the resolution set at 1080p, plus what appeared to be a smbios.plist for an i7 Ivy Bridge .. but i'm still trying to figure out where the smbios.plist fits into the whole picture and how incorrect info in there affects a successful or unsuccessful boot. now i can't find a single flag that will get me close to a successful boot (-x -f -F config=Null config= DSDT=Null DSDT= ... yeah, still don't understand if you're supposed to type the word "Null" or just leave it blank. somewhere i read that the "DSDT" is case-sensitive, but that's all the info i could find on the matter) so far i've not managed a single scenario where i can boot successfully (including the usb installer) without the -x flag .. and i have tried (and documented) a LOT of combinations of a lot of boot flags. in fact, i still have the "Invalid Partition" message at boot-up, though i must have gone through 7 Chameleons by now. maybe it's down to the fact that i'm only ever working in safe boot mode. still plugging away at it, reading reading reading thanks for any more advice. i thought for a second when i sat down at this after work tonight (seems like a day ago) that i came across someone by the name of something like cupcakks, or similar, who had a very similar machine to mine.. but i managed to lose the webpage and hadn't bookmarked it yet. can't find it in my history either. if anyone out there in osxlatitude knows this user i'd be interested to swap notes. three 10-hour sessions and i'm still booting into safe mode. it's a marathon!

would you mind passing on some clues as to how you finally got it working? lots of reading in this forum this week, and i have a feeling i'm close, but just might need that extra morsel of information to finish the puzzle. thank you!

hello there. i'm new to this particular scene, thought i did work on a hackintosh on a dell tower several years ago successfully. i have the e6430 with nvs5200m/intell hd 4000, i5 3320m, 1600x900 display, so not exactly any of the configurations i've seen in here yet. i've read and followed the threads from jake lo and others. i did a step-by-step myhack using the InstallESD.dmg for 10.8.3 ML. i originally used the E6430HD4000.zip from jake lo's guide, hoping to make some headway and then get down to tweaking for my particulary system. but the dsdt didn't work for me. at least, there is no way i could boot off either the usb installer or the successful installation without the boot flag DSDT=Null. at present i can either use DSDT=Null -x to get the installed os x up and running in safe boot mode, or the usb bootloader up and running with the same DSDT=Null flag. this works in 1600x900 using "Graphics Mode" but i'm not convinced this is down to the AppleIntelFramebufferCapri.kext that jake lo offered (i got 1600x900 before renaming the file correctly). however, again it's only in safe mode. without safe mode i get stuck in several places, depending on what boot flags i'm trying. the most success seems to come from just using GraphicsEnabler=Yes, which at least seems to finish the loading screen before leaving me with a black screen. yes, i did see the note about this in Jake Lo's post, but i haven't gotten any steps to work for me. i also get the Invalid Partition Table error, even though i've since rebooted with the usb installer (no DSDT) and ran myhack on my installation hard drive to clean up the cache and permissions, after installing chameleon. so, i'm looking at making my own DSDT.aml file, to see if that will help. but i'm a bit confused as to the wording in the guide. when booting from the usb bootloader, i'm given the opportunity to use the Utilities menu, with Disk Utility and Terminal and MyHack, etc. otherwise carry on and install from the usb onto a chosen hard drive. so if i'm booting off the usb bootloader, how am i supposed to unzip and then open this editor? also, have i missed something completely in all this reading? i know there are very few clean cut answers that work for everyone when it comes to this stuff, but i seem to be having more instances of what's written in the posts not behaving the same way on my end than i am successes based on the research... if that makes sense. i really don't want to just click and point my way through this and pick up the pieces of everyone's hard work. i'd like to understand, or do my best to understand, the whole process. but i'm trying to sort out how to know what success means what and what failure points to what obstacle. e.g. if my DSDT.aml file isn't right or is missing, does that account for graphics problems? are issues related to my graphics pretty much found in kexts and how they're loaded and their permissions? if i edit the chamelion.Boot.plist in the /Extras folder on my installation, is that the right one to be editing? if so why do the changes in the file not reflect properly at boot up, even though i've repaired permissions and run MyHack on the hard drive to rebuild caches and all? in other words, i'm having a hard time determining what i'm seeing as a result of something i did or didn't do between the feeback from the computer and what i'm reading online. if someone else has the same chip as i, but a different resolution monitor, is it any good using their working DSDT.aml file? sorry for all the questions at once. just trying to get a grip on what i'm learning here. figuring how to turn the information into knowledge. been reading and trying for 24 hours now thanks for any help with any of these questions! how to actually use the DSDT extractor would be a great help!