Jump to content
ErmaC

Clover General discussion

19,678 posts in this topic

Recommended Posts

Advertisement

Hello slice.

 

A little suggestion on Clover Install Package.

 

Osxaptio drivers family may add describe information to clover package and I am willing to help translate the describe with these 5 drivers if you want.

 

Thanks.

 

 

从我的 iPhone 发送,使用 Tapatalk

Share this post


Link to post
Share on other sites

I don't think so, but if you have some bios parameters to tweak for this allocation error I will try happily

 

i can boot just fine after running nvram command, even though nvram native is not working

maybe bios setting ? 

Share this post


Link to post
Share on other sites

Guys, I am so confused about NVRAM. if the system supports native NVRAM, is it create a nvram.plist in the EFI folder? Normally I am testing visually like that? I am looking Find My Mac and iMessage for the native NVRAM 'cause if these too work then the system support native NVRAM.  Before BIOS update my motherboard NVRAM support as a native. After the update, v3 BIOS native NVRAM is broked and I am using EmuVariableUefi-64.efi and OsxAptioFix2Drv.efi and checking Find My Mac and iMessage everything works.

 

Now I used these efi and it looks native NVRAM working 'cause imessage and find my mac working. is there a different way to test NVRAM working or not?

 

post-803029-0-24214800-1516209976_thumb.png

post-803029-0-31938700-1516210152_thumb.png

 

I also used @Sherlocks command from the clover change explanations thread;

 

sudo nvram boot-args="-v"

 

And system boots without any problem. But now every start system boots with verbose mode. I checked config.plist no any boot-arg how can I disable this command for normal boot?

 

 

Share this post


Link to post
Share on other sites

Guys, I am so confused about NVRAM. if the system supports native NVRAM, is it create a nvram.plist in the EFI folder? Normally I am testing visually like that? I am looking Find My Mac and iMessage for the native NVRAM 'cause if these too work then the system support native NVRAM. Before BIOS update my motherboard NVRAM support as a native. After the update, v3 BIOS native NVRAM is broked and I am using EmuVariableUefi-64.efi and OsxAptioFix2Drv.efi and checking Find My Mac and iMessage everything works.

 

Now I used these efi and it looks native NVRAM working 'cause imessage and find my mac working. is there a different way to test NVRAM working or not?

 

attachicon.gifScreen Shot 2018-01-17 at 20.10.48.png

attachicon.gifScreen Shot 2018-01-17 at 20.28.23.png

 

I also used @Sherlocks command from the clover change explanations thread;

 

sudo nvram boot-args="-v"

 

And system boots without any problem. But now every start system boots with verbose mode. I checked config.plist no any boot-arg how can I disable this command for normal boot?

Try sudo nvram -c and reboot

 

나의 LG-F800S 의 Tapatalk에서 보냄

Share this post


Link to post
Share on other sites

You should not be using AptioMemoryFix and OsxAptioFixv3 together, use one or the other. Also delete the Nvram.plist from your EFI volume then open terminal and type sudo nvram -c and reboot

Share this post


Link to post
Share on other sites

You should not be using AptioMemoryFix and OsxAptioFixv3 together, use one or the other. Also delete the Nvram.plist from your EFI volume then open terminal and type sudo nvram -c and reboot

 

Ok. Verbose mode disabled. 

Deleted Nvram.plist from EFI

Deleted AptioMemoryFix leave it OsxAptioFixv3 and Reboot.

 

post-803029-0-93654700-1516223390_thumb.png

 

iMessage and Find My Mac working. 

 

sudo nvram -p result look like that;

fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j95%00%00%00%00%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-RBr -ch8*	j95j95a%00
fmm-mobileme-token-FMM	bplist00%dc%01%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%10%0d%11%0d%12%13%14%15%16%1d_%10%0funregisterState_%10%12enabledDataclassesYauthToken^disableContextVuserid]enableContextXusernameXpersonIDWaddTimeTguidXuserInfo_%10%13dataclassProperties%10%00%a1%0f_%10!com.apple.Dataclass.DeviceLocator_%10(AQAAAABaX7ie6TG-CkoeundPpjK4wKQIc-LeE8Q~%11%01%f5_%10%12muratozgul@mac.comY216605003#A%d6%97%ee(>%1f`_%10$15AC4698-1701-4441-8F76-9715B681CA62%d3%17%18%19%1a%1b%1c_%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName[Murat OzgulUMuratUOzgul%d1%0f%1e%d4%1f !"#$%25&VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p71-fmip.icloud.comUtokenUhttps%00%08%00!%003%00H%00R%00a%00h%00v%00%7f%00%88%00%90%00%95%00%9e%00%b4%00%b6%00%b8%00%dc%01%07%01%0a%01%1f%01)%012%01Y%01`%01x%01%8e%01%a3%01%af%01%b5%01%bb%01%be%01%c7%01%ce%01%d7%01%e5%01%ec%01%f7%02%0d%02%13%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00'%00%00%00%00%00%00%00%00%00%00%00%00%00%00%02%19
fakesmc-key-#KEY-ui32	%00%00%00%10
SystemAudioVolumeDB	%f0
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
LocationServicesEnabled	%01
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%023%0f%00%00%10
fakesmc-key-MSPS-ui16	%00%03
fmm-computer-name	Murat%e2%80%99s Mac
bootercfg	(%00
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%08%c0%f0%00
bluetoothActiveControllerInfo	%8d%82%ac%05%01%00%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	0
fakesmc-key-RMde-char	A
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
bluetoothInternalControllerInfo	%8d%82%ac%05%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-BEMB-flag	%00

is that mean my nvram now working as a native?

Share this post


Link to post
Share on other sites

Ok. Verbose mode disabled. 

Deleted Nvram.plist from EFI

Deleted AptioMemoryFix leave it OsxAptioFixv3 and Reboot.

 

attachicon.gifScreen Shot 2018-01-18 at 00.09.03.png

 

iMessage and Find My Mac working. 

 

sudo nvram -p result look like that;

fakesmc-key-MSWr-ui8	%00
fakesmc-key-RPlt-ch8*	j95%00%00%00%00%00
EFILoginHiDPI	%00%00%00%00
fakesmc-key-RBr -ch8*	j95j95a%00
fmm-mobileme-token-FMM	bplist00%dc%01%02%03%04%05%06%07%08%09%0a%0b%0c%0d%0e%10%0d%11%0d%12%13%14%15%16%1d_%10%0funregisterState_%10%12enabledDataclassesYauthToken^disableContextVuserid]enableContextXusernameXpersonIDWaddTimeTguidXuserInfo_%10%13dataclassProperties%10%00%a1%0f_%10!com.apple.Dataclass.DeviceLocator_%10(AQAAAABaX7ie6TG-CkoeundPpjK4wKQIc-LeE8Q~%11%01%f5_%10%12muratozgul@mac.comY216605003#A%d6%97%ee(>%1f`_%10$15AC4698-1701-4441-8F76-9715B681CA62%d3%17%18%19%1a%1b%1c_%10%15InUseOwnerDisplayName_%10%13InUseOwnerFirstName_%10%12InUseOwnerLastName[Murat OzgulUMuratUOzgul%d1%0f%1e%d4%1f !"#$%25&VapsEnvXhostname]authMechanismVschemeZProduction_%10%13p71-fmip.icloud.comUtokenUhttps%00%08%00!%003%00H%00R%00a%00h%00v%00%7f%00%88%00%90%00%95%00%9e%00%b4%00%b6%00%b8%00%dc%01%07%01%0a%01%1f%01)%012%01Y%01`%01x%01%8e%01%a3%01%af%01%b5%01%bb%01%be%01%c7%01%ce%01%d7%01%e5%01%ec%01%f7%02%0d%02%13%00%00%00%00%00%00%02%01%00%00%00%00%00%00%00'%00%00%00%00%00%00%00%00%00%00%00%00%00%00%02%19
fakesmc-key-#KEY-ui32	%00%00%00%10
SystemAudioVolumeDB	%f0
fakesmc-key-BATP-flag	%00
EFIBluetoothDelay	%b8%0b
fakesmc-key-MSTc-ui8	%00
LocationServicesEnabled	%01
fakesmc-key-BNum-ui8	%00
security-mode	none
csr-active-config	g%00%00%00
fakesmc-key-$Num-ui8	%01
fakesmc-key-MSFW-ui8	%01%00
fakesmc-key-REV -ch8*	%023%0f%00%00%10
fakesmc-key-MSPS-ui16	%00%03
fmm-computer-name	Murat%e2%80%99s Mac
bootercfg	(%00
fakesmc-key-$Adr-ui32	%00%00%03%00
fakesmc-key-EPCI-ui32	%08%c0%f0%00
bluetoothActiveControllerInfo	%8d%82%ac%05%01%00%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-MSAc-ui16	%00%00
SystemAudioVolume	0
fakesmc-key-RMde-char	A
flagstate	%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00
bluetoothInternalControllerInfo	%8d%82%ac%05%00%00s%14%b4%18%d1%e7^%8c
fakesmc-key-BEMB-flag	%00

is that mean my nvram now working as a native?

Seems to be working to me

Share this post


Link to post
Share on other sites

Seems to be working to me

 

Thank you. I also tried just AptioMemoryFix.efi this is worked too. You said dont use both same time but when I used both system boots super fast I dont know why?

 

AptioMemoryFix boot time 13s

OsxAptioFixv3 boot time 13s

Both 8s

 

BTW, how should I know which one is better for my system AptioMemoryFix.efi or OsxAptioFixv3.efi? What is the differences?

Share this post


Link to post
Share on other sites

BTW, how should I know which one is better for my system AptioMemoryFix.efi or OsxAptioFixv3.efi? What is the differences?

http://www.insanelymac.com/forum/topic/304530-clover-change-explanations/?p=2570653

Share this post


Link to post
Share on other sites

Regards, I can confirm that the ApatioFixDrv3 and AptioMemoryFix works with native NVRAM. I tested the NVRAM was working with (sudo nvram test = "value") then I restarted and verified with (sudo nvram -p) and it was working perfect. but

 

		<key>NvidiaWeb</key>
		<true/> 
doesnt works.

 

To have the Nvidia web driver working I need to use the

		<key>Arguments</key>
		<string>nvda_drv=1</string>

Share this post


Link to post
Share on other sites

All fine here with a Skylake build (6600k) and OsXAptioFix3Drv. Thank you very much for the update. :)

 

Update: everything ok with the Haswell build in the signature, as well.

Share this post


Link to post
Share on other sites

Try the OsxAptiofixDrv, I was in same boat as you, been using OsxAptioFix2Drv for years, but with 4385, black screen.

 

my laptop needs OsxAptioFix2Drv or OsxAptioFix2Drv-free2000. i'm using OsxAptioFix2Drv-free2000 + EmuVariableUefi-64.efi for years.

it's best result for my laptop. and there is no language issue after update.

 

original OsxAptioFix2Drv sometimes shown failed boot(stop logo). maybe early boot. so i changed other driver.

OsxAptioFix2Drv-free2000 never get failed boot.

Share this post


Link to post
Share on other sites

So let me see if I'm correct.

1. OsxAptioFix3Drv-64.efi is the now the recommended AptioFix as it incorporates and or gets rid of the need for EmuVariableUefi-64 and RC Scripts and is preferred over OsxAptioFix2Drv-64.efi and OsxAptioFixDrv-64.efi?

 

If a newbie was to come along with all three of these being available and all looking so similar which one would he/she choose based on hardware?

 

Which aptio is suited for which hardware or is it just bios manufacturer based?

 

Forgive me if this has been answered.

 

P.S. Clover r4386 working fine here.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

@Sherlocks, STLVNUB:

Problem fixed in r4387.  You can return to same setup and driver names you were using < r4384.

 

@SavageAUS:

The priority is

AptioMemoryFix

OsxAptioFix3Drv

OsxAptioFix2Drv

OsxAptioFixDrv

OsxLowMemFixDrv

 

Use the highest that works.

If you don't need nvram access from OS/X and don't want the extra overhead, delete the first two from the list.

Share this post


Link to post
Share on other sites

 

 

@Sherlocks, STLVNUB:

Problem fixed in r4387. You can return to same setup and driver names you were using < r4384.

 

@SavageAUS:

The priority is

AptioMemoryFix

OsxAptioFix3Drv

OsxAptioFix2Drv

OsxAptioFixDrv

OsxLowMemFixDrv

 

Use the highest that works.

If you don't need nvram access from OS/X and don't want the extra overhead, delete the first two from the list.

Thanks for clarification.

Where is AptioMemoryFix located? I didn't see it in installer.

 

Sent from my SM-G930F using Tapatalk

Share this post


Link to post
Share on other sites

Thanks for clarification.

Where is AptioMemoryFix located? I didn't see it in installer.

 

Sent from my SM-G930F using Tapatalk

I found it. Update Build_Clover.command to v4.6.4  :)

Share this post


Link to post
Share on other sites

OsxAptioFix2Drv-free2000 + EmuVariableUefi-64.efi works again on 4387.

thank you so much!

whrere link download r4387 ?

 

How to install new interface clover r4380 for bios UEFI GPT ?

 

 

Why is it so slow boot when install clover 4380?

 

thank

 

CaiCloverh5.png

 

CaiCloverh6.png

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

  • Recently Browsing   0 members

    No registered users viewing this page.

  • 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
×