Jump to content
KGP-iMacPro

iMac Pro X299 - live the future new with macOS 10.14 Mojave [Successful Build/Successful Guide]

143 posts in this topic

Recommended Posts

Posted (edited)
On 4/19/2019 at 11:20 AM, fabiosun said:

 

I am new with sage 10g configuration and I have had no particular problem in setting it in a basic way. I use to feed also that connector because system could benefit of it in case (as you say) of an extreme OC, but also if you populate more PCIEX slot (in my case some time with a spare GFX or thunderbolt EX card or PCIEX NVME card)

In case I would feed it (if no extra power need it is also safe to have it connected)

 

 

 

@fabiosun,

 

I tried now to also use 3rd EATX connector as you recommended, but my system gets irresponsive after system boot and login under Windows and macOS with such configuration. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Advertisement
Posted (edited)
8 hours ago, KGP-iMacPro said:

 

@FabioSan,

 

I tried now to also use 3rd EATX connector as you recommended, but my system gets irresponsive after system boot and login under Windows and macOS with such configuration. 

Hi @KGP-iMacPro

i am sorry for that but it is very weird this behaviour in your system and if you have some spare time you should have to investigate it

many Asus motherboard have those spare connector in different form (molex,Eatx) and asus advice to connect them

i have connected with a simple gfx pciex connector as one i use for my gfx (6 pin connector)

i have no done any test without it

In photo you can see a WS x299 Sage (no 10G) of a friend of mine he uses to full fill all pciex slot with different things :)

 

happy holidays to you and all people here

 

Screen Shot 2019-04-21 at 8.47.39 AM.png

Edited by fabiosun

Share this post


Link to post
Share on other sites
3 hours ago, fabiosun said:

Hi @KGP-iMacPro

i am sorry for that but it is very weird this behaviour in your system and if you have some spare time you should have to investigate it

many Asus motherboard have those spare connector in different form (molex,Eatx) and asus advice to connect them

i have connected with a simple gfx pciex connector as one i use for my gfx (6 pin connector)

i have no done any test without it

In photo you can see a WS x299 Sage (no 10G) of a friend of mine he uses to full fill all pciex slot with different things :)

 

happy holidays to you and all people here

 

Screen Shot 2019-04-21 at 8.47.39 AM.png

 

Yea.. was using a simple PCIEX cable too. Will further investigate the problems I faced with it. Thanks for your answer and happy holidays to you too! 

Share this post


Link to post
Share on other sites
Posted (edited)

IMG_2541.thumb.jpg.c71f28e77c96ed049a0e60cb942d8926.jpg

 

This is system of mine. sorry for dust and cable management :)

Slot 1 empty, in 2 ThunderboltEx 3 and in slot 3 my GFX

OT

Your Titan Ridge could work in different slot? have you installed in this rig?

I am asking because I have a strange a not well documented " feature" using tb in that mandatory slot for Asus card

 

Edited by fabiosun

Share this post


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

IMG_2541.thumb.jpg.c71f28e77c96ed049a0e60cb942d8926.jpg

 

This is system of mine. sorry for dust and cable management :)

Slot 1 empty, in 2 ThunderboltEx 3 and in slot 3 my GFX

OT

Your Titan Ridge could work in different slot? have you installed in this rig?

I am asking because I have a strange a not well documented " feature" using tb in that mandatory slot for Asus card

 

 

I have TTR in slot-2 from above as recommended by ASUS for the X299 Sage. As far I know, TB adapters just work in this slot assigned to PCH lanes. Also in BIOS TB settings it is the only option available. 

 

In slot-1, I use now a EK water blocked VII without problems, in slot-3, I have my OSX WIFI and in slot-5, I use a water blocked NVMe PCIe adapter for my EVO 970 Pro. 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
7 minutes ago, KGP-iMacPro said:

 

I have TTR in slot-2 from above as recommended by ASUS for the X299 Sage. As far I know, TB adapters just work in this slot assigned to PCH lanes. Also in BIOS TB settings it is the only option available. 

 

In slot-1, I use now a EK water blocked VII without problems, in slot-3, I have my OSX WIFI and in slot-5, I use a water blocked NVMe PCIe adapter for my EVO 970 Pro. 

