Jump to content
ErmaC

Clover General discussion

19,647 posts in this topic

Recommended Posts

I have never needed it before so im unsure if its clover or the new dev beta build.

Even with the driver its slow, i have to have settings like this for decent movement.

attachicon.gifScreen Shot 2018-01-11 at 9.53.27 pm.png

Yea I see its new adition in UEFI Drivers → USBMousse

Share this post


Link to post
Share on other sites
Advertisement

I use only these on drivers64 folder for my legacy mach (sig):

MacBookPro:~ badruzeus$ cd /Volumes/EFI/EFI/CLOVER/drivers64
MacBookPro:drivers64 badruzeus$ ls
AppleImageCodec-64.efi		FSInject-64.efi
AppleKeyAggregator-64.efi	FirmwareVolume-64.efi
AppleUITheme-64.efi		SMCHelper-64.efi
MacBookPro:drivers64 badruzeus$ 

Share this post


Link to post
Share on other sites

 

 

How are you doing with the graphical glitches of the HD3000? do you have any??

I though i was the only one using an ancient cpu nowadays (as a daily driver) :)

 

DVMT does not help, also, at least on my pc, other OSes cannot boot with higher DVMT, so either MacOS is happy with any DVMT value or it just ignores the extra memory.

 

I have a lot of ram so my iHD has the max allowed shared memory available, that is 512M according to MacOS and 1.5G according to Windows (wrong?)

I m using a VRAM patch to increase the value to 1.5G.

This helped a bit.

 

I don t have persistent glitches, they seem ramdon, but actually they start only on some occasions

 

- when i reboot from linux/windows after a long session (4-5hrs +)

- when i use the iHD a lot, for ex. Maya 3d or some 2k+ youtube videos

 

So, this could be wrong but, i think that clover "poisons", or it does not clear, something related to the gpu.

 

That would explain why when i reboot from linux to MacOS i can sometimes see glithes, and i m forced to shutdown and boot MacOS directly.

 

From what i can remember i had no glitches in Mavericks and Yosemite(not sure).

 

I should probably try Mavericks + latest/older clover and see what happens when i have time.

Share this post


Link to post
Share on other sites

I though i was the only one using an ancient cpu nowadays (as a daily driver) :)

 

DVMT does not help, also, at least on my pc, other OSes cannot boot with higher DVMT, so either MacOS is happy with any DVMT value or it just ignores the extra memory.

 

I have a lot of ram so my iHD has the max allowed shared memory available, that is 512M according to MacOS and 1.5G according to Windows (wrong?)

I m using a VRAM patch to increase the value to 1.5G.

This helped a bit.

 

I don t have persistent glitches, they seem ramdon, but actually they start only on some occasions

 

- when i reboot from linux/windows after a long session (4-5hrs +)

- when i use the iHD a lot, for ex. Maya 3d or some 2k+ youtube videos

 

So, this could be wrong but, i think that clover "poisons", or it does not clear, something related to the gpu.

 

That would explain why when i reboot from linux to MacOS i can sometimes see glithes, and i m forced to shutdown and boot MacOS directly.

 

From what i can remember i had no glitches in Mavericks and Yosemite(not sure).

 

I should probably try Mavericks + latest/older clover and see what happens when i have time.

 

Thanks for your input.

 

Can you teach me how to make the VRAM patch? I have 8GB of RAM. I'd like to give it at least 1GB.

 

Is that a clover parch or I need to edit a kext?

 

Thanks in advance!

Share this post


Link to post
Share on other sites

kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

 

Are you the Lilu guy??? Thanks!

 

How do I zero that address??

 

Cheers!

Share this post


Link to post
Share on other sites

kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

Actually I using HD3000 too.

 

10.6 and 10.7 have no glitches issues on HD3000.

 

After 10.8 it have this problem and can be simply fixed by set slide=0 and work well without any glitches.

 

But after 10.11.4 this method have no function and it have more and more glitches and more and more frequently and can’t be reduced.

 

10.6 OK

10.7 OK

10.8 OK with slide=0

10.9 OK with slide=0

