Jump to content
ErmaC

Clover General discussion

19,137 posts in this topic

Recommended Posts

Advertisement
58 minutes ago, Sherlocks said:

@vit9696

thank you for r4846 commit.

this is very great fix. i had problem unknown panic on sandy bridge laptop until this commit.

there is no more instant reboot issue

thanks :)

@Sherlocks Wait, Sandy? Seems no problem here.. but, my Mojave is using HFS+ since 10.14 till 10.14.3 #btw

Or could bcoz something else (we have diff. specs but CPU #LoL )

 

Oh hai, you didn't response my proposition yet since last year?

Spoiler

--- /Users/badruzeus/udk/UDK2018/Clover/rEFIt_UEFI/entry_scan/loader.c	2018-12-21 20:51:48.000000000 +0700
+++ /Users/badruzeus/src/edk2/Clover/rEFIt_UEFI/entry_scan/loader.c	2019-01-17 22:37:40.000000000 +0700
@@ -102,6 +102,9 @@
   { L"\\EFI\\goofiboot\\goofibootx64.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grubx64.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grubx64.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grubx64.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grubx64.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grubx64.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #else
   { L"\\EFI\\grub\\grub.efi", L"Grub EFI boot menu", L"grub,linux" },
   { L"\\EFI\\Gentoo\\grub.efi", L"Gentoo EFI boot menu", L"gentoo,linux", "Gentoo" },
@@ -127,6 +130,9 @@
   { L"\\EFI\\goofiboot\\goofiboot.efi", L"Solus EFI boot menu", L"solus,linux", "Solus" },
   { L"\\EFI\\centos\\grub.efi", L"CentOS EFI boot menu", L"centos,linux", "CentOS" },
   { L"\\EFI\\pclinuxos\\grub.efi", L"PCLinuxOS EFI boot menu", L"pclinux,linux", "PCLinux" },
+  { L"\\EFI\\neon\\grub.efi", L"KDE Neon EFI boot menu", L"neon,linux", "KDE Neon" },
+  { L"\\EFI\\MX18\\grub.efi", L"MX Linux EFI boot menu", L"mx,linux", "MX Linux" },
+  { L"\\EFI\\parrot\\grub.efi", L"Parrot OS EFI boot menu", L"parrot,linux", "Parrot OS" },
 #endif
   { L"\\EFI\\SuSe\\elilo.efi", L"OpenSuse EFI boot menu", L"suse,linux" },
 };

 

 

Thank you before.. (y)

loader.c.patch.zip

Share this post


Link to post
Share on other sites
On 1/16/2019 at 4:58 AM, Badruzeus said:

Are these 2 NVRAM vars created by BootChimeCfg (red rectangles)?

Correct me if I'm wrong; can we run eg. this command via Terminal w/o Shell > fs0:\efi\clover\tools\bootchimecfg then?


sudo nvram specialbootdevice blah blah blah

Thanks.

 

No, those are the macOS variables. These are the variables:

Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Volume' DataSize = 0x01
  00000000: 3C                                               *<*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Index' DataSize = 0x08
  00000000: 00 00 00 00 00 00 00 00-                         *........*
Variable NV+RT+BS '89D4F995-67E3-4895-8F18-454B651D9215:Device' DataSize = 0x2E
  00000000: 02 01 0C 00 D0 41 03 0A-00 00 00 00 01 01 06 00  *.....A..........*
  00000010: 00 1B 03 0A 18 00 EB 3F-00 A9 06 D8 DB 41 A4 91  *.......?.....A..*
  00000020: 54 05 FE EF 46 C3 00 00-00 00 7F FF 04 00        *T...F.........*

 

Share this post


Link to post
Share on other sites

Error building 4848 with GCC 

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:36:15: error: type of 'EmbeddedSound' does not match original declaration [-Werror=lto-type-mismatch]
 extern UINT8 *EmbeddedSound;
               ^
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/sound.c:1:7: note: 'EmbeddedSound' was previously declared here
 UINT8 EmbeddedSound[] = {
       ^
lto1: all warnings being treated as errors
lto-wrapper: fatal error: /Users/stlvnub/src/opt/local/cross/bin/x86_64-clover-linux-gnu-gcc returned 1 exit status
compilation terminated.
/Users/stlvnub/src/opt/local/cross/lib/gcc/x86_64-clover-linux-gnu/8.1.0/../../../../x86_64-clover-linux-gnu/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/DEBUG/CLOVER.dll] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 16:58:25, Jan.18 2019
Build total time: 00:00:43


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

Share this post


Link to post
Share on other sites
On 1/16/2019 at 2:53 AM, pkdesign said:

I'm guessing us users with BIOS (non UEFI) motherboards are out of luck? I get sound when in Clover Shell but not during boot.

 

The boot chime works perfectly using AudioDXE.efi and BootChimeDXE.efi in the drivers64 folder. Those (and only those) two drivers are enough to get the chime going when the macOS boot entry is selected in Clover.

 

The only annoyance for me is that Clover takes 3 extra seconds to start. Hopefully that will be slightly optimized in the future.

 

PS. My laptop does have UEFI but its disabled. I'm using legacy boot.

 

Share this post


Link to post
Share on other sites

I'm having a hard time setting my DefaultVolume in my config.plist, could someone please help me take a look at this bootlog and tell me what to put in the DefaultVolume field? I have tried reversing the endianness as someone suggested on another post ("C4B2367B74CD456F9E87FE3696F379E0"), as well as "Macintosh HD" and "7B36B2C4CD746F459E87FE3696F379E0" but it doesn't seem to work. Specifically, I am trying to set volume 09 as the boot default. I am able to set another drive without issue, so I don't think it's my config that is wrong...

 

1:784  0:002  - [08]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,AB2E508E48943E47B77B4294154D845B)
1:784  0:000          hiding this volume
1:784  0:000  - [09]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7B36B2C4CD746F459E87FE3696F379E0)
1:784  0:000  - [10]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,085E15BDE052F446BB30B7D3714422FC)
1:784  0:000          hiding this volume
1:784  0:000  - [11]: Volume: PciRoot(0x0)\Pci(0x17,0x0)\Sata(0x0,0xFFFF,0x0)\HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60)\VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,749023097C268C4D88A57ED372FE4D36)

