Jump to content

1,569 posts in this topic

Recommended Posts

Se usi ApfsDriverLoader.efi devi usare minimo AptioMemory R21 o successivi 

e non devi mettere il driver apfs.efi in efi

il disco non formattarlo tu in apfs ma lascialo in guid+mac esteso journaled verrà poi convertito automaticamente

se ancora non va prova a riscaricare l'installer e ricrearlo

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)

Stesso identico problema di @clockT, mi sa che al 70% sia l'hard disk.. infatti oggi ho acquistato un ssd per provare li l'installer. Se risolvete fatemi sapere

Edited by DangerNemesis

Share this post


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

Stesso identico problema di @clockT, mi sa che al 70% sia l'hard disk.. infatti oggi ho acquistato un ssd per provare li l'installer. Se risolvete fatemi sapere

 

per ora sono arrivato alla schermata..."impossibile installare...disco troppo piccolo..." con un HHD da 500GB! se risolvi con l ssd fammi sapere

Share this post


Link to post
Share on other sites
6 minutes ago, clockT said:

 

per ora sono arrivato alla schermata..."impossibile installare...disco troppo piccolo..." con un HHD da 500GB! se risolvi con l ssd fammi sapere

Formattalo a modo, seleziona il disco e non la partizione e formatta in hfs

Share this post


Link to post
Share on other sites
26 minutes ago, DangerNemesis said:

Appena mi arriva ci provo!, ma visto che ho un hdd da 1 TB come hai fatto a saltare quel problema che avevi?

 

in poche parole, ci sono due fasi di installazioni, la prima copia tutti i file necessari sul HDD, poi il pc si riavvia da solo e tramite il boot clover selezioni HDD d'istallazione, e qui parte l'installazione vera, ma dopo mi dice che l'hdd ha poco spazio.

 

 

22 minutes ago, gengik84 said:

Formattalo a modo, seleziona il disco e non la partizione e formatta in hfs

 

ho riscaricato la beta. formattato con Gparted il disco, poi riformattato con HighSierra in hfs , selezionato il disco visto che lo uso esclusivamente per prova, ma sempre lo stesso problema

Share this post


Link to post
Share on other sites
2 minutes ago, clockT said:

in poche parole, ci sono due fasi di installazioni, la prima copia tutti i file necessari sul HDD, poi il pc si riavvia da solo e tramite il boot clover selezioni HDD d'istallazione, e qui parte l'installazione vera, ma dopo mi dice che l'hdd ha poco spazio.

Io ho fatto questo procedimento 4 volte, ma se alla 1 installazione quella di 5 minuti ti da quei errori anche se vai avanti (a me lo faceva installare), finita l'installazione vera non mi mostrava nel clover la voce boot with macos(NOME HDD)

Share this post


Link to post
Share on other sites
1 minute ago, DangerNemesis said:

Io ho fatto questo procedimento 4 volte, ma se alla 1 installazione quella di 5 minuti ti da quei errori anche se vai avanti (a me lo faceva installare), finita l'installazione vera non mi mostrava nel clover la voce boot with macos(NOME HDD)

 quindi tu riesci a completare l'installazione?

Share this post


Link to post
Share on other sites

shhh..sembra che l'installazione stia andando a buon fine. l'unico cambiamento che ho fatto è formattato il disco con un titolo in maiuscolo e non minuscolo, oltre ai consigli di gengik84

Share this post


Link to post
Share on other sites
7 minutes ago, clockT said:

 quindi tu riesci a completare l'installazione?

La 2 si, ma non ha senso perche' non va a buon fine la 1, quindi e come se fai un installazione a vuoto

Share this post


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

La 2 si, ma non ha senso perche' non va a buon fine la 1, quindi e come se fai un installazione a vuoto

ah...stasera ti faccio sapere, ora devo uscire, l'installazione sta contnuando.

Share this post


Link to post
Share on other sites
2 minutes ago, DangerNemesis said:

La 2 si, ma non ha senso perche' non va a buon fine la 1, quindi e come se fai un installazione a vuoto

la seconda fase va solo dopo la prima...

 

14 minutes ago, DangerNemesis said:

