Jump to content
arsradu

[HOW TO] Fix Quick Look and Preview issues in Mojave Beta

123 posts in this topic

Recommended Posts

1 minute ago, Cyberdevs said:

Based on your hardware specs you should be able to use the methods provided in the first post. How is your config.plist configured?

Are you using any kexts for activating your GPUs or you just use clover's injections or DSDT/SSDTs for your hardware?

The only kexts I use that effect the GPU are Lilu and Whatevergreen as they allow me to use my DP on the RX580. I can upload my EFI if you want to have a look.

Share this post


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

The only kexts I use that effect the GPU are Lilu and Whatevergreen as they allow me to use my DP on the RX580. I can upload my EFI if you want to have a look.

Yeah upload your EFI folder I will take a look, please remove the following folders from the EFI folder and the following data from your config.plist before uploading it:

Folders:

Apple

Themes

 

Data from config.plist

1. Serial Number

2. MLB

3. UUID or SmUUID if you have them.

Share this post


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

Yeah upload your EFI folder I will take a look, please remove the following folders from the EFI folder and the following data from your config.plist before uploading it:

Folders:

Apple

Themes

 

Data from config.plist

1. Serial Number

2. MLB

3. UUID or SmUUID if you have them.

My EFI.

 

Edited by RedHibby

Share this post


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

My EFI.

 

Thanks for the help but I am pleased to say I have got it working. I had another look at my BIOS and found the IGPU in the advanced system agent. I enabled it and my preview is working perfectly.

Screenshot 2018-08-12 at 23.55.07.jpg

Edited by RedHibby

Share this post


Link to post
Share on other sites
5 hours ago, RedHibby said:

Thanks for the help but I am pleased to say I have got it working. I had another look at my BIOS and found the IGPU in the advanced system agent. I enabled it and my preview is working perfectly.

That's good news ;)

Share this post


Link to post
Share on other sites

As a followup to my earlier posting, I have been able to get this working on my Coffee Lake system I wrote about earlier. (Gigabyte Z370XP SLI, i5-8400, RX-580) The recent Public Beta (18A365a) added some more systems into the graphics support, Pavo wrote this somewhere in the main Mohave pre-release thread.

 

I used Clover Configurator to generate the smbios section for an iMac Pro, removed stuff like the firmware features, etc. -- letting Clover generate that information, and replaced this small smbios section in my main config.plist, took the machine offline and restarted. Preview and QuickLook worked as they should. I did not have to turn on the IGPU in the BIOS settings, nor use inject-intel = true or make any other changes.

 

So Pavo's idea about the smbios settings waaaaaay back when does look like it is on the mark. Hopefully Apple will keep adding more systems so that Preview and QuickLook work right, after all iTunes, Safari, pretty much all of the other apps use jpegs and display them correctly already.

 

Thank you all for your help.

Share this post


Link to post
Share on other sites
55 minutes ago, jerryy2 said:

As a followup to my earlier posting, I have been able to get this working on my Coffee Lake system I wrote about earlier. (Gigabyte Z370XP SLI, i5-8400, RX-580) The recent Public Beta (18A365a) added some more systems into the graphics support, Pavo wrote this somewhere in the main Mohave pre-release thread.

 

I used Clover Configurator to generate the smbios section for an iMac Pro, removed stuff like the firmware features, etc. -- letting Clover generate that information, and replaced this small smbios section in my main config.plist, took the machine offline and restarted. Preview and QuickLook worked as they should. I did not have to turn on the IGPU in the BIOS settings, nor use inject-intel = true or make any other changes.

 

So Pavo's idea about the smbios settings waaaaaay back when does look like it is on the mark. Hopefully Apple will keep adding more systems so that Preview and QuickLook work right, after all iTunes, Safari, pretty much all of the other apps use jpegs and display them correctly already.

 

Thank you all for your help.