--- SNIP ---

2:076  0:043  - [08]: 'Preboot', hidden
2:076  0:000  - [09]: 'Macintosh HD'
2:223  0:147          AddLoaderEntry for Volume Name=Macintosh HD
2:257  0:033      Check if volume Is Hibernated:
2:257  0:000      Check sleep image 'by signature':
2:297  0:040      read prefs \Library\Preferences\SystemConfiguration\com.apple.PowerManagement.plist status=Success
2:297  0:000      using default sleep image name = \private\var\vm\sleepimage
2:329  0:031      sleepimage not found -> Not Found
2:329  0:000      hibernated: no - sign
2:333  0:004          [!] Icon 18 (icons\vol_internal_apfs.icns) not found (path: EFI\CLOVER\themes\Minimalism)
2:447  0:113  - [10]: 'Recovery', hidden
2:447  0:000  - [11]: 'VM'

 

Thanks!

Share this post


Link to post
Share on other sites
Just now, ellaosx said:

Juat set it to LastBootedVolume

 

Unfortunately, I can't since I am using EMUVariableUEFI since my mobo doesn't support native nvram :(

Share this post


Link to post
Share on other sites
16 hours ago, ellaosx said:

install rc script with emuvariable, then LastBootedVolume

 

Oh true, I forgot I could do that. I still wonder what's wrong though, I'm not sure exactly what value should have gone in there to set the macOS volume to be default...

 

Edit: Actually, the last used volume option doesn't seem to stick booting to macOS if change the value to boot into Windows. Ideally I should be able to chose the disk by name or UUID or other value. Any other ideas?

 

Edit 2: It looks like I found the culprit. The boot entry that Clover installed in the NVRAM boot options was pointing to the wrong bootloader. Once I removed that entry, using the full copy-pasted value of HD(2,GPT,A05A9816-69B8-4A81-A144-A918E58508E1,0x64028,0x746A2D60) worked for me.

Edited by WanderingAi

Share this post


Link to post
Share on other sites
On 1/8/2019 at 9:06 PM, al6042 said:

Just tried the last official clover release 4842 and got the following errors while trying to check and configure BootChimeCfg.efi on my H170N-Wifi and Prime Z390-A:

1084557407_Clover4842-BootChimeCfg-Error.thumb.jpg.2f40e28621bd940ff562811527013050.jpg

 

Did I miss something?

 

 

I think BootChimeCfg.efi needs to be executable. Which, depending on where did you get it from, it might not be.

 

Personally I couldn't get my system to play the sound.wav file I placed in the theme folder. Not sure why. Still checking a few things.

Edited by arsradu

Share this post


Link to post
Share on other sites

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

Share this post


Link to post
Share on other sites
1 hour ago, al6042 said:

Nope, 

BootChimeCfg.efi was working fine, that's why the last command in the screenshot worked.

The errors with the other options were gone, as soon as an AudioDxe.efi-file was placed in /EFI/CLOVER/driver64UEFI...

Either as manual copy or with clover 4844...

 

You're correct. After further investigation, it looks like I managed to reproduce the errors you were having. So yeah, it wasn't related to being executable or not. Actually, I think they're made executable anyway, when you drop them in the tools folder. Could be wrong thought. In my case, it was the "sound.wav" file missing from the theme's folder.

 

Still trying to get it to work... So far I managed to set it up... But still no sound on startup. I'm sure there's probably a mistake on my side somewhere.

 

EDIT: if you have more than one SSD/HDD with Clover on it, make sure you set the chime on the correct one.

 

EDIT 2: ok, so now I'm exactly where you are. Managed to set it up for boot (it was a total pain in the rear to find the correct boot EFI partition to load from Shell - for some reason, in my case it was FS11...) and tested it, working fine in Shell, but no sound on boot.

 

My guess is that maybe the sound output device is not selected correctly....? I don't know. What I do know, is that, Clover 4851 has an interface for testing and configuring the boot sound, but it always selects Device Output #1 for some reason...even after I selected Device #8, aaaand...pressing F7 to test that device will freeze the entire UI.

 

screenshot2.thumb.png.528c8b384dbd047e5e4b722f66d49c55.png

 

In my case, I set in the Shell the output device to be the one selected below (nr 8 in the list) but every time I enter here, it shows the first option. My guess is that the output device might haven't been saved. That's why it doesn't make any sound on boot.

 

Also, as I said, pressing F7 here will freeze the interface without making any sound.

 

screenshot3.thumb.png.c76faa99e3cb8460c679310c76e5f72a.png

 

Interestingly enough, it seems to have remembered the correct volume setting (60%). But not the output device.

Edited by arsradu

Share this post


Link to post
Share on other sites
10 hours ago, Slice said:

Correct to


extern UINT8 EmbeddedSound[];

Thats the first thing I tried throws up another error 

/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c: In function 'StartupSoundPlay':
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:81:14: error: assignment to 'UINT8 *' {aka 'unsigned char *'} from 'UINT8' {aka 'unsigned char'} makes pointer from integer without a cast [-Werror=int-conversion]
     FileData = EmbeddedSound;
              ^
[CC] ntfscomp
cc1: all warnings being treated as errors
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 05:28:45, Jan.19 2019
Build total time: 00:00:41


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

Share this post


Link to post
Share on other sites
14 hours ago, Dr. Hurt said:

 

The boot chime works perfectly using AudioDXE.efi and BootChimeDXE.efi in the drivers64 folder. Those (and only those) two drivers are enough to get the chime going when the macOS boot entry is selected in Clover.

 

The only annoyance for me is that Clover takes 3 extra seconds to start. Hopefully that will be slightly optimized in the future.

 

PS. My laptop does have UEFI but its disabled. I'm using legacy boot.

 

That is exactly where I had those two files. As I said, I got chime to work in Clover Shell, but it wouldn’t play on regular boot.

 

I am also confused, where do I acquire those files? There seems to be some confusion about where to obtain those files.

Edited by pkdesign

Share this post


Link to post
Share on other sites

@cecekpawon

 I tried that, too. 

 

On startup, it says: "No device outputs were found. Ensure AudioDxe is loaded."

 

Well...boot log says AudioDxe is loaded...

 

0:152  0:000  Loading AudioDxe-64.efi  status=Success
0:153  0:001   - driver needs connecting

Any idea?

Edited by arsradu

Share this post


Link to post
Share on other sites
15 minutes ago, arsradu said:

@cecekpawon

 I tried that, too. 

 

On startup, it says: "No device outputs were found. Ensure AudioDxe is loaded."

 

Well...it is present in drivers64UEFI...not sure if it's loaded though.

Any idea?

Try to clear the previous settings. To do this, choose option x, then s and v :) it also makes sense to check if the latest AudioDxe-64.efi or AudioDxe.efi is present in the drivers64UEFI folder.