Io ho fatto questo procedimento 4 volte, ma se alla 1 installazione quella di 5 minuti ti da quei errori anche se vai avanti (a me lo faceva installare), finita l'installazione vera non mi mostrava nel clover la voce boot with macos(NOME HDD)

Questo può dipendere dalla mancanza di driver esempio apfs.efi in caso di uso di questo filesyestem

in caso di HFS+ in  caso mancanza o bug di Vbox... da provare in caso con la sostituzione con HFSplus

 

Ovviamente usare Clover aggiornato

Share this post


Link to post
Share on other sites
Posted (edited)

Allora ho formattato l'hard disk come hai fatto tu, ma mi da sempre quei errori..nella partizione EFI che mi hai inviato tu, mi sono accorto che manca aps.efi. adesso non so se serve ma in caso contrario me lo potresti inviare e dirmi dove va inserito? @gengik84

 

Edited by DangerNemesis

Share this post


Link to post
Share on other sites

allora..installazione riuscita ma al boot ho questa schermata

 

1029945312_Schermata2018-06-18alle23_07_19.png.f8ee919e4fb8ee1bf868334d82d39758.png

 

i primi due..titolati prebooter il terzo dovè installato mojave il quarto è la recovery . non capisco questi due preboot rimasti...non è normale

 ora devo sistemare la scheda video che ho in firma e audio... il dsdt, non posso usare lo stesso di high sierra?

Share this post


Link to post
Share on other sites

il preboot è normale ti basta nasconderlo dal config

Certo puoi usare il dsdt... praticamente stessa efi di 10.13 con kext e clover aggiornati

Share this post


Link to post
Share on other sites

ma è normale che finita l'installazione il disco sia suddiviso cosi? poi non riesco neanche a montare l'efi con clover configurator ma solo tramite linea di comando.

screenshots

Share this post


Link to post
Share on other sites

Ciao si certo normalissimo...questa è la struttura in caso di uso di apfs... :)

sicuramente hai una vecchia versione di clover configurator questo il motivo che non ti monta la efi

Share this post


Link to post
Share on other sites
Posted (edited)
2 hours ago, gengik84 said:

Ciao si certo normalissimo...questa è la struttura in caso di uso di apfs... :)

sicuramente hai una vecchia versione di clover configurator questo il motivo che non ti monta la efi

 è vero...che ritardato che sono

 

ma come nascondo il preboot al boot di clover?

 

Edited by clockT

Share this post


Link to post
Share on other sites

ciao a tutti, perché dopo aver creato la USB con C_I_M di High Sierra, se faccio il boot da UEFI, alla schermata di Clover non  mi compare  "install high sierra"? Faccio la stessa procedura con El Capitan (da script) e funziona! Ho provato a realizzare la USB anche con lo script ma non funziona lo stesso.

Share this post


Link to post
Share on other sites

Create install media. È il metodo ufficiale Apple quindi o è clover vecchio che non vede l’installer e infatti devi usare l’ultima versione disponibile oppure è l’installer e in caso  scaricalo nuovamente da App Store e ricrea la usb

Share this post


Link to post
Share on other sites
52 minutes ago, gengik84 said:

Create install media. È il metodo ufficiale Apple quindi o è clover vecchio che non vede l’installer e infatti devi usare l’ultima versione disponibile oppure è l’installer e in caso  scaricalo nuovamente da App Store e ricrea la usb

Forse il problema è proprio l'installer. 

screeshot.tiff

Share this post