Yeah DP7 seems to be more forth coming on the Graphics and overall performance. I recently updated my SandyBridge rig with no IGPU and only the AMD R9 270X and there are almost no issues in regard to preview, quick look and Screen Capture (Video)

I'm confident that with the final release all the issues will be resolved.

Share this post


Link to post
Share on other sites

I turned of my IGPU and Preview fails to open JPG's. Perhaps the next update will sort out Preview for RX580's. Back to switching my IGPU back on. :)

Share this post


Link to post
Share on other sites
Posted (edited)
25 minutes ago, RedHibby said:

I turned of my IGPU and Preview fails to open JPG's. Perhaps the next update will sort out Preview for RX580's. Back to switching my IGPU back on. :)

I believe for iMac17,1 SMBIOS you need to leave the iGPU on because in a real iMac17,1 the intel hd 530 frambuffer is loading when macOS starts, even though there's no RX580 chipset for the dGPU in the iMac17,1 but it is how it's defined.

Edited by Cyberdevs

Share this post


Link to post
Share on other sites

up dated to:10.14 Beta (18A365a). only after Adding a Sapphire 280X . In the second PCI slot (as i couldnt be bothered to change the water cooled loop around.And. As no support for EVGA GTX 1070

All seems to work ok except previewing jpg screen shots

 

Share this post


Link to post
Share on other sites

My mobo has Intel HD Graphics 2500 chip. I have put my activated IGFX in BIOS and tried to configure it by adding IntelGraphicsFixup.kext in /EFI/Clover/kexts/other and removing DSDT. But mojave just completed boot (using -v) and the display just remained black with the text without showing the GUI. In Sierra it caused kernel panic and reboot.

 
  •  

Share this post


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

My mobo has Intel HD Graphics 2500 chip. I have put my activated IGFX in BIOS and tried to configure it by adding IntelGraphicsFixup.kext in /EFI/Clover/kexts/other and removing DSDT. But mojave just completed boot (using -v) and the display just remained black with the text without showing the GUI. In Sierra it caused kernel panic and reboot.

What is the model of you main GPU?

as far as I know the intel HD 2500 is not supported in macOS you can use it to stop the dGPU from being initialized during boot which is not the case in macOS and resolving the black screen issue.

Share this post


Link to post
Share on other sites

Actually HD2500 is my inbuild GPU. If it is unsupported in Mac, I won't be able to enable it and have to use my GT 730 card instead.

Share this post


Link to post
Share on other sites

Yes you need to use your GT730 instead, even if you get the HD2500 to be recognized by macOS you won't have acceleration for the HD2500 GPU anyway so I doubt it would be helpful.

Which version of Mojave are you trying to install? because I guess the transparency issue is now fixed on DP8 and newer releases.

I have fully functional 7790 and R9 270X macOS Mojave since DP8 but I'm not sure about nVidia GPUs but I think your GT730 is supported natively. isn't it?

Share this post


Link to post
Share on other sites

Is there any other solution instead of changing SMBIOS? I don't have iGPU in my processor Xeon 1231v3 (Haswell). My PC is Asus Maximus VII Hero, Xeon 1231v3, Sapphire RX 480 8GB Nitro+

Share this post


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

Is there any other solution instead of changing SMBIOS? I don't have iGPU in my processor Xeon 1231v3 (Haswell). My PC is Asus Maximus VII Hero, Xeon 1231v3, Sapphire RX 480 8GB Nitro+

 

Did you not get to the alternative medicine part of the tutorial? :)

Share this post


Link to post
Share on other sites
On 9/7/2018 at 6:06 PM, Cyberdevs said:

Yes you need to use your GT730 instead, even if you get the HD2500 to be recognized by macOS you won't have acceleration for the HD2500 GPU anyway so I doubt it would be helpful.

Which version of Mojave are you trying to install? because I guess the transparency issue is now fixed on DP8 and newer releases.

I have fully functional 7790 and R9 270X macOS Mojave since DP8 but I'm not sure about nVidia GPUs but I think your GT730 is supported natively. isn't it?