Share this post


Link to post
Share on other sites
12 hours ago, STLVNUB said:

Thats the first thing I tried throws up another error 


/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c: In function 'StartupSoundPlay':
/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/Platform/StartupSound.c:81:14: error: assignment to 'UINT8 *' {aka 'unsigned char *'} from 'UINT8' {aka 'unsigned char'} makes pointer from integer without a cast [-Werror=int-conversion]
     FileData = EmbeddedSound;
              ^
[CC] ntfscomp
cc1: all warnings being treated as errors
make: *** [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit/OUTPUT/Platform/StartupSound.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/stlvnub/src/edk2/Build/Clover/RELEASE_GCC53/X64/Clover/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/stlvnub/src/edk2/Clover/rEFIt_UEFI/refit.inf [X64, GCC53, RELEASE]

- Failed -
Build end time: 05:28:45, Jan.19 2019
Build total time: 00:00:41


o_Ops, ./ebuild.sh exited with error(s), aborting..

 

Same with XCODE

Works with XCODE *EmbeddedSound

 

Edited by STLVNUB

Share this post


Link to post
Share on other sites

@arsradu from your log it sure enough that driver were successfully loaded. If you are already start BootChimeCfg from GUI, I have nothing to says more. Not sure AudioDxe (Clover vs Official) version is really matter here _/|\_

Share this post


Link to post
Share on other sites
1 hour ago, cecekpawon said:

@arsradu from your log it sure enough that driver were successfully loaded. If you are already start BootChimeCfg from GUI, I have nothing to says more. Not sure AudioDxe (Clover vs Official) version is really matter here _/|\_

 

Yeah, I am able to configure, test and set the wav sound I put in my selected theme (Minimalism). It respects the file name (sound.wav), the sample rate (44.1KHz) and the bits per sample (16bps). So... I would say the file is ok, the locations are ok (otherwise I think I wouldn't have been able to test and configure boot sound in the first place), still, upon startup, it says the output device is not found, and ensure AudioDxe is loaded... So...not sure what to say. :)) All seems to be working properly. Still, it doesn't. :))

 