10.10 OK with slide=0

10.11.3 OK with slide=0

10.11.4 glitches no matter with slide value

10.12 glitches no matter with slide value

10.13 glitches no matter with slide value

 

Ps

I using legacy clover to boot on my hd3000.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I say we try something different, protect reserved regions differently. Because macOS does not make a difference between runtime and non-runtime reserved, it only maps the runtime reserved as the same as runtime data. But I would have to think that there is a reason those reserved regions exist and according to the spec you are not supposed to use the memory regardless of the runtime flag. So maybe we should try protected runtime reserved as runtime code and non runtime reserved as runtime data?


kylon, if the issue is not clearing, you may try zeroing 0x10200000 bytes starting with 0x10000000 address. This is the area boot.efi tries to avoid for Sandy and Ivy bridge CPUs, and it may be related.

 

vit, that's only half the range when slide >= 128 for non SB and IB. What about 0x200000 to 0xFE00000? Also, this is a bad idea what if that's where the runtime was just protected? Don't want to wipe that.

 

EDIT: Oops left part of sentence out, lol.

Share this post


Link to post
Share on other sites

I have breaking news for you: Just downgraded to 10.12.6 + HFS, and guys, it is so muuch more fast than 10.13.2 + apfs. Boot is again super fast, no gui slowdowns, everything is smooth. I installed now safari tech preview to be a bit more safe against spectre. All software is working again like it should.

Share this post


Link to post
Share on other sites

Question:

 

I saw at around 750 page that you where talking about patches for Pentium and integrate them directly into Clover version 41xx. Does that happend ? I am asking because I have 2 patches in my config.plist made by vit9696 and Sherlocks and I wanna know if I can remove them or not:

 

Find: b9a00100 000f32

Replace: b9a00100 0031c0

 

Find: 89d804c4 3c22

Replace: 89d804c6 3c22

 

I have the Pentium G3220.

Share this post


Link to post
Share on other sites

Question:

 

I saw at around 750 page that you where talking about patches for Pentium and integrate them directly into Clover version 41xx. Does that happend ? I am asking because I have 2 patches in my config.plist made by vit9696 and Sherlocks and I wanna know if I can remove them or not:

 

Find: b9a00100 000f32

Replace: b9a00100 0031c0

 

Find: 89d804c4 3c22

Replace: 89d804c6 3c22

 

I have the Pentium G3220.

 

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

 

Share this post


Link to post
Share on other sites

These patches in clover:

#1

#2

Use KernelXCPM key in KernelAndKextPatches.

 

 

Thank you ! I deleted the kernel patches and it's working ! 

 

Anyway can somebody take a look on my DSDT and other stuff ? I am asking because the sound via HDMI works only after sleep. Like after sleep the sound works but before it doesn't...

 

https://drive.google.com/open?id=18YGCj5Z3j8cehMOChGtckap0uWmQ6tjA

Share this post


Link to post
Share on other sites

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Share this post


Link to post
Share on other sites

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

Or it can be renamed as LowMemFixup.efi because this problem is a common problem not only in ami aptio bios.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

What about naming it then like:

OsxAptioFixDrv-1011up-64.efi
OsxAptioFixDrv-1010down-64.efi

Or similar...? I don't find the numbering 1,2,3 very useful for non-hackers.

No, these names are historical. 

Fix1 is more advanced.

Fix2 is simplified but supported hibernation.

 

 

@apianti

 

Tested new OsxAptioFix2Drv-64.efi on my NUC6 Skull Canyon (NUC6i7KYK) with 10.13.2.

Tested by merging in changes to my own Clover fork.

It booted no problem and was able to eliminate EmuVariableUefi-64.efi and still have working NVRAM.

 

Will test on other computers in the coming days.

 

But since the new OsxAptioFix2Drv-64.efi is not working for everyone, perhaps it should be renamed OsxAptioFix3Drv-64.efi (or some other name) and original behavior of OsxAptioFix2Drv-64.efi retained.

Not to mention undoing the changes in OsxAptioFixDrv-64.efi that prevent it from being used at all (as you implied in a previous post).

 

