JoeyKing Posted September 24, 2010 Share Posted September 24, 2010 On my harddrive (GPT) I have several partitions with OsX. I installed Chameleon to Part1. I also have say Part2 with OsX. I want to make experiments to Part2, while leaving Part1 in peace. I have /Extra on both partitions. My question: during the boot process, which data from which partition is taken into account? 1. Part1/Extra/com.boot.Apple.plist --> this is loaded by Chameleon, because Part1 is booted. right? Also the Themes from Part1 are always loaded. 2. which DSDT.aml is loaded? - boot Part1 --> obviously Part1/Extra/DSDT.aml - boot Part2 in chameleon. Which one? 3. Kexts in SLE: obviously the ones from the partition I choose to boot. 4. /Library/Preferences/SystemConfiguration/com.apple.Boot.plist: is this considered at all? if yes, it must be per partition 5. Kexts in Part1/Extras obviously when I boot Part1 6. Kexts in Part2/Extras are they taking into account when booting Part2? 7. same for smbios.plist Thanks Joey Link to comment Share on other sites More sharing options...
enochpc Posted September 24, 2010 Share Posted September 24, 2010 As I understand it, nothing from Extra nor the DSDT.aml is loaded until you chose a partition to boot. I have a PC with 10.5.6 iDeneb and 10.6.2 Hazard and both boot fine, and definitely have different boot requirements. Link to comment Share on other sites More sharing options...
JoeyKing Posted September 24, 2010 Author Share Posted September 24, 2010 ..but for sure the com...plist is loaded before anything is chosen, because it sets the Resolution, right? and hence also Graphics enabler etc is set, and I cannot chose between yes or no? confused, Joey Link to comment Share on other sites More sharing options...
enochpc Posted September 24, 2010 Share Posted September 24, 2010 No, because you have separate com.plist files for each install, loads after you select one. The resolution/driver that chameleon loads is just a generic driver, isn't the same as what ultimately loads when you boot. Link to comment Share on other sites More sharing options...
JoeyKing Posted September 24, 2010 Author Share Posted September 24, 2010 so this means the com.plist is read twice: once upon chamelon startup to obtain resolution and timeout and other chameleon specific stuff, and it is read a second time when the kernel is booted? IMHO it would be clearer if the Chameleon developers offered two separate directories: one for starting up chameleon (to be placed on the unique chameleon partition), and another one which is used when the kernel is started (to be replicated in each OsX partition)....most likely they know better :-) than I. Thanks Joey Link to comment Share on other sites More sharing options...
Recommended Posts