And I'm using Clover 4851 (with the built-in AudioDxe) which in this exact commit it says: "update AudioDxe driver to sync with origin". So...I guess there shouldn't be a difference anymore, should it?

 

If you have another version of AudioDxe, I would love to give it a try.

 

Update: nevermind. IT WORKS! :)) It just works AFTER selecting the boot drive, not before, as it probably should, and as Clover's AudioDxe is probably trying to achieve.

 

I guess Clover's AudioDxe is not (yet) compatible with the prebuilt BootChimeCfg.efi? Ooor...there's something missing somewhere.

 

Bottom line, what did I do is: I got Goldfish's sources, compiled everything on my machine, used AudioDxe.efi, BootChimeDxe.efi in /drivers64UEFI and BootChimeCfg.efi and HdaCodecDump.efi in /tools and it works. :)

 

Also, one thing to note is that I had to shut down my computer, and then restart. Simple restart didn't do it for me. Don't know why. Also, there was no error anymore. So I guess they're not compatible yet. So the config file doesn't see the AudioDxe file from Clover. But if it's built with it...it does.

 

There are also other files, such as BootChimeDxe and HdaCodecDump which are missing from the Clover's instructions. They might not be needed. I just took everything as it was from the compiled sources. Just to have all the possible chances of this to work. And, what do you know? It does. :))

 