In this TTR slot condition have you a working USB 3.1 as you can see in attachment?

I can't find any documentation that with thunderbolt card inserted in slot 2 I loose 2 back USB port .

It seems they are shared with slot 2 but I can't find any documentation (I have had same behavior in my previous X99 system so I define it a feature :)

Obviously USB thunderbolt port are working well

 

Screen Shot 2019-04-21 at 12.01.14 PM.png

Share this post


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

In this TTR slot condition have you a working USB 3.1 as you can see in attachment?

I can't find any documentation that with thunderbolt card inserted in slot 2 I loose 2 back USB port .

It seems they are shared with slot 2 but I can't find any documentation (I have had same behavior in my previous X99 system so I define it a feature :)

Obviously USB thunderbolt port are working well

 

Screen Shot 2019-04-21 at 12.01.14 PM.png

 

That's weird and does not happen in my case. Just checked on that. 

 

490689502_Screenshot2019-04-21at12_17_06.png.26dd2b5e3dd947f083c315dd6a435e52.png

 

SD1-T0500D is external Dell 500 MB Tunderbolt3 NVMe and Trident is USB 3.1 Type-C. All 4 back panel USB3.0 ports are working too. Just realised that I mounted the motherboard such that one of the silver contact plates for the USB3.1 Type-A connector accidentally blocks the latter, thus I cannot test it at present, but I am sure it would work too.

 

IMG_4031.thumb.jpg.ee64b07aa6f4efb8a6d7f92ca1309c0c.jpg

 

 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)

All 4 back panel USB3.0 are working well for me also..I have no working USB3.1 type a and C  if TB card is inserted in slot 2 I have no working motherboard USB3.1 Gen1 type a and C I(left ethernet rj connector placed)

Without TB card they are fine...Maybe Titan Ridge card has a better management..I don't know for now

thank you for your confirmation

Edited by fabiosun

Share this post


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

All 4 back panel USB3.0 are working well for me also..I have no working USB3. if TB card is inserted in slot 2 I have no working motherboard USB3.1 Gen1 type a and C I(left ethernet rj connector placed)

Without TB card they are fine...Maybe Titan Ridge card has a better management..I don't know for now

thank you for your confirmation

 

Maybe some other PCIe slot I did not populate but you did is using PCIe lanes assigned to the two USB 3.1 back panel connectors? I don't think that the two USB 3.1 back panel connectors are using PCH lanes assigned to Slot-2, when using any x4 TB adapter in this latter slot. I would be also surprised if the else quite sophisticated PCIe/PCH lane management of the Sage would have conflicting lanes  assigned twice to two respective devices. 

 

My problem is now how to get the silver contact plate actually  blocking my USB3.1 Type-A connector in its place without removing everything incl. water blocking :construction: 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)

BTW.. there is another Boost of approx. 6000 in Skylake-X Geekbench scores either related with 10.14.5 Public Betas or recent modifications within the latest Geekbench software distribution.

Screenshot.thumb.png.fd3ff24eb2b6bae7d6070e9a74bc63be.png

 

1044937749_Screenshot2019-04-20at11_55_25.thumb.png.494d15278dfa78a5e705cabcf6077503.png

 

And that's just with a turbo clock ratio of 47 and CPU core ratio set to Sync All Corse but everything else related to CPU OC just on Auto in BIOS and even SVID enabled.  Nobody should mimic such benchmarks though without extensiv custom water blocking! 

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites

@fabiosun,

 

just found the source for the problem of irresponsive Windows and macOS functionality, which was not at all related with populating the 3rd EATX onbaord connector but related with a BIOS feature I changed in parallel. 

 

Apparently, with Above 4G enabled, Frist VGA 4G Decode must be set to Auto, as else with Frist VGA 4G Decode set to Above 4G, Windows and macOS behave irresponsive after system boot. 

 

 

Share this post


Link to post
Share on other sites

@KGP-iMacPro

I am happy you found the source of irresponsive system..and also very happy is not caused from my indication to connect 3rd EATX power connector :)

 

Also I found the reason of my usb 3.1 problem..it was a combination of cable problem and mounting problem of my back plate...so now I have a full functionality of also those usb connection