NVIDIA GT 730 Is natively supported. Only problem was Preview and Quick Look. As suggested in this forum, enabling HD 2500 was required to solve this problem. But I couldnot make it to work on Mojave and read somewhere that it is not supported since Mavericks. So I changed my SMBIOS to MacPro 6.1 and Preview and Quck Look works perfectly.

Share this post


Link to post
Share on other sites

Its worth mentioning that the 'alternative medicine' will most likely disable the encode/decode capabilities of the external GPU. You can bypass it with the -shikigva=4 bootflag on Skylake/KabyLake rigs...

Share this post


Link to post
Share on other sites
4 hours ago, Coke said:

Its worth mentioning that the 'alternative medicine' will most likely disable the encode/decode capabilities of the external GPU. You can bypass it with the -shikigva=4 bootflag on Skylake/KabyLake rigs...

 

That is indeed good info. Thank you. I haven't tried this method on any Skylake builds yet. At least none with a supported dedicated GPU. So yeah, I could not confirm it working in this particular case. Good to know. Thanks. :)

Share this post


Link to post
Share on other sites

I switched to SMBIOS 6,1 switched off my IGPU and removed Lilu and Whatevergreen. Everything is now working perfectly no issues with preview.

Edited by RedHibby

Share this post


Link to post
Share on other sites
7 hours ago, RedHibby said:

I switched to SMBIOS 6,1 switched off my IGPU and removed Lilu and Whatevergreen. Everything is now working perfectly no issues with preview.

 