Link to post
Share on other sites
Guest
You are commenting as a guest. If you have an account, please sign in.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By arsradu
      Hi guys,
       
      So, this little tutorial is meant to help people fix a new issue with Mojave: opening jpg files (looks like it happens with larger files, not so much with smaller ones) using Quick Look (on spacebar key pressed) or Preview app using the dedicated GPUs.
      The issue is that, when trying to open jpg files (for some reason, it doesn't occur with pngs), the pop-up window would remain in an endless loop. And from that point forward, any other app trying to open the same file, will either become unresponsive (in the case of the Preview app) or just stay in endless loop (in case of Quick Look)
       
      As a workaround, in case the tutorial below doesn't work for you, you can use Grab (built-in app in MacOS) to open said files.
       
      This issues DOES NOT occur using the iGPU. So...if you're comfortable using the iGPU, just switch to that and you should be good to go. You don't need this tutorial.
       
      This tutorial is based on @Cyberdevs' research and testing on this topic (especially useful if you're using an RX series AMD video card), and my own very limited time testing this on my rig. I just thought it would be useful to create a new thread for it so that people can discuss this particular issue here.
       
      The main thing we need to do is actually very simple: we need to enable the iGPU (integrated GPU) by default, in BIOS, while actually being connected to the dedicated GPU.

       
      With that being said, I'll just move on to the actual tutorial.
       
      New (probably better) method.
       
      Switch your SMBIOS in Clover config in regards to the dedicated GPU you're using, instead of the CPU. Take a look here and choose the corresponding SMBIOS closest to your hardware.
      Yeah, that's it.
       
      In case you lose CPU PM with this method, there are multiple ways to fix that, and they do not make the object of this thread.  It worked perfectly fine for me though and I didn't need to change anything else.
       
      In case you wanna try alternative medicine  ...
       
      For ATI GPUs (curtesy of @Cyberdevs' post here).
       
      The discreet GPU should be set as primary in BIOS and your displays should be connected to your discreet GPU
      The iGD/iGPU/iGFX must be enabled in BIOS/UEFI as the secondary GPU.
       
      I removed the DSDT Reconfigured the config.plist to and removed some flags which weren't needed because of the DSDT added the InjectATI + Ornioco Framebuffer (I removed the Orinoco framebuffer because of some weird glitches but it might be useful for other AMD GPUs if you inject the correct framebuffer according to your GPU. No need to inject anything for nVidia GPUs unless your GPU needs it) Added the InjectIntel + ig-platform-id for my intel HD530 (for intel HD 530 I use the 0x19120001 ig-platform-id) Removed com.apple.finder.plist Removed com.apple.QuickLookDaemon.plist rebuild the kextcache and reset the nvram  
      Steps 5 to 7 might not be necessary I just did them anyway, if anyone succeeded to get quicklook working without those steps let me know so I can exclude those steps.

           Also confirmed to work with AMD R9 270X on a SandyBridge rig (without an iGPU) using WhateverGreen + Lilu kexts, which also helped to solve the transparency issue along with the Quick Look problem, it also resolved the buggy Screen Capture (Command+Shift+5) issue as well. 
       
          Also, do:
      nvram cleanup kextcache & prelinked kernel rebuild reboot  More info on that here.
       
       
      For NVIDIA GPUs
       
      This is what I needed for my NVIDIA rig and the MSI motherboard in the signature. Your milage may vary, depending on your hardware. But, the idea should be the same regardless.
       
         For MSi motherboads (check out my motherboard details in the signature)
       
      Set your BIOS to use PEG (dedicated GPU) so you can boot.
      Since you're reading this, chances are that you're already connected to the dedicated GPU and the BIOS is set to PEG. So just go into BIOS and see if you're using the iGPU or the dedicated (PEG) graphics device by default.
      If you're already using this, skip to Step 3 (the part AFTER Reboot). Reboot (I think you don't necessarily need to boot into the OS...but you do need to reboot at least until Clover UI) Reboot back into BIOS and set it from PEG to IGD (integrated graphics) WITHOUT removing the cable. Save Reboot again.  
         The result should be that the OS is tricked into thinking you're booting with the IGPU when in fact you're using the dedicated GPU.
       
         For Gigabyte motherboards
       
         Set:
      Peripherals -> Initial Display Output -> iGFX Chipset -> Internal Graphics -> Enabled
           DVMT Pre-Allocation -> default 64M.
           DVMT Total Gfx Mem -> default 256M Save Reboot  
         You should do this with the cable connected to the dedicated GPU.
       
      You will also need to patch the iGPU from Clover config.
      1. Graphics -> Inject Intel (UNCHECK Inject Nvidia or ATI if it's checked).
      2. ig-platform-id (in my case for Intel HD 4600 Desktop) it was: 0x0d220003
       
      And use IntelGraphicsFixup.kext in Clover/kexts/Other. In my particular case, without the kext, I would get freezes in Safari.
       
      This might be a bug with Mojave and it could be fixed by Apple in the future. but in the meantime, feel free to use this if it helps you fix the issue.
       
      For HP motherboards (including laptops), so far no solution, unless the BIOS somehow allows to switch from eGPU to iGPU and vice-versa.
       
      Cheers!
    • By cvad
      Small tool to download, compile and build the latest Clover X64 package,
      possible include HFSPlus-64.efi.
       
       
       

      The script inside is editable.

       
      Enjoy...
       
      Many thanks to the comrade SunKi for help with creating the script.
       
       
       
       
       
      Best thanks - click "Rate File".
      Clover_Builder.app.v1.2.0.zip
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+J partition.
       
      To use those patched files you must follow HowTo-10.14.x to create an USB installer. You can't just run the app downloaded from Mac App Store.
       
      The patch is made base on 落下爱@pcbeta 10.10.x MBR patch method, and more patch for 10.14 Firmware check by crazybirdy.
       
      What is this patched OSInstaller doing?
      1. Patch the MBR check, allow macOS 10.14 installation on MBR partition.
      2. Patch the Firmware check, bypass the error of "An error occurred while verifying firmware".
      3. Patch to stop auto-convert to APFS , "ConvertToAPFS=false" is no longer worked with 10.14.
      4. This patched MBR OSInstaller will never convert to APFS, and will always install as HFS+J partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+J and GPT HFS+J partition (GPT+recovery).

      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      How to make 10.14 installer for MBR?
      Read HowTo-10.14.x.txt inside the zip file first, same as 10.13, different with 10.12.
      Read HowTo Q/A Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      Read HowTo Q/A Q7. How to install in different computer with only one USB partition?
      Read HowTo Q/A Q8. How to update 10.14.x combo-update to MBR without downloading the full installer app again?
      Read HowTo Q/A Q9. How to update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       
       
      Q: What's the difference between createinstallmedia method and MBR-patch method?
      A: As the following....
      1. createinstallmedia method, needs stage 1, stage 2 installation process, worked with GUID only, always convert to APFS format.
      2. MBR-patch method, install via stage 2 directly, worked with both MBR and GUID, HFS+ and APFS, will never convert the format.
       
       
      OSInstaller version:
      10.14.db3.18A326g=10.14.18A326h
      10.14.db2.18A314h=10.14.18A314k
      10.14.db1.18A293u
       
      Q6. How to download the full installer app via swscan.apple.com, instead of App Store?
      A6. Some people download installer app from App Store, and get only 18 MB size, not the complete installer app (5.68 GB). You should boot to 10.12, or 10.13 to download it again from App Store, or use script Q6-DownloadFullApp/installScript_1014fullapp to download the full installer app via swscan.apple.com.

    • 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 Beta:  For macOS Mojave Beta, use CMJI.tool on page 4 of thread.
       
      Good luck and enjoy
      CECI.tool.zip
      CYI.tool.zip
      CMI.tool.zip
    • By MaLd0n
      Create a bootable copy of macOS Sierra Check out the link http://www.insanelymac.com/forum/files/file/559-flash-drive-maker/   --Install Clover UEFI in USB stick https://sourceforge.net/projects/cloverefiboot/files/Installer/   --Replace Folder CLOVER INSTALLATION.zip   --Install Sierra and boot into system!   --Install Clover UEFI and replace with my folder  CLOVER POST INSTALLATION.zip   --Reboot and activate video!   Bingo!   Now you need a fine tune! I prefer DSDT way, apply all patches in one file, many people prefer many SSDTs or Clover patches!   If you need DSDT edit... Run it RunMe.app   --DSDT My DSDT DSDT.ASUS H61M-A MaLd0n.zip   Patches -FIX ERRORS AND WARNINGS -HPET -SATA -SLPB -DARWIN -EHCx -LPC -HDEF -RTC -IRQs -SBUS -BUS1 -MCHC -ALS0 -SHUTDOWN -LAN -PNLF Clear NVRAM, Purge and Kextcache
          --FakeSMC http://www.hwsensors.com/releases --Audio https://github.com/vit9696/AppleALC --USB https://bitbucket.org/RehabMan/os-x-usb-inject-all/downloads --LAN http://www.insanelymac.com/forum/topic/287161-new-driver-for-realtek-rtl8111/   Credits and thanks to the old and new people in the community who developed patches, kexts and bootloaders!
×