jasjeet Posted July 1, 2014 Share Posted July 1, 2014 Can somebody give me some help to hide my partitions and rename the Windows 7 UEFI and Mac OS X UEFI boot titles? Ive been reading the wiki but really none of my edits have done anything. The only thing I've managed to do is hide the Legacy partitions. Ive attached my config.plist, and i have the partition UUIDs i want to hide. Ive tried using the Hide Key and the custom Entries Key but no luck. Also my SSD has the OS X installation as the first partition, OS X as 2nd, Win 7 as 3rd. Is it possible to hide the OS X installer even if I've installed Clover to that partition? Ideally i just want to see OS X and Win 7 partitions. Also i can't get the timeout and default partition selector to work, any help appreciated. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <false/> <key>AddHDMI_8000000</key> <false/> <key>AddIMEI_80000</key> <false/> <key>AddMCHC_0008</key> <false/> <key>AddPNLF_1000000</key> <false/> <key>DeleteUnused_400000</key> <false/> <key>FIX_ACST_4000000</key> <false/> <key>FIX_ADP1_800000</key> <false/> <key>FIX_INTELGFX_100000</key> <false/> <key>FIX_RTC_20000</key> <false/> <key>FIX_S3D_2000000</key> <false/> <key>FIX_TMR_40000</key> <false/> <key>FIX_WAK_200000</key> <false/> <key>FakeLPC_0020</key> <false/> <key>FixAirport_4000</key> <false/> <key>FixDarwin_0002</key> <false/> <key>FixDisplay_0100</key> <false/> <key>FixFirewire_0800</key> <false/> <key>FixHDA_8000</key> <false/> <key>FixHPET_0010</key> <false/> <key>FixIDE_0200</key> <false/> <key>FixIPIC_0040</key> <false/> <key>FixLAN_2000</key> <false/> <key>FixRegions_10000000</key> <false/> <key>FixSATA_0400</key> <false/> <key>FixSBUS_0080</key> <false/> <key>FixShutdown_0004</key> <false/> <key>FixUSB_1000</key> <false/> <key>NewWay_80000000</key> <false/> </dict> <key>Name</key> <string>DSDT.aml</string> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>Cpu0Ist</string> </dict> </array> <key>HaltEnabler</key> <true/> <key>SSDT</key> <dict> <key>EnableC2</key> <false/> <key>EnableC4</key> <false/> <key>EnableC6</key> <true/> <key>EnableC7</key> <false/> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>npci=0x2000 darkwake=0 kext-dev-mode=1</string> <key>DefaultVolume</key> <string>MacHDD</string> <key>Fast</key> <false/> <key>Legacy</key> <string>PBR</string> <key>Log</key> <false/> <key>Timeout</key> <integer>5</integer> <key>XMPDetection</key> <string>-1</string> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <string>No</string> </dict> <key>FakeID</key> <dict> <key>ATI</key> <string>0x0</string> <key>IMEI</key> <string>0x0</string> <key>IntelGFX</key> <string>0x0</string> <key>LAN</key> <string>0x0</string> <key>NVidia</key> <string>0x0</string> <key>SATA</key> <string>0x0</string> <key>WIFI</key> <string>0x0</string> <key>XHCI</key> <string>0x0</string> </dict> <key>Inject</key> <false/> <key>USB</key> <dict> <key>AddClockID</key> <false/> <key>FixOwnership</key> <false/> <key>Inject</key> <false/> </dict> </dict> <key>DisableDrivers</key> <array> <string>Nothing</string> </array> <key>GUI</key> <dict> <key>Hide</key> <array> <string>Windows</string> <string>BOOTX64.EFI</string> <string>DE94BBA4-06D1-4D40-A16A-BFD50179D6AC</string> <string>3D6B109C-F31C-4246-9CE3-033143A9F360</string> <string>1602040E-76F4-4D86-99EB-8483CBEA56B3</string> <string>64594DE6-AB21-4C2A-9294-004A2D941A17</string> </array> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>Enabled</key> <true/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <false/> <key>Tool</key> <true/> </dict> <key>TextOnly</key> <false/> <key>Theme</key> <string>metal</string> <key>Entries</key> <array> <dict> <key>Volume</key> <string>03D8269E-5072-4B68-84AA-9968F01A2727</string> <key>Title</key> <string>Windows 7</string> </dict> </array> </dict> <key>Graphics</key> <dict> <key>Inject</key> <dict> <key>ATI</key> <false/> <key>Intel</key> <false/> <key>NVidia</key> <false/> </dict> <key>PatchVBios</key> <false/> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <false/> <key>AsusAICPUPM</key> <false/> <key>Debug</key> <false/> <key>KernelCpu</key> <false/> </dict> <key>RtVariables</key> <dict> <key>LogEveryBoot</key> <string>10</string> <key>LogLineCount</key> <integer>3000</integer> <key>MountEFI</key> <true/> </dict> <key>SMBIOS</key> <dict> <key>BiosReleaseDate</key> <string>12/19/13</string> <key>BiosVendor</key> <string>Apple Inc.</string> <key>BiosVersion</key> <string>MP61.88Z.0116.B04.1312061508</string> <key>Board-ID</key> <string>Mac-F60DEB81FF30ACF6 </string> <key>BoardManufacturer</key> <string>Apple Inc.</string> <key>BoardType</key> <integer>11</integer> <key>ChassisAssetTag</key> <string>Pro-Enclosure</string> <key>ChassisManufacturer</key> <string>Apple Inc.</string> <key>Family</key> <string>Mac Pro</string> <key>FirmwareFeatures</key> <string>0400000000000000</string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ProductName</key> <string>MacPro6,1</string> <key>SerialNumber</key> <string>F5KLV135F693</string> <key>Version</key> <string>1.0</string> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> <key>InjectSystemID</key> <false/> </dict> </dict> </plist> 1 Link to comment Share on other sites More sharing options...
Maniac10 Posted July 1, 2014 Share Posted July 1, 2014 Post a boot log to see what's detected. Link to comment Share on other sites More sharing options...
jasjeet Posted July 2, 2014 Author Share Posted July 2, 2014 Here is the preboot.log Edit Managed to hide the partitions using the GUID. The Clover Wiki is wrong, UUID does not work! Also i set DefaultVolume to EFI so that it selects my Windows 7 partition to boot by default with a 5 second timeout. I guess this will need changing when i rename the partition. Now lastly I'm trying to work out how the rename the "Boot Microsoft EFI from EFI" and "Boot Mac OS X from Mac OS X" to something that sounds better. Ideally Boot Windows 7 and Boot Mac OS X. Any help here? I modified my custom boot entry with the correct GUID (previously used UUID) but that didn't work. 0:100 0:100 MemLog inited, TSC freq: 3266930516 0:100 0:000 0:100 0:000 Now is 2.7.2014, 9:53:43 (GMT+2047) 0:100 0:000 Starting Clover rev 2747 on American Megatrends EFI 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000) @C07E5518 0:100 0:000 SelfDirPath = \EFI\BOOT 0:100 0:000 UnicodeCollation Status=Success 0:100 0:000 Total Memory Slots Count = 4 0:100 0:000 Type 17 Index = 0 0:100 0:000 SmbiosTable.Type17->Speed = 1866 0:100 0:000 SmbiosTable.Type17->Size = 4096 0:100 0:000 Type 17 Index = 1 0:100 0:000 SmbiosTable.Type17->Speed = 1866 0:100 0:000 SmbiosTable.Type17->Size = 4096 0:100 0:000 Type 17 Index = 2 0:100 0:000 SmbiosTable.Type17->Speed = 1866 0:100 0:000 SmbiosTable.Type17->Size = 4096 0:100 0:000 Type 17 Index = 3 0:100 0:000 SmbiosTable.Type17->Speed = 1866 0:100 0:000 SmbiosTable.Type17->Size = 4096 0:100 0:000 Boot status=0 0:100 0:000 Clover revision: 2747 running on System Product Name 0:100 0:000 ... with board RAMPAGE IV GENE 0:100 0:000 Clover load options size = 0 bytes 0:104 0:004 Using OEM config.plist at path: EFI\CLOVER\config.plist 0:105 0:000 EFI\CLOVER\config.plist loaded: Success 0:107 0:001 Loading early settings 0:107 0:000 timeout set to 5 0:107 0:000 Default theme: metal 0:107 0:000 Hiding entries with string Windows 0:107 0:000 Hiding entries with string BOOTX64.EFI 0:107 0:000 Hiding entries with string DE94BBA4-06D1-4D40-A16A-BFD50179D6AC 0:107 0:000 Hiding entries with string 3D6B109C-F31C-4246-9CE3-033143A9F360 0:107 0:000 Hiding entries with string 1602040E-76F4-4D86-99EB-8483CBEA56B3 0:107 0:000 Hiding entries with string 64594DE6-AB21-4C2A-9294-004A2D941A17 0:107 0:000 LoadDrivers() start 0:109 0:002 Loading EmuVariableUefi-64.efi 0:109 0:000 EmuVariableUefi Initialize: VariableCommonInitialize = Success, orig services stored, install gEmuVariableControlProtocolGuid = Success 0:111 0:001 Loading FSInject-64.efi 0:111 0:000 Loading OsxAptioFixDrv-64.efi 0:112 0:000 Loading OsxFatBinaryDrv-64.efi 0:112 0:000 Loading VBoxHfs-64.efi 0:113 0:000 - driver needs connecting 0:113 0:000 1 drivers needs connecting ... 0:113 0:000 PlatformDriverOverrideProtocol->GetDriver overriden 0:113 0:000 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok 0:473 0:359 LoadDrivers() end 0:473 0:000 EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success 0:484 0:011 SetMaxResolution: found best mode 6: 1600x1200Video mode change to mode #6: Device Error 0:518 0:034 - Device Error 0:518 0:000 QueryMode 5 Status=Success 0:683 0:164 Video mode change to mode #5: Success 0:683 0:000 Console modes reported: 3, available modes: 0:683 0:000 Mode 1: 80x25 (current mode) 0:683 0:000 Mode 2: 80x50 0:683 0:000 Mode 3: 100x31 0:940 0:256 reinit: self device path=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000) 0:940 0:000 new SelfHandle=C07E5518 0:940 0:000 CPU Vendor = 756E6547 Model=206D5 0:940 0:000 The CPU supported turbo 0:940 0:000 BrandString = Genuine Intel(R) CPU @ 3.30GHz 0:940 0:000 MSR 0xE2 before patch 1E000400 0:940 0:000 MSR 0xE4 00010414 0:940 0:000 MSR 0xCE 00000C00_78012100 0:940 0:000 MSR 0x1B0 00000000 0:940 0:000 FSBFrequency=100MHz 0:940 0:000 Corrected FSBFrequency=100MHz 0:940 0:000 Vendor/Model/Stepping: 0x756E6547/0x2D/0x5 0:940 0:000 Family/ExtFamily: 0x6/0x0 0:940 0:000 MaxDiv/MinDiv: 33.0/12 0:940 0:000 Turbo: 57/57/57/57 0:940 0:000 Features: 0xBFEBFBFF 0:940 0:000 Threads: 12 0:940 0:000 Cores: 6 0:940 0:000 FSB: 100 MHz 0:940 0:000 CPU: 3300 MHz 0:940 0:000 TSC: 3300 MHz 0:940 0:000 PIS: 400 MHz 0:940 0:000 PCI (00|00:00.00) : 8086 3C00 class=060000 0:940 0:000 PCI (00|00:02.00) : 8086 3C04 class=060400 0:940 0:000 PCI (00|00:03.00) : 8086 3C08 class=060400 0:940 0:000 PCI (00|02:00.00) : 1002 6898 class=030000 0:940 0:000 Found Radeon model=ATI Radeon HD 5870 Series 0:940 0:000 PCI (00|02:00.01) : 1002 AA50 class=040300 0:940 0:000 PCI (00|00:01.00) : 8086 3C02 class=060400 0:940 0:000 PCI (00|00:05.00) : 8086 3C28 class=088000 0:940 0:000 PCI (00|00:05.02) : 8086 3C2A class=088000 0:940 0:000 PCI (00|00:05.04) : 8086 3C2C class=080020 0:940 0:000 PCI (00|00:11.00) : 8086 1D3E class=060400 0:940 0:000 PCI (00|00:16.00) : 8086 1D3A class=078000 0:940 0:000 PCI (00|00:19.00) : 8086 1503 class=020000 0:940 0:000 PCI (00|00:1A.00) : 8086 1D2D class=0C0320 0:940 0:000 PCI (00|00:1B.00) : 8086 1D20 class=040300 0:940 0:000 PCI (00|00:1C.00) : 8086 1D10 class=060400 0:940 0:000 PCI (00|00:1C.04) : 8086 1D18 class=060400 0:940 0:000 PCI (00|06:00.00) : 1B21 1042 class=0C0330 0:940 0:000 PCI (00|00:1C.05) : 8086 1D1A class=060400 0:940 0:000 PCI (00|07:00.00) : 1B21 0612 class=010601 0:940 0:000 PCI (00|00:1C.07) : 8086 1D1E class=060400 0:940 0:000 PCI (00|08:00.00) : 1B21 1042 class=0C0330 0:940 0:000 PCI (00|00:1D.00) : 8086 1D26 class=0C0320 0:940 0:000 PCI (00|00:1E.00) : 8086 244E class=060401 0:940 0:000 PCI (00|00:1F.00) : 8086 1D41 class=060100 0:940 0:000 PCI (00|00:1F.02) : 8086 1D02 class=010601 0:940 0:000 PCI (00|00:1F.03) : 8086 1D22 class=0C0500 0:940 0:000 ScanSPD() start 0:941 0:000 SMBus CmdReg: 0x1 0:941 0:000 Scanning SMBus [8086:1D22], mmio: 0xFBF24004, ioport: 0xF000, hostc: 0x1 1:087 0:145 ScanSPD() end 1:087 0:000 Get Acpi Tables List from RSDT: 1:087 0:000 Found table: FACP A M I len=132 1:087 0:000 Found table: APIC A M I len=256 1:087 0:000 Found table: FPDT A M I len=68 1:087 0:000 Found table: MCFG OEMMCFG. len=60 1:087 0:000 Found table: HPET A M I len=56 1:087 0:000 Found table: BGRT A M I len=56 1:087 0:000 Found table: SSDT CpuPm len=839976 1:087 0:000 Calibrated TSC frequency =3266930516 =3266MHz 1:087 0:000 Loading main settings 1:087 0:000 Dropping 3 tables 1:087 0:000 Drop table 0 signature="DMAR" (52414D44) 1:087 0:000 set table: 52414D44, 0 to drop: 1:087 0:000 Drop table 1 signature="SSDT" (54445353) table-id="CpuPm" (0000006D50757043) 1:087 0:000 set table: 54445353, 6D50757043 to drop: true 1:087 0:000 1:087 0:000 Drop table 2 signature="SSDT" (54445353) table-id="Cpu0Ist" (0074734930757043) 1:087 0:000 set table: 54445353, 74734930757043 to drop: 1:087 0:000 Config set Fixes will override FixMask mask! 1:087 0:000 final mask=00000000 1:087 0:000 Config set EnableC7: - 1:087 0:000 Config set EnableC6: + 1:087 0:000 Config set EnableC4: - 1:087 0:000 Config set EnableC2: - 1:087 0:000 Config set FakeCPUID=0 1:087 0:000 Error in Second part of settings0: Not Found 1:087 0:000 Oem smbios.plist not found at path: EFI\CLOVER\smbios.plist 1:087 0:000 smbios.plist not found, not overriding config.plist 1:087 0:000 found 21 volumes with blockIO 1:087 0:000 0. Volume: 1:087 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0) 1:087 0:000 Result of bootcode detection: bootable <null string> (<null string>) 1:088 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:088 0:000 1. Volume: 1:088 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0) 1:088 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:088 0:000 2. Volume: 1:088 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0) 1:089 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:089 0:000 3. Volume: 1:089 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0) 1:089 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:089 0:000 4. Volume: 1:089 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,MBR,0xAE9B3E20,0x800,0xE8E07800) 1:090 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:090 0:000 Volume 'Legacy HD1', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = <null guid> 1:090 0:000 5. Volume: 1:090 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(1,GPT,7CB0030B-C1F3-43A3-A109-07BDFC198579,0x22,0x40000) 1:090 0:000 Volume 'Legacy HD1', LegacyOS '', LegacyIcon(s) 'legacy', GUID = 7CB0030B-C1F3-43A3-A109-07BDFC198579 1:091 0:000 6. Volume: 1:091 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x1,0xFFFF,0x0)\HD(2,GPT,56DAB187-626F-4EC6-A4B1-0B5FCAAEC4EC,0x40800,0x15D4C9800) 1:091 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:091 0:000 Volume 'Legacy HD2', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = 56DAB187-626F-4EC6-A4B1-0B5FCAAEC4EC 1:091 0:000 7. Volume: 1:091 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(1,GPT,DA75A1CA-C634-4632-AFC0-B37FD92FD01A,0x800,0x96000) 1:092 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:092 0:000 Volume 'Legacy HD1', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = DA75A1CA-C634-4632-AFC0-B37FD92FD01A 1:092 0:000 8. Volume: 1:092 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,3CF19D9F-A9CC-4B70-B63A-500C885A0E4B,0x96800,0x32000) 1:093 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:108 0:015 Volume 'EFI', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = 3CF19D9F-A9CC-4B70-B63A-500C885A0E4B 1:108 0:000 9. Volume: 1:108 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(3,GPT,34B99496-2C8E-4B47-9EC1-96F892F2106E,0xC8800,0x40000) 1:108 0:000 Volume 'Legacy HD3', LegacyOS '', LegacyIcon(s) 'legacy', GUID = 34B99496-2C8E-4B47-9EC1-96F892F2106E 1:108 0:000 10. Volume: 1:108 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(4,GPT,BD3EE3E5-845B-4E4D-84C1-38832A23273A,0x108800,0xE8D00000) 1:109 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:109 0:000 Volume 'Legacy HD4', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = BD3EE3E5-845B-4E4D-84C1-38832A23273A 1:109 0:000 11. Volume: 1:109 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000) 1:110 0:000 Result of bootcode detection: bootable <null string> (<null string>) 1:120 0:010 Volume 'EFI', LegacyOS '', LegacyIcon(s) '<null string>', GUID = 1F461330-B56D-4DC0-91C0-752986BA9098 1:120 0:000 This is SelfVolume !! 1:120 0:000 12. Volume: 1:120 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(2,GPT,2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A,0x64028,0x1BF08F0) 1:121 0:000 Volume 'OS X Base System', LegacyOS '', LegacyIcon(s) '<null string>', GUID = 2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A 1:121 0:000 13. Volume: 1:121 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(3,GPT,9955B955-8243-459C-BB4D-88AD503A2C2F,0x1C55000,0x3F800) 1:121 0:000 Volume 'Legacy HD3', LegacyOS '', LegacyIcon(s) 'legacy', GUID = 9955B955-8243-459C-BB4D-88AD503A2C2F 1:121 0:000 14. Volume: 1:121 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(4,GPT,CC59F2F5-78B2-459A-9EB7-961543AB58E7,0x1C94918,0x4A817C8) 1:122 0:000 Volume 'Mac OS X', LegacyOS '', LegacyIcon(s) '<null string>', GUID = CC59F2F5-78B2-459A-9EB7-961543AB58E7 1:122 0:000 15. Volume: 1:122 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(5,GPT,27979390-F9D4-45BC-A745-B6AC6BC453F7,0x67160E0,0x135F20) 1:122 0:000 Volume 'Recovery HD', LegacyOS '', LegacyIcon(s) '<null string>', GUID = 27979390-F9D4-45BC-A745-B6AC6BC453F7 1:122 0:000 16. Volume: 1:122 0:000 PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(6,GPT,C7A4937A-4931-48FB-B045-A67124BD200A,0x684C000,0x16979800) 1:123 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:123 0:000 Volume 'Legacy HD6', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = C7A4937A-4931-48FB-B045-A67124BD200A 1:123 0:000 17. Volume: 1:123 0:000 PciRoot(0x0)\Pci(0x1C,0x4)\Pci(0x0,0x0)\USB(0x3,0x2) 1:123 0:000 USB volume 1:123 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:123 0:000 18. Volume: 1:123 0:000 PciRoot(0x0)\Pci(0x1A,0x0)\USB(0x1,0x0)\USB(0x1,0x0) 1:123 0:000 USB volume 1:123 0:000 USB volume 1:123 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:123 0:000 19. Volume: 1:123 0:000 PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\USB(0x1,0x0) 1:124 0:000 Result of bootcode detection: bootable <null string> (<null string>) 1:124 0:000 USB volume 1:124 0:000 Volume 'Whole Disc Boot', LegacyOS '', LegacyIcon(s) 'legacy', GUID = <null guid> 1:124 0:000 20. Volume: 1:124 0:000 PciRoot(0x0)\Pci(0x1C,0x7)\Pci(0x0,0x0)\USB(0x1,0x0)\HD(1,MBR,0xAE765E1D,0x800,0x3A384800) 1:125 0:000 Result of bootcode detection: bootable Windows (vista,win) 1:125 0:000 USB volume 1:125 0:000 Volume 'Legacy HD1', LegacyOS 'Windows', LegacyIcon(s) 'vista,win', GUID = <null guid> 1:125 0:000 Searching volumes for latest nvram.plist ... 1:125 0:000 8. Volume 'EFI', GUID = 3CF19D9F-A9CC-4B70-B63A-500C885A0E4B - no nvram.plist - skipping! 1:125 0:000 11. Volume 'EFI', GUID = 1F461330-B56D-4DC0-91C0-752986BA9098 - no nvram.plist - skipping! 1:125 0:000 12. Volume 'OS X Base System', GUID = 2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A - no nvram.plist - skipping! 1:128 0:002 14. Volume 'Mac OS X', GUID = CC59F2F5-78B2-459A-9EB7-961543AB58E7 - no nvram.plist - skipping! 1:131 0:003 15. Volume 'Recovery HD', GUID = 27979390-F9D4-45BC-A745-B6AC6BC453F7 - no nvram.plist - skipping! 1:132 0:000 nvram.plist not found! 1:132 0:000 PutNvramPlistToRtVars: nvram.plist not found 1:132 0:000 Invalidating BuiltinIcons... 1:132 0:000 no themes available, using embedded 1:132 0:000 Font 0 prepared WxH=7x12 CharWidth=7 1:132 0:000 Choosing theme <null string> 1:132 0:000 Custom entries start 1:132 0:000 Custom entries finish 1:132 0:000 Scanning loaders... 1:132 0:000 0: 'Whole Disc Boot' no file system 1:132 0:000 1: 'Whole Disc Boot' no file system 1:132 0:000 2: 'Whole Disc Boot' no file system 1:132 0:000 3: 'Whole Disc Boot' no file system 1:132 0:000 4: 'Legacy HD1' no file system 1:132 0:000 5: 'Legacy HD1' no file system 1:132 0:000 6: 'Legacy HD2' no file system 1:132 0:000 7: 'Legacy HD1' no file system 1:132 0:000 8: 'EFI' 1:136 0:003 found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x2,0xFFFF,0x0)\HD(2,GPT,3CF19D9F-A9CC-4B70-B63A-500C885A0E4B,0x96800,0x32000)\EFI\Microsoft\Boot\bootmgfw.efi 1:137 0:001 hiding entry: \EFI\BOOT\BOOTX64.efi 1:137 0:000 9: 'Legacy HD3' no file system 1:137 0:000 10: 'Legacy HD4' no file system 1:137 0:000 11: 'EFI' 1:138 0:000 found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000)\EFI\Microsoft\Boot\bootmgfw.efi 1:139 0:000 hiding entry: \EFI\BOOT\BOOTX64.efi 1:139 0:000 12: 'OS X Base System' 1:143 0:004 Check if volume Is Hibernated: 1:143 0:000 Check sleep image 'by signature': 1:148 0:004 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Not Found 1:148 0:000 using default sleep image name = \private\var\vm\sleepimage 1:153 0:005 sleepimage not found -> Not Found 1:153 0:000 hibernated: no - sign 1:157 0:003 found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(2,GPT,2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A,0x64028,0x1BF08F0)\System\Library\CoreServices\boot.efi 1:159 0:002 13: 'Legacy HD3' no file system 1:159 0:000 14: 'Mac OS X' 1:167 0:007 Check if volume Is Hibernated: 1:167 0:000 Check sleep image 'by signature': 1:174 0:007 read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success 1:174 0:000 SleepImage name from pref: ImageVolume = 'Mac OS X', ImageName = '\private\var\vm\sleepimage' 1:178 0:004 sleepimage not found -> Not Found 1:178 0:000 hibernated: no - sign 1:182 0:003 found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(4,GPT,CC59F2F5-78B2-459A-9EB7-961543AB58E7,0x1C94918,0x4A817C8)\System\Library\CoreServices\boot.efi 1:186 0:003 15: 'Recovery HD' 1:190 0:004 found PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(5,GPT,27979390-F9D4-45BC-A745-B6AC6BC453F7,0x67160E0,0x135F20)\com.apple.recovery.boot\boot.efi 1:191 0:001 16: 'Legacy HD6' no file system 1:191 0:000 17: 'Whole Disc Boot' no file system 1:191 0:000 18: 'Whole Disc Boot' no file system 1:191 0:000 19: 'Whole Disc Boot' no file system 1:191 0:000 20: 'Legacy HD1' no file system 1:191 0:000 Custom legacy start 1:191 0:000 Custom legacy end 1:191 0:000 Custom tool start 1:191 0:000 Custom tool end 1:193 0:001 found tool \EFI\CLOVER\tools\Shell64U.efi 1:193 0:000 Checking EFI partition Volume 8 for Clover 1:193 0:000 Checking EFI partition Volume 11 for Clover 1:194 0:000 Found Clover 1:194 0:000 EmuVariable UninstallEmulation: CloseEvent = Success, original var services restored 1:194 0:000 FindBootOptionForFile: C07E5518, \EFI\CLOVER\CLOVERX64.EFI 1:194 0:000 BootOrder: 4: Boot0002, Boot0000, Boot0003, Boot0001 1:194 0:000 Searching for: PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000)\EFI\CLOVER\CLOVERX64.EFI (Len: 130) 1:194 0:000 and for: HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000)\EFI\CLOVER\CLOVERX64.EFI (Len: 102) 1:194 0:000 FindBootOptionForFile: Not found. 1:196 0:001 EmuVariable InstallEmulation: orig vars copied, emu.var.services installed, CreateEvent VirtualAddressChange = Success, CreateEvent ExitBootServices = Success, set Status=Success 1:207 0:011 GetEfiBootDeviceFromNvram: efi-boot-device-data not found 1:207 0:000 EfiBootVolume not found 1:207 0:000 Searching for DefaultVolume 'MacHDD' ... 1:208 0:000 Default boot entry not found 1:208 0:000 EmuVariable UninstallEmulation: CloseEvent = Success, original var services restored 1:208 0:000 DefaultIndex=-1 and MainMenu.EntryCount=11 1:274 0:066 Found Mouse device: 1:274 0:000 GUI ready 1 Link to comment Share on other sites More sharing options...
Maniac10 Posted July 2, 2014 Share Posted July 2, 2014 If you want to get rid of the "Boot … from …" message just use "FullTitle" instead of "Title". Also, you might want to install the RC scripts to get the nvram variables, required for iCloud and other services. EDIT: looks like you're missing a key for custom entries: In the posted config you've got GUI->Entries->… and it should be GUI->Custom->Entries->… EDIT2: if you do install the RC scripts you'll need the IgnoreNVRAMBoot key to keep Windows 7 as your default boot entry, else the nvram will change it to the last booted OS. Link to comment Share on other sites More sharing options...
jasjeet Posted July 2, 2014 Author Share Posted July 2, 2014 Thanks for the tips, will work out the iCloud stuff after fixing the renaming. So i tried this but no luck I get this in the preboot.log 1:079 0:000 Custom entries start 1:079 0:000 Custom entry 0 "\EFI\BOOT\BOOTX64.efi" "" (99) 0x0 matching "1F461330-B56D-4DC0-91C0-752986BA9098" ... 1:079 0:000 Custom entries finish <key>GUI</key> <dict> <key>Hide</key> <array> <string>Windows</string> <string>BOOTX64.EFI</string> <string>3CF19D9F-A9CC-4B70-B63A-500C885A0E4B</string> <string>27979390-F9D4-45BC-A745-B6AC6BC453F7</string> <string>2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A</string> </array> <key>Language</key> <string>en:0</string> <key>Mouse</key> <dict> <key>Enabled</key> <true/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <false/> <key>Tool</key> <true/> </dict> <key>TextOnly</key> <false/> <key>Theme</key> <string>YosemiteLogin</string> <key>Custom</key> <dict> <key>Entries</key> <array> <dict> <key>Volume</key> <string>1F461330-B56D-4DC0-91C0-752986BA9098</string> <key>FullTitle</key> <string>Windows 7</string> </dict> </array> </dict> </dict> Link to comment Share on other sites More sharing options...
Maniac10 Posted July 2, 2014 Share Posted July 2, 2014 Can you upload your latest config.plist and a full boot log to see what's Clover doing with the custom entries? I need to see the whole picture. Link to comment Share on other sites More sharing options...
jasjeet Posted July 2, 2014 Author Share Posted July 2, 2014 Sure, I've attached them for you. I think this is the problem 1:096 0:000 Checking volume "EFI" (PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000)) ... match! 1:096 0:000 skipped because path `PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x3,0xFFFF,0x0)\HD(1,GPT,1F461330-B56D-4DC0-91C0-752986BA9098,0x28,0x64000)\EFI\BOOT\BOOTX64.efi` is self path! It sees the partition i want to rename, but skips it for some reason. config.plist.zip preboot.log.zip Link to comment Share on other sites More sharing options...
Maniac10 Posted July 2, 2014 Share Posted July 2, 2014 Try not to hide partitions with "bootx64.efi" and "windows", and that "self path" error is to avoid duplicated entries but I'm not sure why it thinks it's duplicated. And you should set the default boot volume not by its name, as there are several "EFI" partitions, but by its GUID which is unique. Link to comment Share on other sites More sharing options...
jasjeet Posted July 2, 2014 Author Share Posted July 2, 2014 I think its duplicated maybe because there is a left over Windows 8 boot loader left on one of my hard disks (Volume 8). Windows 7 is on Volume 11. 1:061 0:000 8. Volume 'EFI', GUID = 3CF19D9F-A9CC-4B70-B63A-500C885A0E4B - no nvram.plist - skipping! 1:061 0:000 11. Volume 'EFI', GUID = 1F461330-B56D-4DC0-91C0-752986BA9098 - no nvram.plist - skipping! 1:061 0:000 12. Volume 'OS X Base System', GUID = 2116E9A9-F6D8-41D1-BC28-88EB7B06AE6A - no nvram.plist - skipping! 1:064 0:002 14. Volume 'Mac OS X', GUID = CC59F2F5-78B2-459A-9EB7-961543AB58E7 - no nvram.plist - skipping! 1:067 0:003 15. Volume 'Recovery HD', GUID = 27979390-F9D4-45BC-A745-B6AC6BC453F7 - no nvram.plist - skipping! Tried removing the "bootx64.efi" and "windows" and used the GUID rather than "EFI" but still the same. Is the syntax correct for my custom entry? Link to comment Share on other sites More sharing options...
Maniac10 Posted July 2, 2014 Share Posted July 2, 2014 The syntax is correct, we just need to figure out why Clover thinks it's duplicated. Try adding Type=Windows to the custom windows entry and the following code to hide all EFI partitions: <dict> <key>Disabled</key> <true/> <key>Hidden</key> <true/> <key>Type</key> <string>Other</string> <key>Volume</key> <string>EFI</string> </dict> This is from my system: 3:412 0:000 Custom entry 3 "\EFI\Microsoft\Boot\bootmgfw.efi" "-s -h" (7) 0x0 matching "GUID_number" ... 3:412 0:000 Checking volume "EFI" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "Mavericks" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "Recovery HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "EFI" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "Yosemite" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "Recovery HD" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... skipped 3:412 0:000 Checking volume "EFI" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw ... match! 3:415 0:002 found PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw...\EFI\Microsoft\Boot\bootmgfw.efi 3:622 0:000 skipped path `PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw…\EFI\BOOT\BOOTX64.efi` because it is a volume and type match for custom entry 6! So Clover adds the custom entry for windows and detects the loader as well but skips it because it matches the type of the custom EFI entry I've created. Clover Configurator can help with all this custom things. Link to comment Share on other sites More sharing options...
jasjeet Posted July 2, 2014 Author Share Posted July 2, 2014 I started with th Clover Configurator, but that seemed to bork my EFI partition and i had to start all over with OSX and Win 7 installations. So for now ill stick to the manual editing, ill have a go with adding the Windows type and report back. I dont want to hide all EFI partitions as then both Windows 8 and Windows 7 loaders will get hidden, no? For that reason i just hide Windows 8 by GUID. I have WIndows 8 and 7 installed as UEFI as well as Yosemite as UEFI. This is using the Clover UEFI Bootloader only too. Link to comment Share on other sites More sharing options...
Maniac10 Posted July 2, 2014 Share Posted July 2, 2014 I have that custom entry and can boot Windows 7 from the EFI partition just fine with this: <dict> <key>FullTitle</key> <string>Boot Windows 7 64bits</string> <key>Type</key> <string>Windows</string> <key>Volume</key> <string>5148B030-E155-4B37-A23C-74EF4CAFDACA</string> </dict> <dict> <key>Disabled</key> <true/> <key>Hidden</key> <true/> <key>Type</key> <string>Other</string> <key>Volume</key> <string>EFI</string> </dict> And the log says: 3:412 0:000 Custom entry 3 "\EFI\Microsoft\Boot\bootmgfw.efi" "-s -h" (7) 0x0 matching "5148B030-E155-4B37-A23C-74EF4CAFDACA" ... 3:412 0:000 Checking volume "EFI" (PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(1,GPT,5148B030-E155-4B37-A23C-74EF4CAFDACA,0x28,0x64000)) ... match! 3:415 0:002 found PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(1,GPT,5148B030-E155-4B37-A23C-74EF4CAFDACA,0x28,0x64000)\EFI\Microsoft\Boot\bootmgfw.efi And when Clover looks for loaders: 3:649 0:000 skipped path `PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,82)\HD(1,GPT,5148B030-E155-4B37-A23C-74EF4CAFDACA,0x28,0x64000)\EFI\BOOT\BOOTX64.efi` because it is a volume and type match for custom entry 6! If you use Clover Configurator just to edit the plist then there's no risk at all. Still I don't know how it could bork your EFI partition as it doesn't do much. Link to comment Share on other sites More sharing options...
jasjeet Posted July 3, 2014 Author Share Posted July 3, 2014 Ok i put Type Windows, and now Windows 7 entry works! I will try change OS X partition now. Odd thing is, the timeout still displays Boot Microsoft EFI from EFI, its only when i move the cursor does it change to "Windows 7". Edit working perfect now! Thanks for the help. Now i will try to fix iCloud and NVRAM. Ive attached the final config.plist and preboot.log for others. If i install Clover to my current OS X Partition with the RC Scripts, will that not destroy the Windows 7 boot loader files? How should i go about doing this? Config.plist.and.Preboot.log.zip Link to comment Share on other sites More sharing options...
Maniac10 Posted July 3, 2014 Share Posted July 3, 2014 The RC scripts will only save the NVRAM content as /nvram.plist then when Clover boots it will search for this file and restore its content into the NVRAM. It won't touch the windows bootloader at all, but it will override Clover's default boot volume to the OSX partition (enables the Startup Disk prefpane), fixed by adding the IgnoreNVRAMBoot key. 3:618 0:000 Searching volumes for latest nvram.plist ... 3:621 0:002 4. Volume 'Mavericks', GUID = F6BDE7CF-0200-4231-803A-5AEC5D747368 Modified = 2014-7-3 4:12:12 - newer - will use this one 3:650 0:000 8. Volume 'Yosemite', GUID = 20BAE835-238D-46FF-BA4B-7A508DE2D0EE Modified = 2014-6-19 1:35:31 - older - skipping! 3:675 0:024 9. Volume 'Recovery HD', GUID = 22A18132-E4DF-4D05-BEB8-6B3258F0AB1B - no nvram.plist - skipping! 3:675 0:000 Loading nvram.plist from Vol 'Mavericks' - loaded, size=2653 3:678 0:003 PutNvramPlistToRtVars ... 3:678 0:000 Adding Key: Clover.BackupDirOnDestVol: Data: Size = 3: Success 3:678 0:000 Adding Key: Clover.KeepBackupLimit: Data: Size = 1: Success 3:678 0:000 Adding Key: Clover.LogEveryBoot: Data: Size = 2: Success 3:678 0:000 Adding Key: Clover.LogLineCount: Data: Size = 3: Success 3:678 0:000 Adding Key: Clover.MountEFI: Data: Size = 36: Success 3:678 0:000 Adding Key: Clover.Theme: Data: Size = 8: Success 3:678 0:000 Adding Key: EFIBluetoothDelay: Data: Size = 2: Success 3:678 0:000 Adding Key: LocationServicesEnabled: Data: Size = 1: Success 3:678 0:000 Adding Key: SystemAudioVolume: Data: Size = 1: Success 3:678 0:000 Adding Key: SystemAudioVolumeDB: Data: Size = 1: Success 3:678 0:000 Adding Key: backlight-level: Data: Size = 2: Success 3:678 0:000 Adding Key: bluetoothActiveControllerInfo: Data: Size = 16: Success 3:678 0:000 Adding Key: bluetoothHostControllerSwitchBehavior: Data: Size = 6: Success 3:678 0:000 Adding Key: efi-boot-device: Data: Size = 216: Success 3:678 0:000 Adding Key: efi-boot-device-data: Data: Size = 85: Success 3:678 0:000 Adding Key: fmm-computer-name: Data: Size = 9: Success 3:678 0:000 Adding Key: fmm-mobileme-token-FMM: Data: Size = 516: Success 3:678 0:000 Adding Key: install-product-url: Data: Size = 68: Success 3:678 0:000 Adding Key: platform-uuid: Data: Size = 16: Success 3:678 0:000 Adding Key: prev-lang:kbd: Data: Size = 4: Success 3:678 0:000 Adding Key: security-mode: String: Size = 4, Val = 'none': Success EDIT: by restoring the NVRAM at boot Clover might pick up different values for some functions (GUI->Theme and RtVariables), overriding the ones in the config.plist. If that happens, just use Clover's prefpane to set them to what you want or by terminal: sudo nvram variable_name=value For example: sudo nvram Clover.Theme=YosemiteLogin Link to comment Share on other sites More sharing options...
jasjeet Posted July 3, 2014 Author Share Posted July 3, 2014 What i meant was, when i install the RC Scripts with Clover Installation PKG, it will wipe my current EFI partition, which will also destroy the Microsoft Boot folder and cause Win 7 to fail to boot? Currently the Clover bootloader installed to the OSX Installation files partition on my SSD, not my actual OSX partition. Is it possible to install the RC Scripts without installing the bootloader again? Link to comment Share on other sites More sharing options...
Maniac10 Posted July 3, 2014 Share Posted July 3, 2014 It is possible to add the scripts manually but I don't know exactly how and I wouldn't recommend doing so either as it will complicate updating Clover. But how did you install Clover in the first place? Is this "OSX Installation" partition in the same disk as Windows? Upload a DarwinDumper report of your disks and boot loaders to see how it's all organized. The installer will only work on the EFI partition of the disk you point it to. For example if in the Clover installer you select this "OSX Installation" partition as destination then it will touch the EFI partition of that disk only, the rest will be left untouched. Anyway, if you don't trust the installer you could try unplugging the Windows disk to make sure it won't be tampered with. And why don't you install Clover to the EFI partition in your OSX disk? That, I believe would be the ideal place for it. Link to comment Share on other sites More sharing options...
jasjeet Posted July 3, 2014 Author Share Posted July 3, 2014 I have a single SSD with these partitions EFI - Clover bootlaoder OS X Yosemite Installer - This is just the OSX installer (10GB) OS X Yosemite - Actual Yosemite installation (40GB) Windows 7 (100GB) The Clover bootloader was installed from my other SSD which had Mavericks installed on it. And Clover was installed to the "OS X Yosemite Installer" partition. So when i installed Windows 7 i believe the bootloader files installed to the EFI partition tied to "OS X Yosemite Installer" partition. Now if i install Clover to "OS X Yosemite" partition wont that just break Windows 7? This is why id rather not install Clover to my "OS X Yosemite" partition, then ill have 2 Clover installations on 2 partitions on the same SSD? Or have i misunderstood and the EFI partition is tied to a disk and not a partition? The EFI on WDC WD2002FYPS-01U1B0 can be ignored, this is the old Win 8 drive. DarwinDumper_2.9.4_AMI_X64_2747_Yos_Jasjeet.zip Link to comment Share on other sites More sharing options...
Maniac10 Posted July 3, 2014 Share Posted July 3, 2014 There can be only one EFI partition per GPT disk. In your SSD you have Clover and the windows bootloader in the same EFI partition but each on their own folder (look at the list below), so I don't think you'll lose the Windows loader after running the installer because right now Clover is the one booting your disk and handles the windows loader just fine. /EFI/Boot/BootX64.efi(Clover r2747) /EFI/Boot/BootIA32.efi(Clover r2747) /EFI/Clover/CloverX64.efi(Clover r2747) /EFI/Microsoft/Boot/bootmgfw.efi (Windows loader) In theory, if you install Clover selecting Yosemite as target and checking the "Install for UEFI boot" option it should: 1- mount the EFI partition from the Yosemite disk (disk0s1) 2- copy the respective files in the CLOVER and BOOT folders 3- install the scripts and/or prefpane to the target partition 4- unmount the partition The rest should be left untouched, be it the Microsoft folder or any MBR-PBR code the disk may contain. Anyway, after all that explanation I've got bad news for you. Sadly this is all pointless for now because Clover's RC scripts won't work properly in Yosemite DP2. There's a workaround but I haven't tested it myself. Take a look here. Link to comment Share on other sites More sharing options...
jasjeet Posted July 3, 2014 Author Share Posted July 3, 2014 Ok thanks for the reassurance, just dont want to have to start over again by messing up the bootloader. I will check out the modded RC script files for Yosemite. Link to comment Share on other sites More sharing options...
jasjeet Posted August 23, 2014 Author Share Posted August 23, 2014 So clovers RC Scripts are working now, but it defaults to Mac OSX bootloader entry rather than my Win 7 GUID. I think thats because of the nvram.plist being present. Any way to get round this? Also still my iMessage doesnt work =/ Link to comment Share on other sites More sharing options...
Maniac10 Posted August 23, 2014 Share Posted August 23, 2014 Make sure you have IgnoreNVRAMBoot enabled, then no matter what the nvram.plist or NVRAM device says, Clover will boot the partition defined in DefaultVolume. If you have those in your config.plist and it still doesn’t work then upload a boot.log please. Link to comment Share on other sites More sharing options...
jasjeet Posted August 23, 2014 Author Share Posted August 23, 2014 Excellent i will try it, thanks. Edit: worked perfectly. Link to comment Share on other sites More sharing options...
bundpard Posted February 7, 2015 Share Posted February 7, 2015 How are you people getting the GUIDs of the partitions? Wasted 30mins looking and searching for how to hide the Recovery partition, and not one mention about how to find the damned GUID. Can't get very far without the first step, why is such an important step omitted from every single guide that pops up on Google. All I'm trying to do is get the GUID of the recovery partition..................... Clover makes life SO INFINITELY difficult, regardless of how well it functions Link to comment Share on other sites More sharing options...
Maniac10 Posted February 7, 2015 Share Posted February 7, 2015 (edited) The GUIDs are in Clover's logs, they're detailed in the volume detection section after this message: found xx volumes with blockIO Example with the GUID in bold: 3:118 0:000 0. Volume: 3:119 0:000 PcieRoot(0x0)\Pci(0x1F,0x2)\VenHw(CF31FAC5-C24E-11D2-85F3-00A0C93EC93B,80)\HD(2,GPT,F6BDE7CF-0200-4231-803A-5AEC5D747368,0x64028,0xDDFAC40) On DefaultVolume you can see the usual ways of pointing to partitions: Volume Name: The name of the volume. E.g. Macintosh. GUID: Globally Unique ID of the volume shown in Clover's boot, preboot or debug log. E.g. 57272A5A-7EFE-4404-9CDA-C33761D0DB3C. Part of Device Path: Also shown in Clover's logs. E.g. HD(1,GPT,57272A5A-7EFE-4404-9CDA-C33761D0DB3C,0x800,0xFF000). Edited February 7, 2015 by Maniac10 Link to comment Share on other sites More sharing options...
bundpard Posted February 7, 2015 Share Posted February 7, 2015 Where are the Clover logs? Looked in the EFI partition under every directory & subdirectory... Also looked in /var/log The difficulties of hiding a partition........really miss chameleon right about now Link to comment Share on other sites More sharing options...
Recommended Posts