I agree there must be Fix3 retaining old Fix1 and Fix2.

And see new one      AptioMemoryFix    

Share this post


Link to post
Share on other sites

Hey slice,

can I add new entries to a plist, using the kext patcher in clover? I read somewhere it only can replace 1:1 lengths?

More specific: How do I replace a

      <key>UnifiedSleepSliderPref</key>
      <true/>

to

      <key>UnifiedSleepSliderPref</key>
      <false/>

Also, does it work with plugins of kexts?

 

Path is:

/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/Mac-27ADBB7B4CEE8E61.plist

(For iMac14,2)

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 Slice
      OK, 4988 released.
      Now, @vector sigma, what have we do to update translations?
    • By fusion71au
      Clover r4989 ISO compiled with GCC and minimal config.plist compatible for use in VMWare Workstation.
       
      Tested with unlocked Workstation 15 running OSX 10.9 -->10.15 guest in Windows X64 host.
       
      Installation
      1. Download and unzip "EFI_Clover_r4989 for VMware.zip". Mount Clover-v2.4k-4989-X64.iso by double clicking on it.
      2. Mount your VM's EFI System Partition eg in terminal
      sudo diskutil mount disk0s1   3. Copy EFI folder from step 1 into the EFI partition
      4. Shutdown the VM, add bios.bootDelay = "3000" to your VM's vmx file
      5. Reboot your VM, press <F2> to access the VMware Boot Manager and add CLOVERX64.efi to the boot menu.
       
      Substitute your own unique and valid MLB and ROM variables in the /EFI/CLOVER/config.plist (Rt Variables section) to activate iMessage/Facetime on your VM.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VirtualBox 5.x.x on a Windows Host
      Following on from my previous guide on how to create a VMware virtual machine running Vanilla OS X El Capitan in Windows, I’ve decided to write a similar guide for creating a VirtualBox El Capitan VM. 
       
      The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are other tutorials and videos on the net about running OS X on Windows machines using pre-made VMDK disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from several threads in the Multibooting and Virtualisation section of this forum and also the wider internet eg
       
      @colt2 HOW TO: Create a bootable El Capitan ISO for VMware
      @dsmccombs comment on faking Ivybridge Processor
      @E:V:A http://forum.xda-developers.com/showpost.php?p=55572430&postcount=6
      @Tech Reviews video tutorial https://www.youtube.com/watch?v=t7X07U63lwg.
      VirtualBox Forum: Status of OSX on OSX
       
      Requirements
         Intel PC with four or more CPU cores running Windows 7 X64 or later OS (2 or more cores needed for OS X)    4GB or more RAM (2GB or more will be needed for OS X)    Hard Disk with at least 40GB free for Virtual Machine    Oracle VM VirtualBox v 5.0.34    Install OS X El Capitan app and Mac or Hack to prepare installation iso <-- Now, no longer necessary to have previous access to a Mac or Hack by building the Installer.app from scratch - see post#75    16GB or larger exFAT formatted USB stick to transfer El Capitan iso from Mac/Hack to Host PC  
      Prepare Installation ISO on your Mac or Hack
      1.  On your Mac or Hack, download "Install OS X El Capitan.app" from the App Store into your Applications folder.
      2.  Download and unzip the CECI.tool (attached to this post) into your ~/Downloads folder. The commands in this executable script are shown below for informational purposes.  Note: you will need approx 16GB of free space on your hard disk for the script to complete.
       
       
       
      3.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 4.  At the end of the process, you will have an El Capitan iso on your desktop - copy this onto an exFAT formatted USB for use on the PC Host later.
       
       
      Create an El Capitan Virtual Machine in VirtualBox
      1.  Open the VirtualBox program and click the "New" button to create a new VM.
       

       
      2.  Select Mac OS X and Mac OS X 10.11 El Capitan (64 -bit) for Operating System type and version.  I named my Virtual Machine "El_Capitan", then clicked next...
       

       
      3.  Leave the Memory size at the recommended 2048 MB, then click next.
       

       
      4.  Choose to "Create a virtual hard disk now", then click the create button.
       

       
      5.  For the hard disk file type, the default is VDI (VirtualBox Disk Image) but I have selected VMDK for inter-operability with VMWare.  Click next...
       

       
      6.  For Storage on physical hard disk, I have chosen the default Dynamically allocated (grows larger to a set limit as you need more disk space).
       

       
      7.  On the File location and size screen, you can set the location of the new virtual hard disk and its size - I recommend changing disk size to 40GB or larger.  When you click the create button, you will now see your new VM in the VirtualBox main GUI.
       

       
      8.  Click the settings button on the Main Menu to tweak a few settings....
         a.  On the System/Motherboard tab in Boot Order, you can uncheck the Floppy Drive (who has these now?)
       

       
         b.  On the System/Processor tab, you can increase the allocated CPU cores to 2
       

       
         c.  On the Display tab, you can increase the allocated Video Memory to 128MB
       

       
         d.  On the Storage tab, click on the icon of the Optical Drive and select "Choose Virtual Optical Disk File". 
       

       
      Navigate and select the El Capitan ISO we created earlier...
       

       
         e.  Click the OK button to finalise the VM settings.
       
       
      Patch El Capitan vbox configuration file with DMI Settings from a Mac
      1.  From the start menu, type cmd and click run as administrator to open an administrative command prompt. 
       

       
      2.  Choose a Mac Model similar to your host system, then type the following lines, followed by <enter>  after each line.  Make sure you first close all VirtualBox Windows and the VirtualBox program, otherwise any changes you make won't stick...
       
      Eg iMac11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F2238BAE" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 MacBookPro11,3
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "MacBookPro11,3" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-2BD1B31983FE1663" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 Macmini6,2
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "Macmini6,2" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Mac-F65AE981FFA204ED" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1 3.  Optional- For some host systems eg those with Haswell and newer CPUs, you might have to spoof an older CPU to avoid VirtualBox errors.  You can try from one of the following if this happens:

      To spoof Lynnfield i5 750 CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000106e5 06100800 0098e3fd bfebfbff To spoof IvyBridge CPU
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 04100800 7fbae3ff bfebfbff or
      VBoxManage.exe modifyvm "El_Capitan" --cpuidset 00000001 000306a9 00020800 80000201 178bfbff 4.  Close the command prompt window.
       
       
      Installation of El Capitan
      We are now ready to start the El_Capitan Virtual Machine....
       



       
      Installation should be relatively straight forward, just following the prompts of the OS X installer:
      1.  Select language, agree to legal terms
       

       
      2.  Use Disk Utility from the Utilities Menu to erase and format the virtual hard drive as a single partition GUID Mac OS X Extended.  I named my drive "Macintosh HD" but you can enter whatever you like eg El_Capitan.
       

       
      3.  Quit DU and choose Macintosh HD to install El Capitan on.
      4.  After 20-30 min (depending on how fast your system is), the installation will complete.  At this point, unmount the El Capitan ISO by clicking the Devices menu from the VM window, click Optical Drives, then choose Remove disk from virtual drive.  The VM is now ready to reboot into OS X from the virtual hard drive.
      5.  At the welcome screen, choose your country and keyboard layout.  You can skip transfer information, location services and logging in with your Apple ID if you wish…
      6.  Create a User Account and select your Time Zone.  You can skip sending diagnostics and usage data to Apple….
      7.  Finally, you will arrive at the El Capitan Desktop.
       

       
      8.  Network/internet and audio should work OOB but on my system, the sounds were distorted.  Unfortunately, there is no QE/CI and the VM resolution will be fixed without the ability to dynamically resize the VM window (no VirtualBox additions for OS X guests atm). 
       
       
      Customization with VBoxManage
      1.  You can change the default resolution of 1024*768 (after shutting down the VM) with the VBoxManage command from the Windows Administrative Command Prompt:
      cd "C:\Program Files\Oracle\VirtualBox\" VBoxManage setextradata "El_Capitan" VBoxInternal2/EfiGopMode N (Where N can be one of 0,1,2,3,4,5) referring to the 640x480, 800x600, 1024x768, 1280x1024, 1440x900, 1920x1200 screen resolution respectively.
       
      Update:  For VirtualBox 5.2.x, the command for changing screen resolution has changed...
       
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution XxY (where X=Horizontal screen resolution, Y=Vertical screen resolution)
      eg
      VBoxManage setextradata "<MyVM>" VBoxInternal2/EfiGraphicsResolution 1280x1024 2.  Adding serials and other SMBIOS details for the System Information Screen
      VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemSerial" "W8#######B6" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBoardSerial" "W8#########1A" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemVendor" "Apple Inc." VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiSystemFamily" "iMac" VBoxManage setextradata "El_Capitan" "VBoxInternal/Devices/efi/0/Config/DmiBIOSVersion" "IM112.0057.03B" A listing of known issues with Mac OS X guests can be found in the VirtualBox Manual - link https://www.virtualbox.org/manual/ch14.html.
       
      Vanilla Mavericks and Yosemite, Snow Leopard from Retail DVD
      The same VM settings for El Capitan will also boot and run vanilla installations of OS X Mavericks and Yosemite .  Attached to this post are installer scripts to create bootable Mavericks (CMI.tool) and Yosemite (CYI.tool) ISOs for VirtualBox and VMware.
       
      With the respective OS X installer apps in the Applications folder, download and run the installer tools using terminal ie
       
      To create a Mavericks ISO on your desktop
      cd downloads chmod +x CMI.tool ./CMI.tool To create a Yosemite ISO on your desktop
      cd downloads chmod +x CYI.tool ./CYI.tool Here is a screenshot of the VM running Mavericks 10.9.5...
       

       
      Finally, those without a Mac/Hack to prepare the install media can purchase a retail Snow Leopard DVD directly from Apple and install OSX 10.6.3 on their virtual machines (Snow Leopard, Lion and Mountain Lion run quite happily in VirtualBox with 1 CPU, 1-2 GB of RAM and the rest of the settings unchanged from above).  Once you update by combo update to SL 10.6.8, you can directly download El Capitan from the App Store for free .
       

       
      UPDATE macOS Sierra 10.12 to 10.12.6: For macOS Sierra, use CSI.tool in post#51.
      UPDATE macOS High Sierra 17A365:  For macOS High Sierra, use CHSI.tool in post#73.
      UPDATE macOS Mojave 18A391:  For macOS Mojave or High Sierra, use macOS_iso_creator.tool on page 4 of thread.
      UPDATE macOS Catalina Beta DP3_19A501i:  For Catalina, @jpz4085 has made an automated batch file to create a Catalina VM in Windows with iMac 14,2 SMBIOS.  You can still use my macOS_iso_creator.tool on page 5 to make an installer ISO to attach to the VM.
       
       
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By JackBauer24
      Hello,
       
      I have installed OSx86 10.11 (El Capitan) on April 2016 on my Asus Z170 Deluxe system.
       
      For installation I used this Thread.
       
      I used it a lot and it worked well. Meanwhile I switched to Linux and I use Win10 time to time. So OSX was forgotten. Also it did not boot correctly anymore.
       
      Now I wanted to start with a fresh installation and use OSX more often again. I want to use OSX 10.13 High Sierra. Is it working on my Asus Z170 Deluxe? I have the same Hardware as of April 2016 only the graphics card was updated to a Nvidia GTX1080.
       
      My Hardware in detail: Asus Z-170-Deluxe (Bios 3801), i7-6700k, EVGA GeForce GTX 1080 SC GAMING ACX 3.0, Samsung 950 Pro/M2 NVME 512MB, HDD 4 TB)
      Can I use some of support files from the old thread for the installation (see attachment)? Can I still use  Clover 2.3k r3292 Special Edition v2 ? Or do I need a newer version?
       
      Has someone installed High Sierra successfully on the Asus Z170 Deluxe ?
       
      About some hints where to start I would be thankful.
       
      regards
      JackBauer24
       
      Z170DeluxeFiles.zip
×