Very happy of this motherboard , it is more simple to configure respect my old Designare ex motherboard and I have a full working sleep / wake without doing anything of strange things..also it seems I can avoid the use of TSC kext in other 

I have a minor cosmetic problem because I am using a PCIEx card adapter for my nvme 960 pro, in it I have windows and OSX sees it with an orange icon , if I put it on a M2 connector it is grey as it should be.

With old x299 designare ex I have not this "cosmetic" problem.

 

Share this post


Link to post
Share on other sites

if you have time also take a look at your image I reposted here

1040741183_ScreenShot2019-04-21at6_28_27PM.png.e424d7f85318675c5b7c16292e427434.png

metal on light blue is not good I think

you can't insert there any usb peripheral because back plate metal is on connector

this was part of my "mounting problem"

Share this post


Link to post
Share on other sites
44 minutes ago, fabiosun said:

if you have time also take a look at your image I reposted here

1040741183_ScreenShot2019-04-21at6_28_27PM.png.e424d7f85318675c5b7c16292e427434.png

metal on light blue is not good I think

you can't insert there any usb peripheral because back plate metal is on connector

this was part of my "mounting problem"

 

Yea.. that's what I said, I should remove everything and properly replug the motherboard, which however is a major endeavour because of my custom water blocking :w00t: 

1 hour ago, fabiosun said:

@KGP-iMacPro

I am happy you found the source of irresponsive system..and also very happy is not caused from my indication to connect 3rd EATX power connector :)

 

Also I found the reason of my usb 3.1 problem..it was a combination of cable problem and mounting problem of my back plate...so now I have a full functionality of also those usb connection

Very happy of this motherboard , it is more simple to configure respect my old Designare ex motherboard and I have a full working sleep / wake without doing anything of strange things..also it seems I can avoid the use of TSC kext in other 

I have a minor cosmetic problem because I am using a PCIEx card adapter for my nvme 960 pro, in it I have windows and OSX sees it with an orange icon , if I put it on a M2 connector it is grey as it should be.

With old x299 designare ex I have not this "cosmetic" problem.

 

 

Great that you removed all USB3.1 issues :thumbsup_anim:

 

Interesting.. I never tried to boot without any TSC kext with this motherboard. I will see what happens in my case. 

 

Are you using SSDT for NVMe in PCIEx card adapter? 

 

1400137911_Screenshot2019-04-21at19_22_45.png.44dff67ba753ff1597cfddbab388eb0c.png

Share this post


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

No

No SSDT at all, basic EFI, few kext used in EFI/CLOVER/Others no more only trim patch and some rename..

 

 

Well if you ever want to use any: https://github.com/KGP/X299-System-SSDTs/tree/master/ASUS WS X299 Sage 10G 

 

But in this case you should also add additional ACPI replacements implemented in the config.plist of my EFI-Folder distribution: https://github.com/KGP/X299-EFI-Folder-Distributions

Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
Posted (edited)
New createInstaller.sh scripts for macOS Mojave 10.14.4 (18E226) and macOS Mojave 10.14.4 (18E2034) - special build

Apple recently changed the index for macOS Mojave 10.14.4 (18E226) on http://swcdn.apple.com/, although resulting Install macOS Mojave.app version remains 14.4.08.
 
347327691_Screenshot2019-04-23at16_12_36.thumb.png.8005338a73baa1ca42fe0be5c3ca8488.png
 
I therefore expect the respective macOS Mojave 10.14.4 build still to be 18E226.

Respective changes for macOS Mojave 10.14.4 (18E226) on http://swcdn.apple.com/ also required minor modifications of createInstall.sh for Mojave 10.14.4 (18E2034), which else also still reveals receptive Install macOS Mojave.app version 14.4.10. 

Corresponding Update of Section D.2) completed. New versions of createInstaller-10.14.4-23042019.sh.zip and  createInstaller-10.14.4-SB-23042019.sh have been linked in the guide in the originating post of this thread. 
 
Enjoy and have fun,
 
kgp.png.f3eb6f1707f72f1a15c8faab1a42573a.png
 