I'll test a few more things now and let you know if I find anything interesting.

Edited by arsradu

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects (for 02.05.2019): Custom memory configuration is unsupported, and provided as is. Full secure boot compatibility is in progress. Hibernation support is missing.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • By glasgood
      CLOVER DUAL BOOT MOJAVE & WINDOWS 10 GUIDE 
       

       
       
      INCLUDES  MBR / LEGACY BIOS  TO  GPT / EFI CONVERSION
      USING MBR2GPT TOOL
       
       
      PREREQUISITE: Two physical discs ( SSD’s or HDD’s )
       
       
       
       
       
      STEP 1 - Clover dual boot configuration 
       
      Open config.plist with Clover Configurator
       
      Boot
       Legacy = PBR Timeout = True ( will remove the Timeout countdown, from Clover boot menu)  

       
      GUI 
      Scan / Custom
       Entries = True  Tool = True  Legacy = False ( removes extra Windows 10 entries )  
      Hide Volume
      - Preboot ( macOS Preboot )
      - Recovery ( macOS Recovery )
       

       
      So at boot you will have two options: boot macOS Mojave or Windows 10 
       
       
       
       
       
       
       
      ————————————————————
       
       
      STEP 2 - Using a drive without Windows 10 installed
       
      Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )
       
      Proceed with a Windows 10 UEFI install.  
      After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover. 
      If Windows 10 is not detected or able to boot,  then verify you installed Windows 10 as UEFI and not MBR ---->  ( Read step 2 - For a drive with Windows 10 installed )
       
       
      OR
       
       
       
      STEP 2 - Using a drive with Windows 10 already installed
       
      Verify your Windows install is  GPT / UEFI or MBR / Legacy BIOS.   
      If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen. 
       

       
       
      But if  Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
      then this is most likely because Windows drive is MBR ( Legacy BIOS ).  You can easily convert MBR to GPT using  Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again  ) 
       
      If Windows 10 install is MBR / Legacy BIOS  then simply convert to GPT / UEFI  following instructions below ( read video summary and view video )
       
       
      ** To use Windows 10  MBR2GPT tool  you must have Windows 10 version 1703 ( creators update  ) or later and less than 3 partitions on 
      the Windows 10 drive **
       
      Video summary:
       
      Confirm Windows 10 drive is MBR Legacy BIOS ( in Windows Disk Management ) Reboot into Windows PE ( Advanced Startup ) Convert from MBR Legacy BIOS to GPT UEFI ( using commands below ) mbr2gpt /validate mbr2gpt /convert Restart Verify Windows 10 drive has changed to GPT UEFI ( in Windows Disk Management )  
       
       
       
      After conversion Windows 10 is ready to use at the Clover boot menu 
       
       
       
      STEP 3 - Stop Windows Boot manager from overriding Clover boot manager
       
      How to stop Windows boot manager from overriding your Hackintosh Clover boot manager when using dual booting between macOS and Windows
       
       
       
       
       
       
    • By AppleBytes
      OK, I've searching for days trying to gather up the tools to make my current install work correctly. I'm well on my way. But all the links to the things I currently must have were apparently nuked "during a forum upgrade". :(
      As far as EFI Studio goes; I can find many links to it. But for Insanelymac, they're broken (due to the upgrade), or for the Netkas site, they're links to either Rapidshare, or Mediafire that also no linger exist. I see many users here indicating that they used it to tweak their DSDT. But the web (google/duckduckgo), Instanelymac, and Netkas seem to have no idea where it's gone.
      Could some kind soul please share a copy, or a link? I'm a loooong time hacker, and would love to bring it back to life. In fact, I'd love to improve it -- or at least bring it up to current times. If only I knew where it was.
      Thank you for all your time, and consideration.
       
      --Chris
       
×