>> Alas, iHackintosh does not provide a "post
>> installation" application, but the iHackintosh flash drive may be used
>> as
>> a "helper", just as you would with, say, UniBeast, to get the
>> just-installed OS X system to boot into the Desktop, after which you may
>> use, say, MultiBeast to install the boot loader.
>>
>
> So since MultiBeast breaks your installation like mine, are you continuing
> to boot your systems using this iHackintosh flash drive? Just curious.
I believe I used a pre-5.0.2 version of MultiBeast For Lion to install
Chameleon, as I was using a "developer" version of Mountain Lion, as I am
an Apple Developer.
However, remember that I was making my machines for Mountain Lion BEFORE
tonymacx86's self-imposed "non-disclosure agreement" vis a vis Mountain
Lion had expired. Perhaps several weeks before, in fact.
But, I was using the very same version of Mountain Lion that, some time
later, EVERYONE, EVERYWHERE, including tonymacx86, was able to get from
the Apple Store.
I can see that my hard drive also has MultiBeast for Lion 4.6.1 on it, and
I may have used portions of that earlier MultiBeast to install Hackintosh
functionality to my Mountain Lion systems. Frankly, I cannot now remember.
One thing is certain, my DC7900 systems have NEVER run anything except
Mountain Lion.
Another thing is certain, my DC7800 SFF system has never run anything
except Lion.
Now, I DO HAVE a DC7800 CMT which was converted to a DC7900 through the
exchange of its motherboard. THAT CMT MAY HAVE run Lion when operating as
a DC7800 CMT ... frankly, at this point I cannot remember ... BUT, when it
was converted to a DC7900 CMT is was definitely, and it still is, running
Mountain Lion.
> It is the DSDT itself which is responsible for making the DC7900 appear to
>> be "Mac like".
>>
>>
> Thank you, that was a great explanation. How are you applying it to your
> system without MultiBeast? Are you putting it in /Extra and telling
> Chimera/Chameleon about it somehow?
You know, sometimes I feel I have to resort to "spoon feeding" OS X.
I am NOT above creating my own /Extra folders, and then moving, by hand,
the DSDT into the root of that folder, and also creating an
/Extra/Extensions folder and moving the VERY FEW kexts which I believe are
necessary.
tonymacx86 has basically abandoned the entire concept of a
pristine/"virgin" /System/Library/Extensions folder (with ALL the
over-riding kexts in /E/E), yet the /E folder is still necessary for the
boot loader.
Frankly, I wish tonymacx86 would get his f-ing head screwed on correctly
and stop changing the course of the OSx86 "ship" when that "ship" is in
the middle of the Atlantic.
FOR THE RECORD, here is the contents of my /Extra folder on Mountain Lion:
dsdt.aml (presently Rev. F) The "final" version ... just happens to be
Rev. F ... I was working on a Rev. G, but that proved to be unnecessary
~dsdt.aml (an earlier version, presumably Rev.E)
~~dsdt.aml (an earlier version, presumably Rev.D)
~~~dsdt.aml (an earlier version, presumably Rev.C)
~~~~dsdt.aml (an earlier version, presumably Rev.B)
~~~~~dsdt.aml (an earlier version, presumably Rev.A) First production version
~~~~~~dsdt.aml (an earlier version, presumably Rev.1) Second development
version
~~~~~~~dsdt.aml (an earlier version, presumably Rev.0) First development
version
... and /Extra/Extensions
FakeSMC.kext Always required
PXHCD.kext Only necessary if a compliant USB 3.0 card is installed
(and only those)
/Modules
(Whatever the boot loader application placed there)
org.chameleon.Boot.plist
smbios.plist
(whatever the application placed there)
/Theme
"crap" which tonymacx86 placed there