That's how you do it. Good job. Glad you managed to fix it. :)

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 jackluke
      Those who use Mojave with an OpenGL (non-Metal) Video Card in "dark mode" have noticed that global transparencies are working fine, while in "light mode" encountered the "grey" Finder menu bar and sidebars issues, this patch is intended for those who want to use Mojave mainly in "light mode" saving some transparencies around, so here is my "hybrid reduce transparency" patch.
       
      It is totally safe, harmless and reversible, it has been deeply tested and will 100% work until restart or logout, even after sleep lock screen it will still work.
      To return with normal "transparency" you can also do that from Accessibility prefpane disabling the "reduce transparency" checkbox.
      To use this patch just double click on this attached shell "mojavehld.command" and it will launch through Terminal.

      [METHOD 1: Enable hybrid transparency]
      After launch the mojavehld.command just follow these steps:
      type 1
      type 4
      close Terminal (CMD+Q) and any other app previously opened.

      (The choice number 3 is not mandatory)

      [METHOD 2: Force hybrid transparency]
      If for some reason after that you will still get Dock and Notification Center without "transparencies" then relaunch the mojavehld.command:
      type 2
      type 1
      type 4
      close Terminal (CMD+Q) and any other app previously opened.
       
      Download attached here: mojavehld.zip
       





    • By headkaze
      Framebuffer patching in Mojave
      Binary patching framebuffers using KextsToPatch in Clover is no longer a viable method in Mojave for Skylake and above. Now you need to use Lilu + WhateverGreen.
       
      Not just for Mojave
      This method of framebuffer patching is not only required for Mojave we recommend it for all previous and future releases of macOS.
       
      Coffee Lake Users
      Please note that the new WhateverGreen will not work with fake Kaby Lake platform-id's. You will need to have either macOS 10.14 Beta 4 (18A336e) or macOS High Sierra 10.13.6 (17G2112). The latter is a special build only available to MacBookPro15,1 or MacBookPro15,2 board id's. You can create a macOS High Sierra 10.13.6 (17G2112) installer by running installinstallmacos.py. (Update: vit9696 added back ability to fake Kaby Lake platform-id's)
       
      Lilu + WhateverGreen
      WhateverGreen is going to replace all the other video patching plugins for Lilu (it currently has merged WhateverGreen, IntelGraphicsFixup, NvidiaGraphicsFixup, Shiki and CoreDisplayFixup). Others will likely follow (such as AppleALC, HibernationFixup and IntelGraphicsDVMTFixup). This is aiming to be the all-in-one solution for video.
       
      Beta Warning
      Please note that it is currently in a "beta" state so use it at your own risk. I am just documenting this here for those of you who want to get framebuffer patching now.
       
      Preliminary
      1. Remove:
      - FakePCIID_Intel_HD_Graphics
      - IntelGraphicsFixup
      - NvidiaGraphicsFixup
      - CoreDisplayFixup
      - Shiki
      2. Turn off all graphics injections in Clover:
      - config.plist/Graphics/Inject/ATI=NO
      - config.plist/Graphics/Inject/Intel=NO
      - config.plist/Graphics/Inject/NVidia=NO
      - config.plist/Graphics/ig-platform-id=
      - config.plist/Devices/FakeID/IntelGFX=

      3. Disable DSDT Clover fixes:
      - AddHDMI
      - FixDisplay
      - FixIntelGfx
      - AddIMEI
      4. Disable UseIntelHDMI
      5. Remove boot argument: -disablegfxfirmware
      6. Remove any IGPU and HDMI entries from:
      - config.plist/Devices/Arbitrary
      - config.plist/Devices/Properties
      - config.plist/Devices/AddProperties
      7. Remove any IGPU and HDMI related SSDT and DSDT from:
      - CLOVER/ACPI/patched
      8. Renaming GFX0 -> IGPU
      - WhateverGreen will do this automatically
      - You may need to include Clover GFX0 -> IGPU rename for other kexts or ACPI patching that require it
       
      Compile Lilu + WhateverGreen
      Download WhateverGreen. Make sure you place the debug version of Lilu into the root of WhateverGreen before you compile. Install Lilu and WhateverGreen kext's into the usual place. Compile WhateverGreen as debug if you want to view debug output.
       
      Having trouble compiling?
      If you're having trouble compiling you can wait for the official binaries or download my (unsupported) build_lilu.sh shell script and run it in a folder to download and build Lilu + WhateverGreen using Xcode automatically. I recommend you try the debug versions first (place them into Clover's EFI/Clover/kexts/Other folder).
       
      Get the device path of your IGPU:
      Download and use the gfxutil tool like so:
      $ ./gfxutil -f IGPU DevicePath = PciRoot(0x0)/Pci(0x2,0x0) ig-platform-id
      For the AAPL,ig-platform-id (AAPL,snb-platform-id for Sandy Bridge) entry Clover requires this value to be in Data format so you need to reverse the bytes. So if you want your platform-id to be 0x3EA50009 first reverse the bytes (0900A53E) then use Xcode's plist editor to add the values to Clover's config.plist.

       
      What ig-platform-id should I use for my system?
      You should choose one that is the closest match to your system. I recommend you do some research on this before choosing one. See post #2 for available options. More info can be found here.
       
      You can determine the generation of your CPU by the first digit after the hyphen.
      Examples:
      - Intel(R) Core(TM) i5-2760QM (Gen 2)
      - Intel(R) Core(TM) i7-5257U CPU @ 2.70GHz (Gen 5)
      - Intel(R) Core(TM) m3-6Y30 (Gen 6)
      - Intel(R) Core(TM) i5-8350U (Gen 8)
       
      Here are some recommended frames:
       
      Gen 2: Sandy Bridge (Intel HD Graphics 2000/3000)
      - Support started with OS X 10.7.x and ended with macOS 10.13.6
      - Metal support is not available
      - Desktop: 0x00030010 (default)
      - Laptop: 0x00010000 (default)
       
      Gen 3: Ivy Bridge (Intel HD Graphics 2500/4000)
      - Support started with OS X 10.8.x
      - Desktop: 0x0166000A (default), 0x01620005
      - Laptop: 0x01660003 (default), 0x01660009, 0x01660004
       
      Gen 4: Haswell (Intel HD Graphics 4200-5200)
      - Support started with OS X 10.9.x
      - Desktop: 0x0D220003 (default)
      - Laptop: 0x0A160000 (default), 0x0A260005 (recommended)
       
      Gen 5: Broadwell (Intel HD Graphics 5300-6300)
      - Support started with OS X 10.10.2
      - Desktop: 0x16220007 (default)
      - Laptop: 0x16260006 (default)
       
      Gen 6: Skylake (Intel HD Graphics 510-580)
      - Support started with OS X 10.11.4
      - Desktop: 0x19120000 (default)
      - Laptop: 0x19160000 (default)
       
      Gen 7: Kaby Lake (Intel HD Graphics 610-650)
      - Support started with macOS 10.12.6
      - Desktop: 0x59160000 (default)
      - Laptop: 0x591B0000 (default)
       
      Gen 8: Coffee Lake (Intel UHD Graphics 630)
      - Support started with macOS 10.13.6 (17G2112) / 10.14 beta 4 (18A336e)
      - Desktop: 0x3EA50000 (default), 0x3E9B0007 (recommended)
      - Laptop: 0x3EA50009 (default)
       
      Framebuffer Patching
      WhateverGreen does most of the work automatically for you and in most cases you do not need any extra Framebuffer Patching. At the minimum though you should choose an ig-platform-id suitable for your system and place it in config.plist/Devices/Properties like this:

      Here are some reasons why you might need extra Framebuffer Patching:
      - Setting DVMT for those who can't set it above 32 MB in BIOS (framebuffer-stolenmem / framebuffer-fbmem)
      - Setting higher VRAM (framebuffer-unifiedmem)
      - Disabling eGPU (disable-external-gpu)
      - Enable pixel clock patch for 4K support (enable-hdmi20)
      - Disabling connectors to enable sleep (framebuffer-pipecount / framebuffer-portcount / framebuffer-conX-type=-1)
      - Removing CNConnectorAlwaysConnected flag for eDP laptop screens on < 10.13.6 (framebuffer-con0-flags=0x00000090)
      - Changing connector types to match your systems ports (framebuffer-conX-type)
       
      Framebuffer Patching Types
      We have three different types of patches:
       
      1. Arbitrary (Recommended)
      framebuffer-patch-enable (required to enable below) framebuffer-framebufferid (optional; defaults to current platform-id) (all below are optional) framebuffer-mobile framebuffer-pipecount framebuffer-portcount framebuffer-memorycount framebuffer-stolenmem framebuffer-fbmem framebuffer-unifiedmem framebuffer-conX-enable (required to enable below) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags 2. All Data
      framebuffer-conX-enable (required to enable below) framebuffer-conX-alldata 3. Find / Replace
      framebuffer-patchX-enable (required to enable below) framebuffer-patchX-framebufferid (optional; defaults to current platform-id) framebuffer-patchX-find framebuffer-patchX-replace framebuffer-patchX-count (optional; defaults to 1) You should place your patches in config.plist/Devices/Properties in Clover config.plist.
       
      Here are some example patches:
      - 32MB BIOS, 19MB stolen (framebuffer) 9MB fbmem (cursor) 2048MB unifiedmem (vram)

       
      - Pipe / Port Count 3 to 2
      - Connector 1 DP to HDMI
      - Connector 2 Disable

       
      Here is an example of the All Data method:

       
      Here is an example of the Find / Replace method:

       
      Debugging
      If you need a dump of your framebuffers in binary use the boot flag -igfxdump. The output will be in /AppleIntelFramebuffer_GEN_KERNX_Y on your boot drive (Eg. AppleIntelFramebuffer_10_17.7). Intel FB-Patcher can File->Open this and generate a config.plist/Devices/Properties patch for Clover. 010 Editor can also parse this file using the IntelFramebuffer.bt template.
      To get debug output from Lilu use the -liludbgall flag and for WhateverGreen use the -wegdbg boot flag. You will need to compile Lilu and WhateverGreen as debug for both of these flags to work.
       
      To view debug paste the following into Terminal (weglog.txt will output to your home directory):
      log show --predicate 'process == "kernel" AND (eventMessage CONTAINS "WhateverGreen" OR eventMessage CONTAINS "Lilu")' --style syslog --source --last boot >weglog.txt
      Credits
      - vit9696 and lvs1974 for WhateverGreen (Full Credits) and Lilu (Full Credits)
      - Andrey1970 for his guide on applelife.ru
      - RehabMan for All Data patching method
       


    • By chebkhaled1960
      Hello everyone 
      i noticed that when you install MacOS Mojave the format of HDD is converted to APFS automatically even if you formatted the HDD with HFS ! 
       
      My question is: i read that APFS is especially for SSD and not HDD, is APFS will damage my HDD or it’s Ok if I used it ?
       
      i need your helps and thank you .
    • By onlyJRevenge
      Ciao ragazzi, 
      volevo anticipatamente nuovamente ringraziare gengik84 per avermi realizzato il medesimo portatile su High Sierra perfettamente funzionante, che fino ad oggi non mi ha mai dato nessun problema.
       
      Ho deciso di installare la developer 11 o se meglio vogliamo chiamarla "DG" che dovrebbe essere l'anticipazione della stabile, tutto funziona correttamente tranne le seguenti cose:
       
      - WiFi non funzionante (prima andava senza problemi, addirittura la 5Ghz)
      - Bug grafici (che ad es. disattivato l'accelerazione hardware da Chrome, non da più problemi)
      - Se non avvio Clover in -v, non parte
       
      Avreste modo di aiutarmi?
      Per il resto, touchpad, tastiera, audio, batteria, ethernet e quant'altro vanno senza problemi.
       
      Grazie anticipatamente e allego la EFI
      EFI.zip
    • By fusion71au
      Making a High Sierra USB Installer Entirely From Scratch in Windows
      This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ).  @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...
       

      Pre-Requisites
      8GB or larger USB drive Boot Disk Utility v2.1.2017rev021b from @CVAD TransMac (free 15 day trial) Paragon Hard Disk Manager Free Download Installer Files Directly from Apple
      1)  Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist (Hint - search page for "InstallESD" to find its URL and others nearby)

      to a folder named "SharedSupport" on your Windows NTFS drive.  A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

      2)  Rename InstallESDDmg.pkg to InstallESD.dmg
      3)  Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
      Note:  You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
      Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
      1.  Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
      2.  Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
      3.  Restore 4.hfs to USB second partition with BDU --->  2nd partition becomes bootable "OS X Base System"
      Paragon Hard Disk Manager to extend HFS Partition to its Full Extent
      Open Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed.  Don't forget to apply the changes at the end...
      Transmac to Copy "SharedSupport" folder to OS X Base System
      1.  Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder.  Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
      2.  In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
      Clover Settings
      Clover configuration is required now.  The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky.  If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
      The location of the important configuration files for Clover are summarized below
      config.plist--->EFI/CLOVER folder DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist) Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here.  You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work. If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI. If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware).  In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine.  Reboot the system to the USB installer to install High Sierra ...
      What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
      Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app.  In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
      -bash-3.2# cd / -bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/ -bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/  
      ...then start installation with the startosinstall utility...
      -bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app  
      The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume.  Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
      cd "/Volumes/Macintosh HD" chmod +x startosinstall.command ./startosinstall.command Updated Download Links for macOS Mojave 10.14GM
      Browse Apple's Developer Beta Software Catalog and find the URLs to download the following 6 installer files...
      BaseSystem.dmg BaseSystem.chunklist InstallInfo.plist InstallESDDmg.pkg AppleDiagnostics.dmg AppleDiagnostics.chunklist  
      startosinstall.command.zip
       
      InstallInfo.plist_edited_10.14beta1.zip
      InstallInfo.plist_edited_10.13.6.zip
×