Edit: Update of createInstaller-10.14.4-SB-23042019.sh as I accidentally renamed and linked old file before. 
Edited by KGP-iMacPro

Share this post


Link to post
Share on other sites
On 4/22/2019 at 3:19 AM, KGP-iMacPro said:

Yea.. that's what I said, I should remove everything and properly replug the motherboard, which however is a major endeavour because of my custom water blocking :w00t: 

 

I made exactly the same mistake. Honestly, just gently bend the overlapping metal back out - it doesn't seem to make any difference to how the port actually works.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • 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 lingaraju06
      I created Mojave installer in my vb vm and my specs are as follows.
      Asus rog rampage vi apex
      I9 7900x
      32gb 3000mhz corsair ram in all 4 slots (8gb each)
      Samsung pm961 nvme ssd
      Rtx 2080ti sli
       
      I have correct bios settings and able to boot to clover and when i start install it stops after end randomseed and on google search it appears to be ram detection issue, in config plist i set to imac 17,1 and under memory i changed the values to suit my hardware, i used notepad++ to edit plist as i dont know how to do in vmware and then it goes past end randomseed but stops at next line stating unable to do something i dont exactly remember and i have no more luck can anyone please help me, thank you. I am total noob and need a step by step guide if u dont mind, thank you once again.
    • By fusion71au
      Run Vanilla OS X El Capitan, Sierra, High Sierra or Mojave in VMware Workstation on a Windows Host
       
      I wanted to make a simple guide on how to create a vanilla OS X El Capitan virtual machine running on a Windows host.  The virtual machine should be useful for testing El Capitan and also for creating installers for use on a real machine/hackintosh.
       
      There are many guides and videos on the net about running OS X on Windows machines using pre-made VMWare disk images but you can never guarantee what else is in there….
       
      I’ve gathered info for this guide from various threads in the Multibooting and Virtualisation section of this forum eg
       
      Workstation 11/12, Player 7/12, Fusion 7/8 and ESXi 6 Mac OS X Unlocker 2 by @Donk How to Install OS X 10.x from Snow Leopard to El Capitan in VMware Workstation 10/12, Player 6/8 or ESXi 5/6 by @MSOK HOW TO: Create a bootable El Capitan ISO for VMware Credit and thanks to @Donk, @Albert Nietsnie and @MSOK for all their hard work in creating and testing the VMware Unlocker program.
       
      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 VMware Workstation 12 or later VMware Unlocker 2.0.7 or later 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#41 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.  Unmount any attached install image/InstallESD.dmg (if currently mounted) by rebooting the system or running the hdiutil unmount command in terminal eg
       
      3.  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….
       
       
       
      4.  Open OS X terminal, then run the following commands to execute the script:
      cd downloads chmod +x CECI.tool ./CECI.tool 5.  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.
       
      Updates:
      @shela has created an ISO generating script compatible with OS X 10.6-10.12: create_osx_iso post #362.
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS 10.13+ using Apple's createinstallmedia utility.
       
      Install and Patch VMware Workstation 12 on your PC
      1.  Download and install VMWare Workstation Player 12 or later
      2.  Download and extract Unlocker 2.0.7 or later to your USB stick…
      3.  Run the win-install.cmd as administrator by right clicking the file in Windows explorer or run it from an Administrative Command Prompt.
       



       
      Create an El Capitan Virtual Machine
      1.  Double click on the VMware Workstation 12 Player icon on your desktop and click “Create a New Virtual Machine”.  Choose “I will install the operating system later” at the How will you install screen….
       

      2.  Select Apple Mac OS X as the Guest operating system and OS X 10.11 as the version.  By default, an OS X 10.11 folder will be created in your Documents\Virtual Machines folder.
       


      3.  Under Specify Disk Capacity, you can leave the default 40GB or set a larger value.  I personally store the virtual disk as a single file.  Click Finish and you will see OS X 10.11 on the Main Screen of Workstation 12.
       


      4.  Next, we need to edit the virtual machine settings to map the virtual SATA CD/DVD drive to the El Capitan installation iso we created earlier.
       


       
      5.  To prevent the virtual machine from crashing in Windows, the virtualHW.version set in the vmx configuration file needs to be changed from 12 to 10 (alternatively, the line smc.version = "0" can be added to the file).  The OS X 10.11.vmx file can be edited with the WordPad program (navigate to the OS X 10.11 virtual machine folder with Windows Explorer and right click on the file to open in WordPad).
       


       
      6.  For HW10, set USB compatibility to USB 2.0, otherwise your mouse and keyboard might not work in the virtual machine.
       

      7.  Finally click “Play virtual machine”
       

      Installation of El Capitan
      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’ve named the 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 and the VM will automatically reboot…
       

      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.  You should eject the Installation iso now by right clicking and selecting “Eject OS X Base System”.  This will allow you to install VMware Tools….
       



      8.  After rebooting, the VM can now be resized or run at full screen resolution.  Audio and network/internet should also work OOB.
       

       
      SMBIOS Customization and iMessage Vars
      To make the Virtual Machine more "Mac like", you can edit the vmx file to add unique identifiers from a real Mac's SMBIOS -
      eg for an iMac 11,3 SMBIOS, you can enter the following lines....
      smbios.reflectHost = "FALSE" board-id.reflectHost = "FALSE" board-id = "Mac-F2238BAE" hw.model.reflectHost = "FALSE" hw.model = "iMac11,3" serialNumber.reflectHost = "FALSE" serialNumber = "W80#######6" Refer How to spoof real Mac in VMware - Multi-booting and Virtualisation.
       
      The critical variables for iMessage/Facetime activation are MLB & ROM.  By default, VMware "reflects" the host's MLB and ROM since it assumes you are running the OSX guest on a real Mac host - see post#42 by @Donk.
       
      If the host is a Windows PC, the following lines need to be added to the vmx file (requires virtualHW.version 12 and smc.version = "0")....
      efi.nvram.var.ROM.reflectHost = "FALSE" efi.nvram.var.MLB.reflectHost = "FALSE" system-id.enable = "TRUE" and the MLB, ROM and optionally system-id entered manually eg
      efi.nvram.var.MLB = "W80######BA1A" (MLB can be 13 or 17 characters long, alphanumeric string) efi.nvram.var.ROM = "<=>?@A" (ROM is entered here as a 6 character ASCII string) uuid.bios = "## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##" <---Optional (if you want to inject a given system-id hexadecimal value) Note the output for ROM from imessage_debug is a 12 character hexadecimal that needs to be entered here as a 6 character ASCII string eg using an Hex to ASCII converter we find that "3c3d3e3f4041" hex is equivalent to   "<=>?@A".
       
      Vanilla Mavericks and Yosemite
      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...
       

       
      Enjoy
       
      Update for macOS 10.12 Sierra
      The above settings still work for macOS Sierra after upgrading to VMware Workstation 12.5 and unlocker 2.0.8 - see post #13.
       
      Update for macOS 10.13 High Sierra and 10.14 Mojave
      See post#30 for macOS_iso_cim.tool script to create ISO for macOS using Apple's createinstallmedia utility.
      Post#41 describes how to build "Install macOS ******.app" on the fly from installer files downloaded beforehand in /SharedSupport folder.
       
      Update for macOS 10.15beta Catalina
      See post Update for macOS Catalina 10.15beta
       
      CECI.zip
      CYI.tool.zip
      CMI.tool.zip
    • By crazybirdy
      Patched OSInstaller.framework to allow macOS 10.14 installation on MBR HFS+ partition.
       
      To use those patched files you must follow HowTo 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 HFS 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+ partition.
      5. This patched MBR OSInstaller method works with both MBR HFS+ and GPT HFS+ partition (GPT+recovery).
      No longer need to set new SMbiosversion, FirmwareFeatures, and FirmwareFeaturesMask with this MBR-patch.
       
      What's the difference between createinstallmedia method, MBR-Manual-Method, and MBR-Automatic-Method?
      As the following....
      1. createinstallmedia method,
          needs stage 1, stage 2 installation process, which is worked with GUID partition only, always convert to APFS format.
      2. MBR-Manual-Method (same as 10.12),
          install via stage 2 manually, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          We can manually format as MBR or GPT, HFS+ or APFS on installation screen like as 10.12.
          We can manually select MBR HFS+ partition to install 10.13 and 10.14 on installation screen now.
          Needn't to update the MBR-Manual-Method files, it will still work on 10.13, and 10.14 future versions, I think so.
          It can be installed as Fresh installation on formated blank partition only, but can't be installed as update from previous version.
      3. MBR-Automatic-Method (new for 10.13+),
          install via stage 2 automatically, which is worked with both MBR and GUID, HFS+ and APFS, will never convert the partition format.
          It can be installed as Fresh installation on formated blank partition, and can be installed as update from previous version.

      How to make 10.14 installer for MBR (MBR-Manual-Method)?
      Just use EasyMBR-InstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.12.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      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 update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      How to make 10.14 installer for MBR (MBR-Automatic-Method)?
      Just use 14MBRinstallerMaker to make installer, it works with both MBR and GPT.
      Read HowTo inside the dmg first, same as 10.13.
      Read HowTo Q/A Q5. How to patch to work with CPU SSE4.1 only for Mojave?
      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 update 10.14.x combo-update to MBR and GPT with installScript directly?
       
      And, need a SMBIOS supported with /System/Library/CoreServices/PlatformSupport.plist.
       


       
      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
      Patch Catalina or Mojave macOS Installer App for Unsupported Machines
       
      Often for economic reasons, Apple prevents the Installer.app for its latest macOS from installing on older machines perfectly capable of running it eg macOS 10.14 Mojave on Unsupported Macs Thread.
       

       
      In Mojave 10.14, @ASentientBot posted a method to patch the distribution file in OSInstall.mpkg to enable the Mojave installer to install on unsupported machines (with or without graphics card metal support). 
       
      In Catalina 10.15beta, the above method no longer works since Apple is checking OSInstall.mpkg for its file signature and the mandatory requirement in Catalina to install to 2 separate apfs volumes necessitates using the original Catalina macOS Base System Installer.  Fortunately, it is still possible to substitute High Sierra’s Apple Signed OSInstall.mpkg inside the Catalina or Mojave InstallESD.dmg by making it R/W.
       
      The procedure below will allow Macs or Hacks able to install High Sierra to also install Catalina or Mojave (eg SMBIOS MacPro5,1, iMac11,3, MacBook Pro7,1 which have been unsupported in macOS 10.14.x and 10.15beta) -credit to @ASentientBot's post.
       
      Prerequisites
      1. Mac or Hack capable of and running High Sierra 10.13.x
      2. An original, untouched copy of OSInstall.mpkg from High Serra InstallESD.dmg - attached OSInstall_10.13.6.mpkg.zip save to your ~/Downloads folder
      3. macOS Installer App eg for Catalina beta or Mojave downloaded to /Applications
      4. Add NVRAM boot arg (or Clover config.plist boot arg on a hack) -no_compat_check to enable system to boot to final completed Mojave or Catalina install.
       
      Procedure
      1. Open Terminal and type the following
       
      open /Applications/Install*/Contents/SharedSupport/InstallESD.dmg (assuming the Catalina or Mojave Installer App is in /Applications)  
      2. Open Disk Utility, click File|New Image|Image from ‘InstallESD”
      3. Save as read/write image, no encryption in /Applications
      4. Unmount InstallESD in DU by clicking the "eject" icon next to it
       
       
      5. Open the R/W InstallSD.dmg in /Applications and replace Catalina’s/Mojave's OSInstall.mpkg with High Sierra’s version by typing in terminal
       
      open /Applications/InstallESD.dmg cp ~/Downloads/OSInstall_10.13.6.mpkg /Volumes/InstallESD/Packages/OSInstall.mpkg  
      6. Unmount InstallESD in DU by clicking the "eject" icon next to it
      7. Replace original Catalina/Mojave InstallESD.dmg with our patched one, making a backup of the original.  In terminal, type
       
      sudo mv /Applications/Install*/Contents/SharedSupport/InstallESD.dmg /Applications/InstallESD_orig.dmg sudo mv /Applications/InstallESD.dmg /Applications/Install*/Contents/SharedSupport/  
      8.  Test the newly patched installer!…

×